sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: preserveWhitespaces:false is too aggresive and not context aware
Labels: feature,area: core,core: basic template syntax,feature: under consideration

<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.

ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->

## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>

## Current behavior
The following snippet should generate "Text1 Text2" but it generates "Text1Text2" when preserveWhitespaces is false.

```
<!-- Original -->
<span>Text1</span>
<span>Text2</span>

<!-- After preserveWhitespace:false -->
<span>Text1</span><span>Text2</span>
```

## Expected behavior
`preserveWhitespaces` should be smarter, perhaps it could be like an enum where I could provide what behavior do I want, something like this (assuming the setting is renamed to `spaceCollapsing`:
* `preserve` - Behaves like `preserveWhitespaces:true` currently does, i.e. leaves things as is
* `remove` - Behaves like `preserveWhitespaces:false` currently does, i.e. removes all spaces
* `collapse` - whitespace is reduced to either a single space or a single newline depending on whether the original spaces contained a newline
* `normalize` - whitespace is reduced to a single space

```
<!-- Original -->
<span>Text1</span>
<span>Text2</span>

<!-- After preserveWhitespace:false -->
<span>Text1</span> <span>Text2</span>
```

## Minimal reproduction of the problem with instructions
https://angular-plbqm5.stackblitz.io
Notice `feugiat.Learn More!` when setting `preserveWhitespaces:false`, there is a lack of space and things look incorrect.

## What is the motivation / use case for changing the behavior?
It causes unexpected behaviors that are hard to notice.
Repository: flutter
Issue: State object's dartdoc can use a lifecycle diagram
Labels: c: new feature,framework,d: api docs,a: quality,c: proposal,P3,team-framework,triaged-framework

Maybe something like 

![image](https://user-images.githubusercontent.com/156888/34059154-a14256d6-e192-11e7-827f-53766eabb427.png)
Repository: material-ui
Issue: [Grid] CSS grid support
Labels: new feature,waiting for 👍,component: Grid

CSS-Grid is now newer and better grid system than flexbox, but they can be used together. Please see the link:
https://css-tricks.com/snippets/css/complete-guide-grid/
And it's now supported by most browsers, and it's matter of time it will become the standard way of defining the grid layout.
Would Material UI implement CSS Grid as well for incoming updates?

### Problems it could solve

- Remove the need for negative paddings.
- Works better for page layouts when the HTML is streamed in chunks which creates layout shifts

### Benchmark

- https://getbootstrap.com/docs/5.2/layout/css-grid/
- https://styled-css-grid.js.org/ 
- https://github.com/twbs/bootstrap/pull/31813 and the [preview](https://deploy-preview-31813--twbs-bootstrap.netlify.app/docs/5.0/layout/css-grid/).
- https://primer.style/components/Grid
- https://orbit.kiwi/components/grid/react/
- https://twitter.com/jxnblk/status/1192475197963677698
- https://rsms.me/raster/, the [announcement](https://twitter.com/rsms/status/1096926590972289025)
- Do we even need a component for it? https://twitter.com/kyehohenberger/status/1138159733767098368
- https://trello.com/c/xHKY1cHg/1345-grid-css-grid
Repository: opencv
Issue: Fixing broken cv2.VideoCapture by adding whitelist options for ffmpeg
Labels: priority: low,category: videoio

A change to ffmpeg that results in things like 'crypto' not being in the default whitelist. As a consequence, cv2.videocapture('XXX.sdp') often fails (for example, for parrot bebop drones). The solution would be to add optional whitelist parameters to cv2.videocapture; is this something someone could do?

For example, the following command successfully plays the stream from the prompt: "ffplay bebop.sdp -protocol_whitelist file,udp,rtp -fflags nobuffer"

but the stream does not get captured by opencv

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->

- OpenCV => :grey_question:
- Operating System / Platform => :grey_question:
- Compiler => :grey_question:

##### Detailed description

<!-- your description -->

##### Steps to reproduce

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->
Repository: vue
Issue: Date Fields appear empty on first load when initialized with Vue
Labels: browser quirks

### Version
2.5.11

### Reproduction link
[https://jsfiddle.net/u1wssnwL/3/](https://jsfiddle.net/u1wssnwL/3/)

### Steps to reproduce
Create an input with a type date and initialize with any valid date value. 

View on Safari IOS and you'll see that it will appear as empty although the value is set because when you click the field, you'll see that the IOS datepicker will be set to the value you provided.

It only affects date inputs that have been initialized with Vue and in the JSFiddle provided, there are 2 date inputs for easier reproduction

### What is expected?
Both date inputs should have the same value

### What is actually happening?
The date input that was initialized with Vue appears empty

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: go
Issue: compress/flate: decompression performance
Labels: Performance,help wanted

### What version of Go are you using (`go version`)?
```
go version go1.9.2 linux/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/fabecassis/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build767750319=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
```

### What did you do?
I noticed that the performance of `"compress/gzip"` is close to 2x slower than the `gunzip(1)` command-line tool. I've tested multiple methods of performing the decompression in this simple repository:
https://github.com/flx42/go-gunzip-bench
In summary, on a `333 MB` gzipped file, for the read-decompress-write process:
- The idiomatic go implementation takes 7.8s.
- Piping to `gunzip(1)` takes 4.4s. 
- Using [cgzip](https://github.com/youtube/vitess/tree/master/go/cgzip), a cgo wrapper on top on zlib, it takes 3.4s

Is there any room for improvement here for the standard implementation? The use case is decompression of downloaded Docker layers, in golang.
Repository: godot
Issue: 3D handles get smaller when MSAA 16x is enabled (`3.x` only)
Labels: bug,topic:rendering,confirmed,topic:3d

**Operating system or device, Godot version, GPU Model and driver (if graphics related):**
master bca97e33cefdf2687ea766fd9bd7032aa98cd0e8, Linux 64, Nvidia prorietary divers 387.34

**Issue description:**
<!-- What happened, and what was expected. -->
Enabling MSAA 16x makes the editor 3D handles very tiny, it only happens when the level is 16


MSAA 16x
![screenshot from 2017-12-16 00-29-17](https://user-images.githubusercontent.com/1103897/34067943-6c0e82da-e1f8-11e7-9e83-981b9355f6a8.png)

not MSAA 16x
![screenshot from 2017-12-16 00-29-02](https://user-images.githubusercontent.com/1103897/34067940-68bb80ba-e1f8-11e7-87b2-35bdb1f5046f.png)



**Steps to reproduce:**


**Link to minimal example project:**
<!-- Optional but very welcome. You can drag and drop a zip archive to upload it. -->
Repository: vscode
Issue: [folding] configure initial collapse state
Labels: feature-request,editor-folding

Maybe I missed something ... I recently migrated my javascript project from netbeans to visual studio code ... in netbeans we use 
```
//<editor-fold defaultstate="collapsed" desc="MySection">
...
//</editor-fold>
```
for defining regions ... I saw I could modify javascript-language-configuration.json to
```
	"folding": {
		"markers": {
			"start": "^\\s*//\\s*(?:(?:#?region\\b)|(?:<editor-fold\\b))",
			"end": "^\\s*//\\s*(?:(?:#?endregion\\b)|(?:</editor-fold>))"
		}
	}
```
SO my request includes 2 questions : 
1. Is it possible to add the editor fold tag to the javascript language configuration (Identical as the configuration for java)
2. Could a defaultstate be added to regions, so when a file is opened regions will be either collapsed or expanded
Repository: opencv
Issue: HEAD build fails with cuda 9.1, VS15.5.2, W10 16299
Labels: priority: low,category: build/install,category: gpu/cuda (contrib)

##### Summary
HEAD (16.12.2017) Build fails with:
 nvcc error : 'cicc' died with status 0xC0000005 (ACCESS_VIOLATION) [I:\opencv-master\build\modules\core\opencv_core.vcxproj]

##### System information (version)

- OpenCV HEAD (16 december 2017) | 3.4RC
- Windows 10 enterprise 64bits 1709 (build 16299)
- VS2017 15.5.2
- Windows SDK 1709 (build 16299)
- Cuda 9.1
- compiler MSVC / 14.12.25827

##### Detailed description

OpenCV build fails at opencv_core, in a such manner:

[output[opencv_core]fails.txt](https://github.com/opencv/opencv/files/1564840/output.opencv_core.fails.txt)

##### Steps to reproduce

I use this bash / powershell script:

$src = "I:/opencv-master/opencv"
$build = "I:/opencv-master/build"
$target = "Visual Studio 15 2017 Win64"
$ipsxe = "I:\IntelSWTools\compilers_and_libraries\windows\bin\ipsxe-comp-vars.bat"
$env:Path += ";C:\Program Files\CMake\bin"
$env:CUDA_PATH = "I:\Nvidia\Cuda\9.1"
$env:GSTREAMER_DIR = "I:/gstreamer/1.0/x86_64/"

#cd I:/opencv-master/
#bash update.sh (`cd opencv && git pull && cd ../opencv_contrib && git pull`)
cd $build
#iex "$ipsxe intel64 vs2017"

rm -r CMake*
cmake -G $target '
    -DBUILD_JAVA=false -DWITH_MATLAB=false -DBUILD_DOC=false -DBUILD_PERF_TESTS=false -DBUILD_TESTS=false '
    -DOPENCV_ENABLE_NONFREE=true -DBUILD_opencv-apps=false -DENABLE_PYLINT=false -DENABLE_CXX11=true '
    -DCUDA_SDK_ROOT_DIR="$env:CUDA_PATH" -DCUDA_ARCH_BIN="5.2" -DCUDA_VERBOSE_BUILD=true '
    -DWITH_OPENCL=true '
    -DCUDA_HOST_COMPILER="C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/Tools/MSVC/14.12.25827/bin/Hostx86/x64/cl.exe" '
    ..\opencv

msbuild.exe OpenCV.sln /verbosity:m /m
#msbuild.exe OpenCV.sln /p:Configuration=Release /verbosity:m /m

##### Comments

Single quotes ending lines in the scripts should be replaced by backquotes / backticks (I used single quote to match Markdown formatting).

I'm available to investigate.
Repository: vue
Issue: Is Vue performing unnecessary re-render when using $listeners?
Labels: improvement

### Version
2.5.11 (and earlier versions)

### Reproduction link
[https://jsfiddle.net/xb4172g8/](https://jsfiddle.net/xb4172g8/)

### Steps to reproduce
1. Open console and observe while typing something into input fields
2. Enter some text into name field -> Vue re-renders all three Textfield components
3. In line 21 replace `{ ...this.$listeners }` with an empty object
4. Once again enter some text into any field -> Vue re-renders only updated Textfield 

### What is expected?
Vue should re-render only the component whose props has changed.

### What is actually happening?
Using `$listeners` in component's render function causes the component to be rendered whenever its parent is updated even though his props hasn't changed.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue: ExpandIcon should use ThemeData instead of Color mapping
Labels: framework,f: material design,c: proposal,P2,team-design,triaged-design

Currently, the `ExpandIcon` is hardcoded to a specific black-value from the `Colors` mapping. As `cardColor` can already be defined in `ThemeData`, it would only make sense to allow the `ExpandIcon` to have its color defined in `ThemeData` too as darker background colors can otherwise conflict in user interface design.

https://github.com/flutter/flutter/blob/e85d099229283989839422ec1e4cef8fdc2af624/packages/flutter/lib/src/material/expand_icon.dart#L105
Repository: go
Issue: cmd/vendor/golang.org/x/arch/arm: several issues in ARM disassembler's plan9 syntax
Labels: NeedsFix

Though the ARM disassembler can decode most instruction binaries into gnu syntax correctly, there are several issues in plan9 syntax decoding.

1. op name
15f715e7|		1	plan9	SDIV R7, R5, R5
It should be "DIV R7, R5, R5", and many others are also incorrect.
MLA should be MULA
UDIV should be DIVU
......

2. LDM/STM
ed003be9|	1	plan9	LDMDB [R0,R2-R3,R5-R7], R11!
2.1 their op name should be MOVM
2.2 () should be used instead of []
2.3 The DB/IA/DA/IB suffixes should be decoded to .W/.P suffixes

3. SWP/SWPB
939007e1|	1	plan9	SWP [R7], R3, R9
3.1. () should be used instead of []
3.2 The parameter order is incorrect

4. VMRS/VMSR
109ae1ee|		1	plan9	VMSR R9, FPSCR
The op name is incorrect

5. FP instructions
5.1 op name: VADD.F32->ADDF, VSUB.F64->SUBD, ......
5.2 register name: S2->F1, S4->F2, ...
5.3 vcvt has incorrect form
5.4 vmov has incorrect form

6. XTB/XTH/XTBU/XTHU should be MOVB/MOVH

7. STREX/LDREX has incorrect parameter order

8. XTAB/XTAH/XTABU/XTAHU has incorrect form
Repository: rust
Issue: Issues with crash handling for iOS for Rust 1.22.1
Labels: A-debuginfo,C-enhancement,O-ios,T-compiler

I'm using `rustc 1.22.1 (05e2e1c41 2017-11-22)` and I'm calling a simple rust function from my iOS app that just panics. The rust function is in a static library and is compiled `cargo build` (debug with -O0). The architecture is aarch64-apple-ios. Here's the rust code:
```
extern crate rand;

pub struct MyStruct {
    i: i32,
}

impl MyStruct {
    pub fn do_stuff(&mut self) -> String {
        panic!("that was a fail");
        return String::from("asdf");
    }
}

#[no_mangle]
pub extern fn panicky_fn() {
    let mut m = MyStruct {
        i: 0
    };
    m.do_stuff();
}
```

When I call it like this, from my root view controller:
```
- (void)viewDidLoad
{
    [super viewDidLoad];
    [Fabric with:@[ [Crashlytics class]]]; // start the crash reporter
    CFTimeInterval start = CACurrentMediaTime();
    srand(time(NULL));
    if (rand() % 2 == 0) {
        panicky_fn();
    }
    // more code...
}
```
Then when the panic occurs, in the left-hand pane of Xcode, it just shows me this generic trace:
```
#0	0x00000001838e9348 in __pthread_kill ()
#1	0x00000001839fd354 in pthread_kill$VARIANT$mp ()
#2	0x0000000183858fd8 in abort ()
#3	0x00000001832bc068 in abort_message ()
#4	0x00000001832bc16c in default_terminate_handler() ()
#5	0x00000001832d454c in std::__terminate(void (*)()) ()
#6	0x00000001832d45c0 in std::terminate() ()
#7	0x00000001832e476c in objc_terminate ()
#8	0x0000000104651470 in _dispatch_client_callout ()
#9	0x000000010465db74 in _dispatch_block_invoke_direct ()
#10	0x00000001864a5a04 in __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ ()
#11	0x00000001864a56a8 in -[FBSSerialQueue _performNext] ()
#12	0x00000001864a5c44 in -[FBSSerialQueue _performNextFromRunLoopSource] ()
#13	0x0000000183d78358 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ ()
#14	0x0000000183d782d8 in __CFRunLoopDoSource0 ()
#15	0x0000000183d77b60 in __CFRunLoopDoSources0 ()
#16	0x0000000183d75738 in __CFRunLoopRun ()
#17	0x0000000183c962d8 in CFRunLoopRunSpecific ()
#18	0x0000000185b27f84 in GSEventRunModal ()
#19	0x000000018d243880 in UIApplicationMain ()
#20	0x0000000104219b68 in main at /Users/michael/Snapchat/Dev/Rotationization/Rotationization/main.m:15
#21	0x00000001837ba56c in start ()
```
And in the crash reporting service, Crashlytics, I just see a stack trace just like it. *However*, when I wrap the call to the rust function like so:
```
dispatch_async(dispatch_get_main_queue(), ^{
    panicky_fn();
}
```
Then both the left-hand pane of Xcode as well as the crash reporting service show the correct stack trace. Can anyone help with this? I want to start using Rust in my app, but I don't feel comfortable doing so until I can monitor crashes with it.
Repository: kubernetes
Issue: Make CrashLoopBackoff timing tuneable, or add mechanism to exempt some exits
Labels: sig/node,kind/feature,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/).
-->

**Is this a BUG REPORT or FEATURE REQUEST?**: Feature request

/kind feature

**What happened**:
As part of a development workflow, I intentionally killed a container in a pod with `restartPolicy: Always`. The plan was to do this repeatedly, as a quick way to restart the container and clear old state (and, in Minikube, to load image changes).
The container went into a crash-loop backoff, making this anything but a quick option.

**What you expected to happen**: 
I expected there so be some configuration allowing me to disable, or at least tune the timing of, the CrashLoopBackoff.

**How to reproduce it (as minimally and precisely as possible)**:
Create a pod with `restartPolicy: Always`, and intentionally exit a container repeatedly.

**Anything else we need to know?**:
I see that the backoff timing parameters are hard-coded constants here:
https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L121
https://github.com/kubernetes/kubernetes/blob/5f920426103085a28069a1ba3ec9b5301c19d075/pkg/kubelet/kubelet.go#L155

One might reasonably expect these to be configurable at least at the kubelet level - say, by a setting like [these](https://github.com/kubernetes/kubernetes/blob/6b03a43b761a8b6f9eac3648cf499f157f161414/pkg/kubelet/apis/kubeletconfig/v1alpha1/types.go#L47). That would be sufficient for my use-case (local development with fast restarts), and presumably useful as an advanced configuration setting for production workloads.

A more aggressive change would allow tuning per-pod.

There are other options for my target workflow:

* Put the pod in a Deployment or similar, kubectl delete the pod, let Kubernetes schedule another, work with the new pod. However, this is much slower than a container restart without backoff (and ironically causes more kubelet load than the backoff avoids). It also relies on using kubectl/the Kubernetes API to do the restart, as opposed to just exiting the container.
* Run the server process as a secondary process in the container rather than the primary process. This means the server can be started/stopped without container backoff, but is trickier to implement  and doesn't offer the same isolation guarantees as exiting the container and starting fresh. It also means I probably can't use the same image I deploy to production (because I probably don't want this extra restart-support stuff floating around in the production image).

**Environment**:
- Kubernetes version (use `kubectl version`): v1.8.0
- Cloud provider or hardware configuration: Minikube 0.23.0 with Virtualbox driver on OSX
Repository: react
Issue: Number input gets cleared when typing period as decimal mark
Labels: Type: Bug,Component: DOM

<!--
  Note: if the issue is about documentation or the website, please file it at:
  https://github.com/reactjs/reactjs.org/issues/new
-->

**Do you want to request a *feature* or report a *bug*?**

Bug

**What is the current behavior?**

My OS and browser are configured to a locale that uses comma as the decimal mark (Finland for those interested). In the codepen below when I accidentally type a period after some number the whole input gets cleared. This is somehow related to the parent component's state being updated because if the `defaultValue` prop is removed from the `<Input>` component the input doesn't get cleared.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template for React 16: https://jsfiddle.net/Luktwrdm/, template for React 15: https://jsfiddle.net/hmbg7e9w/).**

https://codepen.io/anon/pen/aEOgNL?editors=0010

**What is the expected behavior?**

The input should retain its visible value even if it would be invalid (can't be converted to a number).

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**

React 16.2.0 and Chrome 63 on macOS 10.12.6.

Tested in Safari 11.0.2 and typing a period kinda works. After typing the first number after the period it gets converted to a comma but the cursor jumps to the beginning.

Also tested in Firefox 57.0.1 but it seems to think that period is the correct decimal mark.
Repository: rust
Issue: Confusing error message: the trait `std::convert::Into` cannot be made into an object
Labels: C-enhancement,A-diagnostics,P-low,T-compiler,D-verbose,A-trait-objects

I've tried to make a function which will make a new thread, accepting either an `&str` or a `String` for the new thread's name:

```rust
/// Test helper to spawn a named thread.
///
/// The thread executes the work in the `f` closure.
#[cfg(test)]
fn named_thread<'s, F>(name: Into<String>, f: F) -> JoinHandle<()>
               where F: FnOnce(), F: Send + 'static {
    let thr = thread::Builder::new()
                              .name(String::from(name))
                              .spawn(f)
                              .unwrap();
    thr
}
```

This gives:
```
error[E0038]: the trait `std::convert::Into` cannot be made into an object
   --> src/lib.rs:377:1
    |
377 | / fn named_thread<'s, F>(name: Into<String>, f: F) -> JoinHandle<()>
378 | |                where F: FnOnce(), F: Send + 'static {
379 | |     let name = name.into();
380 | |     let thr = thread::Builder::new()
...   |
384 | |     thr
385 | | }
    | |_^ the trait `std::convert::Into` cannot be made into an object
    |
    = note: the trait cannot require that `Self : Sized`
```

Which, from a user POV, is confusing on a few levels:

 * I don't have any mention of `Sized` in my code (must be implicit).
 * Who is `Self` here?
 * Even if I knew where `Sized` came from, and who `Self` was, the error message doesn't tell me what I did wrong.

I'd be interested to know what I did wrong, even if the error message can't be improved.

Thanks