sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Godot 3.2.1 Startup Crash and Missing/Broken Scenes
Labels: bug,topic:editor,confirmed,crash


Godot Engine v3.2.1.stable
<!-- Specify commit hash if using non-official build. -->


GLES3, Intel Mesa Integrated GPU

There was a crash immediately upon opening my project. Before it started crashing it reported missing/broken scenes that were correctly named and in the correct filepath that it was requesting. The backtrace is included here
```
[I] [faye@acerpred ~] godot --verbose                                            20:46:06
Godot Engine v3.2.1.stable.custom_build - https://godotengine.org
XInput: Refreshing devices.
XInput: No touch devices found.
Detecting GPUs, set DRI_PRIME in the environment to override GPU detection logic.
Only one GPU found, using default.
XcursorGetTheme could not get cursor theme
Using GLES3 video driver
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 630 (KBL GT2)
Audio buffer frames: 341 calculated latency: 7ms

CORE API HASH: 10822102301860774635
EDITOR API HASH: 14982495073158502407
Loading resource: res://.config/godot/editor_settings-3.tres
EditorSettings: Load OK!
EditorSettings: Save OK!
Loaded builtin certs
Editing project: /home/faye/Games/Dev/Godot/RPG (::home::faye::Games::Dev::Godot::RPG)
Godot Engine v3.2.1.stable.custom_build - https://godotengine.org
EditorSettings: Save OK!
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 630 (KBL GT2)
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x3c3e0) [0x7f08825d43e0] (??:0)
[2] /usr/bin/godot() [0x1b770a4] (??:?)
[3] /usr/bin/godot() [0x234cca9] (??:?)
[4] /usr/bin/godot() [0x234eebd] (??:?)
[5] /usr/bin/godot() [0x234d4b9] (??:?)
[6] /usr/bin/godot() [0x234eebd] (??:?)
[7] /usr/bin/godot() [0x12afd83] (??:?)
[8] /usr/bin/godot() [0x12b1768] (??:?)
[9] /usr/bin/godot() [0x9506e5] (??:0)
[10] /usr/bin/godot() [0x2a866c7] (??:?)
[11] /usr/bin/godot() [0x2a930d5] (??:?)
[12] /usr/bin/godot() [0x2a94180] (??:?)
[13] /usr/bin/godot() [0x1246c7d] (??:?)
[14] /usr/bin/godot() [0x2a86034] (??:?)
[15] /usr/bin/godot() [0x1bae9ba] (??:?)
[16] /usr/bin/godot() [0x1bb8e10] (??:?)
[17] /usr/bin/godot() [0x774a7a] (??:0)
[18] /usr/bin/godot() [0x75cfc1] (??:0)
[19] /usr/bin/godot() [0x74b07d] (??:0)
[20] /usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7f08825bf002] (??:0)
[21] /usr/bin/godot() [0x74d73e] (??:0)
-- END OF BACKTRACE --
```

I'm unsure of particular steps to reproduce, but the godot project that I had this crash on is included here. The issue persisted even after deleting `.import` to try and reimport everything.

[RPG.zip](https://github.com/godotengine/godot/files/4802021/RPG.zip)
Repository: pytorch
Issue: CUDA error: out of memory when running tensorpipe test_cuda
Labels: triaged,module: rpc,module: tensorpipe

## 🐛 Bug

When running Tensorpipe's test cuda a bunch of time (using stresstests) with the internal infra, I frequently see the following error:

```
line 2453, in test_cuda
>     t1 = torch.rand(3, 3).cuda(0)
> RuntimeError: CUDA error: out of memory
> exiting process with exit code: 10
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> I0618 19:33:56.879187 2552243 tensorpipe_agent.cpp:808] RPC agent for worker2 is shutting down
> Process 2 terminated with exit code 10, terminating remaining processes.
> ERROR
```
## To Reproduce

Run tensorpipe's `test_cuda` a bunch of times on a GPU-enabled machine. 

## Additional context

I took a look at the GPU memory usage when running the test 10 times in parallel with `nvidia-smi` and it did look to be quite high. Although, it's unclear why this would be as this test does not do large GPU allocations, and even running it 10 times concurrently seems like it should not OOM the GPU. 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar @jiayisuse @lw @beauby
Repository: rust
Issue: Misleading Error Message: the trait `Foo` is not implemented for `&dyn Foo`
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics

Here is a minimal example [[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3f1ec48f5216c6f700615bcd401333c8)]:

```rust
pub trait Foo {
    fn bar(&self, _: &dyn Foo) -> bool {
        true
    }
}

impl Foo for u32 {}

fn main() {
    let x = 1;
    let v: Vec<&dyn Foo> = vec![&1, &2, &3];
    v.iter().all(|y| x.bar(y));
}
```

Which produces this error:

```
error[E0277]: the trait bound `&dyn Foo: Foo` is not satisfied
  --> src/main.rs:14:28
   |
14 |     v.iter().all(|y| x.bar(y));
   |                            ^ the trait `Foo` is not implemented for `&dyn Foo`
   |
   = note: required for the cast to the object type `dyn Foo`
```

I find this error to be misleading because:

1) The type of `y` within the closure should be `&&dyn Foo`, not `&dyn Foo`.
2) Even though the type listed in the error message seems wrong, the trait `Foo` _should_ be implemented for `&dyn Foo` if that were the actual type of `y`.

This can be fixed in a number of ways:
```rust
v.iter().all(|&y| x.bar(y));
v.iter().all(|&y| x.bar(&*y));
v.iter().all(|y| x.bar(*y));
v.iter().all(|y| x.bar(&**y));
v.into_iter().all(|y| x.bar(y));
```
All of which are consistent with `y` being of type `&&dyn Foo`, and none of which are suggested by the error message.
Repository: rust
Issue: Tracking issue for moving ui tests to subdirectories
Labels: E-easy,C-cleanup,A-testsuite,E-mentor,T-compiler,C-tracking-issue,E-tedious

**NOTE: see https://github.com/rust-lang/rust/issues/73494#issuecomment-1500919846 for mentoring instructions.**

Looking at https://github.com/rust-lang/rust/tree/master/src/test/ui, github truncates the list to just the first 1000 entries (of 1564 total entries).

This is especially frustrating since github also sorts by name, not by kind, and so its truncation is cutting off whole subdirectories from the view.

TODO:
 - [ ] We should restructure the test suite so that no one directory has more than 1000 entries
 - [x] We should add code to tidy to ensure that future changes do not break the above invariant. (done by #79959)
Repository: pytorch
Issue: caffe2 error during compilation of PyTorch with ROCm on Archlinux
Labels: caffe2

aur package: _python-pytorch-cuda-git_ `ROCM=ON`

```sh

:: Downloading the latest sources for a devel package python-pytorch-cuda-git...

:: Starting the build:
==> Making package: python-pytorch-git 1.3.1.r27648.02e091902f6-1 (Fri Jun 19 07:52:01 2020)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Updating pytorch git repo...
Fetching origin
==> Validating source files with sha512sums...
pytorch ... Skipped
==> Extracting sources...
-> Creating working copy of pytorch git repo...
Reset branch 'makepkg'
==> Starting prepare()...
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Building without cuda and without MKL-DNN
Building wheel torch-1.3.1
-- Building version 1.3.1
cmake --build . --target install --config Release -- -j 8
make: *** No rule to make target 'install'.  Stop.
Traceback (most recent call last):
File "setup.py", line 732, in <module>
build_deps()
File "setup.py", line 311, in build_deps
build_caffe2(version=version,
File "/home/chibo/.cache/pikaur/build/python-pytorch-git/src/pytorch-git/tools/build_pytorch_libs.py", line 62, in build_caffe2
cmake.build(my_env)
File "/home/chibo/.cache/pikaur/build/python-pytorch-git/src/pytorch-git/tools/setup_helpers/cmake.py", line 345, in build
self.run(build_args, my_env)
File "/home/chibo/.cache/pikaur/build/python-pytorch-git/src/pytorch-git/tools/setup_helpers/cmake.py", line 141, in run
check_call(command, cwd=self.build_dir, env=env)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '8']' returned non-zero exit status 2.
==> ERROR: A failure occurred in build().
Aborting...
```

cc @malfet
Repository: create-react-app
Issue: Allow to skip verifyTypeScriptSetup
Labels: issue: proposal,needs triage

Allow users to skip verifyTypeScriptSetup by add `process.env.SKIP_VERIFY_TYPESCRIPT_SETUP === 'true'`
Repository: youtube-dl
Issue: Add Support For AAJ TAK News
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.06.16.1. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [ ] I'm reporting a new site support request
- [ ] I've verified that I'm running youtube-dl version **2020.06.16.1**
- [ ] I've checked that all provided URLs are alive and playable in a browser
- [ ] I've checked that none of provided URLs violate any copyrights
- [ ] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.youtube.com/watch?v=BaW_jenozKc
- Single video: https://youtu.be/BaW_jenozKc
- Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->
Hello YouTube-DL
 Please Add Support For AAJ TAK URL [ https://aajtak.intoday.in/video/pcr-coronavirus-latest-research-claims-that-july-august-will-see-a-peak-covid-19-cases-news-in-hindi-1-1202230.html ] .
Repository: flutter
Issue: CupertinoDatePickerMode.dateAndTime does not have capability to change month and year. 
Labels: c: new feature,framework,f: date/time picker,f: cupertino,c: proposal,P3,team-design,triaged-design

Current  CupertinoDatePicker has different modes to choose but  CupertinoDatePickerMode.dateAndTime does not have capability to change month and year. Can we have new  mode to set like below to select all date fields in single widget.

![Screenshot_2020-06-16-19-57-03-579](https://user-images.githubusercontent.com/2254065/85117577-b30d5a00-b23c-11ea-8340-5e6ad936cd60.jpg)
Repository: rust
Issue: User type annotations can result in different mir-opt test results in CI vs locally
Labels: T-compiler,C-bug,A-reproducibility,A-mir-opt

In #73442, a mir-opt test that I blessed locally [was failing on CI](https://github.com/rust-lang/rust/pull/73442#issuecomment-645951636) and I could not reproduce the failure locally - this was due to the `DefId` in the user type annotations of the test shown below, which appeared to be different locally versus on CI.

```rust
// compile-flags: -Z mir-opt-level=1
// Regression test for #72181, this ICE requires `-Z mir-opt-level=1` flags.

use std::mem;

#[derive(Copy, Clone)]
enum Never {}

union Foo {
    a: u64,
    b: Never
}

// EMIT_MIR rustc.foo.mir_map.0.mir
fn foo(xs: [(Never, u32); 1]) -> u32 { xs[0].1 }

// EMIT_MIR rustc.bar.mir_map.0.mir
fn bar([(_, x)]: [(Never, u32); 1]) -> u32 { x }

// EMIT_MIR rustc.main.mir_map.0.mir
fn main() {
    println!("{}", mem::size_of::<Foo>());

    let f = [Foo { a: 42 }, Foo { a: 10 }];
    println!("{:?}", unsafe { f[0].a });
}
```

You can find my [config.toml here](https://github.com/davidtwco/veritas/blob/52a6d7ec2844df8094bd65a2ad7ca99aaa51cf72/nix/shells/rustc.nix#L7-L137) and I was running tests with `./x.py test src/test/mir-opt --stage 1` (though I couldn't reproduce with a stage2 build either).

cc @rust-lang/wg-mir-opt
Repository: opencv
Issue: DNN Support matrix
Labels: category: documentation,category: dnn,effort: few weeks

Just an idea: 

For Mesa there is a matrix that shows the OpenGL support by different vendors/drivers
https://mesamatrix.net/

I dont know how complicated this would be to make it for opencv, but it would for sure help with making Layer Support transparent for CPU OPENCL and CUDA etc. mesamatrix is opensource.
Repository: flutter
Issue: [Flutter_module] Unresolved reference: **
Labels: c: crash,platform-android,tool,t: gradle,a: existing-apps,P2,team-android,triaged-android

## Steps to Reproduce

1. Create new Empty Activity Application.
2. New flutter module.
3. Add following code to MainActivity
```kotlin
val variable = Manifest.permission.ACCESS_MEDIA_LOCATION
// or
val variable = Build.VERSION_CODES.Q
```

4. Build and run application.

**Results:**

```java
Unresolved reference: ACCESS_MEDIA_LOCATION
```

**Description:**
![image](https://user-images.githubusercontent.com/58068445/85138519-7c076a80-b275-11ea-9958-8ae3ff3cbd12.png)

When the project was imported using the flutter module, a very strange problem appeared. I even created multiple projects to reproduce the problem. I finally learned that this is the problem of the content in `flutterSdkPath/packages/flutter_tools/gradle/module_plugin_loader.gradle`, When I remove it, it will not appear
```gradle
    g.rootProject.afterEvaluate { p ->
        p.subprojects { sp ->
            if (sp.name != 'flutter') {
                sp.evaluationDependsOn(':flutter')
            }
        }
    }
```

**Extra:**
Found this problem because I cannot compile after installed [permission_handler](https://pub.dev/packages/permission_handler) plugin, reported a lot of `Unresolved reference` errors

![image](https://user-images.githubusercontent.com/58068445/85138311-216e0e80-b275-11ea-8e6d-11b9ea333829.png)
Repository: tensorflow
Issue: If TMP is not set, then the build system defaults to the wrong path
Labels: type:build/install,subtype: ubuntu/linux,TF 2.10

<em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em>

**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux release 7.3.1611 (Core)
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no
- TensorFlow installed from (source or binary): source
- TensorFlow version: v2.2.0
- Python version: 3.5.1
- Installed using virtualenv? pip? conda?: no, compiling from source
- Bazel version (if compiling from source): 2.0.0 (it claimed that Tensorflow did not support anything higher)
- GCC/Compiler version (if compiling from source): 8.2.0
- CUDA/cuDNN version: 10.1
- GPU model and memory: Tesla P100, 16280MiB



**Describe the problem**

**Provide the exact sequence of commands / steps that you executed before running into the problem**
When building Tensorflow from source when the `TMP` environment variable is not set, then following warning is shown:

```
Auto-Configuration Warning: 'TMP' environment variable is not set, using 'C:\Windows\Temp' as default
```

Naturally, I would expect it to default to something. However, I'm on a _Linux_ computer, not a _Windows_ computer. On Linux, it should default to something sensible (e.g. `/tmp`, or the current directory), instead of `C:\Windows\Temp` - which clearly isn't going to work - as on Linux this is not a valid file/directory path.

**Any other info / logs**
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

```
Auto-Configuration Warning: 'TMP' environment variable is not set, using 'C:\Windows\Temp' as default
```
Repository: react
Issue: Hiding MUI Components inside React Developer Tools
Labels: Type: Discussion,Component: Developer Tools

Hello, recently we've overhauled a client's website with the usage of [Material UI](https://material-ui.com/). It's been an enjoyable experience, however one thing that really irks me - given the project is pretty large and there's multiple people working on it, sometimes it gets chaotic which component is exactly what and you need to find out which component you should be working on.

My general fallback was using the [React Develeloper Tools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en) extension, however given MUI consists of ready-made JSX components, it essentially spams and halts the usefulness of the 'Components' tab.

![image](https://user-images.githubusercontent.com/17268815/85140844-25cf0300-b246-11ea-98ec-e0d37aea2707.png)

Is there perhaps any way that would allow for filtering of specific packages / jsx elements inside the React Developer Tools?

I know I could technically user regex to filter out a list of all the known MUI Components, but that seems bit overkill.  I sadly suspect such a thing is not supported, but you never know unless you ask.
Repository: TypeScript
Issue: Type inference with conditional for array fails for literal
Labels: Needs Investigation

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.9.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** typescript infer array type conditional literal

**Code**

```ts
function func<T>(opt: {
  value: T;
  arrayValue: T extends any[] ? T : T[];
}) {}

func({
  value: [1, 2, 3],
  arrayValue: [1, 2, 3],
}); // throws error 

const obj = {
  value: [1, 2, 3],
  arrayValue: [1, 2, 3],
};

func(obj);
```

**Expected behavior:**
No error is thrown.

**Actual behavior:**
The commented function call throws the following error:

```
Type 'number[]' is not assignable to type 'number'.(2322)
input.ts(2, 3): The expected type comes from property 'value' which is declared here on type '{ value: number; arrayValue: number[]; }'
```

**Playground Link:** https://www.typescriptlang.org/play/#code/GYVwdgxgLglg9mABKSAeAKgPgBRwA5QBciA3gFCKIBuAhgDYgCmx6A3BYjQE5c0CeANXpMWiRgA8ojMABMAzpzB8A2gF1EAfkTpELNewC+ASlIGyZFBGzlKtBs0TKAjABpEAJjcBmVS47deQWEHZzdPRB8-Y3MIBDkoRDgAIwArRABeUg47EUdXD29ffx5+IXtiUIKIooN2C3ArZJSjdiA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: go
Issue: cmd/compile: optimize xor to complement
Labels: Performance,NeedsInvestigation,compiler/runtime

<!--
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
go version go1.14.4 linux/amd64
</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
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jadenw/.cache/go-build"
GOENV="/home/jadenw/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/jadenw/GOPATH"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build102234605=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Tried to flip bits in a large section of a bitmap using `^= ^uint64(0)` in a loop.

### What did you expect to see?

The compiler treats this as a bitwise complement operation.

### What did you see instead?

The compiler emits an xor against a constant, and treats it differently than a bitwise complement.

https://godbolt.org/z/vxQyD3

If I understand correctly, this could be solved by adding the following rule to `generic.rules`:
```
(Xor(64|32|16|8) (Const(64|32|16|8) [-1]) x) => (Com(64|32|16|8) x)
```
Repository: rust
Issue: rustc uses insane amounts of memory when compiling a function that loads 1500+ function pointers from a DLL
Labels: I-compiletime,T-compiler,A-inference,I-compilemem,C-bug

For my use-case, I'm trying to load a lot of function pointers from a .dll file using the `libloading` crate. However, I can't compile a `load_my_dll()` function if I have more than maybe 1000 function pointers, because rustc uses an insane amount of memory for compilation:

![test](https://user-images.githubusercontent.com/12084016/85151466-19ea3d80-b254-11ea-999a-e98fd0787558.gif)

I can pretty much watch my computer lock up in real time because it runs out of memory (see the pie in the lower left corner).

I've built a test-case here: https://github.com/fschutt/libloading-loadtest

Look in the `generate.py` file, I've currently set it to 2000 function pointers, but that's not even a lot. Larger DLLs will likely need 5000 - 30000 function pointers. Clone the repository and run `cargo check`. After you wait a while, the memory usage will go up dramatically. This bug also happens on nightly.

I think this may have to do with how verbose the code output of generics are. Is there a way to fix it from my side?

### Meta

`rustc --version --verbose`:
```
rustc 1.44.1 (c7087fe00 2020-06-17)
binary: rustc
commit-hash: c7087fe00d2ba919df1d813c040a5d47e43b0fe7
commit-date: 2020-06-17
host: x86_64-unknown-linux-gnu
release: 1.44.1
LLVM version: 9.0
```