sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Multi-step input composing range incorrectly styled on iOS
Labels: a: text input,platform-ios,framework,a: internationalization,a: fidelity,has reproducible steps,P2,found in release: 3.3,found in release: 3.5,team-text-input,triaged-text-input

## Steps to Reproduce

1. Open *Flutter Gallery* and select the *Text field* demo.
1. Tap the *Name* field.
1. Switch to Japanese/Chinese input and begin entering text.

The composing (a.k.a. mark) region is underlined, rather than appearing lightly selected.

See the following screenshots:

## Current Flutter composing style
![img_1413](https://cloud.githubusercontent.com/assets/351029/24939269/fcfc5392-1ef0-11e7-9862-48be9d95e015.PNG)

## Default iOS composing style (from Google Inbox)

![img_1414](https://cloud.githubusercontent.com/assets/351029/24939276/0bdb17f4-1ef1-11e7-8a29-97103bd4fda6.PNG)

## Default iOS selection style (from Google Inbox)

![img_1415](https://cloud.githubusercontent.com/assets/351029/24939281/10af74e6-1ef1-11e7-8a9e-fa8e9bae3969.PNG)



## Flutter Doctor

Running with a local engine with iOS text input patches. Base install is:

```
[✓] Flutter (on Mac OS X 10.12.4 16E195, channel master)
    • Flutter at /Users/cbracken/src/flutter/flutter
    • Framework revision c12c019bcc (6 hours ago), 2017-04-11 13:48:04 -0700
    • Engine revision 5d9a642257
    • Tools Dart version 1.23.0-dev.11.6
```
Repository: vscode
Issue: vscode use webassembly
Labels: under-discussion

Vscode will use webassembly to improve the implementation of the application speed, webassembly standard is not already officially released!

It seems that nodejs 8 will be the first to introduce webassembly;

Hope to answer the next question, thank you, if you have caused trouble, very sorry
Repository: rust
Issue: GDB hardcodes startswith(producer, "clang ") to cope with LLVM debug line info in prologues.
Labels: A-debuginfo,T-compiler,C-bug

Only observed on x86_32, see https://github.com/rust-lang/rust/pull/40367#issuecomment-293623287 and [relevant code in GDB source](https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/i386-tdep.c;hb=8f10c9323357ad190c0383f2fc9d394316447905#l1856).

LLVM appears to generate the .loc` for the first LLVM IR instruction in a function *just before* the last instruction of the prologue, resulting in GDB refusing to break on that location (by file and line number).

Not sure if this is solvable in GDB - perhaps by using the location information from the prologue after the prologue? Or maybe the intention is to actually never do that? It's really not clear from the GDB source.

Before #40367, we used to have a branch from the LLVM IR entry block to the MIR start block, which triggered the problem, but not in an user-visible way. Subsequent instructions were and still are unaffected.

As a workaround, I changed `producer` from `rustc version _` to `clang LLVM (rustc version _)`.

cc @michaelwoerister @Manishearth
Repository: pytorch
Issue: Dice Loss PR
Labels: module: loss,triaged,enhancement,Stale

Hi, I have implemented a Dice loss function which is used in segmentation tasks, and sometimes even preferred over cross_entropy. More info in this paper:
http://campar.in.tum.de/pub/milletari2016Vnet/milletari2016Vnet.pdf
Here's the link of it:
https://github.com/rogertrullo/pytorch/blob/rogertrullo-dice_loss/torch/nn/functional.py#L708
How could I submit a PR?
thanks!
Repository: rust
Issue: Unclear error with type inference failure
Labels: C-enhancement,A-diagnostics,T-compiler,A-inference,D-terse

```rust
struct S {
    v: Vec<(u32, Vec<u32>)>,
}

impl S {
    pub fn remove(&mut self, i: u32) -> Option<std::vec::Drain<u32>> {
        self.v.get_mut(i as _).map(|&mut (_, ref mut v2)| {
            v2.drain(..)
        })
    }
}
```
Errors with:
```
error: the type of this value must be known in this context
 --> src/main.rs:8:16
  |
8 |             v2.drain(..)
  |                ^^^^^
```
I'm not sure which value the error is pointing at here. The fix here is to explicitly specify the type we want to cast `i` into.
Repository: TypeScript
Issue: Iterator interface for LanguageService
Labels: Suggestion,API,Awaiting More Feedback

Currently, functions like `LanguageService.getReferencesAtPosition()` or `getNavigateToItems()` return an array. That means, they have to collect all references/navigation items before returning, and blocks the CPU until then.
If you invoke such a function in repos like angular/angular the returned array can easily have 50k elements and the function can take a very long time to return. That means a UI can only show the results until all items have been aggregated (of course, you can pass a limit, but in the case of `getNavigateToItems()` that can result in the relevant items you wanted not being found because matching is done fuzzily and the function returns early when `limit` items that matched the query fuzzily were found. For example, in angular/angular, a query for _Http_ with a limit will return a lot of not-relevant `http` variables, but a query without a limit will return the `Http` class). If you have to do more filtering, transformation etc to the items you end up with an unneeded extra iteration.

I would like to propose to add or change the API to return an `Iterable` instead. This can be achieved with generators. This would allow the consumer to _pull_ items lazily from the iterator.
That means
 - results (e.g. references, symbols) can be streamed and shown in the UI as soon as they are found in the source
 - requests can be easily cancelled by aborting iteration (e.g. `break` in a `for of`)
 - a limit parameter is not needed anymore, you can just abort the iteration after your limit is reached
 - if you need to perform filtering, transformation etc on the result, you can do that in the same iteration "pipeline"

There is no dependency needed to make this work, it's all in the language.
The returned Iterable can be consumed in a variety of ways, with `for of`, generator delegation, with iteration libraries or Observables, or easily coverted to an Array with `Array.from()`.

This API could be added in a backwards-compatible way by adding a new variant and changing the old one to delegate and convert to array:

```ts
getReferencesAtPosition(fileName: string, position: number): ReferenceEntry[] {
    return Array.from(this.getReferencesIterableAtPosition(fileName, position);
}
getReferencesIterableAtPosition(fileName: string, position: number): IterableIterator<ReferenceEntry> {
    // ...
}
```
Repository: go
Issue: all: check build reproducibility
Labels: Builders,NeedsInvestigation

It'd be nice to have the builder (and ideally also a trybot) check reproducibility of builds. This is not an good thing to add to all.bash, because it is slow and computationally expensive.

The implementation is fairly straightforward. I usually do it by running something like:

```
$ ./make.bash
$ toolstash save
$ for f in `seq 15`; do go build -a -toolexec='toolstash -cmp' std cmd; done
```

However, a simpler (if slower) approach that should also work is to run make.bash many times (n=5? 10?) and check that all the resulting .a and executable files are identical. In fact, I think all the filesystem contents should be identical.

This is about to become more important because the introduction of a concurrent compiler backend provides lots more opportunity to mess up reproducibility. Detection is currently manual (e.g. #19872).

@bradfitz @adams-sarah
Repository: go
Issue: build: run race-enabled toolchain
Labels: Builders,NeedsFix

The compiler already has a concurrent lexer and parser, and it will soon have a concurrent backend. We should have a fast builder running a race-enabled version of the toolchain to catch data races.

I have in mind something like this (very rough sketch):

```
$ ./all.bash  # instead of doing 'go install cmd' after bootstrapping, do 'go install -race cmd'
$ for all-platforms-like-misc-compile; do go build -a std cmd; done
```

This would provide race detector coverage for normal and error conditions, plus all the assemblers. Ideally "all platforms" would ultimately also end up including some variations like -shared, -dynlink, -race, -msan, etc.

There might also be some extra flags to add somewhere to ramp up the concurrency, to try to flush out races.

This is clearly not fully thought out yet. :) Step one is to get a basic builder going and make it easy to improve.

I'm happy to do the legwork on this, but I'll need some help and direction, I fear.

@bradfitz @adams-sarah
Repository: opencv
Issue: Unable to stop the stream: Inapproriate ioctl for device - ARM
Labels: priority: low,category: videoio(camera),incomplete

Hi, 

I noticed an error while I try to open a video file (in this case is an **avi** file), just on ARM arch (bot 32 and 64) .

Once I try to open the file, the following error is fired up:

**Unable to stop the stream: Inapproriate ioctl for device**

Looking into the source code, it seems a problem related to **libv4l**, since the error message it's executed at least from one of these files:line

**modules/videoio/src/cap_v4l.cpp:1833** 
**modules/videoio/src/cap_libv4l.cpp:1879**

The error is fired only on ARM system (verified on Beaglebone Black and DragonBoard 410c), I understand this is a problem related with libv4l and not with opencv libs. 
Perhaps the interaction with both libopencv and lib4vl must be reviewed for ARM arquitecture (maybe some macro not properly defined) ?

Regards,
simon
Repository: flutter
Issue: Support keyboard events in flutter_driver
Labels: a: tests,a: text input,tool,t: flutter driver,customer: crowd,c: proposal,P3,team-tool,triaged-tool

Add an API for sending keyboard events to devices in Flutter Driver tests.

Useful for writing comprehensive tests of text input, input from physical keyboards, IME compose region etc.
Repository: flutter
Issue: Flutter driver finder/scrollIntoView does not scroll lazily-created items into view
Labels: a: tests,c: new feature,tool,framework,t: flutter driver,P3,team-framework,triaged-framework

## Steps to Reproduce

1. Edit `examples/flutter_gallery/test_driver/transitions_perf_test.dart`
1. From the `demos` list, remove `profiled: true` on any demos that include them.
1. Add `profiled: true` to the 'Sliders' demo or other demo that's initially offscreen.
1. `flutter drive test_driver/transitions_perf.dart`

## Flutter Doctor

```
[✓] Flutter (on Mac OS X 10.12.4 16E195, channel master)
    • Flutter at /Users/cbracken/src/flutter/flutter
    • Framework revision 00dfa224d1 (34 minutes ago), 2017-04-13 12:31:04 -0700
    • Engine revision 5c4e20c4c5
    • Tools Dart version 1.23.0-dev.11.6
```
Repository: kubernetes
Issue: Make fsType specifyable in volumeClaimTemplates
Labels: kind/feature,area/stateful-apps,sig/apps,lifecycle/frozen

<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->

**Is this a request for help?** (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No,


**What keywords did you search in Kubernetes issues before filing this one?** (If you have found any duplicates, you should instead reply there.): volumeClaimTemplates fstype

---

**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): Feature Request

Currently, (at least following the API documentation), there is no way to specify an fsType in a volumeClaimTemplates. Some applications (mongodb) that fit the use case of a statefulSet should use a specific file system for some reason (performance). It is therefore desired to make this specifyable.
Repository: rust
Issue: document what "thin pointers" are
Labels: C-enhancement,A-diagnostics,T-compiler,D-confusing

I got the following error message:

    error: casting `*const T` as `usize` is invalid
      --> src/refset.rs:17:9
       |
    17 |         (self.0 as *const T as usize).hash(state);
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
       = help: cast through a thin pointer first

which was quite clear, except that there seems to be no documentation as to what a "thin" pointer is.  I ended up through guesswork casting to a *const usize in between which made this work for me.
Repository: go
Issue: doc: explain how to debug performance problems in Go programs
Labels: Documentation,help wanted,NeedsFix

We should probably have a doc explaining how to debug performance problems in Go programs. There is the profiling blog post, but a larger survey of the field might be good.

/cc @aclements @alandonovan
Repository: vscode
Issue: vscode reads AltGr key as cursor-left move through X11 connections
Labels: bug,help wanted,keybindings,linux

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode -->

- VSCode Version: 1.11.2 (Commit 6eaebe3b9c70406d67c97779468c324a7a95db0e)
- OS Version: Ubuntu 16.04.2 / Windows 10

Steps to Reproduce:

1. install/start X server on Windows system (Xming, MobaXterm or VcXsrv)
2. start code on Linux box (make sure your SSH client has X11 forwarding enbled), use AltGr to compose "{" or similar, cursor jumps left. Interesting to note that both the "{" character and the cursor-left move are produced. This has started with VScode 1.11. Same with code-insiders. Don't get me started.
3. Tested on 4 different computers.
Repository: kubernetes
Issue: CRI: Clearly define the `Privileged` field in the security context
Labels: sig/node,kind/feature,lifecycle/frozen

CRI inherits the `Privileged` field from the kubernetes (and Docker) API. It's there to improve the user experience.
Since CRI is not intended to be directly user-facing, it should translate the field into a set of fields (e.g., capabilities).

At the least, we should clearly define what `Privileged` means in the CRI.

/cc @kubernetes/sig-node-api-reviews @Random-Liu @mrunalp @feiskyer @timstclair
Repository: go
Issue: database/sql: add option to customize Begin statement
Labels: NeedsInvestigation,FeatureRequest

Currently, the `*DB.BeginTx` method looks like this:

```go
func (db *DB) BeginTx(ctx context.Context, opts *TxOptions) (*Tx, error)

type TxOptions struct {
    // Isolation is the transaction isolation level.
    // If zero, the driver or database's default level is used.
    Isolation IsolationLevel
    ReadOnly  bool
}
```

However, there are transaction options across drivers that don't fit into these fields.  For instance:

* In SQLite, [all transactions are serializable](https://www.sqlite.org/isolation.html), but transactions can [specify when to grab the global lock](https://www.sqlite.org/lang_transaction.html) as part of the `BEGIN` statement. There's no way to get at that from the Go SQLite driver (mattn/go-sqlite3#400)
* In PostgreSQL, the [`DEFERRABLE` option](https://www.postgresql.org/docs/9.6/static/sql-begin.html) can be specified when starting the transaction, which does not fit into either of these options.  However, Go users can work around this by using the [`SET TRANSACTION`](https://www.postgresql.org/docs/9.6/static/sql-set-transaction.html) statement.
* In MySQL, the [`WITH CONSISTENT SNAPSHOT`](https://dev.mysql.com/doc/refman/5.7/en/commit.html) option can only be specified when starting the transaction and cannot be specified during [`SET TRANSACTION`](https://dev.mysql.com/doc/refman/5.7/en/set-transaction.html).

It would be nice to have another option in `TxOptions` that allows you to change which statement is used.  As an idea:

```go
type TxOptions struct {
    // Isolation is the transaction isolation level.
    // If zero, the driver or database's default level is used.
    Isolation IsolationLevel
    ReadOnly  bool

    // Modifiers is a partial SQL statement that specifies database-specific transaction options.
    // The database will prefix "BEGIN " or "START TRANSACTION " to form a full SQL statement, whichever is appropriate.
    // The string may or may not have a trailing semicolon.
    // If a database does not support transaction options, then Modifiers is ignored.
    // If not empty, Isolation and ReadOnly are ignored.
    Modifiers string
}
```

While this approach is convenient and ensures that the statement is a `BEGIN` or `START TRANSACTION` statement, it's not particularly performant, as it requires the statement to be prepared on each `BeginTx`.  However, you could imagine adding a method to `DB` like:

```go
// PrepareBegin prepares a SQL statement to begin a transaction.
// modifiers has the same meaning as in TxOptions.
func (db *DB) PrepareBegin(ctx context.Context, modifiers string) (*Stmt, error)

type TxOptions struct {
    // ...

    // Stmt is used to start the transaction if non-nil.
    // It must be the result of a call to PrepareBegin.
    // If non-nil, all other fields are ignored.
    Stmt *Stmt
}
```
Repository: flutter
Issue: Installation needs to be simpler
Labels: tool,a: first hour,customer: crowd,P3,team-tool,triaged-tool

Our current installation process is multi-step, involves the command line, etc. We have data showing that this results in failed installations and abandoned installations.

I think we need to have a single-step install.

I suggest:
- [ ] On Mac OS, have a single DMG that you can drag onto your machine (Apps directory? Home directory?) that includes our git repo, cached binaries, and all the dependencies we can legally bundle. This gets you to the same state you have today, and leaves our current upgrade path intact.
- [ ] On Windows, have an installation app that you can download and run that bundles our git repo, cached binaries, and all the dependencies we can legally bundle, and leaves our current upgrade path intact.
- [ ] On Linux, have a bootstrap script that does the same thing into your home directory.
- [ ] We should pin and bundle all our Dart dependencies. https://github.com/flutter/flutter/issues/6767
- [ ] We should try to shed as many dependencies as we can.
Repository: vscode
Issue: Allow to reset “Don't Show Again” preference
Labels: feature-request,workbench-notifications

VSCode’s “top banner” often includes a “Don't Show Again” button. However it's not clear how a user should undo this action.

Would it be possible to save these preferences to the user's workspace settings, perhaps? Then it is easy for the user to undo this action.

An example of a user needing this: https://github.com/Microsoft/vscode/issues/23314
Repository: opencv
Issue: Issue with BestOf2NearestMatcher on Opencv 3.x.x VS15
Labels: incomplete

##### System information (version)
- OpenCV => 3.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015

##### Detailed description

BestOf2NearestMatcher does not work on Opencv 3 compiled with Visual Studio.
See the code:

##### Steps to reproduce

	vector<cv::DMatch> vDMatchesLR;
	vector<cv::detail::MatchesInfo> vPairwiseMatchesLR;
	cv::detail::BestOf2NearestMatcher mMatcherLR(true, match_conf);
	
	mMatcherLR(vImageFeatruesLR, vPairwiseMatchesLR);
	mMatcherLR.collectGarbage();
	vPairwiseMatchesLR.clear(); // <----- crash
Repository: vscode
Issue: More font options
Labels: feature-request,editor-core

A lot of people use fonts like Fira Code, which doesn't has italics. Wouldn't that be great to have options to force no_italics, no_bold, etc?
Repository: go
Issue: runtime: reuse evacuated map overflow buckets
Labels: Performance,compiler/runtime

runtime/hashmap.go contains this TODO:

```go
		// TODO: reuse overflow buckets instead of using new ones, if there
		// is no iterator using the old buckets.  (If !oldIterator.)
```

This issue is to track this TODO, and make it easier to refer to in commit messages, etc., since I am looking into some related optimizations.
Repository: vscode
Issue: [json] option to format code with leading commas
Labels: help wanted,feature-request,json,formatting

Can we get an option in VS Code to have it format all lists by using leading commas instead of trailing commas?

This would so much simplify editing code and it would also greatly simplify the IDE's automatic code completion (e.g. the VS Code Settings editor).

With the suggested option set to `true`, comma separated lists would proposedly be formatted like this:

```json
{ "workbench.iconTheme": "vs-seti"
, "editor.lineNumbers": "off"
, "editor.tabSize": 2
, "editor.insertSpaces": false
, "editor.autoClosingBrackets": false
}
```

Function calls using line wrapping for their arguments would look like this:

```js
call( 1
    , "test"
    , new Console()
    );
```

a nested sample would look like this:

```json
{ "version": "0.2.0"
, "configurations":
  [ { "type": "node"
    , "request": "launch"
    , "name": "Programm starten"
    , "program": "${file}"
    }
  , { "type": "node"
    , "request": "attach"
    , "name": "An den Port anfügen"
    , "address": "localhost"
    , "port": 5858
    }
  ]
}
```
<hr/>
This formatting style would result in much cleaner, tidier code.
<hr/>

### Moreover, adding a new property to an object would be a snap:

Either copy/paste from an existing property (=> no more syntax errors due to redundant trailing commas, see screenshot below):

![comma error](https://cloud.githubusercontent.com/assets/9283914/25074723/8e40d278-2302-11e7-94d8-d8b35d3321ce.png)

...  or create a new property and you might immediately get IntelliSense right after typing the leading comma of the property to create.
<hr/>

### The suggested formatting style is applicable to all languages
E.g. T-SQL:
```sql
CREATE TABLE
  ( id INT PRIMARY KEY IDENTITY
  , name NVARCHAR(100) NOT NULL UNIQUE CHECK(LEN(name) > 0)
  , created DATETIME NOT NULL DEFAULT(GETDATE())
  , updated DATETIME NOT NULL DEFAULT(GETDATE())
  )
```
Repository: go
Issue: crypto/x509: AKI is left blank even for non-self-signed cert when subject matches CA's subject field
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?
1.8.1
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN="/home/dev/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/dev/go"
GORACE=""
GOROOT="/usr/lib/golang"
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build983119777=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
### What did you do?
Signing any TLS certificates with a matching Subject hits the self-signed cert AKI logic, ignoring the key pairs used,  serial number, extensions, and SAN fields. This potentially leaves the AKI field blank even on non-self-signed certs.
### What did you expect to see?
The AKI field on a signed certificate should match the CA's SKI
### What did you see instead?
The AKI is left blank:
https://play.golang.org/p/MPSqzlITG7
Repository: rust
Issue: Long trait bounds don't get broken up in rustdoc
Labels: T-rustdoc,C-enhancement

Here's an example of some long bounds: [num_traits::NumAssignOps](https://docs.rs/num-traits/latest/num_traits/trait.NumAssignOps.html)

Copy-pasted here:

```rust
pub trait NumAssignOps<Rhs = Self>: AddAssign<Rhs> + SubAssign<Rhs> + MulAssign<Rhs> + DivAssign<Rhs> + RemAssign<Rhs> { }
```

Rustfmt, when given an adequately small width limit, will turn this into:

```rust
pub trait NumAssignOps<Rhs = Self>:
    AddAssign<Rhs>
    + SubAssign<Rhs>
    + MulAssign<Rhs>
    + DivAssign<Rhs>
    + RemAssign<Rhs>
{
}
```

It'd be nice if there were some way to make the rustdoc for these a bit less… awful, by default. Preferably without having to require that the user format their code accordingly.