sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Inspector: Click-drag to increase or decrease property values does not work with tablet/pen
Labels: bug,topic:editor,confirmed,usability,topic:input

**Godot version:** 3.2.1

**OS/device including version:**
Win64, Wacom Intuos

**Issue description:**
With tablet and pen the values get stuck:
![click_drag_values_bug1](https://user-images.githubusercontent.com/47016402/80486484-871bd980-895b-11ea-98b5-8f0e1e110c4c.gif)

With mouse it works fine:
![click_drag_values_bug2](https://user-images.githubusercontent.com/47016402/80486498-8d11ba80-895b-11ea-8978-0089c25aa6e8.gif)
Repository: vscode
Issue: NVDA doesn't read the status line
Labels: bug,upstream,accessibility,upstream-issue-linked

Testing https://github.com/microsoft/vscode/issues/96265

All NVDA reads is: `No status line found`.
Repository: node
Issue: Different configurations watched same file returned same instance
Labels: fs

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: 
* **Platform**: all
* **Subsystem**: fs

Using two different configurations watched the same file, the second configuration will not take effect.

### What steps will reproduce the bug?

1. The process will exit.
``` js
const fs = require('fs');

fs.watchFile('a.js', {persistent: false} , () => {
  console.log(1)
});

fs.watchFile('a.js', () => {
  console.log(2)
});
```

2. The Process does not exit.
``` js
const fs = require('fs');

fs.watchFile('a.js', () => {
  console.log(2)
});

fs.watchFile('a.js', {persistent: false} , () => {
  console.log(1)
});

```

### How often does it reproduce? Is there a required condition?

unrequired condition.

### What is the expected behavior?

Neither 1 nor 2 will exit the process.

### What do you see instead?

1. The process will exit.

### Additional information

When watched, the StatWatcher instance is de-instanced by filename, and the same instance is returned each time the same file is watched.
Repository: godot
Issue: Tilemap: set_cellv(map_point, -1) does not work with Ysort
Labels: bug,topic:physics

**Godot version:** 3.2.1

**OS/device including version:** Wine64

**Issue description:**
![ysort_set_tile_bug](https://user-images.githubusercontent.com/47016402/80494673-37dba600-8967-11ea-9490-47a5037d24ee.gif)

If the Tilemap in question has the **ysort** property enabled, only the first tile will be set to -1.
As soon as ysort is disabled, set_cellv works as expected.
In fact, the Tilemap does not seem to ever leave the Area2D of the player, even tough it should when moving from tile to tile. So this might be an Area issue too.

Player Code:
```
func _on_Area2D_body_entered(body):
	if "yellow_tile" in body.name:
		$Label.text = "is in tile"
		yellow_tile = body
		var map_point = yellow_tile.world_to_map(global_position + Vector2(16,16)) #-16,-16 = yellowtile position
		yellow_tile.set_cellv(map_point, -1, false, true)
		yellow_tile.call_deferred("update_dirty_quadrants")
```
Thanks to user Grandro on Discord who has figured this out!

**Steps to reproduce:**
Move player on a Tilemap tile.

**Minimal reproduction project:**
[Grid_set_tile_ysort_bug.zip](https://github.com/godotengine/godot/files/4546130/Grid_set_tile_ysort_bug.zip)
Repository: pytorch
Issue: [docs] Unclear return type of torch.randint and extra comma in arg spec
Labels: module: docs,triaged

1. Note two commas in function spec
2. It's unclear if default output is `torch.int64` (in practice it is) or `torch.get_default_dtype()` which is usually `torch.float32`. It's unclear what `torch.set_default_tensor_type()` reference has to do with `torch.randint`'s return type since by default it returns an integral tensor

https://pytorch.org/docs/master/torch.html?highlight=torch%20randint#torch.randint

![image](https://user-images.githubusercontent.com/1041752/80506047-62346000-8975-11ea-99f7-81c7832a1cfb.png)
Repository: TypeScript
Issue: Missing autocomplete with optional chaining operator
Labels: Bug,Domain: Completion Lists

**TypeScript Version:**  3.8 and 3.9 nightly

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** optional chaining, autocomplete, intellisense

**Code**
The `BaseDataClass` experiences the issue here, most likely due to some of the funkiness with generic types. (Other classes extend `BaseDataClass` in practice, which is why it has these generics.)

I recognize this example is pretty unusual, but I'm reporting the optional chaining operator issue specifically in case it is helpful for improving autocomplete for the operator in general.
```ts
export interface BaseClass<TProps>
{
    getValue<TKey extends keyof TProps>(propertyName: TKey): TProps[TKey];
}
export class BaseClass<TProps> { }


interface IBaseData
{
	BaseDataProp: string;
}

export interface BaseDataClassProps<TData extends IBaseData>
{
	Data?: TData;
}

export class BaseDataClass<
	TData extends IBaseData = IBaseData,
	TProps extends BaseDataClassProps<TData> = BaseDataClassProps<TData>>
	extends BaseClass<TProps & BaseDataClassProps<TData>>
{
	public exampleMethod(): void
	{
		// this.getValue("Data")!.
		// autocompletes to:
		this.getValue("Data")!.BaseDataProp;

		// this.getValue("Data")?.
		// does not autocomplete to:
		this.getValue("Data")?.BaseDataProp;
	}
}
```

**Expected behavior:**
In the `exampleMethod` above, typing `this.getValue("Data")?.` and then requesting autocomplete (Ctrl+Enter) should give the same suggestions as given for `this.getValue("Data")!.`

**Actual behavior:**
No suggestions given for `this.getValue("Data")?.`

**Playground Link:**
[Playground Link](https://www.typescriptlang.org/play/?ts=3.9.0-dev.20200427&ssl=34&ssc=1&pln=1&pc=1#code/KYDwDg9gTgLgBASwHY2FAZgQwMbDgIUwGdgBhAG2KIB4AVABSgjCID4BYAKAG8u5+4Ac2AwAapnIBXYHQDSwAJ5xQqJABMicANaKI6OAyYtWACjBG0MBQDlMAW2AAuA-IUBKZ4eZEA2rVcAugDcXAC+XKCQsHDYlESahCQUVHSM3qxw3HDhnFxcyKgYOHgAkonAACKYMJhcvJwAkOVVNWlgzkQwUMiCIZw5EeDQ8AVoWLgExJXVmMnxbTS0LZjKIKoacGVTyxw8XA3LAPyey30DnJHDMXEJ2zNzNPtLM6vrmlsky3AAvJvNMwAaJ4LV7AdS3T73G4LOg7H6TSE1B4w541Vi7BoqMEbcoPVJGTQAMgR0yR0IJsJm6Lq+zAkgARuQENhVvYwORgABZEQACwgahMHjgADcIAg1Pt6g0GgB6GVwGA8hBEAB0wjEEmkJgARMttW4AIQq-ay+WYSQwCDYCB2dkiYCaS2OE2K5VqkTiKTAHV6w0q-6tIx9E1yhVK1Xqz1a3UzfWHY2NU1wNQQB1wJAQeDmy3W20c1AKiDOxOuiMezXemM1OP+u6B5h9Bo5HJAA)
Repository: rust
Issue: `rustc` should prefer statically linking native dependencies with unspecified kind if `crt-static` is enabled
Labels: A-linkage,T-compiler,C-bug

The main goal of `+crt-static` (at least on non-Windows targets) is to produce self-contained statically linked executables.

With this goal in mind `rustc` switches linking of 1) Rust crates and 2) libc to static if possible. (The `libc` part is done in the libraries through lazy `cfg`s though.)
However, for native dependencies with unspecified kind `rustc` will still prefer the dynamic version of the library if both are available.

Unfortunately, doing this is not entirely trivial because `-Bstatic -lmylib` won't just prefer the static version (e.g. `libmylib.a`), it will *require* it.
So we need to check for the existence of `libmylib.a` first (in which directories exactly?) and then pass `-l:libmylib.a` instead of `-lmylib` if it exists.

cc https://github.com/rust-lang/rust/pull/71586 https://github.com/rust-lang/rust/issues/39998
Repository: flutter
Issue: String.fromEnvironment without a const silently does the wrong thing in the VM
Labels: engine,dependency: dart,customer: crowd,has reproducible steps,P2,found in release: 2.2,team-engine,triaged-engine

As [44083](https://github.com/flutter/flutter/pull/44083) was merged in, I would expect it to be working in at least dev, but I am not able to get it to work as expected. I set the channel to dev (flutter channel dev), then did an upgrade (flutter upgrade). Then I issued the following:
flutter -run -t lib/main_generic.dart --dart-define=ENV=DEV

In my main_generic.dart I do this:
var env = String.fromEnvironment("ENV", defaultValue: "PROD");

The env variable always returns PROD.

Should this not be picked up and return DEV instead of defaulting to PROD?

@jonahwilliams
Repository: go
Issue: x/text/collate: unexpected result of KeyFromString()
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`)?

<pre>
$ go version
1.1.13
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
```
go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/bba/Library/Caches/go-build"
GOENV="/Users/bba/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/bba/.gvm/pkgsets/go1.13/global"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/bba/.gvm/gos/go1.13"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/bba/.gvm/gos/go1.13/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/bba/text/go.mod"
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=/var/folders/tg/tb44y2693qd2s6j53chrywyw0000gn/T/go-build299346317=/tmp/go-build -gno-record-gcc-switches -fno-common"
```
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
https://play.golang.org/p/__hCo4kcE86



### What did you expect to see?
	str = bytesToString(ctor.KeyFromString(buf, "L·"))
	println("", str) // 1711

The str will be "17110183" instead of "1711".


### What did you see instead?
"1711"
Repository: terminal
Issue: About dialog appears abruptly, without animation
Labels: Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

@DHowett-MSFT I think this PR introduced a new problem that the about dialog no longer opens and closes smoothly with an animation, it appears and disappears abruptly, also the dialog border color is greyish in light theme instead of the accent color (maybe its intended).

_Originally posted by @AnuthaDev in https://github.com/microsoft/terminal/pull/5224#issuecomment-620703529_
Repository: rust
Issue: Enabling `+crt-static` in a blanket way breaks dynamic libraries including proc macros
Labels: A-linkage,T-compiler,C-bug

This is pretty much https://github.com/rust-lang/cargo/issues/7563 generalized, which was fixed in https://github.com/rust-lang/rust/pull/69519, which I don't consider a correct or satisfactory solution.
https://github.com/rust-lang/rust/pull/71586 may be a good preliminary reading.

---
If you are building something with Cargo and set `-C target-feature=+crt-static` through `RUSTFLAGS`, or `crt-static` is enabled by default through a target specification, it will be set for all crates during the build, including proc macros and cdylibs (and build scripts?).

In most cases this is not an intention when we are enabling `crt-static`.
In most cases the intention is to enable it for executables only.

So if enabling `crt-static` for executables (via env var or a target spec) also enables it for libraries, it usually results only in "collateral damage".
If the target doesn't support `+crt-static` for libaries, we just get an error like https://github.com/rust-lang/cargo/issues/7563 reported.
If the target supports `+crt-static` for libraries, we get a very weird library which is unlikely to work when dynamically loaded as a proc macro crate (I didn't verify that though).

As a result, we need a way to enable `crt-static` for executables without collaterally damaging libaries.
Moreover, this way should be the default.

---
https://github.com/rust-lang/rust/pull/71586#discussion_r416054543 lists some possible alternatives of doing this.

- Automatically enable `-Ctarget-feature=-crt-static` for proc macro crates or all libraries in Cargo (cc @ehuss), modifying RUSTFLAGS. Question: how to opt-out?
- Introduce a new options `-Ctarget-feature=+crt-static-dylib` controlling static linking of libraries instead of `-Ctarget-feature=-crt-static`. It would almost never be used on Unix-like targets (not sure about windows-msvc and wasm).
- Keep the existing meaning of `crt-static`, but introduce a new option `-C disable-crt-static-for-dylibs` or something. Cargo would then use it for proc macro crates or all libraries. Question: how to opt-out?
- Ignore `+crt-static` for libraries if the target doesn't support it. This is fragile, musl actually supports it despite the current value of the flag of the musl target spec. If the flag is enabled, proc macros will break.
- Ignore `+crt-static` for libraries always. It is almost never used on Unix-like targets (not sure about windows-msvc and wasm). `+crt-static-dylib` looks strictly better.
- Have two `crt-static` defaults in target specs - one for executables and one for libraries. Solves one half of the problem, but explicit `+crt-static` in `RUSTFLAGS` will still cause collateral damage.
Repository: pytorch
Issue: rsub incorrectly exposed in torch
Labels: triaged,better-engineering

```
>>> torch.rsub
<built-in method rsub of type object at 0x113435ad0>
```

I believe this is supposed to be an implementation for the magic method `__rsub__`; so this should be made uniform with the rest of the magic methods (which are directly exposed by their names).
Repository: pytorch
Issue: Tensor.is_same_size not documented
Labels: module: docs,triaged

https://pytorch.org/docs/master/search.html?q=is_same_size&check_keywords=yes&area=default#

Seems to be a thing for conveniently testing if sparse sizes actually match. Maybe shouldn't be a method as it is right now.
Repository: pytorch
Issue: Tensor.as_strided_ is not documented
Labels: module: docs,triaged

https://pytorch.org/docs/master/search.html?q=as_strided_&check_keywords=yes&area=default#
Repository: pytorch
Issue: torch.clamp_max clamp_min shouldn't be there
Labels: triaged,better-engineering

~~Maybe they're not supposed to be in torch namespace?~~
Repository: pytorch
Issue: Multi-Process Single-GPU is bad
Labels: oncall: distributed,triaged,module: data parallel

I'm sorry to do this, but since your release states that you plan to deprecate Single-Process Multi-GPU, I have to talk about all the issues I have with MPSG.

First, this mode takes up a CPU thread per GPU you have. I'm sure that the developers of pytorch are used to working with servers that have tens of CPU cores and the number of cores is much much greater than the number of GPUs, but students like me who are trying to stretch their compute budgets don't necessarily have this luxury. For example, I have a workstation with 4 GPU's and 8 cores. Another with 2 GPU's and 4 cores. Those extra threads are needed for data loading, let alone anything else I want to do with the machine.

Second, killing jobs is hard and often results in zombie processes that have to be tracked down and killed manually. CTRL-c should kill all processes and the user shouldn't have to do anything else. This is how it works with DataParallel. On a related note, these extra processes often output stuff to the console in duplicate, which really clutters output. Sometimes even after the head is killed.

Third, the mode is error prone when it comes to data loading. We're supposed to use DistributedSampler to ensure that each node loads a different partition of the data. It's not easy to verify that it is working and not creating duplicates, and I'm often trying to do something just a little fancier than what DistributedSampler was designed to do. Failure in this case is silent. You just get worse results.

Finally, I just don't like the API of it. It feels like there's all this code clutter "if args.distributed" everywhere and you have to call "reduce_tensor" for each metric you compute. If you forget, everything still "works" your results are just inaccurate. You also have to launch your program with "python -m torch.distributed.launch --nproc_per_node=xx" which is esoteric and clutters your console. 

As a result, I find myself using DataParallel almost all the time, even though I know it's slower. It's usually not that much slower though. I hope to be able to keep it.

What I really hope for is more support for it. Why is it slower? Can that speed gap be closed somewhat? It uses more GPU memory too, especially on GPU 0. Trying to use the new "Channels Last" with it results in no speedup, but if I test on a single GPU, sometimes the speedup is significant.

Thanks! I really appreciate PyTorch on the whole. It's an invaluable tool for students like me.


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar
Repository: go
Issue: x/playground: detect and run Benchmark functions
Labels: NeedsInvestigation,FeatureRequest

### What did you do?

Wrote a Playground source file containing a Benchmark function, for which I wanted to see the allocations per operation (a number that does not depend in any way on the absolute running time of the program):
https://play.golang.org/p/LKZwUYcGLaG

```
package main

import (
	"runtime"
	"testing"
)

func BenchmarkAlloc(b *testing.B) {
	b.ReportAllocs()

	for n := b.N; n > 0; n-- {
		x := new(int)
		runtime.KeepAlive(x)
	}
}
```

### What did you expect to see?

Output similar to `go test -bench .`:
```
goos: linux
goarch: amd64
pkg: example.com
BenchmarkAlloc-6        1000000000               0.285 ns/op           0 B/op          0 allocs/op
PASS
ok      example.com     0.346s
```


### What did you see instead?

```
runtime.main_main·f: function main is undeclared in the main package

Go build failed.
```

![6b1nRZe6KaY](https://user-images.githubusercontent.com/5200974/80529459-7e300580-8965-11ea-94d8-ca9f7cd43b34.png)

CC @andybons @dmitshur @toothrot @cagedmantis 

See previously #24311, #6511, #32403.
Repository: PowerToys
Issue: [Run][Folder plugin] No autocomplete text on directories
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

# Environment

```
Windows build number: [run "ver" at a command prompt]
PowerToys version: 
PowerToy module for which you are reporting the bug (if applicable):
```

# Steps to reproduce

<!-- A description of how to trigger this bug. -->
There is no autocomplete text when searching for directory paths. 

# Expected behavior

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

# Actual behavior

<!-- What's actually happening? -->

# Screenshots

<!-- If applicable, add screenshots to help explain your problem. -->
![image](https://user-images.githubusercontent.com/56318517/80531818-0d322300-8950-11ea-84e6-ad985734218d.png)
Repository: pytorch
Issue: [RuntimeError] Tensor creation using storage fails
Labels: module: error checking,triaged

```
>>> x=torch.tensor(4)
>>> x.storage()
 4
[torch.LongStorage of size 1]
>>> torch.Tensor(x.storage())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: result.storage().dtype() == storage.dtype() INTERNAL ASSERT FAILED at "../aten/src/ATen/native/Resize.h":103, please report a bug to PyTorch.
```
Repository: go
Issue: cmd/compile: arch.MAXWIDTH on amd64 out of date?
Labels: NeedsInvestigation,compiler/runtime

https://github.com/golang/go/blob/b1b67841d1e229b483b0c9dd50ddcd1795b0f90f/src/cmd/compile/internal/amd64/galign.go#L17

Most amd64 implementations only support 48 bits of linear address space, but apparently Intel's Ice Lake product line launched last year and support up to 57 bits.

Theoretically fixing this should be as simple as bumping that constant up, but I'm nervous there are other constants that will need to be bumped too. E.g., probably code that uses the `(*[big]T)(ptr)[:n:n]` idiom might need to be tweaked.

Noticed in discussion on #37805.

/cc @ianlancetaylor
Repository: godot
Issue: get_string_size() and get_wordwrap_string_size() don't recognize the tab character.
Labels: bug,topic:gui

**Godot version:**
3.2.1
**OS/device including version:**
Windows 10
**Issue description:**
In the TextEdit you can insert a TAB character into your text and it takes up space.  However if you test the size with `get_string_size()` or `get_wordwrap_string_size()`, you will get 0.  

the code `get_string_size("\t\tHello")` only returns the size of "Hello".
the code `get_wordwrap_string_size("\t\tHello\n", 100)` only returns the size of "Hello" and "\n".
Repository: PowerToys
Issue: [Run][WindowWalker Plugin] Find apps minimized in Systray
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

Windows 10

```
Windows build number: 1909
PowerToys version: v0.16.1
PowerToy module for which you are reporting the bug (if applicable): Window Walker
```

# Steps to reproduce

Launch PowerToys
Launch outlook.exe
Set outlook.exe to hide to systray when minimized
Hit Windows Key + Ctrl
Type outlook
# Expected behavior

Items, such as Outlook minimized to systray would be found

# Actual behavior

Any app, including outlook will not be found, when minimized to the systray. If this should be a feature request, please move to feature queue. 

# Screenshots

<!-- If applicable, add screenshots to help explain your problem. -->