sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vue
Issue: Functional single file component with components option.
Labels: feature request,improvement,has PR

### Version
2.5.13

### Reproduction link

NG pattern (functional)
https://codesandbox.io/s/004vv2onw0

OK pattern (no functional)
https://codesandbox.io/s/q9k5q8qq56

### Steps to reproduce
I found can't use `components` option when  `functional` single file component.

```html
<template functional>
  <div>
    <some-children />
  </div>
</template>

<script>
import SomeChildren from "./SomeChildren"

export default {
  components: {
    SomeChildren
  }
}
</script>
```

It's occure `Unknown custom element`.

### What is expected?
Not occure `Unknown custom element` and use child component

### What is actually happening?
It's occure `Unknown custom element`

---

In workaround, it not occure when use `Vue.component`.

```js
import Vue from "vue"
import SomeChildren from "./SomeChildren"
Vue.component("some-children", SomeChildren);

export default {}

// can use  <some-children />
```


<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: create-react-app
Issue: Resolve symlinks using Node resolution mechanism
Labels: issue: bug,issue: needs investigation

Copying my comment from #1107 since that issue is pretty crowded and I want it to be here instead.

----

Having read some discussions in https://github.com/nodejs/node/pull/6537 and https://github.com/isaacs/node6-module-system-change I think we're actually already being inconsistent in how we handle symlinks.

Let's forget about the issue about compiling source code for a second. I feel like that can be solved by https://github.com/facebookincubator/create-react-app/issues/1333 and thus is not the most important one here.

The important part here is that the resolution should match Node algorithm so that our webpack setup matches our test setup. I thought that was the case, but I was wrong.

Consider this structure:

```
my-comp
  index.js // already compiled
  package.json // react is a peer dependency

my-app
  node_modules
    my-comp // symlink to my-comp folder
```

It turns out that if `my-comp` doesn't declare a dependency on `react`, it *can find React in the browser builds but not in tests*.

<img width="696" alt="screen shot 2018-01-21 at 12 25 54" src="https://user-images.githubusercontent.com/810438/35194148-462b1d9c-fea6-11e7-83da-8beda0655109.png">
<img width="1082" alt="screen shot 2018-01-21 at 12 26 06" src="https://user-images.githubusercontent.com/810438/35194149-46498f66-fea6-11e7-813c-ac8f71bfe48f.png">

We introduced this regression in https://github.com/facebookincubator/create-react-app/pull/1359.

We probably missed it because if `my-comp` *does* explicitly depend on React (e.g. as a `devDependency`), the test passes (and in the browser we just get two Reacts).
Repository: rust
Issue: #[link(name=…)] makes life hard for non-cargo build systems
Labels: A-linkage,T-dev-tools,C-feature-request

I'm not sure how that feauter is handled by rustc (and cargo?).

My Nix-based build system (carnix) cannot build packages using it, because it has no way to tell a library declared in this way has to be used (I tried just grepping over the source files, but that fails because some modules might not get compiled, depending on the platform and features).

I'd like at least one of the following:

- help on what options I need to pass to rustc in order to compile these crates anyway,
- or a new command in cargo and/or in rustc to output flags for these files (such as `cargo:rustc-flags=…`) without compiling anything, that can then be passed to rustc to actually compile the crate.
Repository: angular
Issue: style binding handling css `calc` function improperly
Labels: type: bug/fix,area: animations,freq2: medium,hotlist: google,P3

<!--
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
<!-- Describe how the issue manifests. -->
`style.paddingLeft="calc(10px + 1px * 1)` does nothing. (but `style.paddingLeft="calc(10px)` does)
`[ngStyle]="{'padding-left': 'calc(10px + 1px * 1)'}"` works as expected.


## Expected behavior
<!-- Describe what the desired behavior would be. -->
`style.paddingLeft="calc(10px + 1px * 1)` works as same as `[ngStyle]="{'padding-left': 'calc(10px + 1px * 1)'}"`

## Minimal reproduction of the problem with instructions
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-->
https://stackblitz.com/edit/angular-gde28w

## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->


## Environment

<pre><code>
Angular version: 5.x.x
<!-- Check whether this is still an issue in the most recent Angular version -->

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  <!-- run `node --version` -->
- Platform:  <!-- Mac, Linux, Windows -->

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
Repository: rust
Issue: ./x.py build --on-fail=/bin/bash has no effect
Labels: T-bootstrap,C-bug

Trying to look into #43982, I was running `./x.py build --jobs=4 --on-fail=/bin/bash`. Once I hit the ICE, the build exited without dropping me to a shell as I had expected. @nagisa wanted to try and repro this.

re-uploaded [build log](https://github.com/rust-lang/rust/files/1650313/build.log) as a gist:
https://gist.github.com/Mark-Simulacrum/f660624e0195d733da752649a6cf7538
Repository: rust
Issue: Misleading error message when passing a reference to an FnOnce and a non-reference is expected
Labels: C-enhancement,A-diagnostics,T-compiler

Compiling this code:
```rust
struct Foo {}

impl Foo {
    pub fn foo(&self) -> String {
        "foo".to_owned()
    }
}

fn main() {
    let foo = Foo{};
    let closure = move || foo;

    call(&closure);
}

fn call<F: FnOnce() -> Foo>(f: F) {
    println!("{}", f().foo())
}
```

[gives me the following error](https://play.rust-lang.org/?gist=962c9bd74d972a21741a179447a75965&version=nightly):
```
error[E0525]: expected a closure that implements the `Fn` trait, but this closure only implements `FnOnce`
  --> src/main.rs:11:19
   |
11 |     let closure = move || foo;
   |                   ^^^^^^^^^^^
12 | 
13 |     call(&closure);
   |     ---- the requirement to implement `Fn` derives from here
   |
note: closure is `FnOnce` because it moves the variable `foo` out of its environment
  --> src/main.rs:11:27
   |
11 |     let closure = move || foo;
   |                           ^^^
```

`call` *does* expect a closure which implements `FnOnce`, not one which implements `Fn` as the error message suggests. Accordingly, the line "expected a closure that implements the `Fn` trait, but this closure only implements `FnOnce`" is very misleading.

The actual problem here is that a reference to an `FnOnce` is being passed, rather than the `FnOnce` itself. It would be great if the error message reflected this fact.
Repository: flutter
Issue: Document that WillPopScope prevents swipe to go back on MaterialPageRoute
Labels: framework,customer: mulligan (g3),d: api docs,d: examples,customer: crowd,P2,team-framework,triaged-framework

## Steps to Reproduce

1. Add a `MaterialPageRoute` to your app's page stack
    ```dart
    return new MaterialPageRoute<Null>(
      settings: settings,
      builder: (BuildContext context) => new StoryPage(itemId: itemId),
    );
    ```
1. Wrap that page's `Scaffold` in a `WillPopScope` widget
    ```dart
    return new WillPopScope(
      onWillPop: () async {
        return true;
      },
      child: new Scaffold(
        …
      ),
    );
    ```
1. Try to swipe to go back on iOS. The page won't swipe.

This also occurs if you replace the `MaterialPageRoute` with a `CupertinoPageRoute`.

I think this might be an unintended side-affect of fixing #8269.

For a live example of this, [see my repo here](https://github.com/dudeofawesome/hn_flutter/blob/03077e9c1681a6223b4f95e2b41f2a516e9ebb30/lib/pages/story.dart#L308).

## Flutter Doctor

```
[✓] Flutter (on Mac OS X 10.13.2 17C205, locale en-US, channel master)
    • Flutter version 0.0.21-pre.284 at /Users/DudeOfAwesome/Library/Developer/flutter
    • Framework revision 7cdfe6fa0e (2 days ago), 2018-01-20 00:36:00 -0800
    • Engine revision e45eb692b1
    • Tools Dart version 2.0.0-dev.16.0
    • Engine Dart version 2.0.0-edge.93d8c9fe2a2c22dc95ec85866af108cfab71ad06

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/DudeOfAwesome/Library/Android/sdk
    • Android NDK at /Users/DudeOfAwesome/Library/Android/sdk/ndk-bundle
    • Platform android-27, build-tools 27.0.3
    • ANDROID_HOME = /Users/DudeOfAwesome/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] iOS toolchain - develop for iOS devices (Xcode 9.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.2, Build version 9C40b
    • ios-deploy 1.9.2
    • CocoaPods version 1.3.1

[✓] Android Studio (version 3.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] IntelliJ IDEA Ultimate Edition (version 2017.2.5)
    • Flutter plugin version 18.1
    • Dart plugin version 172.4343.25

[✓] Connected devices
    • iPhone X • C927CB75-4D41-426B-9B32-D859B2FC5FFD • ios • iOS 11.2 (simulator)
```
Repository: TypeScript
Issue: No error when namespace export is used before assigned
Labels: Bug,Help Wanted


<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.6.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** namespace decorator same class

**Code**

```ts
@C1.Decorator
export class C1{ }
export namespace C1 { 
  export function Decorator<T>(target: T) { }
}
@C1.Decorator
@C2.Decorator
export class C2 { }

export namespace C2 { 
  export function Decorator<T>(target: T) { }
}
```

**Expected behavior:** if this is not a feature, decorator should be defined at runtime, or it should provide some warning or error during compilation?

**Actual behavior:** decorator from namespace C1 used on class C1 is undefined, decorator from C1 is defined when used on C2, decorator from C2 is undefined

**Playground Link:** https://www.typescriptlang.org/play/index.html#src=%40C1.Decorator%0D%0Aexport%20class%20C1%7B%20%7D%0D%0Aexport%20namespace%20C1%20%7B%20%0D%0A%20%20export%20function%20Decorator%3CT%3E(target%3A%20T)%20%7B%20%7D%0D%0A%7D%0D%0A%40C1.Decorator%0D%0A%40C2.Decorator%0D%0Aexport%20class%20C2%20%7B%20%7D%0D%0A%0D%0Aexport%20namespace%20C2%20%7B%20%0D%0A%20%20export%20function%20Decorator%3CT%3E(target%3A%20T)%20%7B%20%7D%0D%0A%7D

**Related Issues:** I did not find any
Repository: rust
Issue: The "method references Self" object-safety rule is overly restrictive
Labels: A-trait-system,T-lang,C-feature-request,T-types,A-trait-objects

Is there any reason why the following trait method can't be object safe?

```rust
trait Trait {
    fn take_and_return_box(self: Box<Self>) -> Box<Self>;
}
```
Intuitively, it would return `Box<T>` when called on a `Box<T>` where `T: Trait`, and `Box<Trait>` when called on a `Box<Trait>`. The compiler would do an unsize coercion on the `Box<T>` returned by the vtable method, combining it with the vtable of the `Box<Trait>` that was passed in.

If I'm not mistaken, the object safety rule could be relaxed to allow methods that reference the `Self` type in the return value, as long as it's a type that meets certain `CoerceUnsized` requirements:

- Let `ReturnType<Self>` be the return type of the method, e.g. `Box<Self>`
- For a given type `T`, let `ReturnType<T>` be `ReturnType<Self>` with every occurrence of `Self` replaced with `T`
- The trait method is object safe if the following conditions are met:
    - `ReturnType<Trait>: Sized`
    - for every type `T: Unsize<Trait>`, `ReturnType<T>: CoerceUnsized<Trait>`.

Note: this is very similar to what I think the object-safety rules for [arbitrary_self_types (#44874)](https://github.com/rust-lang/rust/issues/44874) will look like
Repository: flutter
Issue: `TapGestureRecognizer` leaked by `_RenderSlider` and `_RenderRangeSlider`
Labels: c: crash,framework,has reproducible steps,P2,found in release: 3.10,team-framework,triaged-framework

These classes uses `TapGestureRecognizer` but does not dispose it.

- `RenderToggleable`
- `_RenderCupertinoSwitch`
- `_RenderSlider`

Is it the intended implementation?

A parent class of `TapGestureRecognizer`, `PrimaryPointerGestureRecognizer` uses `Timer` and has `dispose` method.

`LongPressGestureRecognizer` is used similarly.
Repository: vue-element-admin
Issue: Can U support Parcel(https://parceljs.org)
Labels: discussion

Webpack is too complicated
Thanks!
Repository: vscode
Issue: Support reading/writing chunks in remote fs
Labels: feature-request,api,remote,api-proposal

This is a follow up from #32503 where `IFileService.updateContent()` now accepts a `ITextSnapshot` to prevent loading the entire buffer into memory. I left a TODO [here](https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/files/electron-browser/remoteFileService.ts#L366) to use `ITextSnapshot` directly and not the current fallback `snapshotToString`
Repository: react
Issue: Fabric Todos
Labels: Type: Umbrella,React Core Team

For my own notes here are some spill-overs from the Fabric renderer commit.

- [ ] Update currentProps for updates in the commit phase. Needs a host effect to be marked and we need a hook to do host updates in the persistent mode.
- [x] Actually use currentProps when extracting events in the component tree.
- [ ] Resuming will need to be able to not reuse host nodes used by another thread.
- [ ] Should always clone direct siblings of a changed node, in case they will relayout.
Repository: go
Issue: x/mobile: accessing field on nil on iOS raises exception instead of panicking (gomobile)
Labels: NeedsInvestigation,mobile

The spec says accessing a field (`x.foo`) should panic if `x` is `nil`, but it seems that in an iOS library built with gomobile, the result is an EXC_BAD_ACCESS exception being raised.

Please answer these questions before submitting your issue. Thanks!

#### What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Here's an example that works fine in a regular Go program but the equivalent compiled into an iOS app crashes: https://play.golang.org/p/KsIyVll7NE0.


#### What did you expect to see?

Accessing a field on nil panics, and is handled by a surrounding defer/recover block.


#### What did you see instead?

Accessing a field on nil raises a native exception, crashing the program unrecoverably.

#### System details

```
go version go1.9.2 darwin/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/verm/remix/amp"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.9.2/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/36/92jbhtpj41s6q3w4fcq2v01w0000gn/T/go-build431793073=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
GOROOT/bin/go version: go version go1.9.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.9.2
uname -v: Darwin Kernel Version 16.7.0: Mon Nov 13 21:56:25 PST 2017; root:xnu-3789.72.11~1/RELEASE_X86_64
ProductName:	Mac OS X
ProductVersion:	10.12.6
BuildVersion:	16G1114
lldb --version: lldb-900.0.64
  Swift-4.0
```
Repository: electron
Issue: webContents.startDrag() for dragging and dropping remote files out of Electron into local filesystem
Labels: enhancement :sparkles:,platform/macOS

* Electron version: 1.7.10
* Operating system: Mac OS X Sierra

Hey guys! I love what you've done with Electron. Keep it up! 💯 

I'm building a remote file explorer in Electron. I would like to have the ability to drag files *out* of Electron into the Mac OS X Finder. This can be achieved using `webContents.startDrag()` but this only works for **local files** that already exist. Since my file explorer manages remote files, I do not have a local file path to pass to webContents.startDrag() yet. 

Is there any way to implement this kind of remote file drag-drop behavior with Electron? I was thinking of listening to the 'drop' event, intercepting the path, and downloading the files to this path via Node.js code. 

However, Electron never seems to call any event after the webContents.startDrag() file has been successfully moved. Any ideas?

This has been asked on StackOverflow as well with no solution as of today:
https://stackoverflow.com/questions/43209509/is-it-possible-to-drag-a-remote-file-out-of-electron-app-onto-the-file-system?rq=1
Repository: flutter
Issue: Warn that flutter run/build must be run before building directly inside Xcode
Labels: tool,platform-mac,a: quality,P2,team-tool,triaged-tool

It's currently easy to land on obscure error messages when the user opens the template created project's xcode project directly and then tries to build. Add a build phase script to check for the staleness or absence of `Generated.xcconfig` or some such.
Repository: vue
Issue: Vue.extend mutates original object
Labels: discussion

### Version
2.5.13

### Reproduction link
[http://jsfiddle.net/vmvabzam/](http://jsfiddle.net/vmvabzam/)

### Steps to reproduce
- run the fiddle and look at the code vs the html

### What is expected?
`Foo.props` should still be an array after extending it

### What is actually happening?
`Foo.props` are normalized after using Vue.extend on it

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: The mutable borrow is released when matching on a Option<&mut Self> in a function, but not when the function is inlined
Labels: T-compiler,A-NLL,C-bug,NLL-polonius

```rust
#![feature(nll)]

struct Node {
    value: char,
    children: Vec<Node>,
}

impl Node {
    fn new(value: char) -> Self {
        Self {
            value,
            children: Vec::new(),
        }
    }

    fn add_child(&mut self, value: char) -> &mut Self {
        self.children.push(Self::new(value));
        self.children.last_mut().unwrap()
    }

    fn get_child(&mut self, value: char) -> Option<&mut Self> {
        self.children.iter_mut().find(|n| n.value == value)
    }

    fn add_word(&mut self, word: String) {
        let mut cursor = self;
        for c in word.chars() {
            // The extracted version of the function works
            // cursor = cursor.get_or_add(c);

            // But the inlined version of the function does not.
            cursor = match cursor.get_child(c) {
                Some(node) => node,
                None => cursor.add_child(c),
            };
        }
    }

    fn get_or_add(&mut self, value: char) -> &mut Self {
        match self.get_child(value) {
            Some(node) => node,
            None => self.add_child(value),
        }
    }
}

fn main() {}
```

```
error[E0499]: cannot borrow `*cursor` as mutable more than once at a time
  --> src/main.rs:34:25
   |
32 |             cursor = match cursor.get_child(c) {
   |                            ------ first mutable borrow occurs here
33 |                 Some(node) => node,
34 |                 None => cursor.add_child(c),
   |                         ^^^^^^ second mutable borrow occurs here
```

[Originally from Stack Overflow](https://stackoverflow.com/q/48395307/155423)
Repository: flutter
Issue: Document and test a mechanism to require a certain Flutter version to build
Labels: c: new feature,tool,P2,team-tool,triaged-tool

Right now there is no way to specify the required Flutter version in the `pubspec.yaml`. One should be able to pin the build to a specific version (or commit) of Flutter so that the build is reproducible in the future. Furthermore, there is no way currently to ensure developers working on a shared codebase all use the same version of Flutter, making collaboration on bugfixing and debugging potentially impossible.

tl;dr it would be nice if it were possible to specify the version of Flutter to use just like one could specify the Dart SDK version to use.
Repository: flutter
Issue: Provide an easy way to select the version of Flutter to use
Labels: c: new feature,tool,P3,team-tool,triaged-tool

This ties in with #14229 — it would be great if there was a way to select the version of Flutter to use from the `flutter` tool. Currently to my understanding the manual process to do so is:

```bash
$ cd flutter
$ git checkout [branch, tag or commit hash]
$ cd ../my-app/
$ flutter packages get
```

(assuming both the `flutter` folder and the `my-app` folder live in the same directory)

What would be nice would be able to use a command like `flutter switch-to [version]` (e.g., `flutter switch-to 0.0.20`). Ideally running `flutter run` or `flutter build` could do this automatically, but that poses the question of how it would work for people working on multiple projects using different versions of Flutter at the same time.
Repository: create-react-app
Issue: Knowing when dev compile is done
Labels: issue: proposal

<!--
  PLEASE READ THE FIRST SECTION :-)
-->

### Is this a bug report?

No

### How to tell when webpack dev compile is ready?

I want to be able to run a second process after the dev server is up and running and the compile is done, e.g. run a mock api server. Normally the webpack compiler emits a 'done' event that you can hook into and start a new process or do something else. With CRA, the compiler object is hidden away in the `start` script.

Is there any way of accessing this event without ejecting?
Repository: flutter
Issue: Enable tree shaking of platform specific code
Labels: framework,dependency: dart,c: proposal,P3,team-framework,triaged-framework

Flutter apps can conditionally render platform specific UI using the APIs in [platform.dart](https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/foundation/platform.dart).

Currently these APIs depend on non-const state, resulting in this conditionally code not being tree-shakeable. We should support making this const, at least in release builds.