sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vue
Issue: vdom: warn innerHTML not watch when the string have some escaped chars
Labels: improvement

### Version
2.5.17-beta.0

### Reproduction link
[https://codepen.io/cxtom/pen/XYKgde](https://codepen.io/cxtom/pen/XYKgde)

### Steps to reproduce
1. using v-html and the string has \&quot; \&#39;
2. ssr
3. warn not match during hybrating in browser

### What is expected?
not warn The client-side rendered virtual DOM tree is not matching server-rendered content

### What is actually happening?
warn The client-side rendered virtual DOM tree is not matching server-rendered content.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: pytorch
Issue: error when import caffe2.python.onnx.backend
Labels: caffe2

when i transform onnx to caffe2, i meet this problem <_>

import caffe2.python.onnx.backend
Segmentation fault (core dumped)

can someone help me, thank you very very much
Repository: rust
Issue: aobench hangs when compiled with -C target-cpu=native
Labels: O-macos,I-hang

I've ported ISPC ambient occlusion benchmark to use `std::simd` portable vector types here: https://github.com/gnzlbg/aobench

Running the binary with

```
cargo run --release -- 800 600 --algo vector
```

works fine. However, using:

```
RUSTFLAGS="-C target-cpu=native" cargo run --release -- 800 600 --algo vector
```

the binary hangs in `std::sys::unix::stack_overflow::imp::signal_handler::ha55d20b1873e8199`:

![screen shot 2018-06-06 at 11 43 36](https://user-images.githubusercontent.com/904614/41030596-f49dc68e-697e-11e8-8e71-3f44aaa3909e.png)

This happens on a MacBook Air (13-inch, Mid 2012) with a 1.8 GHz Intel Core i5. The following fails to compile

```
RUSTFLAGS="-C target-cpu=hawell" cargo run --release -- 800 600 --algo vector
```

and the following

```
RUSTFLAGS="-C target-cpu=help" cargo run --release -- 800 600 --algo vector
```

fails to compile with: 

```
error: malformed cfg value or key/value pair: `Available CPUs for this target:`
```
(no cpus listed)
Repository: flutter
Issue: Android release build not working with disabled signing
Labels: c: new feature,tool,t: gradle,P2,team-tool,triaged-tool

Hi,

We want to disable the signing of the APK because we sign it on the build server.
Therefore we changed the build.gradle (from module app) to
```groovy
release {
            signingConfig null
}
```

So far this works and the gradle build produces an unsigned APK. This APK is named _app-release-unsigned.apk_.
And this name is the problem, the flutter build exits then with the message

> Gradle build failed to produce an Android package

As far as we see, this is because the flutter build checks if an APK named _app-release.apk_ is created.

Our workaround is now to have the following build.gradle:
```groovy
release {
            signingConfig null

            applicationVariants.all { variant ->
                variant.outputs.all { output ->
                    output.outputFileName = "app-release.apk"
                }
            }
}
```

Would be great when the android build could offer the possibility to produce an unsigned APK. For iOS this is already possible with the flag _--no-codesign_.

Regards,
Florian
Repository: go
Issue: encoding/xml: add support for xml version 1.1
Labels: NeedsInvestigation,FeatureRequest



### What version of Go are you using (`go version`)?
go 1.10.2

### Does this issue reproduce with the latest release?
n/a

### What operating system and processor architecture are you using (`go env`)?
GOHOSTARCH="amd64"
GOHOSTOS="darwin"


There are any plans to add support for XML version 1.1 in the "encoding/xml" lib?



thanks!
Repository: rust
Issue: Custom (synonym) suggestions for nonexistent methods
Labels: C-enhancement,A-diagnostics,T-compiler

Currently if the user types a method that does not exist, a suggestion may be provided if what was typed is reasonably close to an existing method.
```rust
let set = ::std::collections::HashSet::new();
set.insrt(0u8); // = help: did you mean `insert`?
```
However, this only catches typos — completely different names aren't considered "close". I think it'd be helpful, especially for people coming from other languages (or switching between them frequently) to be able to specify custom suggestions for potential alternate names, so that something like the following works:
```rust
let set = ::std::collections::HashSet::new();
set.add(0u8); // = help: did you mean `insert`?
set.push(0u8); // = help: did you mean `insert`?
// etc.
```
Repository: kubernetes
Issue: Validation Tightening is not Generally Possible
Labels: kind/bug,sig/api-machinery,priority/important-longterm,lifecycle/frozen,wg/api-expression

I have made this comment on a few PRs so maybe it's time to document and/or build a mechanism.

You cannot generally make validation tighter, because any existing objects that violate the new rule will not be able to be updated, and in many cases, deleted (because deletions involving finalizers require a sequence of updates).

This is because, to validate updates, we validate BOTH the transition, AND the final state of the object. It's this last part that is problematic.

It should be possible to address this by adding a new class of validation function that ONLY gets called on new objects, but then we have these problems:
* When is it safe to promote the logic into the main validation function? There's no way to know.
* This solves the problem for apiserver, but not for any clients that were sending invalid objects. Especially automated clients will suddenly and without recourse be quite broken.

Even at version boundaries it's hard to tighten validation, since objects have to be round-trippable and there are still old objects in the system.

So, new API authors: start out with restrictive validation; it's easier to relax than to tighten.

Existing API authors: prepare to write defensive clients.

/kind bug
/sig api-machinery
Repository: react-native
Issue: Set polyfill says it is [object Object] but should say [object Set]
Labels: JavaScript,Priority: Low,Bug

## Environment

Any - you can reproduce the issue using only file

https://github.com/facebook/react-native/blob/master/Libraries/vendor/core/Set.js

and any Javascript encironment.

EDIT: Just for the bot, it is completely irrelevant:

Environment:
  OS: Windows 10
  Node: 10.3.0
  Yarn: Not Found
  npm: 6.1.0
  Watchman: Not Found
  Xcode: N/A
  Android Studio: Version  3.1.0.0 AI-173.4720617

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: 0.55.4 => 0.55.4

## Description and Steps to Reproduce

Here is code that creates a simple Set object and then uses the spread operator to spread the Set's contents into a new array.

First, using an environment where the above file was executed/loaded (plus its own dependencies), and I also short-circuited the detection at the beginning that determines whether the polyfill is applied:

```js
const s1 = new Set([1,2,3]);
console.log(Object.prototype.toString.call(s1));
```

Result:

```
[object Object]
```

## Expected Behavior

Now for comparison a clean ES6+ environment without anything loaded, so we get a native Set implementation:

```js
const s1 = new Set([1,2,3]);
console.log(Object.prototype.toString.call(s1));
```

Result:

```
[object Set]
```
Repository: go
Issue: net/http: provide some Transport knob (bool?) to keep max 1 TLS dial in flight at once when discovering http2 support
Labels: NeedsFix,FeatureRequest

Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
go version go1.10.2 darwin/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
Container Linux by CoreOS stable (1745.5.0)

### What did you do?
Attached NginX client replicates this issue. It requires some minimal reconfiguration for a test HTTP2 server. The client<->Nginx hop is HTTP2 and the NginX<->Service hop is HTTP1.1. This is a typical config. I've verified NginX is exposing an HTTP2 virtual server endpoint with the h2c utility.

Any HTTP2 client for an NginX HTTP2 reverse proxy should replicated this behavior. 
NginX sets http2_max_concurrent_streams to 128 by default so it should accept the 3 concurrent streams in this test.

I've also included an equivalent HTTP2 client for http2.golang.org. httptrace reports this client does one TLS handshake per request; however, all three requests use the same connection.

So, for some reason not visible via httptrace, the client is multiplexing requests to a Go HTTP2 server; but, is not multiplexing requests to an NginX HTTP2 reverse proxy.

### What did you expect to see?
I expected to see the go http client multiplex these concurrent HTTP2 requests on a single HTTP2 connection to the NginX HTTP2 reverse proxy.

I expected that only one TLS handshake would be done.

### What did you see instead?
Instead of multiplexing these requests on one NginX reverse proxy connection, the client sends each request on a separate connection. 

The duplicate TLS handshakes reported by httptrace for http2.golang.org don't make sense if all requests are using the same connection.

[nginx.conf.txt](https://github.com/golang/go/files/2077767/nginx.conf.txt)
[simSwitch.go.txt](https://github.com/golang/go/files/2077768/simSwitch.go.txt)
[http2client.go.txt](https://github.com/golang/go/files/2077769/http2client.go.txt)
[simSwitch-httptrace.txt](https://github.com/golang/go/files/2077770/simSwitch-httptrace.txt)
[http2client-httptrace.txt](https://github.com/golang/go/files/2077771/http2client-httptrace.txt)
Repository: svelte
Issue: SVG baseVal
Labels: feature request,perf,stale-bot,compiler,temp-stale

It turns out that this...

```js
rect.x.baseVal.value = 200;
```

...is faster than this:

```js
rect.setAttribute('x', 200);
```

This might be something we can use to our benefit.
Repository: rust
Issue: Method resolution for trait object types does not prefer inherent methods
Labels: A-trait-system,T-lang,C-bug,T-types,A-trait-objects

Normally, inherent methods are given precedence over all trait methods, so that there is no ambiguity.

However, this behavior does not appear to be implemented for trait object types:

```rust
trait Foo {
    fn f(&self) { }
}

impl Foo {
    fn f(&self) { }
}

impl Foo for i32 { }

struct Bar;

impl Bar {
    fn f(&self) { }
}

impl Foo for Bar { }

fn main() {
    let x: &Foo = &42i32;
    x.f();
    let bar: &Bar = &Bar;
    bar.f();
}
```

https://play.rust-lang.org/?gist=7d4534a5d973249c66244b9affa03199&version=stable&mode=debug

What's worse, UFCS does not allow for specifying that you want the inherent method, because `Foo::f(x)` in this code will remain ambiguous. In general, UFCS isn't designed to support disambiguating to inherent methods because inherent methods are supposed to always take precedence.
Repository: rust
Issue: Great stack overflow error messages
Labels: A-debuginfo,T-libs

As a coder 
Given I have a fn main() { main() }
Then I expect the following output:

```
Exception in thread "main" java.lang.StackOverflowError
	at X.main(X.java:3)
	at X.main(X.java:3)
	at X.main(X.java:3)
	at X.main(X.java:3)
```

Obviously this is an example of how Java handles stack overflows, but you get the idea.

There didn't seem to be a tracking issue for this, so here is one. 
(Some discussion here: https://users.rust-lang.org/t/how-to-diagnose-a-stack-overflow-issues-cause/17320/9 )

I've had a little look and I naively think we need to do something like this in sys_common/util.rs

```
    #[allow(dead_code)] // stack overflow detection not enabled on all platforms    
    pub unsafe fn report_overflow() {
        dumb_print(format_args!("\nthread '{}' has overflowed its stack\n",
                            thread::current().name().unwrap_or("<unknown>")));

        #[cfg(feature = "backtrace")]
        {
            let log_backtrace = backtrace::log_enabled();

            use sync::atomic::{AtomicBool, Ordering};

            static FIRST_PANIC: AtomicBool = AtomicBool::new(true);

            if let Some(format) = log_backtrace {
                if let Ok(mut stderr) = Stderr::new() {
                    let _ = backtrace::print(&mut stderr, format);
                }
            } else if FIRST_PANIC.compare_and_swap(true, false, Ordering::SeqCst) {
                dumb_print(format_args!("note: Run with `RUST_BACKTRACE=1` for a backtrace."));
            }
        }
    }
```

Quite possibly one can ditch the first panic checks. I'm sure there's lots of concerns here, e.g. have we got enough stack headroom to report without going pop.
Repository: react
Issue: Consider removing Mobile Safari empty onclick hack
Labels: Component: DOM,Type: Needs Investigation,React Core Team

See https://github.com/facebook/react/issues/238 and https://github.com/facebook/react/pull/1536 for historical context.

Is that still relevant? The code is here:

https://github.com/facebook/react/blob/52fbe7612e0527b8c86decac519c344626f6bd72/packages/react-dom/src/client/ReactDOMFiberComponent.js#L244-L245

Even if it's relevant, can we just feature test it, and not do this hack on other browsers? Seems like a waste of memory for event handlers (even though the function is the same every time).
Repository: godot
Issue: gui events don't propagate to parent control nodes
Labels: bug,confirmed,topic:gui

**Godot version:** 3.0.2

**Issue description:**

From the docs, regarding event propagation:


"Second, it will try to feed the input to the GUI, and see if any control can receive it. If so, the Control will be called via the virtual function Control._gui_input() and the signal “input_event” will be emitted (this function is re-implementable by script by inheriting from it). If the control wants to “consume” the event, it will call Control.accept_event() and the event will not spread any more. **Events that are not consumed will propagate up, to Control’s ancestors.**"

from http://docs.godotengine.org/en/3.0/tutorials/inputs/inputevent.html?highlight=input%20events

I interpreted this to mean that if a Control subclass node does not handle the event, the parent of that node would then be able to accept that event through it's own `_gui_input` method.  However, that doesn't seem to be the case.  Only the control that has focus will get the `_gui_input` call.

Am I misunderstanding what that line means?
Repository: TypeScript
Issue: json files should be usable in .d.ts files without breaking things
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
resolveJsonModule import definition

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
As a .json file is a static resource, it should be able to be referenced in a global.d.ts file for example without that file being automatically treated as a module. The reason for this is that a .json file may be used to simply enforce valid translation keys, and you shouldn't need to suck the whole .json file into the transpilation process to do that.

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

Example:

```
import translations from "../assets/translations/en-AU.json"
type $translate = {
    instant: (translationKey: keyof typeof translations) => string,
    use: Function,
    proposedLanguage: Function
}
```

The downside of the current method again is that the translations file is output in the transpilation process, which is wasteful if the file is large.

What the above code snippet is trying to achieve, should be allowed in a .d.ts file without breaking global declaration functionality.

## 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. new expression-level syntax)
Repository: TypeScript
Issue: JSDoc comment for destructuring param: description text not displayed
Labels: Bug,Help Wanted,Domain: JSDoc

**TypeScript Version:**  
2.9

**Search Terms:**  
JSDoc destructuring param

**Code**
```javascript
/**
 * @param {Object} arg
 * @param {number} arg.id - This param description won't show up
 */
function foo({ id }) {}
```
**Expected behavior:**
In VSCode 1.24.0, when typing `foo(`, IntelliSense should display the full param description, including its type and text.

**Actual behavior:**
The type is displayed ("number"), but not the text ("This param description won't show up"):
![image](https://user-images.githubusercontent.com/7039479/41089435-1a345002-6a42-11e8-9564-955250f6eccc.png)

**Related Issues:**
https://github.com/Microsoft/TypeScript/issues/19645

**Additional remark**
When omitting the {Object} line, the param text shows up correctly:
![image](https://user-images.githubusercontent.com/7039479/41090000-7c75bcb4-6a43-11e8-960a-a735efcd0280.png)
Repository: rust
Issue: The run-pass/issue-36856.rs fails on beta for mips{el}-linux-gnu
Labels: O-MIPS,T-compiler

The test starts failing after revert in #50137. This issue is still present in FastISel which incorrectly sign extends i1 constants to I32 when selecting binary ops [link](https://github.com/llvm-mirror/llvm/blob/master/lib/CodeGen/SelectionDAG/FastISel.cpp#L621). I was able to trigger the issue reliably on mips32 https://godbolt.org/g/b3LBWo while other platforms seem to not use the FastISel consistently. For example for arm it needs to be forced https://godbolt.org/g/yWmPMu. Is it ok to revert the mentioned pull until the proper fix gets landed to LLVM repo @nox ?
Repository: opencv
Issue: imread  block resources when it can't read image
Labels: incomplete

<!--
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.2.0-1
- Operating System / Platform => Windows 64 Bit/CentOs 7
- Compiler => Intelij Idea 2018.1.4
-->

- OpenCV =>3.2.0-1
- Operating System / Platform =>  Windows 64 Bit/CentOs 7
- Compiler => Intelij Idea 2018.1.4



##### Detailed description
I use opencv library for Java 

    public void deskew(File imageFile) {
    	try (ExonarMetrics.MetricTimer timer = exonarMetrics.getMetricTimerForMetricName(ExonarMetrics.OPENCV_PROCESSING_TIME)) {
            Mat imageMat = Imgcodecs.imread(imageFile.getAbsolutePath(), Imgcodecs.CV_LOAD_IMAGE_GRAYSCALE); 


imread can't read attached image,it throws an exception (it's not a problem for my case)and block them, because of this  I can't delete this image because it's in use(it's a big problem for me). 

            double angle = computeSkewFromImageFile(imageFile);
            logger.debug("Computed angle: {}", angle);

            imageMat = rotate(imageMat, angle);
            Imgcodecs.imwrite(imageFile.getAbsolutePath(), imageMat);

        } catch (Exception e) {
            exception.createException(OcrExceptionHandler.OPENCV_EXCEPTION_TYPE, e.getMessage());
        }
    }

##### Steps to reproduce
Try to read this image , and without closing program try to delete this image
[tryIt.zip](https://github.com/opencv/opencv/files/2080423/tryIt.zip)

-->
Repository: pytorch
Issue: Different behavior of LSTM and LSTMCell implementation 
Labels: module: numerical-stability,module: rnn,triaged,module: numerical-reproducibility

## Issue description
I was testing the difference between LSTM and LSTMCell implementations, ideally for same input they should have same outputs, but the outputs are different, looks like something fishy is going on.

The numbers are different that's still okay, but the problem is I am getting very different performances(accuracy and other metrics, not O(t)) while testing these two models.
Can you please check the issue?

## Code example
import torch
from torch import nn
from torch.autograd import Variable
print torch.__version__
torch.manual_seed(666)
rnn = nn.LSTM(10, 20, 1)
input = Variable(torch.randn(5, 3, 10))
h0 = Variable(torch.zeros(1, 3, 20))
c0 = Variable(torch.zeros(1, 3, 20))
output, (hn, cn) = rnn(input, (h0, c0))

print ("From LSTM")
print hn[0]

rnncell = nn.LSTMCell(10, 20)
hx = Variable(torch.zeros(3, 20))
cx = Variable(torch.zeros(3, 20))
out = []
for i in range(5):
           hx, cx = rnncell(input[i], (hx, cx))
           out.append(hx)

print ("from LSTM Cell")
print hx
## System Info

- PyTorch or Caffe2: pytorch
- How you installed PyTorch (conda, pip, source): pip
- Build command you used (if compiling from source):
- OS: ubuntu
- PyTorch version: 0.3.1 
- Python version: 2.7.12
- CUDA/cuDNN version: NA
- GPU models and configuration: NA
- GCC version (if compiling from source):
- CMake version: NA
- Versions of any other relevant libraries:


cc @zou3519
Repository: go
Issue: database/sql: *Rows.Err() does not return errors from *Rows.Scan()
Labels: Documentation,NeedsInvestigation

I'm not really advocating for the behavior to change, but the usage of the word "iteration" in the current documentation of [`Rows.Err()`](https://golang.org/pkg/database/sql/#Rows.Err) is ambiguous with respect to the behavior of `*Rows.Scan()`.  More examples and/or more precise documentation would help.

### What version of Go are you using (`go version`)?

go version go1.10.2 linux/amd64

### Does this issue reproduce with the latest release?

Yes

### What did you do?

https://play.golang.org/p/1xbP8gEMNtb

### What did you expect to see?

(Given a certain reading of the `Rows.Err()` docs:)

```
2018/06/07 10:24:45 Error from Scan(...): sql: Scan error on column index 0: sql/driver: couldn't convert 42 into type bool
2018/06/07 10:24:45 Error from Err(): sql: Scan error on column index 0: sql/driver: couldn't convert 42 into type bool
```

### What did you see instead?

```
2018/06/07 10:24:45 Error from Scan(...): sql: Scan error on column index 0: sql/driver: couldn't convert 42 into type bool
2018/06/07 10:24:45 No error from Err()
```