sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Feature Request]: setAboutPanelOptions should allow hiding the Electron version
Labels: enhancement :sparkles:

### Preflight Checklist

I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

12.0.2

### What operating system are you using?

macOS

### Operating System Version

Catalina 10.15.7

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

If I set `applicationVersion` to `1.0.0` and the `version` to `Build 1234`, the About panel displays the version as `Version 1.0.0 (12.0.2)`.  It seems it is not possible to override the behavior of the About panel showing the Electron version in parentheses.

### Actual Behavior

I would like to override the About panel's Version line to not display the Electron version number and instead display `Version 1.0.0 (Build 1234)`.

### Testcase Gist URL

_No response_
Repository: flutter
Issue: [in_app_purchase] 0.5.1+1 - Android purchaseUpdatedStream on restart not working as intended
Labels: platform-android,p: in_app_purchase,package,P2,team-android,triaged-android

If you create a new project, setup in app purchases and place a break point on the listener for InAppPurchaseConnection.instance.purchaseUpdatedStream you will notice the following.

the notes on this stream say:
  /// * If a purchase is not completed ([completePurchase] is not called on the
  ///   purchase object) from the last app session. Purchase updates will happen
  ///   when a new app session starts instead.

On iOS - works exactly like this.  If you don't call completePurchase and restart the app, you will receive an event upon starting the app on the purchaseUpdatedStream.

On Android - You will get the purchase updates when you place the purchase (so you know everything is working and wired up and everything), BUT if you don't call complete purchase and restart the app, you do not get the even on the purchaseUpdatedStream upon startup.  

As far as I can tell there is no way to call completePurchase on that Google purchase if you run into an issue somewhere during the chain on the first try.  Really need a way to get PurchaseStatus.purchased items on startup that have not be completePurchase() for one reason or another.  Like I said, on iOS this works as documented.  On Android I can't see any way to get these transaction upon restart.
Repository: node
Issue: Integer overflow/UB when writing large buffers to TLS streams
Labels: tls

* **Version**: 14.15.3
* **Platform**: Linux qa01-api-servers-9626 5.4.0-1040-gcp #43-Ubuntu SMP Fri Mar 19 17:49:48 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
* **Subsystem**: https, streams

### What steps will reproduce the bug?

```js
const https = require("https");
  
const req = https.request({
        hostname: "httpbin.org",
        port: 443,
        path: "/post",
        method: "POST"
});
req.on("error", console.error);
req.on("response", r => console.log("response", r.statusCode))
req.write(Buffer.alloc(2147483616));
req.end();
```

### How often does it reproduce? Is there a required condition?

Consistently.

### What is the expected behavior?

Either a nice error saying that stream chunks can only be up to `INT_MAX`, or for the stream to automatically slice up large chunks.

*edit* the limit isn't `INT_MAX` actually ... in the above test case it's around 2,147,483,540 bytes, which I'm guessing is body + about 107 bytes of some overhead that sums to `INT_MAX`.

### What do you see instead?

```
Error: write EPROTO 139931020609408:error:140D010F:SSL routines:SSL_write:bad length:../deps/openssl/openssl/ssl/ssl_lib.c:1962:

    at afterWriteDispatched (internal/stream_base_commons.js:156:25)
    at writevGeneric (internal/stream_base_commons.js:139:3)
    at TLSSocket.Socket._writeGeneric (net.js:783:11)
    at TLSSocket.connect (net.js:767:12)
    at Object.onceWrapper (events.js:421:28)
    at TLSSocket.emit (events.js:327:22)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1132:10) {
  errno: -71,
  code: 'EPROTO',
  syscall: 'write'
}
```

### Additional information

The error claims to be from the `write` syscall, but it looks to be in openssl upstream of the syscall:

https://github.com/nodejs/node/blob/e46c680bf2b211bbd52cf959ca17ee98c7f657f5/deps/openssl/openssl/ssl/ssl_lib.c#L2000-L2006

For comparison, an `fs.WriteStream` will properly write files exceeding Linux's `write(2)` limit of 2,147,479,552 bytes.

```
[pid  2112] write(17, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2147483616) = 2147479552 <1.787290>
[pid  2112] write(17, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4064) = 4064 <0.000060>
```

#27861 looks like it would make this possible to hit in other scenarios also, maybe there should be a limit on the concatenated segment size.
Repository: flutter
Issue: `FLUTTER/bin/internal/shared.sh` presumes NFS is well-behaved for flocks, and breaks otherwise
Labels: tool,platform-linux,P3,team-tool,triaged-tool

Based on similar issues filed and already closed without resolution, I found that the function `_lock` in `bin/internal/shared.sh` presumes well behaved `flock` functions in Linux.  However, at least Centos with NFS (my setup), the presumption is false, and the function fails.  It works if patched like this:

```
function _lock () {
  # if hash flock 2>/dev/null; then
  #   flock --nonblock --exclusive 7 2>/dev/null
  # elif hash shlock 2>/dev/null; then
  #   shlock -f "$1" -p $$
  # else
  #   mkdir "$1" 2>/dev/null
  # fi
  mkdir "$1" 2>/dev/null
}
```

But that clearly is not a universal patch.
Repository: godot
Issue: `Performance.get_monitor(Performance.OBJECT_ORPHAN_NODE_COUNT)` doesn't print real number of orphan nodes
Labels: bug,topic:core

**Godot version:**
3.3.rc.custom_build b38a36923


**Issue description:**
When running, in one frame, code which adds a lot of nodes to scene tree and later remove them, then `erformance.get_monitor(Performance.OBJECT_ORPHAN_NODE_COUNT)` starts to show numbers bigger than 0 but editor orphan nodes monitor doesn't show any leak.
  


**Steps to reproduce:**
1. Put at the end of function `_process` in `FunctionExecutor.gd` lines
```
	print(Performance.get_monitor(Performance.OBJECT_ORPHAN_NODE_COUNT))
	assert(Performance.get_monitor(Performance.OBJECT_ORPHAN_NODE_COUNT) == 0)
```
2. Run `FunctionExecutor.tscn`
3. Wait


**Minimal reproduction project:**
https://github.com/qarmin/Qarminer/archive/refs/heads/master.zip
Repository: go
Issue: cmd/cover: inconsistent NumStmt with prometheus
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

It is indeed the latest release

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/root/.go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/root/.go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.2"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2943966716=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

git clone https://github.com/prometheus/prometheus
cd prometheus/promql/parser
go test -coverprofile=wrong.out
go tool cover -html wrong.out


### What did you expect to see?

Get the HTML coverage report

### What did you see instead?

Error message `cover: inconsistent NumStmt: changed from 2 to 1`

The wrong.out contains indeed (running `grep generated_parser.y.go wrong.out | grep 178`
```
github.com/prometheus/prometheus/promql/parser/generated_parser.y.go:178.0,180.0 2 1
github.com/prometheus/prometheus/promql/parser/generated_parser.y.go:179.0,178.0 2 1
github.com/prometheus/prometheus/promql/parser/generated_parser.y.go:176.0,178.0 1 1
github.com/prometheus/prometheus/promql/parser/generated_parser.y.go:178.0,180.0 1 1
```

I found this by modifying the `cover`message with adding `%#+v` about other fields
Repository: PowerToys
Issue: [Color Picker] Editor on Demand
Labels: Idea-Enhancement,Product-Color Picker

## 📝 Description

  Add user assignable hotkeys for more direct access to editor functions.

    A modifier key that would open the editor when held while clicking to select a colour, adding the ability to have the editor when you need it and hidden when you don’t.

    A history hotkey that would skip colour selection and open the editor to the history tab.

    Discrete history selection hotkeys to previously selected colours.


Expected Behavior

  -Modifier Key

    Only functions in operating modes which do not open the editor by default, ie copy to clipboard mode.

    Holding the modifier while clicking to select a colour opens the editor after executing the existing functions of the current operating mode.

  -History Hotkey

    Once the colour picker is active pressing this key would open the editor with the history tab in focus and default to the last selected colour on the edit tab if none selected from history.

  -Discrete History Hotkeys

    Once the colour picker is active pressing these keys would carry out the functions of the selected operating mode as if the colour had just been selected manually.

    Can be acted upon by the modifier key in non editor modes.
  

Benefits

  -Modifier

    The flexibility of editor tools when you need them, workflow efficiency when you don’t.

  -History

    Much quicker way of getting to the history tab when working with a pallet of sampled colours.

  -Discrete History

    Macros macros macros.

    Quick colour recall when using a pallet of sampled colours.

    When used with modifier key quick way to go back and tweak a colour.

---

If you'd like to see this feature implemented, thank the devs for all their hard work and add a 👍 reaction to this post.


Thank you for powertoys, your hard work allows me to work more efficiently and is greatly appreciated.
Repository: TypeScript
Issue: Adding jsdoc to overriding method makes inherited jsdoc disappear
Labels: Suggestion,Needs Proposal,Domain: JSDoc

When adding doc to a class for API level,  if we add more doc inside the implementation, we lost some documentation ! 
ex here, i add ` * @example $AA.method() ` and if i add tag `@implement` or any others in the childClass, we lost documentations from parent and for   the API level.

This image show tag:`@example $AA.method() ` is removed!,  because we add more doc in `AA.method` !
![image](https://user-images.githubusercontent.com/24865815/113451614-5399c880-93d0-11eb-8037-35d10eb5f935.png)

The expected behavior should be look like this (push docs and no replace) .
Work only if we add in parent , but should work if we add in child class.
![image](https://user-images.githubusercontent.com/24865815/113451902-f05c6600-93d0-11eb-867a-f34e301e7b49.png)


- VS Code Version:
Version : 1.55.0 (user setup)
Commit : c185983a683d14c396952dd432459097bc7f757f
Date : 2021-03-30T16:01:55.261Z
Electron : 11.3.0
Chrome : 87.0.4280.141
Node.js : 12.18.3
V8 : 8.7.220.31-electron.0
OS : Windows_NT x64 10.0.19042



Steps to Reproduce:

Add doc to `AA.method` will remove some docs in the `A.method`
```js
abstract class A {
	/**  `method` to be implement for the class AA
	 * @example $AA.method()
	 */
	abstract method(): any;
}

class AA extends A {
	/**
	 * @implements more info on the implementation
	 */
	method() {
		throw new Error('Method not implemented.');
	}
}
```

<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: TypeScript
Issue: allowJs cross-file "go do declaration" / "find references" for `exports.foo =` missing some references
Labels: Bug,Help Wanted,Effort: Moderate,Domain: Symbol Navigation,Rescheduled

# Bug Report

Summary: "find references" and "go to declaration" misses references across files when using allowJs `exports.foo = foo;`-style exports and `const {foo} = require(`-style imports.

### 🔎 Search Terms

go to declaration
find all references
checkjs
allowjs

### 🕗 Version & Regression Information

- This changed between versions 4.0.7 and 4.1.5, though I believe the behavior in 4.0.7 is also not ideal

### ⏯ Playground Link

This cannot be demonstrated in the Bug Workbench, so I have created a Stackblitz reproduction linked to github.  However, Stackblitz is *also* unable to reproduce it for some reason.

https://stackblitz.com/edit/typescript-repro-1
https://github.com/cspotcode/repros-stackblitz/tree/allowjs-declarations

### 💻 Code

```js
// src/index.js
// BUG: "Go to definition" on foo shows "no definition found for foo"
// TS 4.0.5 BUG: "Go to definition" links to the first `foo` in `exports.foo = foo;`, whereas I believe it should link to `async function foo` to match .ts checking behavior.
// GOOD: "Find references" includes `exports.foo = foo;` from libfoo.js
// BUG: "Find references" does not include `async function foo` nor `foo()` from libfoo.js
const {foo} = require('./libfoo');

// GOOD: "Go to definition" on foo jumps to `async function foo` in libfoo.js
// GOOD: "Find references" includes `exports.foo = foo;`
// BUG: "Find references" does not include `async function foo` nor `foo()` from libfoo.js
foo();
```

```
// src/libfoo.js
// BUG: "Find references" on the local `foo` in this file does not include anything from `index.js`
// BUG: "Find references" on the `foo` in `exports.foo` in this file does not include anything; jumps to self.
// GOOD: "Go to definition" on the `foo` in `exports.foo` in this file jumps to `async function foo`

exports.foo = foo;
/** jsdoc here */
async function foo() {}

foo();
```

### 🙁 Actual behavior

"Find references" on `foo` is missing references from other files.  The `BUG:` comments in the example enumerate exactly what is wrong.

### 🙂 Expected behavior

"Go to definition" for all `foo` identifiers should link to `async function foo()`
"Find references" for any `foo` identifiers should list all references in both .js files.
Repository: pytorch
Issue: Batched multi_dot / chain_matmul + let it accept a tensor instead of tuple
Labels: triaged,enhancement,module: linear algebra

This is useful for computing an accumulated transition matrix from individual transition matrices:

- First usecase: (BxN1xN2, BxN2xN3, ...) -> BxN1xN3
- Second usecase: (BxTxNxN, dim = 1) -> BxNxN -> this could save an unbind call and maybe a GPU sync (could also be (TxBxNxN, dim = 0) -> BxNxN)

Also may be useful to allow this for logmm in addition to mm: https://github.com/pytorch/pytorch/issues/54064

In the wild this happens in https://github.com/ajabri/videowalk/blob/master/code/model.py#L149 (computing the cycle's total transition matrix)

Originally requested here: https://github.com/pytorch/pytorch/issues/52868#issuecomment-812745774 @heitorschueroff

cc @jianyuh @nikitaved @pearu @mruberry @heitorschueroff @walterddr @IvanYashchuk
Repository: flutter
Issue: [custom devices] Add release / profile mode support
Labels: c: new feature,tool,P3,team-tool,triaged-tool

Currently custom devices only support debug mode. In the future, we could look at enabling release & profile mode.

This depends on #75823 (linux ARMv7 support).

Running the app is easily implemented:
- add `runRelease` and `runProfile` command in custom devices config (behaviour similiar to `runDebug` command)
- document those in the JSON schema

For building, we need ARMv7 artifacts (`gen_snapshot`, ideally also flutter engines). I'm not sure what layout other embedders expect, but for flutter-pi the finished `app.so` should be contained in the asset bundle.
Repository: PowerToys
Issue: Can't Reach FancyZones From Start Menu
Labels: FancyZones-Editor,Product-FancyZones

### Microsoft PowerToys version

0.35.0

### Running as admin

No

### Area(s) with issue?

FancyZones

### Other Software

Windows 10 Start menu

### Steps to reproduce

1. Click the Start button in the Windows 10 taskbar.
2. Type:
fancyzones

### ✔️ Expected Behavior

FancyZones should appear so I can click on it and change settings.

### ❌ Actual Behavior

I saw some Internet search results.

The inability to start FancyZones from the Start menu makes it inconsistent with other Control Panel-like applications such as the ones for managing printers or monitors.

![printers](https://user-images.githubusercontent.com/1581929/113464009-86e35400-93de-11eb-9294-d7b98bd3fd08.png)
![monitors](https://user-images.githubusercontent.com/1581929/113464010-88ad1780-93de-11eb-93b5-9c1101b0c3d1.png)
Repository: pytorch
Issue: Improve CUDA extension building experience
Labels: module: binaries,module: cuda,triaged,enhancement

## 🚀 Feature

Requesting in addition to releasing `cudatoolkit` to also release `cudatoolkit-dev`.

## Motivation

It's so convenient that `pytorch` comes with the `cudatoolkit`.  Thank you to whoever had this bright idea in the first place!

Unfortunately when it comes to pytorch CUDA extensions one has to install a matching cuda system-wide, which is not always straightforward and there are all kinds of build problems around it. Very often JIT builds fail despite having the right cuda installed system-wide and there isn't always even the log why - often the build just hangs w/o any traceback.

But the most common problem is:
```
    Exception: Installed CUDA version 11.0 does not match the version torch was compiled with 11.1, 
unable to compile cuda/cpp extensions without a matching cuda version.
```

Would it be too difficult to also release `cudatoolkit-dev` which would enable building cuda extensions like `fairscale` and `deepspeed` w/o needing a matching system-wide cuda?

This is especially an issue for those of us that do a lot of testing and integration work and to be able to have various cuda toolkit builds contained to different virtual environments like conda would make such testing so much easier.

Thank you!


cc @ezyang @seemethere @malfet @walterddr @ngimel
Repository: godot
Issue: Export: dependencies are not detected when using load() to load resources
Labels: topic:editor,topic:porting,documentation

3.2.3.stable.mono
Win10


**Issue description:**
When exporting, and choosing "Export selected resources" or "Export selected scenes" under "Resources" tab, dependent resources are auto-detected and exported - but not if dependency is by a `load()` directive.
This makes the feature much less reliable and not turnkey. It is advisable that the exported scripts will be parsed and resources that are literally mentioned in them using `load()` will be automatically export too.


**Steps to reproduce:**
1. Project->Export...
2. Resources tab
3. Export Mode: "Export selected resources" or "Export selected scenes"
4. Under "Resources to export:", select a script (or a scene that has uses a script) that loads a resource using `load("res://...") ` (and this resource is not used anywhere else)
5. Click "Export Project"
6. Run the exported project on the target platform, and see that this resource is missing
Repository: TypeScript
Issue: Support the Language Service being aware of the build version of TypeScript
Labels: Suggestion,Awaiting More Feedback

# Suggestion

Goal: Have the language service be aware that you are writing TypeScript syntax which will not build in your project.

Assumption: The `"typescript"` dependency stays locked for users for longer than the version of TypeScript in the language service. In cases like VS Code, a user's TSServer version is nearly always the most recent release, but their building version of TypeScript gets put in a lockfile and requires manual updates.

Result: When we see new TS syntax like: `?.` or `[min: number, max: number]` raise diagnostics if the discovered version of TypeScript (or babel etc? ) would support that syntax.

## 🔍 Search Terms

new syntax errors backwards compatability

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.

## ✅ Viability 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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

 - TypeScript infers the build version of TypeScript in a project 
 - We keep a list of syntax nodes + fields which are added in a new release
 - During checking, if any of those nodes are found, we check that the build version of TypeScript is compatible with the syntax 

## 📃 Motivating Example

1. Someone else uses a .d.ts feature which your version build of TypeScript does not support 
2. Your editor gives you auto-complete or fixits for features like `?.` but your build version of TypeScript does not support it

## Short Comings:

The biggest shortcoming is that I'm not 100% we can be certain about the version of a project's TypeScript. If "typescript" the dependency is around that doesn't mean that it's the tool being used to eventually convert the code. This could maybe be solved by having a map of `@babel/plugin-transform-typescript@1.2.3` = TS 3.2.1 or be a configuration option,
Repository: vscode
Issue: [Gutter] Git Decorations bounding box and appearing
Labels: bug,editor-rendering

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
The clicking area is larger than indicated, i often hit the Git when trying to Fold code .

https://user-images.githubusercontent.com/13949704/113471923-38ba6900-944f-11eb-9d66-95b81a85bc70.mp4

Beyond decreasing the hitbox size, it may be solved by moving the Folding icons ~2-4px right .

Also, when its Visibility is set to "hover", it appears even when user hovers over the Folding area . This should be set to the Decorations area only .