sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: wasm test failures do not contain error messages
Labels: A-testsuite,O-wasm,C-bug

When our tests fail in bors on a wasm target, there is no error message except `RuntimeError: unreachable` ([example](https://dev.azure.com/rust-lang/rust/_build/results?buildId=2616)). There is nothing to print the panic message to the console.

I think this could be fixed by adding [console_error_panic_hook](https://github.com/rustwasm/console_error_panic_hook) as dependency somehow, but I'm not quite sure how to do this.

Here's an example project that sets up this dependency to run with a test: [async-fn-size](https://github.com/Mark-Simulacrum/async-fn-size). Thanks to @Mark-Simulacrum for figuring this out!
Repository: godot
Issue: KinematicBody does not collide with new position of a moved KinematicBody - can tunnel through
Labels: bug,confirmed,topic:physics

**Godot version:** 3.1.1

**OS/device including version:** Windows 8.1

**Issue description:**
If two kinematic bodies move toward each other using move_and_collide() in the same frame, they can intersect, or even tunnel through, since the collision does not seem to take into account the updated position of the KinematicBody that moved first.

![image](https://user-images.githubusercontent.com/7751182/60951075-5aaca900-a2c6-11e9-8e36-47c81f4418dc.png)


**Steps to reproduce:**
Put one kinematic body above the other with space in between.  Move the bottom kinematic body up toward the top body using move_and_collide().  In the same physics process frame, move the top body down below the new position of the bottom body.  Note that the top body can partially (or even completely, if the movement is large enough) pass through the bottom body without registering a collision.


**Minimal reproduction project:**
[test_broken_collision1.zip](https://github.com/godotengine/godot/files/3376344/test_broken_collision1.zip)
Repository: create-react-app
Issue: Missing documentation for process.env.CI
Labels: issue: proposal

The `npm run build` command is affected by the environment variable `CI`, but it is not well documented.

This is what the [existing documentation](https://facebook.github.io/create-react-app/docs/running-tests#continuous-integration) says about it:
> When creating a build of your application with npm run build linter warnings are not checked by default. Like npm test, you can force the build to perform a linter warning check by setting the environment variable CI. If any warnings are encountered then the build fails.

By looking at the source code or playing with the command, there are several side effects:
- Some errors are silenced:
https://github.com/facebook/create-react-app/blob/7b196fa4d6f4a98b93a460440adfef206e214652/test/fixtures/__shared__/util/setup.js#L105
- There is no color in the output anymore
- Another side effect [here](https://github.com/facebook/create-react-app/blob/7b196fa4d6f4a98b93a460440adfef206e214652/test/fixtures/__shared__/util/setup.js#L37)

I believe it would be a good choice to have no undocumented side effect.

---

Use cases where it is a problem:
- I want to master my CI pipeline: I can't just set an environment variable without knowing exactly what it does.
- I want to treat warnings as errors locally and the only option seems to be to set the `CI` option (this is a problem in intslef): I would also like to know what it does and keep the colors in the output.
- The usage of `npm build` don't talk about the envinroment variables, neither does `npm help build`, it is then confusing to see the behavior change between computers.
```
$ npm build -h  
npm build [<folder>]
```

Thank you for reading this.

Best,
Simon
Repository: ant-design
Issue: multiple TreeSelect onChange params different
Labels: 🗣 Discussion,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://codepen.io/Enivia-Q/pen/GbzpPG](https://codepen.io/Enivia-Q/pen/GbzpPG)

### Steps to reproduce
1. check tree nodes from drop-down list
2. delete checked items from input box
3. console.log(extra.allCheckedNodes)

### What is expected?
change from drop-down list and input box but getting different-type nodes list

### What is actually happening?
got same-type node list

| Environment | Info |
|---|---|
| antd | 3.20.1 |
| React | 16.8.6 |
| System | Windows |
| Browser | Chrome 75.0.3770.100 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: Addon-backgrounds: Add parameter to enable grid by default
Labels: feature request,good first issue,help wanted,has workaround,addon: backgrounds

**Is your feature request related to a problem? Please describe.**
No.

**Describe the solution you'd like**
I'd like a new [Options Parameter](https://storybook.js.org/docs/configurations/options-parameter/) to control the initial setting of the "Toggle Background Grid" setting, e.g. `showBackgroundGrid`, so that I can enable it by default.

**Describe alternatives you've considered**
According to https://github.com/storybookjs/storybook/issues/5853#issuecomment-475466382 it looks like it's possible to implement your own grid with the Storybook Background Addon.

**Are you able to assist bring the feature to reality?**
No.

**Additional context**
I think that should be enough info, but let me know if there's anything else I can provide. Thanks!
Repository: flutter
Issue: Support for Client Certificate in the WebView widget?
Labels: c: new feature,p: webview,package,team-ecosystem,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     Please check out our documentation first:
      * https://flutter.dev/
      * https://api.flutter.dev/

     If you can't find the answer there, please consider asking a question on
     the Stack Overflow Web site:
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     Please don't file a GitHub issue for support requests. GitHub issues are
     for tracking defects in the product. If you file a bug asking for help, we
     will consider this a request for a documentation update.

-->
I am trying to use the [WebView widget ](https://pub.dev/packages/webview_flutter), but the URL that am accessing needs a Client Certificate (as the URL is enabled with 2-way SSL). 

Does the Flutter WebView widget support passing of the client certificate for 2-way SSL communication?
Repository: flutter
Issue: PageView does not have optional scrolling on both ends.
Labels: c: new feature,framework,f: scrolling,P3,team-framework,triaged-framework

The following widget should have an optional property to add the behaviour of swiping from thirdDay to firstDay and from firstDay to thirdDay. At this point some gimmick needs to be done to have this applied.

```dart
Widget build(BuildContext context) {
    return Scaffold(
      backgroundColor: Theme.of(context).secondaryHeaderColor,
      body: Column(
        children: <Widget>[
          header(currentPage, _pageController),
          Expanded(
            child: PageView(
              controller: _pageController,
              onPageChanged: (index) {
                pageChanged(index);
              },
              children: <Widget>[
                firstDay(context),
                secondDay(context),
                thirdDay(context)
              ],
            ),
          ),
        ],
      ),
    );
  }
```
Repository: rust
Issue: Rustdoc should not fail to generate documentation when deep types are involved
Labels: T-rustdoc,C-bug

Ref. https://github.com/rust-lang/rust/issues/62059

To fix the referenced issue we raised the recursion limit, however if there is a type that exceeds this limit again, we will start failing to generate documentation for the crate in question and all the dependent crates using these deep types again.

rustdoc uses the regular trait selection mechanism to check for auto-traits, so it is not too easy to make rustdoc to ignore those failures and not generate an entry for the implementation in rustdoc instead of erroring.

Ideal behaviour would be a warning during documentation generation and a missing entry in the "Implementors" section.
Repository: pytorch
Issue: CMAKE_PARSE_IMPLICIT_LINK_INFO Function invoked with incorrect arguments
Labels: module: build,triaged,module: flaky-tests,has workaround

https://circleci.com/gh/pytorch/pytorch/2160467?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

```
Jul 09 16:47:24 CMake Error at cmake/Modules/FindOpenMP.cmake:287 (cmake_parse_implicit_link_info):
Jul 09 16:47:24   CMAKE_PARSE_IMPLICIT_LINK_INFO Function invoked with incorrect arguments
Jul 09 16:47:24   for function named: CMAKE_PARSE_IMPLICIT_LINK_INFO
Jul 09 16:47:24 Call Stack (most recent call first):
Jul 09 16:47:24   cmake/Modules/FindOpenMP.cmake:481 (_OPENMP_GET_FLAGS)
Jul 09 16:47:24   cmake/Modules/FindMKL.cmake:172 (FIND_PACKAGE)
Jul 09 16:47:24   cmake/Modules/FindMKL.cmake:265 (CHECK_ALL_LIBRARIES)
Jul 09 16:47:24   cmake/Dependencies.cmake:131 (find_package)
Jul 09 16:47:24   CMakeLists.txt:270 (include)
Jul 09 16:47:24 
Jul 09 16:47:24 
Jul 09 16:47:24 CMake Error at cmake/Modules/FindOpenMP.cmake:287 (cmake_parse_implicit_link_info):
Jul 09 16:47:24   CMAKE_PARSE_IMPLICIT_LINK_INFO Function invoked with incorrect arguments
Jul 09 16:47:24   for function named: CMAKE_PARSE_IMPLICIT_LINK_INFO
Jul 09 16:47:24 Call Stack (most recent call first):
Jul 09 16:47:24   cmake/Modules/FindOpenMP.cmake:481 (_OPENMP_GET_FLAGS)
Jul 09 16:47:24   cmake/Modules/FindMKL.cmake:172 (FIND_PACKAGE)
Jul 09 16:47:24   cmake/Modules/FindMKL.cmake:265 (CHECK_ALL_LIBRARIES)
Jul 09 16:47:24   cmake/Dependencies.cmake:131 (find_package)
Jul 09 16:47:24   CMakeLists.txt:270 (include)
```
Repository: vue
Issue: Cannot bind external web-component's 'value' property as an object
Labels: has workaround

### Version
2.6.10

### Reproduction link
[https://embed.plnkr.co/2KKE9ixZJLrRB6FUNIou/](https://embed.plnkr.co/2KKE9ixZJLrRB6FUNIou/)

### Steps to reproduce
Steps to reproduce (see the attached plunkr):

1. Create a web-component (not using Vue).
2. Expose a 'value' property in this web component that accepts/returns non-string objects (e.g. a Date object).
3. Instantiate the web component in Vue and bind the property using :value.prop syntax

### What is expected?
The object is passed as is.

### What is actually happening?
The object is converted to string before being set to the web-component 's property.

---
It is more and more common to include third party components written in other frameworks and directly use it in Vue.
However, it seems that the Vue code always expect the 'value' property to be of type string. Let's suppose to import a date selector as ES5 web custom component, that defines the 'value' property to be a Date object.
Vue will always pass this value as string instead. Using a different property name works as expected.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: go
Issue: archive/zip: reject certain invalid archives
Labels: NeedsInvestigation

This is not a defect report, but a suggestion to review the Zip archive reader with this new and authoritative zipbomb treatise in mind:

https://www.bamsoftware.com/hacks/zipbomb/
Repository: pytorch
Issue: DispatchStub should report what operator it failed to find kernel for
Labels: module: internals,module: cpu,triaged

In #22681 we get an unhelpful error message because it just says that CUDA kernels is missing, it doesn't say what is missing. It would be good of dispatch stub gave more information. Maybe we can pass in a string constant to the template parameter and update the macro to stringify the struct name to pass in.

cc @cpuhrsch @VitalyFedyunin @colesbury
Repository: go
Issue: cmd/go: go mod init doesn't import nested module, tidy picks older version
Labels: NeedsInvestigation,modules

In this case, the `glide.lock` file depends on a version of `github.com/hashicorp/consul` that uses modules and submodules. Before `go mod tidy`, we are depending on `v1.5.1`, a commit with date 2019-05-22. After `go mod tidy`, the dependency has regressed to the latest available `api` submodule version, `v1.1.0`, a commit with date 2019-05-08.

This is a dependency regression which could potentially have broken code relying on new features added between the two commits, something that `go mod tidy` shouldn't be able to do.

I suspect that `go mod tidy` needs to use a pseudoversion commit in this case, perhaps `github.com/hashicorp/consul/api v1.1.1-0.20190522201912-40cec98468b8`.


```
% go version
go version devel +a05c132064 Wed Jul 10 15:52:04 2019 +0000 linux/amd64
% ls
glide.lock  main.go
% cat glide.lock
hash: 0a6384395a31012cdcb431685f7cbe2ab3e4fb82412f708c491a785002881ed0
updated: 2019-06-05T16:36:27.768346055+02:00
imports:
- name: github.com/hashicorp/consul
  version: 40cec98468b829e5cdaacb0629b3e23a028db688
  subpackages:
  - api
% cat main.go
package main
import _ "github.com/hashicorp/consul/api"

func main() {
}
% go mod init m
go: creating new go.mod: module m
go: copying requirements from glide.lock
% cat go.mod
module m

go 1.13

require github.com/hashicorp/consul v1.5.1
% go mod tidy
% cat go.mod
module m

go 1.13

require (
	github.com/hashicorp/consul/api v1.1.0
	github.com/hashicorp/go-msgpack v0.5.4 // indirect
	github.com/hashicorp/memberlist v0.1.4 // indirect
	golang.org/x/crypto v0.0.0-20190325154230-a5d413f7728c // indirect
	golang.org/x/net v0.0.0-20190403144856-b630fd6fe46b // indirect
	golang.org/x/sync v0.0.0-20190227155943-e225da77a7e6 // indirect
	golang.org/x/sys v0.0.0-20190403152447-81d4e9dc473e // indirect
)
```
Repository: go
Issue: archive/zip: provide API for resource limits
Labels: Security,NeedsInvestigation

Zip unpacking can generate outputs thousands of times larger than the input. We should provide a security API that lets callers limit the resources that can be spent for unpacking untrusted archives.

It might be enough to limit the output size, if CPU and memory are always dependent on it.

See https://www.bamsoftware.com/hacks/zipbomb/ and #33026
Repository: rust
Issue: Should Rust still ignore SIGPIPE by default?
Labels: A-runtime,T-lang,T-libs-api,A-maybe-future-edition,I-lang-radar

Back in 2014, the Rust startup code (which runs before main) started ignoring SIGPIPE by default: https://github.com/rust-lang/rust/pull/13158

This dates back to when Rust had a runtime and a green-threads implementation, and more magic handling of I/O. The pull request mentions that it "brings the behavior inline with libgreen".

This doesn't seem to be documented anywhere, as far as I can tell; at a minimum, this needs documentation.

But I'd like to question whether we should still do this by default. See https://github.com/rust-lang/rust/issues/46016 for some recent discussion of this. This changes the default behavior of pipes from what people might expect when writing UNIX applications. Rust currently resets the signal mask in a child process, but that's only if you use *Rust* to launch the child process rather than calling a library to do so. And in addition to that, signal handlers are process-wide, and people might not expect Rust to change process-wide state like this. This also means that Rust *libraries* will not have the same behavior as Rust *applications*.

Either way, this is something we need to document far better. Some people will want one behavior, and some people will want the other, so whichever we use as the default needs careful documentation and a documented procedure to change it.

EDIT (based on a suggestion from @Centril): Perhaps we could control this with an attribute on `main` or on the top-level module?
Repository: vscode
Issue: ability to get/set currently selected debug configuration
Labels: help wanted,feature-request,api,debug

Currently, we can run `vscode.debug.startDebugging(workspaceFolder, configName)` to run the debugger from the extension. Is there a way to change currently selected debug configuration from the extension? Something like `vscode.debug.changeCurrentDebugger(workspaceFolder, configName)` would be very helpful.
Repository: flutter
Issue: Fail gracefully with a helpful message when the cache directory is not/can't be made writable
Labels: c: crash,tool,a: quality,customer: crowd,P2,team-tool,triaged-tool

This can probably happen when we try to lock the cache directory:

https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/cache.dart#L136

So far this is 7.3% of tool crashes in 1.7.8+hotfix.3. It's hard to tease apart, but file permissions issues, including in the cache, were 23% of crashes in the previous stable release.
Repository: go
Issue: cmd/go: unexpected TestScript/get_brace timeout on illumos-amd64-joyent
Labels: Testing,NeedsInvestigation,OS-illumos

From the `illumos-amd64-joyent` builder in https://build.golang.org/log/e8f2fee14aa5f386edc64b79dfeba4f092088200:

```
go test proxy running at GOPROXY=http://127.0.0.1:38179/mod
--- FAIL: TestScript (0.00s)
    --- FAIL: TestScript/get_brace (443.52s)
        script_test.go:191: 
            # Set up some empty repositories. (6.969s)
            # Clone the empty repositories into GOPATH.
            # This tells the Go command where to find them: it takes the place of a user's meta-tag redirector. (0.965s)
            # Commit contents to the repositories. (1.060s)
            # 'go get' should refuse to download or update the confusingly-named repo. (434.441s)
            > cd $GOPATH/src/example.com/foo
            $WORK/gopath/src/example.com/foo
            > ! go get -u 'example.com/{confusing}'
            [stderr]
            package example.com/{confusing}: example.com/{confusing}: invalid import path: malformed import path "example.com/{confusing}": invalid char '{'
            [exit status 1]
            > stderr 'invalid char'
            > ! go get -u example.com/foo
            [signal: interrupt]
            FAIL: testdata/script/get_brace.txt:40: test timed out while running command
            
FAIL
FAIL	cmd/go	522.698s
```

I have no idea where all that time went; it's not obvious to me whether this is due to a `cmd/go` bug or an `illumos` kernel or filesystem bug.
Repository: pytorch
Issue: torch.fill_() exists and modifies the input tensor: Expected or bug?
Labels: module: bc-breaking,triaged,module: deprecation,module: ux

Seems like in-place functions are method only, but torch.fill_() exists, is undocumented, but is declared in both native_functions.yml and derivatives.yaml.

    import torch
    a = torch.zeros(3)
    torch.fill_(a, 1)
    print(a)

This prints:

    tensor([1., 1., 1.])

Is this expected?

- PyTorch Version (e.g., 1.0): master

cc @ezyang @SsnL @gchanan
Repository: rust
Issue: Better greedy layout computation for generators
Labels: C-enhancement,T-compiler,A-coroutines,I-heavy,C-optimization

I've been thinking about a new approach for computing the layout of generators, since I merged #59897. Actually, I've been thinking about it before that, but the approach there felt a bit safer to start with.

The idea is that we use the struct layout computation, rather than the enum computation, as a starting point, and add in the fact that fields can overlap. The basic algorithm is simple:

- We iterate through every field, in descending order of alignment and number of conflicts with other fields*.
- For each field, pick the first offset (with respect to its alignment) that it's still allowed to occupy, given the other fields that we've already placed.

Because we're working in descending order of alignment (and alignments are all powers of 2), we should be able to use a "segment-tree-like" data structure with a bitset of fields that are still allowed to be placed at a given position. This means that updating the tree is logarithmic in the number of alignment levels, and so is searching for the first position a field is allowed to occupy. 

This greedy algorithm should be an improvement over the current algorithm, which doesn't attempt to overlap any fields that are live across more than one yield in the generator. It also wouldn't force "overlap-zone" fields to always come after "non-overlap" fields, which means we can do a better job of eliminating padding. Finally, the logic should be easier to follow in code than the current optimization (once the data structure is written).

This problem is NP-complete, so there might be better algorithms than this out there. I'd love to hear suggestions!

---

(*) The number of conflicts is the number of other fields in this struct that cannot be overlapped with the current field. The exact heuristic may change. Today, we use number of conflicts to help us decide which fields get to stay in an "overlap zone" and which get kicked out. Then, we use order of alignment to lay out the fields in each zone.
Repository: flutter
Issue: Remove FlutterBinaryMessenger implementation from FlutterViewController
Labels: team,engine,P2,team-engine,triaged-engine

It's left in there for now to help with the migration away from FlutterViewController publicly being a FlutterBinaryMessenger.  Unfortunately if you don't have Werror turned on the change just shows up as a warning.  We should have a grace period before we remove it.
Repository: node
Issue: There appears to be a bug with the http2 header decoding
Labels: help wanted,http2

<!--
Thank you for reporting a possible bug in Node.js.

Please fill in as much of the template below as you can.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify the affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you can.
-->

* **Version**: 10.15.3
* **Platform**: node: 10-alpine official docker image
* **Subsystem**: http2

<!-- Please provide more details below this comment. -->

This comes from googleapis/nodejs-datastore#415. It looks like occasionally http2 headers objects are being provided from the `http2` module with invalid and clearly incorrect header keys. For example, some bad headers objects look like these

```
[Object: null prototype] {
 ':status': 200,
 'content-disposition': 'attachment',
 'content-type': 'application/grpc',
 ' pø0': 'Wed, 10 Jul 2019 23:39:46 GMT',
 'alt-svc': 'quic=":443"; ma=2592000; v="46,43,39"'
}

[Object: null prototype] {
   ':status': 200,
   'content-disposition': 'attachment',
   'content-type': 'application/grpc',
   'A\u0000\u0000\u0000': 'Wed, 10 Jul 2019 22:37:34 GMT',
   'alt-svc': 'quic=":443"; ma=2592000; v="46,43,39"'
 }

[Object: null prototype] {
 ':status': 200,
 'content-disposition': 'attachment',
 'content-type': 'application/grpc',
 ' ÐÕJ': 'Wed, 10 Jul 2019 23:58:43 GMT',
 'alt-svc': 'quic=":443"; ma=2592000; v="46,43,39"'
}
```

while valid headers look like this:

```
[Object: null prototype] {
 ':status': 200,
 'content-disposition': 'attachment',
 'content-type': 'application/grpc',
 date: 'Wed, 10 Jul 2019 23:05:02 GMT',
 'alt-svc': 'quic=":443"; ma=2592000; v="46,43,39"'
}
```

In all of the cases we have seen, it looks like the `date` key is replace with this garbled nonsense. My guess is that it is relevant that that header is the one most likely to be encoded in the format [Literal Header Field Never Indexed — Indexed Name](https://http2.github.io/http2-spec/compression.html#rfc.section.6.2.3) because the value changes with every request.