sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: tour: Search in table of contents
Labels: Documentation,help wanted,NeedsInvestigation,FeatureRequest

Context: http://tour.golang.org/*

The tour is a good reference for quick examples, when you are not familiar with go yet. It would be useful to be able to search in the contents of the tour. At least in its table of contents.
Repository: rust
Issue: Tracking issue for `?` operator and `try` blocks (RFC 243, `question_mark` & `try_blocks` features)
Labels: B-RFC-approved,T-lang,T-libs-api,B-unstable,B-RFC-implemented,C-tracking-issue,A-error-handling,F-try_blocks,Libs-Tracked,S-tracking-design-concerns

Tracking issue for rust-lang/rfcs#243 and rust-lang/rfcs#1859.

Implementation concerns:
- [x] `?` operator that is roughly equivalent to `try!` - #31954
- [x] `try { ... }` expression - https://github.com/rust-lang/rust/issues/39849
    - [x]  resolve `do catch { ... }` syntax question
        - Resolved as `try { .. }`, - https://github.com/rust-lang/rust/issues/50412
    - [x] resolve whether catch blocks should "wrap" result value (first addressed in https://github.com/rust-lang/rust/issues/41414, now being settled anew in https://github.com/rust-lang/rust/issues/70941)
    - [ ] Add a test confirming that it's an `ExprWithBlock`, so works in a match arm without a comma
    - [ ] Address issues with type inference (`try { expr? }?` currently requires an explicit type annotation somewhere).
- [x] settle design of the `Try` trait (https://github.com/rust-lang/rfcs/pull/1859)
    - [x] implement new `Try` trait (in place of `Carrier`) and convert `?` to use it (https://github.com/rust-lang/rust/pull/42275)
    - [x] add impls for `Option` and so forth, and a suitable family of tests (https://github.com/rust-lang/rust/pull/42526)
    - [x] improve error messages as described in the RFC (https://github.com/rust-lang/rust/issues/35946)
- [x] reserve `try` in new edition
- [x] block `try{}catch` (or other following idents) to leave design space open for the future, and point people to how to do what they want with `match` instead
Repository: neovim
Issue: visual effect for operations
Labels: enhancement,gsoc

Replicated from [StackOverflow](http://stackoverflow.com/questions/35171726/is-there-visual-flash-effect-for-editing)

What we are looking is to visually flash briefly the affected areas of vim editing in normal mode. For example, when editing

``` C
if (true) {
    //line to be deleted
}
```

if we do dd on //line to be deleted, this affected area should be flashed before deleting, The same we can do using Vd. What we are looking is same effect as that of Vd using dd. This should work for all editing operations like c, y etc

May be the effect can be controlled using a configuration option
Repository: youtube-dl
Issue: francetv unable to find ID
Labels: geo-restricted

Trying to download from here:
http://television.telerama.fr/television/regardez-cargos-la-face-cachee-du-fret-ou-l-invisible-armada-de-la-mondialisation,137619.php

Which is using this iframe:
http://embed.francetv.fr/?ue=a69734825a04041ae3b51fd8b41f87f1&autoplay=1

And:

[francetv] a69734825a04041ae3b51fd8b41f87f1&autoplay=1: Downloading webpage
ERROR: Unable to extract video ID;

ID is located here: http://sivideo.webservices.francetelevisions.fr/tools/getInfosOeuvre/v2/?idDiffusion=NI_620048&catalogue=Catalogue_programmes&callback=_jsonp_loader_callback_request_0

...

```
_jsonp_loader_callback_request_0({"id":"NI_620048", ...
```

Thanks!
Repository: rust
Issue: The Vec should not needlessly overallocate capacity if it is guaranteed to fail.
Labels: C-enhancement,A-collections,T-libs-api

Current Vec / RawVec allocation strategy is to at least double the capacity on
reallocation. This leads to unnecessary panic when the new overallocated
capacity exceeds std::isize::MAX. If allocating std::isize::MAX would be
sufficient it should do so instead.

For example I would expect the following to work on 32-bit platform (provided
that there is sufficient amount of memory):

``` rust
fn main() {
    let mut v = std::vec::from_elem(1 as u8, (std::isize::MAX / 2 + 1) as usize);
    v.push(1);
}
```
Repository: vscode
Issue: Automatically Activate Markdown Preview
Labels: feature-request,markdown

I would like to eliminate the step of pressing `ctrl+k v` to preview the md file I open. For the preview should always be on.

Thank you
Repository: flutter
Issue: Make it real easy to open an issue with crash reports and logs
Labels: c: new feature,team,tool,a: triage improvements,P3,team-tool,triaged-tool

Imagine a `flutter report-bug` command. It could grab any crash report from iOS, any recent logs, the flutter version, the Dart version, and then send it off to GitHub as an issue.

We want to make it as simple as

Example UI:

```
$ flutter report-bug
Sorry you ran into trouble, but we appreciate the bug report.

This command collects potentially relevant information and opens a public bug report for the Flutter team as a GitHub issue. Please review the information before you confirm.

Flutter version: ...
Dart version: ...
OS: mac
Crash file: path/to/file
Log: path/to/file or print out what we will send

OK to make this information public as a GitHub issue? [y/N]
```
Repository: youtube-dl
Issue: site support request: www.tg4.ie
Labels: site-support-request

Sample URL: http://www.tg4.ie/ga/player/baile/?pid=4742502074001

`$ youtube-dl --version
2016.01.27`

```
$ youtube-dl -v http://www.tg4.ie/ga/player/baile/?pid=4742502074001
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.tg4.ie/ga/player/baile/?pid=4742502074001']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.01.27
[debug] Python version 2.7.6 - Linux-3.13.0-77-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv 9.18-6, avprobe 9.18-6, ffmpeg 2.5.3-1kxstudio1, ffprobe 2.5.3-1kxstudio1, rtmpdump 2.4-n87-gita9f353c-ppa8
[debug] Proxy map: {}
[generic] ?pid=4742502074001: Requesting header
WARNING: Falling back on generic information extractor.
[generic] ?pid=4742502074001: Downloading webpage
[generic] ?pid=4742502074001: Extracting information
ERROR: Unsupported URL: http://www.tg4.ie/ga/player/baile/?pid=4742502074001
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/generic.py", line 1289, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "/usr/lib/python2.7/dist-packages/youtube_dl/compat.py", line 248, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=etree.TreeBuilder(element_factory=_element_factory)))
  File "/usr/lib/python2.7/dist-packages/youtube_dl/compat.py", line 237, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
ParseError: syntax error: line 2, column 0
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 666, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 313, in extract
    return self._real_extract(url)
  File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/generic.py", line 1908, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://www.tg4.ie/ga/player/baile/?pid=4742502074001
```
Repository: rust
Issue: Add rustc --emit=link-info for staticlib link-line output
Labels: A-frontend,T-compiler,C-feature-request

When linking rust into C++ projects, I use `rustc --crate-type=staticlib` to generate a static library which I can link into the overall project. Since there's no standard for transitive dependency declaration in the C ABI for static libraries, rustc prints out a list of libraries which need to be linked along with the staticlib. (https://github.com/rust-lang/rust/issues/25820#issuecomment-106480235)

This is very helpful in development, but not ideal for automation. I propose adding an `--emit=link-info` option (`--emit=libs`? `--emit=ldflags`?) to write the required link line out to a file for use later, similar to `--emit=dep-info` for makefile dependency generation.

Order of evaluation is a little trickier than with dep-info since it has to work the first time, but this should simplify funky stderr hacks like

``` make
libfoo.a libfoo.a.out: foo/lib.rs
    rustc -g --crate-type staticlib --crate-name foo \
      --emit dep-info,link=$@ $< \
      2> $@.out || cat $@.out >&2
-include foo.d

prog: RUST_LIBS = $(shell awk '/^note: library: / {print "-l"$$3}' libmp4parse.a.out)
prog: prog.o libfoo.a
    $(CXX) $(CXXFLAGS) -o $@ $^ $(RUST_LIBS)
```

into

``` make
libfoo.a libfoo.a.link: foo/lib.rs
    rustc -g --crate-type staticlib --crate-name foo \
      --emit dep-info,link=$@,link-info=$@.link $<
-include foo.d

prog: prog.o libfoo.a
    $(CXX) $(CXXFLAGS) -o $@ $^ $(shell cat libfoo.a.link)
```
Repository: youtube-dl
Issue: Site support request: cops.com
Labels: site-support-request

Hello,

Could you add cops.com as a supported website? They seem to break full episodes into separate clips for showing advertisements in-between.

Example of a full episode: http://www.cops.com/cops2805/

Thanks.
Repository: neovim
Issue: python remote plugin: warn when file doesn't export handlers
Labels: enhancement,provider,complexity:low

While developing a Python3 plugin for neovim, I used a directory structure like this:

```
.
├── requirements.txt
├── rplugin
│   ├── __init__.py
│   └── python3
│       ├── myplugin.py
│       ├── __init__.py
└── tests
    ├── __init__.py
    ├── myplugin_tests.py
```

When I attempted to use `vim-plug` to load the plugin from the filesystem and called `UpdateRemotePlugins`, I got the following error in the nvim python log:

```
2016-02-08 00:32:52,269 [ERROR @ host.py:_load:94] 2780 - /home/siddharthist/[...]/rplugin/python3/__init__.py exports no handlers
```

The expected behavior is that neovim would only warn or silently ignore python files that don't export handlers, because there are lots of valid use cases for having another non-plugin python file in the same directory as the plugin file. 

I fixed it in my case by renaming `myplugin.py` to `__init__.py`. 

What do you all think? 
### Extra Info

I'm using Arch Linux,

```
$ nvim --version
NVIM 0.1.1 (compiled Jan 22 2016 15:40:18)
Build type: RelWithDebInfo
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -Wconversion -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/build/neovim/src/build/config -I/build/neovim/src/neovim-0.1.1/src -I/usr/include -I/usr/include -I/usr/include/luajit-2.0 -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/build/neovim/src/build/src/nvim/auto -I/build/neovim/src/build/include
Compiled by builduser

Optional features included (+) or not (-): +acl   +iconv    +jemalloc 
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"
```
Repository: go
Issue: doc: add guidance on new vs. literal usage
Labels: Documentation,NeedsInvestigation

One thing I observed with new gophers, is having trouble judging is when to use `new` and when to take the address of struct literal.

Adding a bit of guidance in the wiki or effective_go.html would be quite useful.

Suggestion for guidance:
- prefer the literal
- if you don't initialize the struct with values, use new
- if you did use new, don't initialize values later, prefer switching the code to a literal instead.
Repository: electron
Issue: [Enhancement] Applescript API
Labels: enhancement :sparkles:

Is it possible to have an Applescript API for Mac apps made with Electron?
Repository: go
Issue: runtime: _cgoCheckPointer0 extreme overhead
Labels: compiler/runtime

1. What version of Go are you using (go version)?
   go1.6rc2
2. What operating system and processor architecture are you using?
   linux/amd64
3. What did you do?
   Call C code with cgo.
4. What did you expect to see?
   Almost the same performance with GODEBUG=cgocheck=1 and GODEBUG=cgocheck=0.
5. What did you see instead?
   22 times more running time with GODEBUG=cgocheck=1 than with GODEBUG=cgocheck=0.

The overhead is 22x in [practice](https://groups.google.com/forum/#!topic/golang-nuts/ccMkPG6Bi5k) and 36000 in this contrived example:

$ GODEBUG=cgocheck=1 go test -bench=. -run=-
testing: warning: no tests to run
PASS
BenchmarkCGO-4        50          28792524 ns/op
ok      github.com/tgulacsi/go/cgo22    1.855s
:gthomas@waterhouse: ~/src/github.com/tgulacsi/go/cgo22
$ GODEBUG=cgocheck=0 go test -bench=. -run=-
testing: warning: no tests to run
PASS
BenchmarkCGO-4   2000000               796 ns/op
ok      github.com/tgulacsi/go/cgo22    2.988s
:gthomas@waterhouse: ~/src/github.com/tgulacsi/go/cgo22

The code is at https://github.com/tgulacsi/go/tree/master/cgo22

[cgo22.zip](https://github.com/golang/go/files/122255/cgo22.zip)
Repository: vscode
Issue: Support variables when resolving values in settings
Labels: feature-request,config

Hi,

I was just reading the [latest updates](https://code.visualstudio.com/updates) and it says one can install `typescript@next` globally and then set `typescript.tsdk` so VS Code can use the appropriate version/installation. In a team environment, I'd like to put that setting in our project, something like:

`.vscode/settings.json`:

``` json
{
    "typescript.tsdk": "%APPDATA%/npm/node_modules/typescript/lib"
}
```

The problem is restarting VS Code results in an error:

```
The path c:\Projects\Derp\%APPDATA%\npm\node_modules\typescript\lib doesn't point to a valid tsserver install. TypeScript language features will be disabled.
```

Now the setting needs to be per-person because I highly doubt my teammates have `tsc` installed in `C:\Users\Olson\AppData\Roaming\npm\node_modules\typescript\lib` :wink:

Could we get environment variables evaluated on that and all other settings that involve paths?

I haven't tested other paths, but I see these in the Default Settings:
- `git.path`
- `markdown.styles`
- `json.schemas`
- `typescript.tsdk`
- `php.validate.executablePath`
Repository: rust
Issue: Guard pages are disabled on musl.
Labels: O-musl,C-bug,A-stack-probe

In #30629 I [disabled guard pages on musl](https://github.com/rust-lang/rust/pull/30629/files#diff-1a00e90827d8a240091012902881fdc4R184). I did this because one of the pthread calls (I've forgotten which) was segfaulting during runtime initialization on i686-unknown-linux-musl, with my local build of musl, and I just wanted it working.

It should at least be on for x86_64 where it's known to work on the bots.
Repository: rust
Issue: Specifying linkage on externs silently removes indirection
Labels: A-linkage,A-codegen,T-compiler,C-bug,requires-nightly

When compiling the following code:

``` c
// externs-c.c
unsigned char myarr[10]={1,2,3,4,5,6,7,8,9,10};
unsigned char (*implicitvar)[10]=&myarr;
unsigned char (*explicitvar)[10]=&myarr;
```

``` rust
// externs-rust.rs
#![feature(linkage)]

extern {
    static implicitvar: *const [u8;10];
    // Should have no effect, external linkage is the default in an extern block
    #[linkage="external"]
    static explicitvar: *const [u8;10];
}

fn as_option(p: *const [u8;10]) -> Option<&'static [u8;10]> {
    unsafe{std::mem::transmute(p)}
}

fn main() {
    println!("implicitvar = {:?}",as_option(implicitvar));
    println!("explicitvar = {:?}",as_option(explicitvar));
}
```

using

```
clang -c externs-c.c && rustc externs-rust.rs -C link-args=./externs.o
```

running `./externs` will output something like the following:

```
implicitvar = Some([1, 2, 3, 4, 5, 6, 7, 8, 9, 10])
explicitvar = Some([168, 4, 122, 85, 85, 85, 0, 0, 0, 0])
```

Wat.

Taking a look at the IR:

``` llvm
; externs-c.ll
@myarr = global [10 x i8] c"\01\02\03\04\05\06\07\08\09\0A", align 1
@implicitvar = global [10 x i8]* @myarr, align 8
@explicitvar = global [10 x i8]* @myarr, align 8
```

``` llvm
; externs-rust.ll
@implicitvar = external global [10 x i8]*
@explicitvar = external global [10 x i8]
@_rust_extern_with_linkage_explicitvar = internal global [10 x i8]* @explicitvar
```

So, Rust removes a layer of indirection defining `static explicitvar: [u8;10]` and adding a new variable `static _rust_extern_with_linkage_explicitvar: *const [u8;10]=&explicitvar`. All mentions of `explicitvar` in Rust source code get replaced with `_rust_extern_with_linkage_explicitvar`. This results in the C version and this new Rust version **not having the same type**! To get “correct” behavior in the example above, you would need to define `static explicitvar: *const *const [u8;10]` instead.

This weird assymmetry between the types associated with symbols in Rust and in C is a source of great confusion and can easily lead to bugs. In the example above, we just read 2 bytes past some pointer by interpreting it as a 10-byte array.

This weird behavior was introduced in #12556 (see also #11978), the rationale being weak linkage and the fact that some pointers can't be null in the Rust typesystem. While true, I don't think that's sufficient rationale to add this layer of indirection. I think the layer of indirection should be removed completely. For weak linkage, a restriction can be added to allow only zeroable types.
Repository: opencv
Issue: cvUndistortPoints returns imprecise results
Labels: feature,category: imgproc

cvUndistortPoints calculates the result iteratively. Currently, the number of iterations is five (hardcoded), which is not enough to get the correct result.
Repository: opencv
Issue: buildPyramid segfaults  with Clang
Labels: incomplete

Following test program segfaults if compiled with Clang:

```
#include <opencv2/opencv.hpp>
#include <vector>

int main() {
        cv::Mat  I(1000,1000,CV_8UC1);
        std::vector<cv::Mat>  P; 
        cv::buildPyramid(I, P, 30);
        return P.size();
}
```

clang --version
Ubuntu clang version 3.6.2-1 (tags/RELEASE_362/final)

cat /etc/os-release 
NAME="Ubuntu"
VERSION="15.10 (Wily Werewolf)"

OpenCV sources from github at tag 3.1.0
compile config: 
 cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local  -D BUILD_EXAMPLES=ON -D INSTALL_C_EXAMPLES=ON -D INSTALL_PYTHON_EXAMPLES=ON -D BUILD_NEW_PYTHON_SUPPORT=ON -D WITH_V4L=ON -D WITH_QT=ON -D WITH_OPENGL=ON -D WITH_CUDA=OFF -D WITH_IPP=OFF  .
Repository: rust
Issue: Named functions don't implement Debug
Labels: A-type-system,T-lang,C-feature-request,T-types

Trying to compile (https://play.rust-lang.org/?gist=3b38f384f0f7ddecc142&version=stable):

```
fn foo() {}
fn main() {
    println!("{:?}", (foo as fn())); // Works
    println!("{:?}", foo);   // Fails
} 
```

It seem that named functions have to be coerced to anonymous ones in order to implement `Debug`. This means any structs containing functions don't derive `Debug`, which makes unit testing tricky.
Repository: go
Issue: go/build: Import seems to require absolute srcDir
Labels: FrozenDueToAge

While investigating go/types issue https://github.com/golang/go/issues/14215, I noticed that (after fixing the obvious go/types bug), build.Import didn't find the desired package if srcDir was relative. Computing its absolute path (relative to cwd) fixed the problem.

Reminder to investigate behavior. Fix and/or document.
Repository: youtube-dl
Issue: Improve regression detection with continous testing
Labels: request

It seems the youtube-dl project has abandoned the idea of using tests with travis-ci to keep all IEs always working (last passed build was 2 years ago, [#2571](https://travis-ci.org/rg3/youtube-dl/builds/99421929)). Not that it's a bad idea, since it's hard to keep up with all those sites. But a side effect of that is that it's harder to detect test fails that are due to a new commit, and not a website change.

What's I'd like to propose, is to keep the current testing infrastructure as a dashboard for working/non-working IEs, and add another "testsuite" that would test each commit for regressions: if a test is failing, the previous commit would be tested as well, and if it fails, it's not considered a regression.

I've made a simple proof of concept https://gist.github.com/anisse/6093f8b5814ab3ce7140 in bash. This could be improved/rewritten, in order to be integrated with travis-ci.

What do you guys think ?
Repository: opencv
Issue: LineIterator is missing from Java bindings
Labels: feature,priority: low,category: java bindings

Title says it all. I now have to implement my own Bresenham algorithm.
Repository: TypeScript
Issue: JSX: a way to make all the properties of value-based elements optional
Labels: Suggestion,In Discussion

It's not documented, but currently, if the `JSX.ElementAttributesProperty` interface is declared empty,

``` ts
declare namespace JSX { interface ElementAttributesProperty {} }
```

then the _element attributes type_ becomes same as the _element instance type_. However, if the element instance type is a class, this leads to a situation where the compiler requires that all the members of the class be represented as attributes since they're not optional (and even cannot be marked as such as the class syntax doesn't allow optional members).

``` ts
class MyComponent {
  myProp: string;
  private myMethod(): void;
}
var a = <MyComponent myProp='value'/>;
// error: Property 'myMethod' is missing in type MyComponent
```

This prevents me from using JSX for type-checking Angular 1 templates (you can find my experiments in this area [here](https://github.com/thorn0/babel-plugin-transform-ng1-jsx)).

What if we introduce some way to tell the compiler that not all the properties are required, but only some of them? E.g. those having a certain decorator?

A related issue: #5151
Repository: go
Issue: cmd/asm: accepts MOVB (BX)(R8*4), AH incorrectly
Labels: NeedsFix,compiler/runtime

`MOVB (BX)(R8*4), AH`
The assembler accepts this instruction but silently misassembles it to:
`MOVB (BX)(R8*4), SP`
This is because we need the RAX prefix for the indexed address, but then the RAX prefix also forces the use of standard register naming instead of the weird *H register naming.

gas rejects this instruction `movb (%rbx,%r8,4),%ah` with `can't encode register '%ah' in an instruction requiring REX prefix.`

@rsc