sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: flutter_tool should support discovery of observatory instances without log scanning
Labels: platform-android,tool,a: existing-apps,customer: dream (g3),P3,team-android,triaged-android

Internal: b/124499560

This might involve tmp files for active ports or some other methodology. Currently Android uses log scanning, haven't looked into iOS too much

cc @mehmetf
Repository: rust
Issue: Incorrect error note, possibly incorrect error altogether ?
Labels: C-enhancement,A-diagnostics,T-compiler

In both stable and the latest nightly, [the following code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=ac030833cb7e72ad043b7a07f48e766a):
```rust
trait Trait {}
impl<T> Trait for Box<T> {}
impl<T: 'static + Copy> Trait for T {}
```
Will fail with this message:
```
error[E0119]: conflicting implementations of trait `Trait` for type `std::boxed::Box<_>`:
 --> src/main.rs:3:1
  |
2 | impl<T> Trait for Box<T> {}
  | ------------------------ first implementation here
3 | impl<T: 'static + Copy> Trait for T {}
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `std::boxed::Box<_>`
  |
  = note: downstream crates may implement trait `std::marker::Copy` for type `std::boxed::Box<_>`
```
If I understand how traits work across crates, the note on that error is false.

While I'm opening an issue about the erroneous note, I'm concerned that the error altogether might be mistaken. Is there a reason for my example code to not be allowed ?

Thanks for your time.
Repository: TypeScript
Issue: JavaScript: default parameter causes type to be incorrectly inferred 
Labels: Suggestion,Awaiting More Feedback,Domain: JavaScript

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

From https://github.com/Microsoft/vscode/issues/62013

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.0-dev.20181027

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**
For the javascript:

```js
var SomeObject = {
    SomeFunction: function (SomeInput) {
        return SomeInput * 2;
    },
    SomeOtherFunction: function (SomeOtherInput, SomeOptionalInput = SomeObject.SomeFunction(2)) {
        return SomeOtherInput * SomeOptionalInput;
    }
};

SomeObject
```

Hover over `SomeObject`

**Bug:**
Type is `any`. If the default parameter is removed then the type is correct
Repository: go
Issue: database/sql: Documentation clarification regarding Tx
Labels: Documentation,help wanted,NeedsFix

The docs state:
```
Tx is an in-progress database transaction.

A transaction must end with a call to Commit or Rollback.

After a call to Commit or Rollback, all operations on the transaction fail with ErrTxDone.

The statements prepared for a transaction by calling the transaction's Prepare or Stmt methods are closed by the call to Commit or Rollback.

```

The documentation should clarify if that is only the case if Commit or Rollback return a nil error.
What happens if they return a non-nil error? Should we try and call Commit or Rollback again? Will other operations still return ErrTxDone?
Repository: pytorch
Issue: Non-Zero Padding in Convolution Module
Labels: module: nn,module: convolution,triaged

## 🚀 Feature
Non-Zero Padding is currently only supported by explicitly padding the input before doing the convolution.
It would be better (more memory efficient, faster and userfrindly) to add an additional parameter "padding_value" to the convolution module.

## Motivation
Zero padding is sufficient to control the dimensions of the output. However, there is no clear motivation for the padding to be zero-valued. On the contrary, zero padding might even deteriorate the end results. Thus, the user should be able to specify an arbitrary value for the padding. 

## Pitch

To realise the additional parameter the following changes would needed to be made.

- Python API (Conv1d, Conv2d, Conv3d): [torch/nn/modules/conv.py](https://github.com/pytorch/pytorch/blob/master/torch/nn/modules/conv.py)
- Convolution Logic: [aten/src/ATen/native/Convolution.cpp](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/Convolution.cpp)
- Header Generation: [aten/src/ATen/nn.yaml](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/nn.yaml), [aten/src/ATen/native/native_functions.yaml](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/native_functions.yaml), [/tools/autograd/derivatives.yaml](https://github.com/pytorch/pytorch/blob/master/tools/autograd/derivatives.yaml)
- THNN, THCUNN headers: [aten/src/THNN/generic/THNN.h](https://github.com/pytorch/pytorch/blob/master/aten/src/THNN/generic/THNN.h) [aten/src/THCUNN/generic/THCUNN.h](https://github.com/pytorch/pytorch/blob/master/aten/src/THCUNN/generic/THCUNN.h)
- Convolution Implementation (in THNN and THCUNN): [SpatialConvolutionMM](https://github.com/pytorch/pytorch/blob/master/aten/src/THNN/generic/SpatialConvolutionMM.c), [SpatialDilatedConvolution](https://github.com/pytorch/pytorch/blob/master/aten/src/THNN/generic/SpatialDilatedConvolution.c)...
- Unfolding operations [im2col](https://github.com/pytorch/pytorch/blob/master/aten/src/THCUNN/im2col.h)

## Additional context

@bengisuelis, @cdemirsoy and I implemented the above discribed modifications for gpu (THCUNN) convolutions and would like to contribute our code. 
We did not add the functionality for external librarys (wrapper neeeded) and Cpu executed code (THNN). For those cases we currently throw a runtime error "padding_value not yet supported".


cc @albanD @mruberry @jbschlosser
Repository: pytorch
Issue: [Caffe2]How to accelerate group convolution in Caffe2?
Labels: caffe2

I have update my cuDNN from 6. to 7. but there seems no speedup. The build was forked form the latest source and CUDA=8.0. What should I do to make a further acceleration?
Repository: pytorch
Issue: Use a dill-based multiprocessing library and serialization
Labels: module: multiprocessing,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Use a dill-based multiprocessing library to enhance multiprocessing experience.

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
Currently multiprocessing uses pickle, which has disadvantages. Not everything can be pickled easily. For example, dynamically created classes and nested classes will fail. If instead of multiprocessing, pytorch used a drop-in replacement that uses dill, e.g. `multiprocess` a fork of multiprocessing, these problems should be alleviated with few or no side-effects.

## Pitch

<!-- A clear and concise description of what you want to happen. -->
Multiprocessing in torch should not be limited by the brittle pickle system. I want to be able to create python programs without the limitations of pickle, but still use pytorch and its multiprocessing system.

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->
Repository: create-react-app
Issue: Jest CSS enhancement suggestion: don't lose classNames in snapshot tests.
Labels: issue: needs investigation

We've been using react-app-rewired with create-react-app v1 and react-scripts-ts for Typescript support for a while, and are starting to look at the new v2.1 release with Typescript support.

One of the enhancements we are using in jest snapshot tests is to output the classnames from css imports in the snapshot. This enables the ability to test parts of a component where a change in props or a user interaction is supposed to result in a change in css being applied to the component (e.g. as a simple make-believe example, changing className from "" to "locallyModified" where there is a `:local(.locallyModified) { color: #FFFF44; }` class in the css).

The snapshot then contains `<div className="locallyModified">` instead of simply `<div>`, which highlights an issue when someone makes a change that breaks the behaviour identifying when the conditional styling should be altered.

The actual cssTransforms.js file is simply:
```javascript
const idObj = new Proxy(
  {},
  {
    get: function getter(target, key) {
      return key;
    }
  }
);

module.exports = idObj;
```
Is it possible to consider adding this to react-scripts/config/jest/cssTransform.js by default? Or is there a reason why it couldn't/shouldn't be widely used?
Repository: go
Issue: text/template: confusing overlay template behavior when it starts with a BOM
Labels: NeedsDecision

The program below prints `Master: overlay` once, the second prints nothing. And no error. The program is a variation of this example: https://golang.org/pkg/html/template/#example_Template_block -- which is how we do template "inheritance" in Hugo. And judging by the issue reports in this area, adding a BOM marker seems to be a fairly common practice among text editors. I can work around this on my end, but this behavior is very surprising.

https://play.golang.org/p/MQRb5HUk6eH

```go
package main

import (
	"fmt"
	"log"
	"os"
	"text/template"
)

func main() {
	for _, prefix := range []string{"", "\ufeff"} {
		var (
			master  = `Master: {{block "list" .}}block{{end}}`
			overlay = prefix + `{{define "list"}}overlay{{end}}`
		)

		masterTmpl, err := template.New("master").Parse(master)
		if err != nil {
			log.Fatal(err)
		}
		overlayTmpl, err := template.Must(masterTmpl.Clone()).Parse(overlay)
		if err != nil {
			log.Fatal(err)
		}

		if err := overlayTmpl.Execute(os.Stdout, ""); err != nil {
			log.Fatal(err)
		}

		fmt.Println()
	}
}

```

https://github.com/gohugoio/hugo/issues/4895
Repository: svelte
Issue: Transitions in custom Elements
Labels: bug,custom element

Seems like there is a problem with svelte-transitions in customElements, js works properly, adding css: animation, right before destroy, but there are no visual effects...

Seems like it can`t set animation for Shadow CSS.
Repository: create-react-app
Issue: Type check test files
Labels: tag: breaking change,tag: enhancement,issue: typescript

## Bug report

I created a new project with the `--typescript` flag, and added a type for my component's props like so:

```tsx
type AppProps = {
  name: string
};

class App extends Component<AppProps> {
  render() {
    return (
      ...
    );
  }
}
```

In index.tsx when I write something like (note the missing prop):

```tsx
ReactDOM.render(<App />, document.getElementById('root')); // name prop is missing
```

I get an error in both my editor (VSCode) and on my console when I run `yarn start`.

However in my tests if I have something like:

```tsx
it('renders without crashing', () => {
  const div = document.createElement('div');
  ReactDOM.render(<App />, div);
  ReactDOM.unmountComponentAtNode(div);
});
```

I get the type error in my editor but **NOT** when I run `yarn test`, the tests run successfully in fact.

Is this intended?
Repository: go
Issue: x/build/cmd/gomote: 'gomote ssh' on plan9 can't see files installed by 'gomote put'
Labels: help wanted,OS-Plan9,Builders,NeedsInvestigation

### What did you do?

```
~$ gomote create plan9-386
user-bcmills-plan9-386-0

~$ gomote put14 user-bcmills-plan9-386-0

~$ gomote push user-bcmills-plan9-386-0
# […]

~/go/src$ gomote run user-bcmills-plan9-386-0 /bin/pwd
/tmp/workdir

~/go/src$ gomote run user-bcmills-plan9-386-0 /bin/ls /tmp/workdir
/tmp/workdir/go
/tmp/workdir/go1.4

~$ gomote ssh user-bcmills-plan9-386-0
$ ssh -p 2222 user-bcmills-plan9-386-0@farmer.golang.org # auth using https://github.com/bcmills.keys
# […]
# `gomote push` and the builders use:
# - workdir: /tmp/workdir
# - GOROOT: /tmp/workdir/go
# - GOPATH: /tmp/workdir/gopath
# - env: GO_BUILDER_NAME=plan9-386 GO_TEST_TIMEOUT_SCALE=2
# Happy debugging.
# […]

cpu% ls /tmp/workdir
ls /tmp/workdir
ls: /tmp/workdir: '/tmp/workdir' file does not exist
cpu%
```

### What did you expect to see?

The files reported by `gomote run […] /bin/ls /tmp/workdir` are also visible when running `ls /tmp/workdir` under `gomote ssh`.


### What did you see instead?

The files placed by `gomote put14` and `gomote push` are not visible to the `gomote ssh` process.

@bradfitz tells me that the the ssh and buildlet processes don't share that part of the filesystem namespace.

@0intro, any ideas?
Repository: rust
Issue: stack overflow with many unused variables
Labels: I-crash,A-lints,E-needs-test,T-compiler,C-bug

I had a `main()` that was filled with ~5400 `let x = 0;`s, one per line.

When trying to build the program, rustc crashes.

````
warning: unused variable: `x`
    --> src/main.rs:5406:6
     |
5406 |     let x = 0;
     |         ^ help: consider using `_x` instead

warning: unused variable: `x`
    --> src/main.rs:5407:6
     |
5407 |     let x = 0;
     |         ^ help: consider using `_x` instead


thread '<unknown>' has overflowed its stack
fatal runtime error: stack overflow
Compile terminated by signal 6
error: Could not compile `many_warn`.

Caused by:
  process didn't exit successfully: `/home/matthias/.cargo/bin/sccache rustc --crate-name many_warn src/main.rs --color always --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=1383ca9b11585a98 -C extra-filename=-1383ca9b11585a98 --out-dir /tmp/many_warn/target/debug/deps -C incremental=/tmp/many_warn/target/debug/incremental -L dependency=/tmp/many_warn/target/debug/deps -C target-cpu=native` (exit code: 2)
````

crashes nightly 1.32, beta 1.31.0-beta.1 and stable 1.30.0.
`cargo check` works though.
Repository: flutter
Issue: Move diagnostics to separate top level library
Labels: c: new feature,framework,would be a good package,P3,team-framework,triaged-framework

The diagnostics functionality as mentioned in issues such as #9568 is too useful to be bundled inside Flutter and tied up with other items that pull in UI-dependencies. The use case and benefit would be developing similar plugins for Dart apps running in non-UI VMs to inspect data structures.
Repository: TypeScript
Issue: "Import assignment cannot be used when targeting ECMAScript modules." should come with a codefix
Labels: Suggestion,In Discussion,Domain: Quick Fixes

**TypeScript Version:**  3.2.0-dev.20181030

**Code**

**a.ts**
```ts
import abs = require("abs");
```
**tsconfig.json**
```ts
{
    "compilerOptions": {
        "target": "esnext"
    }
}
```

The error message is `Import assignment cannot be used when targeting ECMAScript modules. Consider using 'import * as ns from "mod"', 'import {a} from "mod"', 'import d from "mod"', or another module format instead.`. This indicates that we could provide a code fix.

**Expected behavior:**

There is a codefix that offers to change this to `import abs from "abs";`, or `import * as abs from "abs";`. If `--esModuleInterop` is set and the imported value is not used only as a namespace, we should prefer a default import.

**Actual behavior:**

No codefix.
Repository: flutter
Issue: Provide API in TextField to open the keyboard
Labels: a: text input,c: new feature,framework,engine,P2,team-engine,triaged-engine

From https://github.com/flutter/flutter/issues/15882#issuecomment-433563683:

I've just discovered calling `FocusScope.of(context).requestFocus(...)` is not good enough. It does not [request for the keyboard](https://github.com/flutter/flutter/blob/9bf8502fef3f35d8d3ba692ce0383e9f55a34624/packages/flutter/lib/src/material/text_field.dart#L491). This can be an issue in the following case:

1. Tap on text field. We provide it focus. This opens the keyboard.
2. Tap Android back button. Keyboard is dismissed. Field still has focus.
3. Tap on text field again. We try to provide it focus again but this doesn't do anything. **There is no way to get the keyboard back up.** 

In order to display the keyboard, we need to call `requestKeyboard` on the `EditableTextState` but this is [not exposed to us](https://github.com/flutter/flutter/blob/9bf8502fef3f35d8d3ba692ce0383e9f55a34624/packages/flutter/lib/src/material/text_field.dart#L441) as the global key is private.
Repository: flutter
Issue: Date Time Picker needs seconds picker
Labels: c: new feature,framework,f: material design,f: date/time picker,P3,team-design,triaged-design

it will be a great if you a the native widget Date and Time picker allows seconds to be picked.
Hope it will be in upcoming release. Meanwhile I am trying to add a number picker on after saving the date time.
Repository: create-react-app
Issue: Add baseUrl and paths in tsconfig.json and jsconfig.json
Labels: issue: proposal

`tsconfig.json` or  `jsconfig.json`: 
```js
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*":["src/*"]
    }
  }
}

```
see https://github.com/facebook/create-react-app/issues/5118

This will help VSCode and other IDE to resolve path in TypeScript & JavaScript.
Repository: godot
Issue: Viewport Texture generate mipmaps ignored
Labels: topic:rendering,confirmed,documentation

___

***Note:** This issue has been confirmed several times already. No need to confirm it further.*

___

Not sure if that's expected behavior but Im using the viewport texture on sprite and I tried to use textureLod(...) so I could get blurry version of that and it doesn't work. Setting flags in editor doesn't help either.

Any workarounds to force generating Lods from Viewport Texture? something like in SCREEN_TEXTURE that has Lods
Repository: create-react-app
Issue: yarn pnp doesn't work with typescript
Labels: issue: bug

Set up a pnp typescript project
`npx create-react-app pnp --use-pnp --typescript` or `npx create-react-app pnp --typescript --use-pnp` order doesn't matter

You then get

```
yarn add v1.12.1
[1/5] 🔍  Resolving packages...
[2/5] 🚚  Fetching packages...
[3/5] 🔗  Linking dependencies...
[5/5] 📃  Building fresh packages...
success Saved lockfile.
success Saved 8 new dependencies.
info Direct dependencies
├─ @types/jest@23.3.9
├─ @types/node@10.12.1
├─ @types/react-dom@16.0.9
├─ @types/react@16.4.18
├─ react-dom@16.6.0
├─ react-scripts@2.1.0
├─ react@16.6.0
└─ typescript@3.1.4
info All dependencies
├─ @types/jest@23.3.9
├─ @types/node@10.12.1
├─ @types/react-dom@16.0.9
├─ @types/react@16.4.18
├─ react-dom@16.6.0
├─ react-scripts@2.1.0
├─ react@16.6.0
└─ typescript@3.1.4
✨  Done in 14.72s.
We detected TypeScript in your project (src/App.test.tsx) and created a tsconfig.json file for you.

It looks like you're trying to use TypeScript but do not have typescript installed.
Please install typescript by running yarn add typescript.
If you are not trying to use TypeScript, please remove the tsconfig.json file from your package root (and any TypeScript files).


Aborting installation.
  node --require /Users/bond/Projects/pnp-test/.pnp.js has failed.

Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.
```

---
Environment

```

  System:
    OS: macOS 10.14
    CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 8.12.0 - /usr/local/bin/node
    Yarn: 1.12.1 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  npmGlobalPackages:
    create-react-app: Not Found
```
Repository: vscode
Issue: Surface the 'origin and 'presentationHint' attributes of a Source in the Loaded Scripts Explorer
Labels: feature-request,debug

When a Source appears in the CALL STACK panel during debugging, its `presentationHint` modifies the row's appearance, and its `origin` displays on the second line of the hover tip.

Please apply `presentationHint` in the same way on the LOADED SCRIPTS panel.

Please also surface `origin` there, either by appending in italics (as currently happens in the OPEN EDITORS panel) or as a second line of the hover tip.
Repository: rust
Issue: "does not live long enough" when returning Option<impl trait>
Labels: A-lifetimes,A-impl-trait,C-bug

This doesn't compile:
```
use std::cell::RefCell;

struct B;
struct A {
    b: B,
}

impl A {
    fn b(&self) -> Option<impl Iterator<Item = &B>> {
        Some(::std::iter::once(&self.b))
    }
}

fn func(a: RefCell<A>) {
    let lock = a.borrow_mut();
    if let Some(_b) = lock.b() {}
}
```

However, it compiles when impl trait is replaced with the concrete type:
```
fn b(&self) -> Option<::std::iter::Once<&B>> {
```

It also compiles with impl trait if `Option` is removed:
```
impl A {
    fn b(&self) -> impl Iterator<Item = &B> {
        ::std::iter::once(&self.b)
    }
}

fn func(a: RefCell<A>) {
    let lock = a.borrow_mut();
    let _b = lock.b();
}
```
Repository: godot
Issue: Tilemap Node : No way to change the offset while painting
Labels: enhancement,topic:editor

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if non-official. -->
Version : 3.0.6

**OS/device including version:**
<!-- Specify GPU model and drivers if graphics-related. -->


**Issue description:**
<!-- What happened, and what was expected. -->
There is no way to change the offset of tiles while we are painting, so if the tilesets have different dimensions, they can't be connected with each other.
As shown here.
![tileoffsets](https://user-images.githubusercontent.com/41776584/47792121-572d4f00-dd41-11e8-842e-daa1f572cf53.png)
Repository: go
Issue: fmt: docs slightly disorganized and slightly contradictory
Labels: Documentation,NeedsFix

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?

1.11

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?

N/A

### What did you do?

Read the fmt docs. Someone in IRC asked about padding, and I went and looked, and thought "that seems slightly inaccurate", then reread it and thought "wait that can't be right, can it?" and eventually concluded that things were confusing.

### What did you expect to see?

Something I could follow without much effort.

### What did you see instead?

A confusing tangle. Width and explicit argument indexes are both "immediately preceeding the verb", but actually width won't immediately preceed the verb if precision is present, or an explicit argument index for that matter. I know what width and precision *are* because I'm used to C, but some kind of vague conceptual introduction might be nice. Explicit argument indexes are described separately from every other aspect of the formatting verbs, after an unrelated tangle of things.

Before filing this, I decided to see if I could write something I thought was better. After some effort, I'm pleased to state that I have no idea but I have at least made an effort, so I should have a change submitted for code review "soon". (I think it's justified just by getting the explicit argument indexes moved in with the rest of the stuff.)