sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: has_method does not work on class
Labels: bug,topic:core

**Godot version:**
current master


**OS/device including version:**
Windows, don't think it matters


**Issue description:**
Investigating #22833 I found out that `has_method` does not work with classes.
Consider the following script:

```
extends Node

class Test:
	static func foo():
		print("foo")

func _ready():
	Test.foo() # works as expected
	print(Test.has_method("foo")) # false although Test has this method
```

In #22833 this bug makes it impossible to use a static func of a class in array.sort_custom().

**Steps to reproduce:**
Call `has_method` on a class.

**Minimal reproduction project:**
[sfhm.zip](https://github.com/godotengine/godot/files/2454253/sfhm.zip)
Repository: godot
Issue: Escape should discard Output panel (but not Shader editor when discarding a tooltip)
Labels: enhancement,topic:editor,usability

**Godot version:**
<!-- Specify commit hash if non-official. -->
b17e71b6e5e035f49b5b3b5b55b9cdac80215d72

**Issue description:**
<!-- What happened, and what was expected. -->
The output area will not be closed when `Escape` is pressed. 
This used to work in previous versions.

**Steps to reproduce:**
1. Open the output area
2. Press `Escape`
3. Output area will not be close
Repository: kubernetes
Issue: Exposing ephemeral storage metrics to prometheus 
Labels: sig/storage,kind/feature,help wanted,sig/instrumentation,needs-triage

**Is this a BUG REPORT or FEATURE REQUEST?**:

/kind feature

Now, we only expose PVC related volumes metrics to protheus, https://github.com/kubernetes/kubernetes/pull/51553
but we need ephemeral storage metrics too, such as EmptyDir usage and capacity info.

/assign 
/sig storage
/cc @jingxu97 @gnufied
Repository: rust
Issue: Add the ability to copy a skeleton trait impl from a trait doc entry
Labels: T-rustdoc,C-feature-request,A-rustdoc-ui,T-rustdoc-frontend

refiled from rust-lang/rfcs#621
Repository: pytorch
Issue: Could not find a package configuration file provided by "Torch" with any of   the following names:
Labels: module: cpp-extensions,triaged

C++ build documentation seems has code bugs:

Simply following the tutorial of newest libtorch doc, just got errors.

```
CMake Error at CMakeLists.txt:5 (find_package):
  By not providing "FindTorch.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Torch", but
  CMake did not find one.

  Could not find a package configuration file provided by "Torch" with any of
  the following names:

    TorchConfig.cmake
    torch-config.cmake

  Add the installation prefix of "Torch" to CMAKE_PREFIX_PATH or set
  "Torch_DIR" to a directory containing one of the above files.  If "Torch"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!
See also "/Volumes/xs/tmp/libtorch_learn/example-app/build/CMakeFiles/CMakeOutput.log".
```

It's cmake issue, I think documentation should more specific and make Torch finable.

cc @yf225 @glaringlee
Repository: TypeScript
Issue: [Feature] make generated codes from enum could be minified when not used
Labels: Suggestion,In Discussion

## Search Terms

For now TypeScript will transform enum from

```ts
enum Test {
    Key = 1
}
```
to

```ts
var Test;
(function (Test) {
    Test[Test["Key"] = 1] = "Key";
})(Test || (Test = {}));
```
This result is not friendly for uglyify or tree-shaking.
When `Test` is not be used, the generated code block always remain as dead codes.

## Suggestion

prefer to generate codes below:
```ts
var Test = /*#__PURE__*/(function () {
    var e = {}
    e[e["Key"] = 1] = "Key";
    return e
})();
```
## Examples
![image](https://user-images.githubusercontent.com/1667873/46602882-0d778d00-cb24-11e8-8847-cbb3483e0960.png)

The suggestion version will be removed.

## 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: godot
Issue: Moving folder AA to folder BB which have folder with same name(AA) cause error moving instead merge.
Labels: enhancement,topic:editor,usability

**Godot version:**
3.1 b17e71b


Windows 10


**Issue description:**
When I try to copy folder with name AA to folder BB which contain folder with name AA, error "Error moving:" was occur. 

I think that Godot should merge this folder to one. 

When we paste files, the warning message should stay as is "Please Confirm... ...  Overwrite   Cancel "

But when we paste folders, I think the warning should change text "Overwrite" to "Merge and Overwrite".


**Steps to reproduce:**
1. Create res://AA folder
2. Create res://BB folder
3. Create res://BB/AA folder
4. Try to cut folder res://AA and paste it to res://BB

https://streamable.com/vibga
Repository: rust
Issue: Tracking issue for warning for rust_2018_idioms by default
Labels: A-lints,C-tracking-issue,WG-epoch,S-tracking-impl-incomplete,A-edition-2018

`#[warn(rust_2018_idioms)]` is not going to be enabled by default for Rust 2018 because we are taking a conservative stance and we aren't sure about how good the suggestions are yet.

The plan is to enable this lint by default some number of releases / months after Rust 2018 ships.

# Progress

- [x] `bare_trait_objects` is now set to warn (https://github.com/rust-lang/rust/pull/61203)
- [x] `ellipsis_inclusive_range_patterns` will soon be set to warn (https://github.com/rust-lang/rust/pull/61342)
- [ ] `unused_extern_crates` has [open issues](https://github.com/rust-lang/rust/pull/59483#issuecomment-478232879)
- [ ] https://github.com/rust-lang/rust/issues/91639
- [x] `elided_lifetimes_in_paths` has open issues (https://github.com/rust-lang/rust/issues/60199, https://github.com/rust-lang/rust/issues/55768)
- [x] #44294
- [ ] #51881
- [ ] #56038
- [ ] #56328
- [ ] #57274
- [ ] #77713

This summary was last updated from [this comment](https://github.com/rust-lang/rust/issues/54910#issuecomment-1002041036); check to see if there are new comments since then.

/cc @Centril @aturon @Mark-Simulacrum
Repository: opencv
Issue: T-API: Using Mat expressions with async UMat functions
Labels: bug,category: core,category: ocl,category: t-api

Invalid objects lifetime is observed.

related: #12754 (workaround in DNN module, but problem is still here).
Repository: flutter
Issue: Flutter tool should collect C++ crashes in dev mode and offer to report them
Labels: c: new feature,tool,P2,team-tool,triaged-tool

Engine crashes should be rare.

Ideally we should catch engine crashes, and offer to report them.  Whether we catch them just using the flutter tool (to read logs) or we do something more like adding breakpad to the engine in debug mode, we could catch crashes (e.g. https://github.com/flutter/flutter/issues/19590) and the `flutter` tool could prompt the user to report them to our crash database.

It's possible we could automatically report them, but that would require more consideration as the stacks my include non-Flutter code.

Thoughts?
Repository: TypeScript
Issue: Odd quick fix ordering for misspelled identifiers
Labels: Bug,Needs Proposal,In Discussion

I believe that "misspelled identifier" quick fixes should precede the "remove unused declarations".

![image](https://user-images.githubusercontent.com/972891/46625525-2a429f00-cae9-11e8-9fee-27b1c38e0b37.png)

If anyone wants to take this on, this should just be a matter of

1. Making a test case for this, and
2. Shifting the order of which quick fix is registered first.
Repository: pytorch
Issue: input_device, output_device, devices_used properties
Labels: module: nn,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

People keep requesting a .device property on layers, and that's legitimately turned down with the response "_Modules can hold parameters of different types on different devices, and so it’s not always possible to unambiguously determine the device._" e.g., #12135 A simple ".device" property doesn't work well.

In fact, I think what people really want is:

- Tell me where I can put inputs.
- Tell me where outputs are produced.
- Tell me what devices are actually used internally by this module.
- Convert this input into something you can use.
- Produce output in this preferred format.

For example, just because a module stores parameters on a GPU doesn't mean it is limited to GPU inputs.

## Pitch

I'd suggest thinking more about a simple API to query the relationship between modules and inputs. In principle, these can be pretty complex ("if you give me an X I give you a Y", etc.), but maybe just something for the common cases. E.g.,

    m.input_devices() --> ["cuda:0", "cuda:*", "cpu"]
    m.output_devices() --> ["cuda:0"]
    m.required_devices() --> ["cuda:0"]

By convention, input_devices()[0] would be the preferred device for inputs.

A default implementation based on next(m.parameters()).device would return [device] for all three methods, and return [] if there are no parameters; this seems to reflect current practice and assumptions.

Without an API, people are going to hardcode assumptions about the relationship between parameters, modules, and devices that are unnecessarily restrictive or simply wrong in general.

In addition, forward and backward methods might get a preferred_device keyword argument that allows them to put results on the preferred output device.

cc @albanD @mruberry @jbschlosser
Repository: TypeScript
Issue: findAllRefs doesn't work for property of `typeof import("./foo")`
Labels: Bug

**TypeScript Version:** 3.2.0-dev.20181006

**Code**

```ts
/// <reference path="fourslash.ts" />

// @Filename: /a.ts
////export const [|x|] = 0;

// @Filename: /b.ts
////function f(a: typeof import("./a")) {
////    a.[|x|];
////    a.[|x|];
////}

verify.singleReferenceGroup("const x: 0");
```

**Expected behavior:**

Test passes.

**Actual behavior:**

Test fails. The references in `function f` aren't found.
Repository: create-react-app
Issue: Support for a workbox.config.js override file
Labels: contributions: up for grabs!,issue: proposal,difficulty: medium

As per https://github.com/facebook/create-react-app/pull/5111#issuecomment-425458687, there was discussion around the `c-r-a` v2 timeframe for allowing developers to override the default `workbox-webpack-plugin` (i.e. service worker generation) configuration with their own external `workbox.config.js` file. This functionality did not end up making it into the final release, though.

I'd love to see that happen, as putting together a one-size-fits-all default config can [leave some developers confused](https://github.com/facebook/create-react-app/issues/5316).

I'm happy to submit a PR for that and update the docs accordingly, but I wanted to see if there was any prior art around external, user-controllable configuration files that did make it into the `c-r-a` v2  release. I'd rather just use a similar approach for Workbox if that solution for another plugin already exists.

If there is no prior art for configuring other plugins in v2, I'd like to confirm that folks like @gaearon and @Timer are fully on board with the idea of external config files, since it's been a contentious point in the past.
Repository: go
Issue: runtime: arena mapping creates large core files and bad mlockall behavior
Labels: Performance,NeedsFix

```
package main

var p *int

func main() {
	*p = 0
}
```

Run with
```
$ ulimit -c unlimited
$ GOTRACEBACK=crash go run test.go
$ ls -l core
```

Go 1.11 and tip generate a ~100MB core.  Go 1.10 and earlier only generate a ~2MB core.
Probably related to the arena changes in 1.11.

@aclements @heschik @hyangah
Repository: vscode
Issue: Add selectionBackground defaults
Labels: feature-request,ux

The selectionBackground color token controls the background color of text selection outside of the editor. So this affects text in native input elements like search, selecting text in the debug console, settings editor, other places. If one isn't defined, it comes from the OS and is different between macOS and windows. Maybe the OS picks different colors in some scenarios, like for different windows themes.

e.g. in Dark+

MacOS

![image](https://user-images.githubusercontent.com/323878/46511718-08a19900-c805-11e8-8452-f6789b3e4fc2.png)

Windows

![image](https://user-images.githubusercontent.com/323878/46511726-1820e200-c805-11e8-9322-94f11dd12115.png)

I think that adding defaults for this token would be a good idea just so it looks consistent. It's also an issue for editor instances pretending to be input boxes - the settings and extensions input boxes that use the suggest widget. If selectionBackground isn't configured, they don't know the native selection color and fall back on the editor selection background which doesn't always look good in that context, so setting a default selectionBackground will make those input consistent with the native inputs. But maybe people like the native text selection look?

@misolori 
@Tyriar 
?
Repository: go
Issue: spec: clarify requirements for duplicate constants in interface-typed map literal keys and switches
Labels: Documentation,NeedsInvestigation

The Go spec disallows duplicate constants in map literal keys, and allows compilers to reject duplicate constants in switch cases.

However, the Go spec does not formally allow interface-typed constants, and doesn't mention how to handle constants that are implicitly or explicitly converted to interface type. The existing compilers handle these situations in differing ways:

    package p
    
    // #1
    var _ = map[interface{}]int{
    	0: 0,
    	0: 0,
    }
    
    // #2
    var _ = map[interface{}]int{
    	interface{}(0): 0,
    	interface{}(0): 0,
    }
    
    func _() {
    	// #3
    	switch interface{}(0) {
    	case 0:
    	case 0:
    	}
    
    	// #4
    	switch interface{}(0) {
    	case interface{}(0):
    	case interface{}(0):
    	}
    }

cmd/compile rejects 1, 2, and 3.

go/types rejects 1 and 3.

gccgo (8.0) rejects none.

/cc @griesemer @ianlancetaylor
Repository: rust
Issue: Refiled: "Rustfmt/pretty-print types in error messages"
Labels: A-frontend,C-enhancement,A-diagnostics,T-compiler,WG-diagnostics,D-diagnostic-infra

Refiling...

> For any highly generic library (`futures` is the one that I hit this issue with a lot) it's easy for types to become unreadable very fast. Even `impl Trait` only helps so much (we're using `Box<Trait>` a lot in our code so `impl Trait` won't get us better error messages). A good solution would be to `rustfmt`-style pretty-print types in the error messages so that it's possible for humans to parse them. It might be useful to make this optional or otherwise limit the maximum size because I can imagine this causing `diesel`'s types to take hundreds of lines to print. Probably some kind of overrideable heuristic would be useful to implement here.

https://github.com/rust-lang/rfcs/issues/2358
Repository: storybook
Issue: Storysource addon - allow prism configuration
Labels: feature request,ui,addon: storysource

If you are reporting a bug or requesting support, start here:
### Bug or support request summary

Have added Storysource and was expecting to be able to configure Prism syntax highlighting - eg. choose the theme, tweak the highlight style and so on. However I can't find anything in the docs about that - I can see the Prettier settings but nothing about Prism? That all seems hard-coded. This is an issue as the chosen theme is really hard to read and clashes badly with our own design.

Not sure if I'm just missing something, or if this is a feature request...

### Steps to reproduce

n/a I think

### Please specify which version of Storybook and optionally any affected addons that you're running

- "@storybook/react": "^3.3.15",
- "@storybook/addon-storysource": "^3.4.11",

### Affected platforms 

n/a I think

### Where to start

n/a I think

### Acceptance criteria

- Ability to choose theme for Prism when using Storysource
- Ability to configure/extend the styles applied to the Story tab, eg. the highlight style
Repository: rust
Issue: Path::ancestors can contain empty path
Labels: T-libs-api,A-io

With the following code
```rust
use std::path::Path;

fn main() {
    let mut ancestors = Path::new("foo/bar").ancestors();
    assert_eq!(ancestors.next(), Some(Path::new("foo/bar")));
    assert_eq!(ancestors.next(), Some(Path::new("foo")));
    assert_eq!(ancestors.next(), None);
}
```
I'd expect to have the last assertion being ok but it isn't since this "ancestors.next()" is in fact Path::new("")
Repository: opencv
Issue: Cannot silence warnings from cv::VideoCapture with cv::utils::logging::setLogLevel
Labels: feature,category: videoio

<!--
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).

Please:

* Read the documentation to test with the latest developer build.
* Check if other person has already created the same issue to avoid duplicates. You can comment on it if there already is an issue.
* Try to be as detailed as possible in your report.
* Report only one problem per created issue.


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 => 3.4.1
- Operating System / Platform => Windows 64 Bit 
- Compiler => Visual Studio 2017

##### Detailed description

**/modules/videoio/src/cap_ffmpeg_impl.hpp** ignores OpenCV's logging infrastructure and prints directly to STDERR which results in an unreadable character mess for multi-threaded applications.

##### 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
-->
```.cpp
cv::utils::logging::setLogLevel( cv::utils::logging::LOG_LEVEL_FATAL );
cv::VideoCapture capture;
capture.open( "path to a nonexistent file" );
```
Repository: pytorch
Issue: [Feature request]:  add `LayerNormLSTMCell`
Labels: module: rnn,triaged

As layer normalization recently becomes a standard trick to train RNN, it would be very convenient to support it.

Here I write up an initial version

```python
class LayerNormLSTMCell(RNNCellBase):

    def __init__(self, input_size, hidden_size, bias=True, ln_preact=True):
        super(LayerNormLSTMCell, self).__init__(input_size, hidden_size, bias, num_chunks=4)
        
        self.ln_preact = ln_preact
        if self.ln_preact:
            self.ln_ih = nn.LayerNorm(4*self.hidden_size)
            self.ln_hh = nn.LayerNorm(4*self.hidden_size)
        self.ln_cell = nn.LayerNorm(self.hidden_size)

    def forward(self, input, hx=None):
        self.check_forward_input(input)
        if hx is None:
            hx = input.new_zeros(input.size(0), self.hidden_size, requires_grad=False)
            hx = (hx, hx)
        self.check_forward_hidden(input, hx[0], '[0]')
        self.check_forward_hidden(input, hx[1], '[1]')
        
        # hidden states and preactivations
        h, c = hx
        ih = input @ self.weight_ih.t() + self.bias_ih
        hh = h @ self.weight_hh.t() + self.bias_hh
        if self.ln_preact:
            ih = self.ln_ih(ih)
            hh = self.ln_hh(hh)
        preact = ih + hh
        
        # Gates
        f, i, o, g = preact.chunk(4, dim=1)
        g = g.tanh()
        f = f.sigmoid()
        i = i.sigmoid()
        o = o.sigmoid()
        
        # cell computations
        c = f*c + i*g
        c = self.ln_cell(c)
        h = o*c.tanh()
        
        return h, c
````

cc @zou3519
Repository: vue
Issue: A deliberately empty slot-scope attribute will not be rendered as a scoped slot
Labels: improvement

### Version
2.5.17

### Reproduction link
[https://jsfiddle.net/decademoon/50wL7mdz/759740/](https://jsfiddle.net/decademoon/50wL7mdz/759740/)





### Steps to reproduce
```
<foo>
  <bar slot-scope/>
</foo>
```

### What is expected?
`<bar slot-scope>` should be a scoped slot.

### What is actually happening?
`<bar slot-scope>` is rendered as a child as if `slot-scope` were not present.

---
As a workaround, I've been using a dummy variable to force it to be a scoped slot:

```<bar slot-scope="scope"/>```

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: Lifetime inference and Pin
Labels: A-type-system,T-compiler,A-inference,C-bug,T-types

There appears to be some lifetime inference issue with how `Deref` is implemented for `Pin`, so that I get issues about how the pin does not live long in code that should clearly work. For example, this gives an error about how the pin does not live long enough:

```rust
fn foo<'a>(x: Pin<&'a i32>) -> &'a i32 {
    &*x
}
```

https://play.rust-lang.org/?gist=5749b0645d17308d62501924e618e49d&version=nightly&mode=debug&edition=2015

cc #49150
Repository: vscode
Issue: Show/log which extension has thrown an exception
Labels: feature-request,extensions,log

pls see https://github.com/Microsoft/vscode/issues/60046. When we catch the extension in the provideHover API call then we can know which extension is handling the call and we could report this to the user.
Repository: go
Issue: cmd/vet: warn about changing fields in non-escaping variables if they are not set after assignment
Labels: NeedsInvestigation,Analysis

It's a common mistake for new users of Go* to accidentally attempt to set a field on a non-pointer receiver.

For instance:

```
type Something struct{
     Done bool
}

func (s Something) Bar() {
     if s.Done {
         return
     }
     // Code goes here
     s.Done = true
}
``` 

The above is legal in Go 1.x because s is passed by value to Bar, but the change only lasts for the duration of the function call since the local version on the stack was modified, not the value which the method was called on. This is almost always a bug and I can't think of any situations where that would be the intention of the programmer when attempting to set a property inside of a method.

This proposal is to make it illegal to modify a property on a receiver when the receiver is passed-by value. Arguments other than the receiver would unaffected.

This could be done either as a`go vet` check in Go 1.x, or a language change in Go2.

* I don't have any numbers to support this claim, but blaming new users means I wouldn't need to admit if it were to theoretically be a mistake that I might still occasionally make.