sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Closing VSCode when an update is available sometimes restarts VSCode
Labels: bug,install-update,windows

Issue Type: <b>Bug</b>

### Steps to Reproduce

1. Have VSCode update available.
2. Close VSCode application with system close button in the top right or right-clicking the task bar.

### Observed Behavior

1. VSCode closes.
2. VSCode applies update.
3. VSCode restarts.

### Expected Behavior

1. VSCode closes.
2. VSCode waits until the user restarts VSCode before applying update.

Or, somewhat less ideally:

1. VSCode closes.
2. VSCode applies update.
3. VSCode *does not* restart.

### Explanation

When an application is closed, the user expects it to close. The user isn't chosing "Apply update and restart". That isn't what the "close" button means.

I often have VSCode always open. That means that when I'm closing VSCode, I'm often shutting down at the end of the day or shutting down applications to log out or restart. This current behavior means I have to close VSCode, wait for the update, let it restart, and then close it again or else I risk a less-than-graceful application close.

I have noticed that the application is not always consistent about this behavior. Sometimes updates do apply and do not restart VSCode, but most often the application restarts itself even though the application was told to *close*.

VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2295)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: enabled_on<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.87GB (8.12GB free)|
|Process Argv|--crash-reporter-id 98c15074-97fa-4b5d-aaad-1e3a740795af|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (9)</summary>

Extension|Author (truncated)|Version
---|---|---
unique-lines|bib|1.0.0
xml|Dot|2.5.1
vscode-edit-csv|jan|0.6.0
rainbow-csv|mec|1.9.1
mssql|ms-|1.10.1
remote-wsl|ms-|0.58.2
powershell|ms-|2021.6.2
homebrewery-vscode|off|0.1.1
remove-empty-lines|use|0.0.8


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
bridge0708:30335490

```

</details>

<!-- generated by issue reporter -->
Repository: flutter
Issue: Support plugins for 3rd party embeddings
Labels: c: new feature,tool,c: proposal,P3,a: plugins,team-tool,triaged-tool

## Use case

Currently, the flutter tool only supports plugins for official embeddings, such as linux, windows, android, etc. But there also are a lot of 3rd party embedders, such as [flutter-pi](https://github.com/ardera/flutter-pi), the [sony-embedder](https://github.com/sony/flutter-embedded-linux), [flutter-rs](https://github.com/flutter-rs/flutter-rs), 

## Proposal

I wrote a design doc for this: https://flutter.dev/go/plugin-support-for-custom-embeddings

The implementation I could do myself.

fyi: @HidenoriMatsubayashi
Repository: pytorch
Issue: Should we be upcasting integral types to int64 in torch.sum and torch.prod?
Labels: triaged,module: numpy,module: reductions,module: python array api

The [Array API Standard](https://data-apis.org/array-api/latest/API_specification/statistical_functions.html#sum-x-axis-none-keepdims-false) specifies that the returned array from the operations `sum` and `prod` should have the same dtype as the input tensor.

**How is it currently done?**
Currently, both NumPy and PyTorch will promote signed integral types to `int64` to avoid overflow. Yet, for floating point types, they will return the same type as the input array instead of `float64`.

**How can it be fixed?**
Both NumPy and PyTorch already accept a `dtype` parameter which will cast the input and perform the reduction in the specified dtype. The intent of this is to pass a higher precision dtype in cases where overflow is a concern.

`sum` is the most popular reduction and one of the most popular operators. In order to deprecate this carefully, users would be required in a future release to specify the dtype parameter. This could mean changing their code in a lot of places which is quite disruptive.

cc @mruberry @rgommers @heitorschueroff @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi
Repository: pytorch
Issue: `x.to(memory_format=torch.contiguous_format)` does not always return a contiguous tensor
Labels: module: docs,triaged,module: memory format,needs design

## 🐛 Bug

`x.to(memory_format=torch.contiguous_format)` does not always return a contiguous tensor


## To Reproduce

```
import torch
N, C, H, W = 10, 3, 32, 32
x = torch.empty(N, C, H, W).transpose(0, 1)
print(x.stride())
print(x.to(memory_format=torch.contiguous_format).stride())
```

## Expected behavior

`x.to(memory_format=torch.contiguous_format)` should return a contiguous tensor (unless I am misreading the API)

## Environment

pt master

cc @ezyang @gchanan @svekars @carljparker @VitalyFedyunin @jamesr66a @brianjo @mruberry @ppwwyyxx @zou3519 @bdhirsh @jbschlosser @anjali411
Repository: pytorch
Issue: Caffe2 tensor to ATen conversion doesn't initialize PyTorch CUDA state
Labels: caffe2,module: internals,module: cuda,triaged

Steps to reproduce:
1. Revert https://github.com/pytorch/pytorch/commit/f3f7e92be5c2e3f2078dce12445481377ecb482d
2. Apply https://github.com/pytorch/pytorch/pull/61642
3. Run cuda_tensor_interop_test (e.g. https://app.circleci.com/pipelines/github/pytorch/pytorch/351662/workflows/2a2c9b83-8528-41d2-bc1f-7db11f5535d6/jobs/14815511)

The problem is that ATen CUDA tensors have the invariant that if you have an ATen CUDA tensor, the CUDA context is assumed to have been initialized, but the Caffe2-ATen interop conversion doesn't do this initialization.

Unfortunately, the fix isn't as simple as adding a call to `detail::getCUDAHooks().initCUDA()` because getCUDAHooks lives in ATen and the Tensor constructor lives in ATen/core, so this call direction is not allowed. I suppose we could move the definition site of the hooks and call it a day. 

It is a bit annoying, however, because the Caffe2-ATen tensor conversion *doesn't really matter* in the long term. So I am also a bit tempted to do something like, remove the implicit conversion from the tensor itself, and then just put the wrapping function somewhere in ATen (not ATen/core). I do not know how much code would break on account of this, but it is worth noting the implicit conversion is already guarded by EXPOSE_C2_OPS so it is at least bounded by sites of that macro.

cc @ngimel @ezyang @bhosmer @smessmer @ljk53 @bdhirsh
Repository: terminal
Issue: Add support for rotating panes around in the window, without changing the layout
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

> In tmux it's possible to move/swap opened panes in different ways.
> 
> Moving panes around in tmux:

```
C-a C-o        rotate window ‘up’ (i.e. move all panes)
C-a M-o        rotate window ‘down’
```

https://man7.org/linux/man-pages/man1/tmux.1.html:
```
     rotate-window [-DUZ] [-t target-window]
                   (alias: rotatew)
             Rotate the positions of the panes within a window, either
             upward (numerically lower) with -U or downward (numerically
             higher).  -Z keeps the window zoomed if it was zoomed.
```

From @kostrse in #4922
Repository: vscode
Issue: Unable to use shortcuts like Cmd+A, Cmd+C, Cmd+V inside an iframe inside a webview on macOS
Labels: bug,help wanted,webview

Edit: This is unrelated to clipboard operations, because Cmd+A doesn't work either.

I created a simple repro here that opens an iframe inside a webview:

https://github.com/DanTup/vs-code-webview-copy-paste

The webview contains a text input. You cannot copy, paste, or even Select All inside that text input.



(Original post below)

---

I'm embedding an app inside a webview using an iframe (avoiding the iframe is not likely feasible). In order to have VS Code keyboard shortcuts still work, keypresses are passed over using the code here:

- https://github.com/microsoft/vscode/issues/65452#issuecomment-586036474
- https://github.com/microsoft/vscode/issues/65452#issuecomment-586485815

This works for many keypress (for example opening the command palette), however it's not possible to use Cmd+C to copy to the clipboard. Edit -> Copy works as expected.

It's not clear if there needs to be some extra handling in the webiew or iframe to make this work, or if it needs support from VS Code.
Repository: pytorch
Issue: cudnn_batch_norm_backward is extremely imprecise for some input shapes
Labels: module: cudnn,triaged

## 🐛 Bug

For certain input shapes, `grad_input` always results in floats whose mantissa is almost exclusively zeroes.  For example:
```
>>> x = torch.rand((1, 1, 64, 32), device='cuda', dtype=torch.float, requires_grad=True)
>>> bn = torch.nn.BatchNorm2d(1).cuda()
>>> bn(x).backward(torch.full_like(x, 1e7))
>>> grad_median = x.grad[x.grad != 0].median()
>>> print(float(grad_median))
```

With cudnn enabled, I get `0x1.0p+2` which is just a power of two with all-zero mantissa. Whereas with cudnn disabled I get `-0x1.dc2ca8p-10` which is a substantially different result.

With a larger input shape of `(1, 1, 64, 64)` there is no issue. In my testing, it seems that whether an input works or not is a function only of the input shape. 

## Environment

 - PyTorch Version (e.g., 1.0): '1.10.0a0+gita152c12d
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Python version: 3.8
 - CUDA/cuDNN version: CUDA 11.3 / cudnn 8.2.1
 - GPU models and configuration: RTX 2060


cc @csarofeen @ptrblck @xwang233
Repository: flutter
Issue: [flutter analyze] add --set-exit-if-error option to fail if gets an error from the linter
Labels: tool,a: quality,c: proposal,team-tool

## Use case

I would like to use the tool `flutter analyze` on our CI workflow, so, if we get a failure (fatal) from the linter
the CI fails.

Currently, I can list all the outputs, fatal, warnings, and infos, but I don't have an out-of-the-box way to make it 
run an `exit` so the bash scripts on CI fails.

## Proposal

This out of the box way already exists on `flutter format` tool and is `--set-exit-if-changed`, it fails if something needs to be changed, it would be awesome to have an option like this one but for `flutter analyze`, maybe:
- `set-exit-if-fatal`
- `set-exit-if-warning`
- `set-exit-if-info`
- `set-exit-if-any-fails`

One way to do it is with a bash script but is not out of the box using Flutter 2 (https://github.com/flutter/flutter/issues/20855):
```bash
RESULT=$(flutter analyze --no-pub --no-fatal-infos --no-fatal-warnings)

if [[ $RESULT == *"error •"* ]]; then
    echo "----> :O Some files have linter fatal errors, check Dart Analysis"
    exit 1
else
    echo "----> All things are good :)"
fi
```
Repository: TypeScript
Issue: New Error: error TS2590: Expression produces a union type that is too complex to represent
Labels: Needs Investigation,Rescheduled

Baseline: TS 4.3.2
Test: e0648173719f8f2a01d775e326d8590556bb16cd

New error: `error TS2590: Expression produces a union type that is too complex to represent.`

Dependencies
```json
    "@fluentui/react-northstar": "^0.56.0",
    "@types/react": "^16.9.11"
```

tsconfig.json
```json
{
    "compilerOptions": {
        "strictNullChecks": true,
        "skipLibCheck": true,
        "jsx": "react",
    }
}
```

test.tsx
```tsx
import { Alignment, ComponentSlotStylesPrepared, TeamsThemeStylesProps, ToolbarCustomItemProps, ToolbarItemProps } from "@fluentui/react-northstar";
import * as React from "react";

// No error if this is absent or at the end of the file
type Unused = ComponentSlotStylesPrepared<NonNullable<TeamsThemeStylesProps["ToolbarCustomItem"]>, any>;

type ItemProps = ToolbarItemProps | ToolbarCustomItemProps;

type ItemPropsWithTooltip = ItemProps & {
  key?: string;
  tooltip?: string;
  tooltipAlign?: Alignment;
};

declare const ToolbarItem: React.ElementType<ItemPropsWithTooltip>;
declare const props: ItemPropsWithTooltip;
const { tooltip, key, tooltipAlign, ...rest } = props;

const _ = <ToolbarItem {...rest} />; // TS2590
```
Repository: PowerToys
Issue: [FancyZones Editor] Possibility to change the number of zones in the custom layouts as for templates.
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones

The possibility to increase/decrease the number of zones for custom layouts as it was done for the templates should be available when editing a custom layout as well.

_Originally posted by @ARainTech in https://github.com/microsoft/PowerToys/issues/12402#issuecomment-885041263_
Repository: PowerToys
Issue: FancyZones additive canvas editor keyboard support
Labels: Issue-Bug,FancyZones-Editor,Product-FancyZones,Status-Reproducible

### Microsoft PowerToys version

0.41.4

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

1. Edit canvas layout with a stack of 10+ zones
2. Use keyboard to access zones buried on the bottom of other zones (thanks for this)
3. Appearance of zone that is active (the one on the bottom of stack) is still at the bottom of stack and blocked by overlapping zones


### ✔️ Expected Behavior

Activate lower level zone and have it appear on top of other zones for clear manipulation of size/position.

### ❌ Actual Behavior

Appearance of zone that is active (the one on the bottom of stack) is still at the bottom of stack and blocked by overlapping zones.
Side note: 
When activating lower level zones with mouse the zone appears on top of stack of other zones.

### Other Software

_No response_
Repository: rust
Issue: type_length_limit is inconsistently warned about with incremental
Labels: T-compiler,A-incr-comp,C-bug

I have this library crate:
```rust
#![type_length_limit = "95595489"]

pub fn main() {
    println!("Hello, world!");
}
```

When I build it with `1.55.0-nightly (27277d966 2021-07-16)` I get no warnings.

When I try to perform edition migrations with it by running `cargo +nightly fix --edition`, I get warnings:
```
   Migrating src/lib.rs from 2018 edition to 2021
warning: unused attribute
 --> src/lib.rs:1:1
  |
1 | #![type_length_limit = "95595489"]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_attributes)]` on by default

warning: crate-level attribute should be in the root module
 --> src/lib.rs:1:1
  |
1 | #![type_length_limit = "95595489"]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

warning: 2 warnings emitted
```

As far as I know, this attribute is valid and has effect where it currently is, and either the 2021 edition migration is slightly broken, the 2021 edition has changed the behaviour of this attribute in a way I haven't seen documented.

`rustc --version --verbose`:
```
rustc 1.55.0-nightly (b41936b92 2021-07-20)
binary: rustc
commit-hash: b41936b92cd8463020207cb2f62a4247942ef2e4
commit-date: 2021-07-20
host: x86_64-apple-darwin
release: 1.55.0-nightly
LLVM version: 12.0.1
```
Repository: godot
Issue: Vulkan: Weird behavior with emissive materials when VoxelGI and ReflectionProbes is set as Interior
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.0.dev

### System information

Mx Linux (Debian Based)

### Issue description

When adding VoxelGI +  ReflectionProbes and this last one is set as Interior, weird lighting issue happens.

No Interior
![image](https://user-images.githubusercontent.com/1168582/126699991-8ef454a6-d4e2-479c-a9fa-4a6abc807efc.png)

Internal
![image](https://user-images.githubusercontent.com/1168582/126700074-c8a55cf6-e343-43a0-9810-28eadc26790d.png)


### Steps to reproduce

Use minimal reproduction project and set RefProbes as internal.

### Minimal reproduction project

[GiPlusRefs.zip](https://github.com/godotengine/godot/files/6864849/GiPlusRefs.zip)
Repository: terminal
Issue: Enabling automatic startup via task manager is funky or something
Labels: Help Wanted,Issue-Bug,Product-Terminal,Needs-Tag-Fix,Priority-3

The opposite of #10699 I think. I don't really know, Dustin said to file this during triage so I did.

If you have `startOnLogin: false`, and enable us in the task manager, then when we boot, we'll _turn it back off_.
Repository: TypeScript
Issue: Reusing function type with different parameters amount (overloading)
Labels: Bug

# Bug Report

Is there any reason it's not possible to re-use a function type that is overloaded aka has different possible amount of arguments?

In the playground I put some code that shows this issue, but I will put a quick snippet here:

```ts
declare function foo(c: {a: number; b: string}): void
declare function foo(a: number, b: string): void


foo({ a: 1, b: "2" })

foo(1, "2")

// This doesn't work but is relatively understandable
const bar1: typeof foo = (a_c, b) => {
    a_c
    b
}

// This should work, why it doesn't?
const bar2: typeof foo = (...args) => {
    args
}

// it works fine, but you can't access the second parameter
const bar3: typeof foo = (a_c) => {  
    a_c
}

// it works fine, but you can't access the parameters
const bar4: typeof foo = () => {
}

```

`bar2` in this example doesn't work, and the error that is given is `Type '(args_0: number | { a: number; b: string; }, args_1: unknown) => void' is not assignable to type '{ (c: { a: number; b: string; }): void; (a: number, b: string): void; }'.`

### 🔎 Search Terms

arguments overload parameter function

### 🕗 Version & Regression Information

In 4.4.0-beta & 4.3.5:

![image](https://user-images.githubusercontent.com/8672915/126703377-b80719a0-cadf-46c6-8580-bbddf3d11b14.png)

In 4.2.3 and before:

![image](https://user-images.githubusercontent.com/8672915/126703454-f85b4703-ed19-4920-b1f5-5609feffb982.png)


### ⏯ Playground Link

https://www.typescriptlang.org/play?target=99&jsx=0&ts=4.3.5#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVJxwAowAueAbynNWQFsAjEGAbngfIGcMYtUBzAL4BKcgDccWYAFgAUKEiwEKdNjwFi1eLUbMANOy48+-UfAlS5V2YkJEK8LQEYDHeACIATO-gjrt4hcPb2FrAHow+AAVAAssTnhgHBBOVAByDHgAdxwYAGt2ZEz4+DhobDEQCABPeDRQGG4oVGAoBggQOTA8bnZYJ3IMaoAHEBxEDXgAXngiKAB9MFdhaYA+Sjl4LcdFze2GOUFwyNiSzhicZAhgbNy8gyyY2qxMpJT0jAB+Lp7MhlhPIMRmMJgFprMAHRQ2D8TgrKbrCh7LYwziHY7wF63fIJRB8ECuIrwaqXeBgZoZRxgMApBIYGIITjgPA3YawKB0EAYZg-VC9f4wADMQNG40mMzmi3hiK2yJ2YHRsjkEUxmRyOKQ+MJmRJyDJFMyUGptPg9IQbJgHK5zDRsm6fL+sAALCKQeLZtKNrIjrIgA

### 🙁 Actual behavior

It just errors out when trying to use "...args" to get all the possible arguments of the function

### 🙂 Expected behavior

To be able to use "...args" or similar to get the arguments and typescript to not complain just for trying to use it
Repository: go
Issue: time: UnmarshalJSON does not respect escaped unicode characters
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

1.16.6

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

The playground.

### What did you do?

Unmarshaled a JSON string containing an escaped unicode character into a `time.Time`.

https://play.golang.org/p/MV6VeYcalrQ

### What did you expect to see?

I expected it to parse correctly as per the JSON spec.

### What did you see instead?

It did not understand the escaped character.
> parsing time ""2009-11-10T23:00:00\u005a"" as ""2006-01-02T15:04:05Z07:00"": cannot parse "\u005a"" as "Z07:00"
Repository: ant-design
Issue: Add index to tagRender callback on Select with mode="tags"
Labels: help wanted,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.

### What problem does this feature solve?
Is needed when you use a custom render an want to show the index in some way.
In my case, I need to show the numeration of a inputted words: user inputs a word "example" and I want to show a tag with [1. example], inputs another word "example2" and want to show [1. example] [2. example2]

### What does the proposed API look like?
```
<Select 
    mode="tags" 
    tagRender={({ ...props, index}) => renderTagWithIndexInside(index)}
/>
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: Import statement completions don't work if in front of certain statements
Labels: Bug,Help Wanted,Effort: Moderate,Domain: Completion Lists,Fix Available

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

- suggest / suggestions
- complete / completions
- import statement completions
- completionInfo

### 🕗 Version & Regression Information
4.4.0-dev.20210722

Not a regression


### 💻 Code
For a JS file:

```js
import 

join('a', 'b')
```

Start typing `join` after `import` to add an import for the `path` node module


### 🙁 Actual behavior

No suggestions returned

### 🙂 Expected behavior

We'd expect import statement suggestions for `join`. If I comment out `join('a', 'b')`, I see this working as expected


The specific response is for the `completionInfo` request is: 

```
Success: false . Message: No content available.
```
Repository: flutter
Issue: DraggableScrollableSheet with non-scrollable child will dismiss sheet with shade remaining underneath.
Labels: framework,f: material design,f: scrolling,f: gestures,customer: google,P2,team-design,triaged-design

b/194407719

Present a persistent bottom sheet (presented via ScaffoldState.showBottomSheet() ) with a DraggableScrollableSheet, with a non-scrollable widget in its builder's subtree. Drag upwards to expand the sheet, then drag down on the non-scrollable widget.

Expected: dismisses the sheet, leaving the underlying app usable
Actual: dismisses the sheet, leaving a shade on the whole app, rendering the app unusable until restart.

## Steps to Reproduce

Please see example demonstration: https://dartpad.dev/?id=58a143bfee818f3d8318de75d3f679e9&null_safety=true
Press the FAB to launch the sheet, expand it to full-height, then drag down on the sheet header.

No relevant logging was shown during this interaction.