sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Using the `viewport` stretch mode and resizing the window (or using "shrink" value other than 1) results in black screen if MSAA is forced on in NVIDIA or AMD settings
Labels: bug,topic:rendering,confirmed,topic:thirdparty

**Godot version:** Git https://github.com/godotengine/godot/commit/7d6f210ccb5de9ef414f94ad42f9f3dea14c0493

**OS/device including version:** Fedora 27, NVIDIA 390.48

**Issue description:** When the window scaling mode is set to `2d` or `viewport`, setting the `display/window/stretch/shrink` project setting to a value other than 1 will cause the running project's rendering to break (it will appear to be frozen at the splash screen). If the window is resized by the user, it will turn into a black screen. No errors can be seen in the Debugger dock of the editor.

This also occurs when using the `viewport` stretch mode after resizing the window, even if `display/window/stretch/shrink` is set to 1.

**Steps to reproduce:** After making sure the window scaling mode is set to `2d` or `viewport`, set `display/window/stretch/shrink` to a value other than 1 in the Project Settings then run the project.

**Minimal reproduction project:** [shrink_bug.zip](https://github.com/godotengine/godot/files/1932373/shrink_bug.zip)

___

**Update:** I can still reproduce this as of https://github.com/godotengine/godot/commit/6110bdee138febf3b04b47bc15b834bda7b99d52 (Fedora 30, NVIDIA 418.74). When the bug occurs, this appears in the console when Godot is started with `--verbose`:

```
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 1282        Severity: High  Message: GL_INVALID_OPERATION error generated. Source and destination dimensions must be identical with the current filtering modes.
   At: drivers/gles3/rasterizer_gles3.cpp:123.
```
Repository: flutter
Issue: SceneBuilder requires having only one root layer
Labels: engine,c: rendering,P2,team-engine,triaged-engine

If you push two layers onto a SceneBuilder, the second is silently dropped on the floor.

The first time you push a layer onto a scene builder, DefaultLayerBuilder::PushLayer sees it doesn't have a root layer yet, and uses the new layer as its root layer.

Then you pop that layer, and we set the current layer to the parent of the current layer, which is null, since the current layer is the root layer and the root layer has no parent.

When you then push the second layer onto the scene builder, DefaultLayerBuilder::PushLayer sees it has a root layer, sees it doesn't have a current layer, and exits without doing anything.

IMHO we have two choices:

1. Document and (in debug builds) assert that you only push a single layer onto the SceneBuilder. (Similarly, assert that when you pop, there is a layer to pop.)

2. Make SceneBuilder support having multiple root layers (e.g. by actually having SceneBuilder always create itself its own root layer, and push and pop on that).

This manifests itself currently when you use SceneBuilder e.g. to create an image with toImage. If you happen to push two child layers (which is easy to do when using the framework), you will silently only get the first in the output, even though no exceptions are thrown to suggest anything went wrong.

cc @chinmaygarde @gspencergoog
Repository: TypeScript
Issue: Option to disable sorting when running organize imports
Labels: Suggestion,Awaiting More Feedback,Domain: Organize Imports

_From @ssi-hu-tasi-norbert on April 20, 2018 9:9_

<!-- Do you have a question? Please ask it on https://stackoverflow.com/questions/tagged/vscode. -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.22.2
- OS Version: win 10

Sort should be optional. I have imports from 3rd parties above and app imports below and I don't want to mix them. With a separator( for me it is a comment // app) these two sections  can be sort separatedly.
Anyway, this is a great feature.

Thanks,

Norbert

_Copied from original issue: Microsoft/vscode#48263_
Repository: kubernetes
Issue: Volume metrics causing node to become not ready
Labels: kind/bug,sig/storage,lifecycle/frozen

<!-- This form is for bug reports and feature requests ONLY!

If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).

If this may be security issue, please disclose it privately via https://kubernetes.io/security/.
-->

**Is this a BUG REPORT or FEATURE REQUEST?**:
@kubernetes/sig-storage-bugs 

**What happened**:
In this [discussion](https://github.com/kubernetes/kubernetes/issues/36499#issuecomment-383192634), it was reported that running df on nodes with 100 pods is causing the node to become not ready, and switching to SSDs for the boot disk helped alleviate this issue.

**What you expected to happen**:
Collecting metrics should not cause the node to become unstable
Repository: flutter
Issue: Support splitting a Flutter app's assets into multiple packages
Labels: c: new feature,tool,framework,engine,c: proposal,P2,team-engine,triaged-engine

For Android Instant Apps, and probably for Fuchsia and probably for hot updates, we will want to split an apps' assets into blobs of data each of which can be shipped separately and loaded independently. It would probably make sense to do it along `package:` boundaries like we do for Dart code.

cc @zanderso @tvolkert @jason-simmons @chinmaygarde @cbracken
Repository: flutter
Issue: Flutter needs a way to manage image assets by locale
Labels: c: new feature,tool,framework,a: assets,P2,team-framework,triaged-framework

Both iOS and Android asset systems have ways to manage images per-locale.  Maybe those are already sufficient?

Or maybe we need some combined method as part of the `pubspec.yaml` flutter assets tag system?

(Filing based on a comment from @Hixie in an email.)
Repository: go
Issue: bytes, strings: optimize Contains with fast-path for sub-slices 
Labels: Performance,NeedsDecision

Consider the following:
```go
func Benchmark(b *testing.B) {
	buf := make([]byte, 1<<20)
	rand.Read(buf)
	for n := 64; n <= len(buf); n <<= 1 {
		b.Run(fmt.Sprintf("%d", n), func(b *testing.B) {
			for i := 0; i < b.N; i++ {
				bytes.Contains(buf, buf[n-64:n])
			}
		})
	}
}
```

On my machine, this prints:
```
Benchmark/64-8         	100000000	        11.8 ns/op
Benchmark/128-8        	100000000	        22.3 ns/op
Benchmark/256-8        	50000000	        29.1 ns/op
Benchmark/512-8        	30000000	        56.9 ns/op
Benchmark/1024-8       	20000000	       101 ns/op
Benchmark/2048-8       	10000000	       195 ns/op
Benchmark/4096-8       	 5000000	       393 ns/op
Benchmark/8192-8       	 2000000	       976 ns/op
Benchmark/16384-8      	 1000000	      1749 ns/op
Benchmark/32768-8      	  300000	      3968 ns/op
Benchmark/65536-8      	  200000	      8312 ns/op
Benchmark/131072-8     	  100000	     18300 ns/op
Benchmark/262144-8     	   50000	     35918 ns/op
Benchmark/524288-8     	   20000	     75942 ns/op
Benchmark/1048576-8    	   10000	    156854 ns/op
```
In this situation, the substring is sliced out of the parent slice. It should be know that the parent contains the substring in O(1) with something similar to:
```go
func Contains(b, subslice []byte) bool {
	if (*reflect.SliceHeader).(unsafe.Pointer(&b)).Data <= (*reflect.SliceHeader).(unsafe.Pointer(&subslice)).Data && (*reflect.SliceHeader).(unsafe.Pointer(&b)).Data + uintptr(len(b)) >= (*reflect.SliceHeader).(unsafe.Pointer(&subslice)).Data + uintptr(len(subslice)) {
		return true
	}
	return Index(b, subslice) != -1
}
```
(the above code is not correct as there is special consideration to manipulating `unsafe.Pointer`, but the general approach is the same)
Repository: flutter
Issue: All-purpose Media widget
Labels: c: new feature,framework,a: video,P3,team-framework,triaged-framework

It's a rather minor request, and totally up for discussion, however I feel that Flutter would benefit from having a generic ``Media`` widget, alongside ``Image`` and ``VideoPlayerController``.

Back in the days, when glittering GIFs ruled the world, if a website hosted images it hosted images, when it hosted videos – it hosted videos. Nowadays the lines are blurring, and Webm is slowly but surely pushing GIF out of the picture. Thus, websites that used to host files like PNG, JPG and GIF (all possible to be displayed through ``Image`` widget), also host MP4 and WEBM files now (both possible to be displayed through ``VideoPlayerController``), and sometimes even MP3 and other media formats.

Thus, if I wanted to grab, say, 50 newest files files from Imgur, half of them or so would be Webm. And that makes it impossible to display them all in a grid of ``Image`` widgets. Of course I could go through each and every one of them, check what's the file extension, compare it to my list of image extensions, list of sound extensions, list of video extensions, and create a widget based on that, so a PNG file will be displayed in ``Image``, and Webm will be displayed in ``VideoPlayerController``.

Question is: should that be the case? Shouldn't an all-purpose ``Media`` widget take care of that?

Another possibility would be an inline Chrome window, but it doesn't give full control over how is the media being displayed, and I don't think that a grid of 200 or so Chrome windows is a particularly good idea.

Thoughts? Opinions? Already exisitng solutions?
Repository: rust
Issue: Module decarations when using include! are relative to the included file
Labels: T-lang,C-feature-request

I'm not sure if this is actually a bug or intended behavior, but when using the `include!` macro to include a file which contains module declarations i.e. `mod foo`, it searches for the module relative to the included file's path and not relative to the file which uses the `include!`.

Here's some example code to demonstrate this:

mod.rs:
```
include!(concat!(env!(OUT_DIR), "/foo.in")); 
```

foo.in:
```
mod bar;
```
Example compiler output:
```
error[E0583]: file not found for module `bar`
 --> <OUT_DIR>/foo.in:1:5
  |
1 | mod bar;
  |     ^^^^^^^^^
  |
  = help: name the file either bar.rs or bar/mod.rs inside the directory "<OUT_DIR>"
```

This makes it impossible to have module declarations from generated code in a build script, for example.

## Meta
`rustc --version --verbose`:

rustc 1.25.0 (84203cac6 2018-03-25)
binary: rustc
commit-hash: 84203cac67e65ca8640b8392348411098c856985
commit-date: 2018-03-25
host: x86_64-unknown-linux-gnu
release: 1.25.0
LLVM version: 6.0
Repository: rust
Issue: Invalid collision with TryFrom implementation?
Labels: A-trait-system,T-lang,C-bug

Sorry for the code dump. This is the smallest code I could make to reproduce the problem.

```rust
use std::marker::PhantomData;
use std::convert::TryFrom;

trait Integer {}
impl Integer for u8 {}

trait Adapter<I: Integer>: TryFrom<I> + Into<I> {}

enum Choice {
    Foo,
    Bar,
    Baz
}

impl From<Choice> for u8 {
    fn from(c: Choice) -> u8 {
        match c {
            Choice::Foo => 1,
            Choice::Bar => 2,
            Choice::Baz => 3,
        }
    }
}

impl TryFrom<u8> for Choice {
    type Error = ();
    fn try_from(i: u8) -> Result<Choice, ()> {
        match i {
            1 => Ok(Choice::Foo),
            2 => Ok(Choice::Bar),
            3 => Ok(Choice::Baz),
            _ => Err(()),
        }
    }
}

impl Adapter<u8> for Choice {}

struct Pick<I: Integer, A: Adapter<I>> {
    phantom: PhantomData<A>,
    value: I,
}

impl<I: Integer, A: Adapter<I>> From<A> for Pick<I, A> {
    fn from(a: A) -> Pick<I, A> {
        Pick {
            phantom: PhantomData,
            value: a.into(),
        }
    }
}

impl<I: Integer, A: Adapter<I>> TryFrom<Pick<I, A>> for A {
    type Error = A::Error;

    fn try_from(p: Pick<I, A>) -> Result<A, Self::Error> {
        A::try_from(p.value)
    }
}
```

Attempting to compile this produces:

```
error[E0119]: conflicting implementations of trait `std::convert::TryFrom<Pick<_, _>>`:
  --> src/main.rs:53:1
   |
53 | impl<I: Integer, A: Adapter<I>> TryFrom<Pick<I, A>> for A {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T, U> std::convert::TryFrom<U> for T
             where T: std::convert::From<U>;

error[E0210]: type parameter `A` must be used as the type parameter for some local type (e.g. `MyStruct<A>`)
  --> src/main.rs:53:1
   |
53 | impl<I: Integer, A: Adapter<I>> TryFrom<Pick<I, A>> for A {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ type parameter `A` must be used as the type parameter for some local type
   |
   = note: only traits defined in the current crate can be implemented for a type parameter
```

I've spent several hours looking at this and I can't figure out why I'm getting these errors. The type parameter `A` is being used as the type parameter for a local type. Maybe the compiler can't tell because it is nested inside `TryFrom<>`?

But I'm also not sure why the first error occurs at all. The rule it conflicts with can basically be described as "types with infallible conversions implicitly implement fallible conversions." But in my case there is no infallible conversion. So I don't see where the conflict is arising from.

If there is really a bug and I'm not just overtired, this may impact #49305.
Repository: rust
Issue: Warnings and error suggestions are wrong when originating from inside proc-macros
Labels: C-enhancement,A-macros,T-compiler

For example

```
warning: unused import: `Form`
  --> example/src/main.rs:11:26
   |
11 | #[derive(Debug, Default, Form)]
   |                          ^^^^
   |
   = note: #[warn(unused_imports)] on by default

error[E0369]: binary operation `+` cannot be applied to type `&str`
  --> example/src/main.rs:18:26
   |
18 | #[derive(Debug, Default, Form)]
   |                          ^^^^ `+` can't be used to concatenate two `&str` strings
help: `to_owned()` can be used to create an owned `String` from a string reference. String concatenation appends the string on the right to the string on the left and may require reallocation. This requires ownership of the string on the left
   |
18 | #[derive(Debug, Default, Form.to_owned())]
   |
```

when the expanded source contains

```rust
use self::gtk::{Widget, Button, ComboBoxText, Label};

// and

let _ = "a" + "b";
```

with ComboBoxText being unused.
Repository: rust
Issue: Tracking issue for f32 and f64 methods in libcore
Labels: T-libs-api,C-tracking-issue,A-intrinsics,A-floating-point,Libs-Tracked

https://github.com/rust-lang/rust/pull/49896 removes from libcore (and moves to libstd) three methods of `f32` and `f64` (that were only usable through the unstable trait `core::num::Float`) because they’re implemented by calling LLVM intrinsics, and it’s not clear whether those intrinsics are lowered on any platform to calls to C’s `libm` or something else that requires runtime support that we don’t want in libcore:

* `abs`: calls `llvm.fabs.f32` or `llvm.fabs.f64`
* `signum`: calls `llvm.copysign.f32` or `llvm.copysign.f64`
* `powi`: calls `llvm.powi.f32` or `llvm.powi.f32`

The first two seem like they’d be easy to implement in a small number of lower-level instructions (such as a couple lines with `if`, or even bit twiddling based on IEEE 754). `abs` in particular seems like a rather common operation, and it’s unfortunate not to have it in libcore.

The `compiler-builtins` crate has Rust implementations of `__powisf2` and `__powidf2`, but in LLVM code those are only mentioned in `lib/Target/WebAssembly/WebAssemblyRuntimeLibcallSignatures.cpp` so I haven’t found evidence that `llvm.powi.f32` and `llvm.powi.f32` call those functions.

PR #27823 “Remove dependencies on libm functions from libcore” similarly moved a number of other `f32` and `f64` methods to libstd, but left these three behind specifically. (And unfortunately doesn’t discuss why.)

Maybe it’s fine to move them back in libcore? (As inherent methods, assuming #49896 lands.)

CC @alexcrichton
Repository: neovim
Issue: While recording a macro, no pause is given to see result of command
Labels: enhancement,ux

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: v0.3.0-1056-ga1530ec
- Vim (version: 7.4) behaves differently? no
- Operating system/version: Linux/WSL
- Terminal name/version: conhost/1803
- `$TERM`: xterm-256color N/A

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
q
:echo "foo"
```

### Actual behaviour
status line reads `recording @q`

### Expected behaviour
status line should temporarily display `foo` before reverting to `recording @q`
Repository: vscode
Issue: end keyword matching for Ruby, Lua, Julia, Elixir, Crystal and others
Labels: feature-request,languages-basic,editor-bracket-matching

<!-- Do you have a question? Please ask it on https://stackoverflow.com/questions/tagged/vscode. -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.22.0
- OS Version: Manjaro Linux 17.1.8

Steps to Reproduce:

1. Open a Ruby `.rb` file
2. Try to match `end` keywords

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

Hi community!

I'm happy user of Vim and VSCode :smile:

On Vim I can match Ruby, Lua, Julia, Elixir, Crystal `end` keywords using matchit.

By example, the following code is for Crystal on Vim:

![crystal](https://user-images.githubusercontent.com/3067335/29022601-a35ac1f2-7b2f-11e7-9067-fd6b626068ed.gif)

Would be nice to have something similar on VSCode.
Repository: pytorch
Issue: [caffe2] global average pool in caffe2
Labels: caffe2

- Caffe2:
- from source
- Python version:2.7
- CUDA/cuDNN version:cuda 8.0/cudnn 6
- GPU models and configuration:1070


How can achieve the global average pool in caffe2
Repository: puppeteer
Issue: Serialize Uint8Arrays better
Labels: feature,good first issue,chromium

### Steps to reproduce

**Tell us about your environment:**

* Puppeteer version: 1.3.0
* Platform / OS version: macOS Sierra
* URLs (if applicable): ...
* Node.js version: master

**What steps will reproduce the problem?**

_Please include code that reproduces the issue._

1. Open a new page with puppeteer
2. Run `page.evaluate(() => new Uint8Array(1024 * 1024 * 10)`

**What is the expected result?**

Puppeteer takes over 20 seconds to serialize/deserialize 10MB and the resulting object is not a Uint8Array. 

**What happens instead?**

A Uint8Array should be returned and it should take a reasonable amount of time (single-digit miliseconds tops and not seconds).

----

This basically would require inspecting objects returned from `evaluate`, detecting they're Uint8Arrays and then serializing them differently.
Repository: godot
Issue: [Bullet] Bullet Physics HingeJoint motor stops and restarts spinning every 360°
Labels: bug,confirmed,topic:physics,topic:3d


**Godot version:**
Godot 3.0.2 official

**OS/device including version:**
macOS Sierra 10.12.6


**Issue description:**
Using HingeJoint and activating motor it stops and restarts spinning every 360°.
This happens only using default physics engine settings (Bullet).
Switching to Godot physic engine the motor spins regurarly.


**Steps to reproduce:**
Create a simple 3D scene and add a camera.
Add a StaticBody and a RigidBody with its own MeshInstance and CollisionShape using a cube as mesh.
Add a HingeJoint and in its nodes properties set the StaticBody (Node A) and the RigidBody (Node B).
In the HingeJoint properties enable the motor and run the project.

I made also a video, see the second half.
https://youtu.be/htBEKQu8Iy4


**Minimal reproduction project:**
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
[HingeJoint_issue.zip](https://github.com/godotengine/godot/files/1935516/HingeJoint_issue.zip)
Repository: pytorch
Issue: Jetson TX1 Caffe2 installation fails on latest JetPack release
Labels: caffe2

PyTorch GitHub Issues Guidelines
--------------------------------

Using the Latest Jetpack 3.2 on a Jetson TX1 and a completely fresh OS setup, Caffe2 installation fails. 

Steps: 
 
git clone --recursive https://github.com/pytorch/pytorch.git
cd pytorch
git submodule update --init
cd scripts
./build_tegra_x1.sh 

Error message: 

```
[ 79%] Linking CXX executable ../bin/operator_fallback_gpu_test
../lib/libcaffe2_gpu.so: undefined reference to `void caffe2::math::BiasCHW<float, caffe2::CUDAContext>(float const*, int, int, float*, caffe2::CUDAContext*)'
collect2: error: ld returned 1 exit status
caffe2/CMakeFiles/elementwise_op_gpu_test.dir/build.make:115: recipe for target 'bin/elementwise_op_gpu_test' failed
make[2]: *** [bin/elementwise_op_gpu_test] Error 1
CMakeFiles/Makefile2:1614: recipe for target 'caffe2/CMakeFiles/elementwise_op_gpu_test.dir/all' failed
make[1]: *** [caffe2/CMakeFiles/elementwise_op_gpu_test.dir/all] Error 2
[ 79%] Building CXX object caffe2/CMakeFiles/caffe2_pybind11_state_gpu.dir/python/pybind_state_mkl.cc.o
../lib/libcaffe2_gpu.so: undefined reference to `void caffe2::math::BiasCHW<float, caffe2::CUDAContext>(float const*, int, int, float*, caffe2::CUDAContext*)'
collect2: error: ld returned 1 exit status
caffe2/CMakeFiles/operator_fallback_gpu_test.dir/build.make:115: recipe for target 'bin/operator_fallback_gpu_test' failed
make[2]: *** [bin/operator_fallback_gpu_test] Error 1
CMakeFiles/Makefile2:1570: recipe for target 'caffe2/CMakeFiles/operator_fallback_gpu_test.dir/all' failed
make[1]: *** [caffe2/CMakeFiles/operator_fallback_gpu_test.dir/all] Error 2
[ 80%] Building CXX object caffe2/CMakeFiles/caffe2_pybind11_state_gpu.dir/python/pybind_state_gpu.cc.o
[ 80%] Linking CXX shared module python/caffe2_pybind11_state_gpu.so
[ 80%] Built target caffe2_pybind11_state_gpu
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
```

Can someone give me a hint on how to get things running?
Repository: flutter
Issue: Fill remaining space between slivers with sliver
Labels: c: new feature,framework,f: scrolling,customer: crowd,P3,team-framework,triaged-framework

Is there a sliver to fill the remaining space between slivers? I'm having a lot of trouble trying to find something that works in Flutter for this.

Here is an example of two `ListView` slivers. I'm looking for a sliver to push down the second sliver to the bottom of the screen.

![bitmap](https://user-images.githubusercontent.com/36620537/39094757-2def8d0c-4678-11e8-8ce8-5b68cd714894.png)


`SliverFillRemaining` (which fills up the empty space if it's available) nearly does this but "there is never any room for anything beyond this sliver" so you can't display the second `ListView` sliver.

Also, you can't measure the `ListView` at run time so you can't just create your own Sliver that calculates the height of the remaining space - height of the second `ListView`.

```
class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    final outer = new SliverList(
        delegate:
            new SliverChildListDelegate(new List<Text>.generate(20, (int i) {
      return new Text("List 1 - Item $i");
    })));

    final inner = new SliverList(
        delegate:
            new SliverChildListDelegate(new List<Text>.generate(3, (int i) {
      return new Text("List 2 - Item $i");
    })));

    return new Scaffold(
      body: new CustomScrollView(
        slivers: <Widget>[outer, inner],
      ),
    );
  }
}
```