sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: Crash on start leaves orphaned processes
Labels: platform/windows,bug :beetle:,8-x-y,9-x-y,10-x-y

### Preflight Checklist
* [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:** Electron 9, 8
* **Operating System:** Windows 10 (1909)

### Expected Behavior
I expect that Electron cleans up processes if the app crashes on start

### Actual Behavior
It leaks the main, GPU, and network service processes

### To Reproduce
main.js:
```
throw new Error("test");
```

Run that program. In [Process Explorer](https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer), search for "electron.exe" (doesn't seem to show up in Task Manager for me) and observe the 3 leaked processes.

It seems that I'm forced to add an `uncaughtException` handler at the very top to exit.
```
process.on("uncaughtException", (err) => {
  throw err;
});
```

Which I'd prefer not to do. I was seeing a crash in my app at the very top of main.js because of one of the requires, so I'd have to add this handler above the requires even which is strange to me.

Can Electron handle this gracefully?
Repository: electron
Issue: Implement BrowserWindow.setOpacity on Linux
Labels: enhancement :sparkles:,platform/linux

<!--  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 a feature request that matches the one I want to file, without success.

### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->

BrowserWindow.setOpacity is not implemented on Linux, only on Mac and Windows.

### Proposed Solution

I have a local patch and I will submit a PR.

### Alternatives Considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
None

### Additional Information
<!-- Add any other context about the problem here. -->
None
Repository: electron
Issue: Implement electron.DesktopCapturer.SetSkipCursor(DesktopCapturerSource.id)
Labels: enhancement :sparkles:

<!--  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 a feature request that matches the one I want to file, without success.

### Problem Description
<!-- Is your feature request related to a problem? Please add a clear and concise description of what the problem is. -->

Until https://bugs.chromium.org/p/chromium/issues/detail?id=1007177 is implemented we need a way to hide the cursor when capturing a Window. And we need to hide and show dynamically as the source continued to be captured (i.e. without restarting the capture)

### Proposed Solution
<!-- Describe the solution you'd like in a clear and concise manner -->

I have a local patch and I will submit a PR, the api looks like:
electron.DesktopCapturer.SetSkipCursor(DesktopCapturerSource.id)

### Alternatives Considered
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
None

### Additional Information
<!-- Add any other context about the problem here. -->
Older bug https://github.com/electron/electron/issues/7584
Repository: bitcoin
Issue: Implement PayJoin / Pay-to-EndPoint
Labels: Feature

PayJoin (also called pay-to-end-point or P2EP) is a special type of CoinJoin between two parties where one party pays the other. This coinjoin type has different (probably better) privacy properties. The transaction then doesn't have the distinctive multiple outputs with the same value, and so is not obviously visible as an equal-output CoinJoin. 

An overview of PayJoin with additional information and links can be found here https://en.bitcoin.it/wiki/PayJoin

Implementing PayJoin would potentially need OpenSSL to communicate with the PayJoin server (unless I am misunderstanding how PayJoin works) as such, implementing this would have similar objections to BIP 70.

Looking forward to hearing thoughts.
Repository: pytorch
Issue: torch::jit::script::Module::to(torch::kDouble) also casts buffers
Labels: oncall: jit,triaged

## 📚 Documentation

The C++ API documentation for ``torch::jit::script::Module::to(at::Device, at::ScalarType, bool)``
indicates that the function casts all Parameters to ``at::ScalarType``, however, the function also casts the Module's buffers. 

The documentation in question is in:
https://pytorch.org/cppdocs/api/structtorch_1_1jit_1_1_module.html#_CPPv4N5torch3jit6Module2toEN2at6DeviceEN2at10ScalarTypeEb

And you can see the behaviour of the function in: 
https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/api/module.cpp

relevant code:
```
void Module::to_impl(
    const c10::optional<at::Device>& device,
    const c10::optional<at::ScalarType>& dtype,
    bool non_blocking) {
  for (at::Tensor e : parameters()) {
    module_state_to(e, device, dtype, non_blocking);
  }
  for (at::Tensor e : buffers()) {
    module_state_to(e, device, dtype, non_blocking);
  }
}
```

I'm not sure if this is a bug, a documentation issue, or I'm being a bit pedantic, so I'm raising it as a documentation issue, but I believe the behaviour of the python API is different. IIRC model.double() leaves buffers of type ``torch.long`` unchanged, but buffers of type ``torch::kLong`` are cast to ``torch::kDouble`` by to() using the C++ API.



cc @suo
Repository: flutter
Issue: When front end server unexpectedly exits "the Dart compiler exited unexpectedly", no additional crash info
Labels: team,tool,P2,team-tool,triaged-tool

Copied from https://github.com/flutter/flutter/issues/58468
```
[  +19 ms] "flutter run" took 9,975,116ms.
the Dart compiler exited unexpectedly.
[  +49 ms] Running shutdown hooks
```
No info about what the exit was or post-exit stdout/err draining before the `throwToolExit`.
Repository: neovim
Issue: Keep command-line pop-up menu open while typing
Labels: enhancement,completion,cmdline-mode

- `nvim --version`:

<details>
<summary>
output
</summary>
<p>
NVIM v0.4.3
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/tmp/neovim-20191107-13403-1or2rj3/neovim-0.4.3/build/config -I/tmp/neovim-20191107-13403-1or2rj3/neovim-0.4.3/src -I/usr/local/include -I/tmp/neovim-20191107-13403-1or2rj3/neovim-0.4.3/deps-build/include -I/usr/local/opt/gettext/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include -I/tmp/neovim-20191107-13403-1or2rj3/neovim-0.4.3/build/src/nvim/auto -I/tmp/neovim-20191107-13403-1or2rj3/neovim-0.4.3/build/include
Compiled by brew@Mojave.local

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.4.3/share/nvim"

Run :checkhealth for more info
</p>
</details>

- `vim -u DEFAULTS` (version: ) behaves differently? Irrelevant since vim does
  not have `wildoptions=pum`

- Operating system/version: Mac OS X 10.14.6

- Terminal name/version: kitty 0.17.4

- `$TERM`: xterm-kitty

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
:e<Tab><C-p>c
```

Or

```
nvim -u NORC
:set wildmode=longest:full
:e<Tab>c
```
### Actual behaviour

When you type the `c`, the completion popup menu closes.

![1](https://user-images.githubusercontent.com/4657140/83581573-0f117800-a4f4-11ea-98cd-7465ba54fe7e.gif)

### Expected behaviour

When you type the `c`, the completion popup menu should stay open and just be
filtered.

Like in insert mode in the command-line window (BTW this is with `set completeopt+=noselect`)
![2](https://user-images.githubusercontent.com/4657140/83581748-8810cf80-a4f4-11ea-8801-8a3894c1c059.gif)
Repository: flutter
Issue: [web]: filter/blur incorrectly rendered by the HTML backend
Labels: engine,platform-web,c: rendering,e: web_html,has reproducible steps,customer: web10,P2,customer: house,found in release: 3.3,found in release: 3.6,team-web,triaged-web

To produce the effect on the red waves (that actually slowly continuously animate like waves when run) a MaskFilter.blur(BlurStyle.outer, 10) is used, I suspect it is the culprit that looks bad on DomCanvas, but until I isolate it and demonstrate it in a stand-alone example I’m not 100% sure.

Expected (Canvaskit rendering):
![image002](https://user-images.githubusercontent.com/56849473/83584701-c4482e00-a4fc-11ea-94a1-a6f55b99b98a.png)

Actual (Dom rendering):
![image003](https://user-images.githubusercontent.com/56849473/83584759-e80b7400-a4fc-11ea-9612-62a687073ea5.png)
Repository: pytorch
Issue: Format issue in `torch.quantization.add_quant_dequant`  documentation parameter section
Labels: module: docs,triaged

## 📚 Documentation

#### Link

https://pytorch.org/docs/stable/quantization.html#torch.quantization.add_quant_dequant

#### API

`torch.quantization.add_quant_dequant` 

#### Issue

In the "Parameters" section, there is an input :

**we want to quantize** (*that*) –

which should be part of the description for input argument `module`
Repository: godot
Issue: ViewportTexture flashes when mapped into emission
Labels: bug,topic:rendering,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:	
https://github.com/godotengine/godot/issues?q=is%3Aissue	
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
v3.2.1.stable.official

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
macOS, Radeon Pro 560 4gb Graphics, GLES3.


**Issue description:**
<!-- What happened, and what was expected. -->

I'm mapping display a control node on a mesh in 3d by using ViewportTexture (as both albedo
and emission, with transparency on). The mesh in question is dynamically added to the scene.
When the mesh becomes visible - it seems that the texture is not immediately computed and it
flashes rather brightly once loaded.

**Steps to reproduce:**

1. Download [MeshFlash.zip](https://github.com/godotengine/godot/files/4720690/MeshFlash.zip)
2. Unzip
3. Open it in Godot
4. Run several times until it flashes (sometimes it doesn't flash on the first run).

**Minimal reproduction project:**

See above.
Repository: TypeScript
Issue: import type from from "./specifier" fails to parse correctly
Labels: Bug

**TypeScript Version:**  4.0.0-dev20200616

**Search Terms:** import type declaration from name parsing

**Code**

```ts
import type from from "./a"
```

**Expected behavior:** Should parse as `import from from "./a"` parses fine.

**Actual behavior:** Parses as an import declaration and expression statement

This is such an edge case. Not sure if any user will actually run into this (doesn't affect me, but thought I should open it anyway... perhaps this is not even worth fixing).
Repository: godot
Issue: the game suddently crash without error
Labels: bug,topic:dotnet,crash

Godot version:

Godot v3.2.1.stable.official download from weisbite

Mono binding including version:

Running platform: pc windows 10
Language: C#

Issue description:

I followed a tutorial on youtube to make a terraria like tile light system, and found out when I tried to use SetShaderParam to enable the shader, the app will crash without error.

Steps to reproduce:
1. Add a Sprite with a texture and set up material and shader's file with below code:
shader_type canvas_item;

uniform sampler2D light_values;

void fragment() {
	float alpha = 1.0 - texture(light_values, UV).g;
	
	COLOR = vec4(vec3(0.0), alpha);
}
in the _Process method, call SetShaderParam to update its texture.
2.Added another sprite and a camera as its child. put this sprite at same level as the step 1 sprite.
3.For step 2 sprite, reset the sprite's scale or texture in its _Process method.
4.when the app is launched, you can see it will stopped for no reason. and can not find any error in the editor.
PS: This will only happened in the editor running mod, once we pack the app, and generate exe with release mod, it wont happen.
Repository: go
Issue: x/build/maintner: GitHubIssue.ID field is never populated
Labels: Builders,NeedsInvestigation

Similarly to #28745, the `ID` field of a `GitHubIssue` is always zero:

```Go
corpus, err := godata.Get(context.Background())
if err != nil {
	log.Fatal(err)
}
num := 0
corpus.GitHub().ForeachRepo(func(gr *maintner.GitHubRepo) error {
	return gr.ForeachIssue(func(gi *maintner.GitHubIssue) error {
		if gi.ID != 0 {
			num++
		}
		return nil
	})
})
fmt.Printf("%d GitHub issues with non-zero IDs.\n", num)

// Output:
// 0 GitHub issues with non-zero IDs.
```

The field was added in [CL 37888](https://golang.org/cl/37888), but `GithubIssueMutation.ID` is not set anywhere. It should probably be set in the `githubIssueDiffer.Diff` method, with care taken that it's populated for both new and existing issues (it would be unhelpful to populate it only for new issues, as no one could rely on the field then).

An alternative fix is to document that it's always zero and/or to remove it.

This isn't high priority because the `Number` field is usable as a workaround; filing so I can look it up. (Fixing this is made harder by #37603.)
Repository: bitcoin
Issue: support BIP39 mnemonic in descriptors
Labels: Feature

Supporting BIP39 mnemonic in descriptors would allow less painful imports and scans of third party wallet seeds.

I think it could be used almost identical as the existing `xpriv` key.

Example:
`pkh(bip39(room,cross,cube,glance,infant,setup,renew,more,lion,glimpse,retreat,tone,chief,vanish,brisk,destroy,destroy,bounce,knee,analyst,autumn,meadow,divorce,since)/44'/0'/0'/0/0)`
(or slightly different to support the "passphrase")
Repository: pytorch
Issue: BCEWithLogitsLoss() not equal to BCELoss() with sigmoid()
Labels: module: loss,triaged

Calling BCEWithLogitsLoss() gives different results than calling sigmoid with BCELoss(). Please see the example below.

pred = tensor(
       [[ 1.6094e+01],
        [ 5.1216e-01],
        [-9.5367e+00],
        [ 2.4377e+01],
        [ 3.5349e+01],
        [ 2.5894e+01],
        [ 3.1808e+01],
        [ 1.8592e-01],
        [-2.8377e+00],
        [-9.0343e+00],
        [ 1.5208e+01],
        [ 4.8932e+00],
        [-5.4581e+00],
        [ 1.8190e+01],
        [ 1.0950e+01],
        [ 1.7572e+01],
        [-2.2359e+01],
        [ 2.0425e+01],
        [ 1.9340e+02],
        [ 8.5044e-01]])

targ = tensor([[0.],
        [1.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.],
        [1.],
        [0.],
        [0.],
        [0.],
        [0.],
        [0.]])

print (F.binary_cross_entropy_with_logits(pred, targ), nn.BCEWithLogitsLoss()(pred, targ), nn.BCELoss()(torch.sigmoid(pred), targ))


# Error still occurs with float64
pred, targ = pred.double(), targ.double()
print (F.binary_cross_entropy_with_logits(pred, targ), nn.BCEWithLogitsLoss()(pred, targ), nn.BCELoss()(torch.sigmoid(pred), targ))

# Error still occurs with two samples
# NB: However the error goes away with two samples with float64
pred, targ = pred[:2], targ[:2]
print (F.binary_cross_entropy_with_logits(pred, targ), nn.BCEWithLogitsLoss()(pred, targ), nn.BCELoss()(torch.sigmoid(pred), targ))

# Try with these values instead and the error gets magnified even more
pred2 = tensor(
       [[ 1.6094e+01],
        [ 5.1216e-01],
        [-9.5367e+00],
        [ 2.4377e+01],
        [ 3.5349e+01],
        [ 2.5894e+12],
        [ 3.1808e+01],
        [ 1.8592e-01],
        [-2.8377e+00],
        [-9.0343e+00],
        [ 1.5208e+01],
        [ 4.8932e+00],
        [-5.4581e+00],
        [ 1.8190e+01],
        [ 1.0950e+07],
        [ 1.7572e+06],
        [-2.2359e+01],
        [ 2.0425e+01],
        [ 1.9340e+02],
        [ 8.5044e-01]])

Pytorch - 1.5.0+cu101
Python - 3.6.9
Results are the same with CPU and GPU
Repository: pytorch
Issue: error when specifying sparse=True in embedding
Labels: module: sparse,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
neural network training work without sparse=True, but do not work with sparse=True.

## To Reproduce
https://colab.research.google.com/drive/1m1xhqu9s_4YdZoDjkTTNu2P58O0Cwv7J?usp=sharing
Steps to reproduce the behavior:

1. just run all
it give this error,
```
RuntimeError: set_indices_and_values_unsafe is not allowed on a Tensor created from .data or .detach().
If your intent is to change the metadata of a Tensor (such as sizes / strides / storage / storage_offset)
without autograd tracking the change, remove the .data / .detach() call and wrap the change in a `with torch.no_grad():` block.
For example, change:
    x.data.set_(y)
to:
    with torch.no_grad():
        x.set_(y)
```

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->
it work with sparse=True


cc @vincentqb
Repository: flutter
Issue: [Feature Request] [Navigator] Expose current route(s)
Labels: c: new feature,framework,f: routes,c: proposal,P3,team-framework,triaged-framework

## Use case

I have chat in my application with notifications.
When the app receives notifications from a specific user while it's open and that conversation is already, the notification should not be displayed.

To know when that happens, I need to get the current route and see which one is it.


## Current Solutions Status

I know `ModalRoute.of(context)` can get you some information on the route, but it will only return the route that is part of the context.

## Current Workaround

Currently the only workaround I found is by creating a minimal mimic of the navigator and maintaining (another) history on my own.

That is, when I want to push a new roue I'm adding it to a list, and when it's out I'm removing it.
While it works, that info is already kept on the `Navigator` - one just can't access it.

## Proposal

Add a property to `NavigatorState`:

- `List<Route> get history`: Return a list of all routes that are "alive"
- `Route get currentRoute`: Return the current route (one that will return true for `Route.isCurrent`).
Repository: rust
Issue: ffi-safe lint should be more aggressive in checking ffi stability of sub-types
Labels: C-enhancement,A-lints,A-FFI

According to [this answer](https://internals.rust-lang.org/t/question-about-c-abi-stability/12449/4?u=sharazam), this code:

```rust
pub struct A { a: usize, b: usize }

#[repr(C)] 
pub struct B { 
    a: A 
}
```

... should emit a warning that `struct A` is still `#[repr(Rust)]`, so the layout of `B` isn't completely defined, specifically the order of the fields `a` and `b` are not specified in `#[repr(Rust)]`. I'm not sure if the `ffi-safe` lint is active or not, but it would be very useful, so I know that if a type is marked `#[repr(C)]`, all sub-types are also marked `#[repr(C)]`.

Another question: When compiling to a `cdylib`, why does cargo use `#[repr(Rust)]` for publicly visible structs of a crate. It would be nice if, when compiling to a `cdylib` with this code:

```rust
pub fn foo(b: B) -> A { b.a }
```

... there could be automatic warnings:

- `foo` is a public function, should be marked as `#[no_mangle]`
- `B` and `A` should be marked as `#[repr(C)]`

... because the only representation that you usually want when compiling to a `cdylib` is `#[repr(C)]` (or `#[repr(C, u8)]` for enums).
Repository: TypeScript
Issue: Add quick fix to convert type-only import into normal import
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
convert type import 

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
I'd like to have a quick fix to convert a type-only import into a normal import if the imported type is used in a value position.

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->
Now that #36400 is supported, TypeScript auto-creates type-only imports for us. However, if we later decide to use the imported type in a value position, the described workflow in #36400 is still awkward. By adding a quick fix, TypeScript could make this more smooth for the developer.

## Examples

```ts
import type { Foo } from "./foo";

// ... 1000 lines below

const something = Foo.staticMethod();
//                ~~~ Error: Foo cannot be used as a value
```
When placing the cursor on `Foo` here, TypeScript should offer converting the type-only import into a normal import.

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).