sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Bug: particles_2d + lightmask + viewport
Labels: bug,topic:rendering,confirmed,topic:particles

**Godot version:**
3.1.1.stable.official

**OS/device including version:**
Ubuntu 18.04.3 LTS

**Issue description:**
1. If you mask particles with a light (light_2d: mode = mask), weird visual bugs happen in the Editor. If you F6 ..., the visual bugs are gone and everything looks fine.
2. Now, if you instantiate this scene via a viewport, you still have the same visual bugs in the editor but now, if you F6 ... these visual bugs stay.

**Steps to reproduce:**
create 2 scenes

scene 2: particle-effect with light_2d as mask.
for the mask create a white/transparent image. (you know how to mask things with transparency)

scene 1: viewport instantiates scene 2 as child
create a sprite on the viewport-level -> new viewport texture and choose the viewport. 

look attached file...
![Screenshot_20200115_140516](https://user-images.githubusercontent.com/59728370/72436235-3e6f5480-37a0-11ea-8c8c-69f758616521.png)

**Minimal reproduction project:**
see: **Steps to reproduce:**
Repository: terminal
Issue: Tab titles are truncated but not ellipsized
Labels: Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3,Tracking-External

I see that tabs in WT 0.8 have fixed length and that, if the case, their title is truncated, the same occurs in other GNU/Linux terminals only that these add `...` to the truncated title: also WT should do this, I think, maybe `~/work/...` is better than `~/work/`.

I see that the `+V` on the window title is attached to the lats tab. Would it be better to attach it to the `reduce to icon` button of the window? In this way, one should gain some more 'space' for the tab length... 

See the attachment:

![example](https://user-images.githubusercontent.com/35931460/72442948-bc862800-37ad-11ea-9436-5f5759847e6e.png)

between the `V` and the `-` there is a wasted space in the window title.
Repository: pytorch
Issue:  0 INTERNAL ASSERT FAILED at /pytorch/c10/util/intrusive_ptr.h:348, please report a bug to PyTorch.
Labels: triaged,module: assert failure

I had tried to run below code but it throws below error

terminate called after throwing an instance of 'c10::Error'
  what():  owning_ptr == NullType::singleton() || owning_ptr->refcount_.load() > 0 INTERNAL ASSERT FAILED at /pytorch/c10/util/intrusive_ptr.h:348, please report a bug to PyTorch. intrusive_ptr: Can only intrusive_ptr::reclaim() owning pointers that were created using intrusive_ptr::release(). (reclaim at /pytorch/c10/util/intrusive_ptr.h:348)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7fe2ec16e813 in /home/lmdi/.local/lib/python3.7/site-packages/torch/lib/libc10.so)
frame #1: <unknown function> + 0x1838c8f (0x7fe2ee001c8f in /home/lmdi/.local/lib/python3.7/site-packages/torch/lib/libtorch.so)
frame #2: THStorage_free + 0x17 (0x7fe2ee72ab37 in /home/lmdi/.local/lib/python3.7/site-packages/torch/lib/libtorch.so)
frame #3: <unknown function> + 0x71d0d7 (0x7fe334d080d7 in /home/lmdi/.local/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
<omitting python frames>
frame #19: __libc_start_main + 0xe7 (0x7fe343e7eb97 in /lib/x86_64-linux-gnu/libc.so.6)

Aborted (core dumped)


## Code example

#Import modules
import torch
#from scipy.io.wavfile import write

#set torchhub cache directory

torch.hub.set_dir('/home/lmdi/torchhub_cache/')
waveglow = torch.hub.load('nvidia/DeepLearningExamples:torchhub', 'nvidia_waveglow')


## System Info
PyTorch version: 1.3.1
Is debug build: No
CUDA used to build PyTorch: 10.1.243

OS: Ubuntu 18.04.3 LTS
GCC version: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
CMake version: Could not collect

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 10.2.89
GPU models and configuration: GPU 0: GeForce GTX 1660
Nvidia driver version: 440.44
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] numpy==1.18.0
[pip3] torch==1.3.1
[pip3] torchvision==0.4.2
[conda] Could not collect
Repository: flutter
Issue: ERROR: Running multiple emulators with the same AVD is an experimental feature.
Labels: c: crash,platform-android,tool,P2,team-android,triaged-android

From crash logging.

```
ProcessException: Process exited abnormally:
emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature.
Please use -read-only flag to enable this feature.
  Command: C:\Users\...\AppData\Local\Android\sdk\emulator\emulator.exe -avd Pixel_3_API_24
  | at RunResult.throwException | (process.dart:172 )
  | at _DefaultProcessUtils.run | (process.dart:322 )
  | at <asynchronous gap> | (async )
  | at AndroidEmulator.launch | (android_emulator.dart:53 )
  | at EmulatorsCommand._launchEmulator | (emulators.dart:73 )
  | at <asynchronous gap> | (async )
  | at EmulatorsCommand.runCommand | (emulators.dart:46 )
  | at FlutterCommand.verifyThenRunCommand | (flutter_command.dart:637 )
  | at _asyncThenWrapperHelper.<anonymous closure> | (async_patch.dart:75 )
  | at _rootRunUnary | (zone.dart:1134 )
  | at _CustomZone.runUnary | (zone.dart:1031 )
  | at _FutureListener.handleValue | (future_impl.dart:140 )
  | at Future._propagateToListeners.handleValueCallback | (future_impl.dart:682 )
  | at Future._propagateToListeners | (future_impl.dart:711 )
  | at Future._completeWithValue | (future_impl.dart:526 )
  | at Future._asyncComplete.<anonymous closure> | (future_impl.dart:556 )
  | at _rootRun | (zone.dart:1126 )
  | at _CustomZone.run | (zone.dart:1023 )
  | at _CustomZone.runGuarded | (zone.dart:925 )
  | at _CustomZone.bindCallbackGuarded.<anonymous closure> | (zone.dart:965 )
  | at _microtaskLoop | (schedule_microtask.dart:43 )
  | at _startMicrotaskLoop | (schedule_microtask.dart:52 )
  | at _runPendingImmediateCallback | (isolate_patch.dart:118 )
  | at _RawReceivePortImpl._handleMessage | (isolate_patch.dart:175 )
```

Maybe we can parse out the 'Running multiple emulators' bit, and throw a tool exit instead of crashing.

/cc @blasten
Repository: go
Issue: x/build/maintner: track GitHub Projects
Labels: Builders,NeedsFix,FeatureRequest

Maintner doesn't track GitHub Projects.

@rsc wanted to use them recently in gopherbot but couldn't.

This is a tracking bug for supporting them.
Repository: flutter
Issue: If a label has been manually removed, fluttergithubbot should not re-add it
Labels: team-infra,P3,triaged-infra

When somebody decides that a label is not relevant for a PR and removes it, the bot should not re-add it when a new commit is pushed.

/cc @dnfield
Repository: terminal
Issue: initialPosition should set both coordinates when one number exists
Labels: Help Wanted,Area-Settings,Product-Terminal,Issue-Task,good first issue

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**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.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Environment

```none
Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 0.8.10091.0

Any other software?
```

# Steps to reproduce

Set `initialPosition` to "#" (any number will work).

# Expected behavior

That number will set both the X and Y coordinates of the Terminal on launch. This matches the functionality of `padding`.

# Actual behavior

Only the X coordinate gets set.
Repository: godot
Issue: AnimationPlayer saved multiple values for same keyframe
Labels: bug,topic:editor

**Godot version:**
Godot_v3.1.2-rc1_win64

**OS/device including version:**
Windows 7

**Issue description:**
Sometimes the AnimationPlayer saves bad keyframe data

**Steps to reproduce:**
This is happening randomly I do not know how to reproduce this

Video showing the problem:
https://streamable.com/nq0m2

In the video it is clearly visible that there are multiple values stored for the same exact keyframe


**Minimal reproduction project:**
Don't have one as I don't know how to reproduce this
Repository: go
Issue: x/build: use Google Cloud for aix/ppc64 and linux/ppc64x builders
Labels: Builders,NeedsInvestigation,new-builder,arch-ppc64x

Google Cloud now supports POWER:

https://cloud.google.com/blog/products/gcp/ibm-power-systems-now-available-on-google-cloud

Maybe we can start running the AIX and linux/ppc64x builders on GCP (and scale VMs dynamically as needed) instead of OSUOSL (where we have a fixed and limited capacity).

/cc @laboger @trex58 @toothrot
Repository: go
Issue: x/tools/go/analysis/passes/shadow: shadowing not detected on deferred usage 
Labels: NeedsInvestigation,Tools,Analysis

<!--
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 go1.13.4 darwin/amd64
</pre>

### What did you do?
ran
```
go install golang.org/x/tools/go/analysis/passes/shadow/cmd/shadow
go vet -vettool=$(which shadow) main.go
```
on

```go
package main

import "fmt"

func main() {
	err := fmt.Errorf("one")
	defer func() { fmt.Printf("deferred err is %v\n", err) }()
	{
		err := fmt.Errorf("two")
		fmt.Printf("err is %v\n", err)
	}
}
```

### What did you expect to see?
```
./main.go:9:3: declaration of "err" shadows declaration at line 6
```
This is a simplified example but the intention of the defer is to print whatever the value of `err` is before returning. Since the `err` is redeclared in the new scope it shadows the initial declaration err. The `defer` then prints "deferred err is one" instead of the intended "deferred error is two".

### What did you see instead?
No vet error
Repository: pytorch
Issue: PyTorch C++ API docs only tracks master branch
Labels: module: cpp,triaged,module: doc infra

## 📚 Documentation

Currently, PyTorch C++ API docs (https://pytorch.org/cppdocs/) only tracks the master branch. Ideally we should add PyTorch version selector into it, similar to the Python API docs (https://pytorch.org/docs/stable/index.html).


cc @yf225 @ezyang @zou3519
Repository: rust
Issue: lint on dbg! of non-reference with return value not used
Labels: A-lints,T-lang,C-feature-request

The `dbg!` macro takes its argument by value, so that it can return that same value. See https://github.com/rust-lang/rust/issues/59943 for some background.

We should lint on code that calls `dbg!` on a non-reference value (thus consuming that value) and doesn't do anything with the return value. The lint could suggest taking a reference.
Repository: rust
Issue: Don't infer regions in type checking
Labels: C-enhancement,A-lifetimes,T-compiler,A-inference,A-NLL

This is a tracking issue for avoiding region inference in item body type checking. The goal would be to use `ReErased` where we currently use `ReVar` as much as possible.

The motivations for this are:

* It would avoid doing region inference twice (once in typeck, once in borrowck).
* It might improve caching since there are fewer distinct types.
* It ensures that region inference cannot affect later passes.

cc @nikomatsakis
Repository: flutter
Issue: [flutter_tools] Migrate platforms away from .flutter-plugins
Labels: tool,c: API break,P2,team-tool,triaged-tool

https://github.com/flutter/flutter/pull/48614 moves the plugins list to `.flutter-plugins-dependencies`. `.flutter-plugins` will be kept for a whilee to avoid breaking existing apps, but should be removed after the migration is complete
Repository: go
Issue: testing,go/doc: no way to properly distribute non-trivial runnable examples
Labels: NeedsInvestigation

I filed #35852 as a proposal to try to describe this problem and propose a solution, but since it was declined, I'm falling back to simply filing an issue about the problem. The fact that the solution got rejected doesn't mean that the problem doesn't exist.

--

We can have examples which show up in the godoc but aren't runnable, and runnable examples which are run as part of `go test`. This is enough for most use cases.

However, take the case where one has more than a handful of examples in a single package, and they each take a non-trivial amount of time to run, such as 200ms. Since they cannot run in parallel with themselves or any other test within the same package, `go test` can take multiple more seconds than it really needs to.

The root of the problem is that there's no way to write examples which are:

1) Part of the documentation (i.e. godoc)
2) Runnable (i.e. on godoc.org, or via `go test`)
3) Scalable (i.e. can be run in parallel)

Below are some workarounds I considered:

* Rewriting some of the examples as tests. Not good, because they are lost in the godoc, and hidden from the users. Loses point 1.
* Splitting the examples in multiple packages. This makes `go test ./...` faster, as there's built-in parallelism between packages being tested. However, this splits up godoc pages, and it's not unreasonable to have more than a handful of examples in a single package. Loses point 1.
* Make some of the examples non-runnable. Perhaps the best option today, but still not great. A runnable example is always verified by `go test`, and it's easier for the user to see what it does and how to run it. Loses point 2.

In the proposal above I tried exploring a couple of solutions to allow running examples in parallel. Are there other solutions we can look into?

/cc @bcmills @leitzler @rsc
Repository: flutter
Issue: [New Feature] TextStyle.verticalShift property
Labels: c: new feature,framework,engine,a: typography,P2,team-engine,triaged-engine

It is now becoming easier to precisely position text as desired, however the vertical axis is still lacking in the ability to shift up and down relative to the baseline. Currently, to accomplish shift, it is difficult if not impossible, making aligning slightly misaligned fonts a pain to do, as we always layout along the baseline.

I propose `TextStyle.verticalShift` property which would apply a logical pixel vertical shift relative to the baseline and be specified as a proportion of the font size. For example, with verticalShift as `-0.5` and fontSize of `10`, the text (ascent and descent) would be transformed by 5 logical pixels downwards. If used in isolation, the line would then be "shorter" and the entire line would move up to compensate. However, when in a multi-span line, this shift would leave the other spans unmodified, causing a relative alignment shift. The ascent and descent would both be shifted by the same amount.

This is useful in cases where certain languages do not naturally line up as expected. A small shift can be applied to spans in one language to account for the mismatch.

This is not prioritized as there is currently nobody asking for this, but I do believe that this can be a useful tool that many people do not know they want as it does not seem to exist in other layout systems.

I will provide some diagrams/design doc shortly.
Repository: rust
Issue: Support whole program devirtualization
Labels: A-LLVM,C-enhancement,A-trait-system,T-compiler,C-optimization

When doing LTO, LLVM supports a devirtualization pass that converts some indirect calls to static, inlineable calls. This can unlock a lot of optimizations when dynamic dispatch is used frequently in a program.

I don't know how hard this would be to support in Rust. Clang has a flag `-fwhole-program-vtables` which we would need to emulate. From there it seems like it might "just work". I'm opening this issue to start collecting more information.

I also found #11915 which mentions this, but not sure if any of the information there is still accurate.
Repository: TypeScript
Issue: Enable a library to support an older compiler than the one used to build it
Labels: Suggestion,Awaiting More Feedback

## Search Terms

TS1086, getter, incompatible, 3.7

## Use Case

Consider a library API like this:

```ts
export class Book {
  get title(): string { return "Untitled"; }
}
```

If I compile this library using TypeScript 3.7, the resulting .d.ts file cannot be consumed by a project that uses TypeScript 3.5.  The build will fail with this error:

```
error TS1086: An accessor cannot be declared in an ambient context.
```

Today, this error is considered ["Working as Intended"](https://github.com/microsoft/TypeScript/issues/33939#issuecomment-544192622).  For libraries that seek to maximize compatibility, this policy causes us to get stranded on a relatively old compiler release. 🤔 

Note that the above source code is not using any new 3.7 language features. The class property getter syntax is the same in TS 3.5.   In other words, _backwards-compatible source code does NOT produce backwards-compatible .d.ts files._

## Proposed change

Let's introduce a new option in **tsconfig.json**:

```ts
  "dtsCompatibilityVersion": "3.5.0"
```

This would have two effects:

- If my source code accidentally uses newer 3.7 syntax, the compiler will report an error to warn me.
- The emitter will avoid introducing incompatible constructs in the .d.ts files (e.g. emit `readonly title: string` instead of `get title(): string` for the above example)

Where constructs can be transformed to equivalent older constructs (like what [downlevel-dts](https://github.com/sandersn/downlevel-dts) does), that's nice to have.  But it's NOT required. Reporting an error is perfectly acceptable, as long as _backwards-compatible source code can produce backwards-compatible .d.ts files._

How far back do we want to be compatible?  The `dtsCompatibilityVersion` option leaves this decision up to the library author, while enabling them to use the latest compiler engine.

## 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).
Repository: godot
Issue: String nodes cannot grab focus even with set_focus_mode(FOCUS_ALL)
Labels: bug,topic:gui

**Godot version:**
v3.1.2

**OS/device including version:**
Windows 10 Pro education 64 bit

**Issue description:**
Clicking on the String node with the mouse doesn't grab the focus and redirect it to the SubBtn node even though I use set_focus_mode()

**Steps to reproduce:**
download the project if you don't have it
debug the GUIOption scene
click on charg mk 1 text
notice the root node is selected and not the label I marked as focusable in the script

**Minimal reproduction project:**
[AstroWars.zip](https://github.com/godotengine/godot/files/4068169/AstroWars.zip)
Repository: godot
Issue: Forwarding focus neighbours causes odd side effects
Labels: bug,confirmed,topic:gui

**Godot version:**
v3.1.2

**OS/device including version:**
Windows 10 Pro education 64 bit

**Issue description:**
selection from alternative version does opposite of expected.
setting focus neighbour in Menu1 scene doesn't allow one below it to be selected
unsetting focus neighbour allows the one below it to be selected

**Steps to reproduce:**
download the project if you have the old version
debug the Menu1 scene
press down
notice the left arrow below it is selected
edit Menu1 scene and set Weapon1 top and bottom focus neighbours to the Weapon2 node
debug the Menu1 again
press down
notice that the focus didn't change and the exact opposite of what should happen happened

**Minimal reproduction project:**
[AstroWars.zip](https://github.com/godotengine/godot/files/4068184/AstroWars.zip)
Repository: pytorch
Issue: [TorchScript] Device comparison implemented in eq but not ne
Labels: oncall: jit,triaged

## 🐛 Bug

In a scripted module "a.device != b.device" doesn't work because of no matching signatures, while "not a.device == b.device" works. 

## To Reproduce

Minimal example: 
```import torch
from torch import nn
class MyModel(nn.Module):
    def __init__(self):
        super().__init__()
    def forward(self):
        a = torch.zeros(1)
        if a.device != a.device:
            return torch.zeros(1)
        else:
            return torch.ones(1)
m = MyModel()
scripted = torch.jit.script(m)
```

The above doesn't work, "a.device != a.device" -> "not a.device == a.device" works. 

## Expected behavior

not equal should also work

## Environment

FB intern

@eellison 


cc @suo
Repository: pytorch
Issue: models after prepare/prepare_qat contains `qconfig` which prevents pickling
Labels: oncall: quantization,low priority,triaged

We should remove qconfig after module swapping

cc @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @jerryzh168 @dzhulgakov