sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: :help viewer should support markdown (or markdoc)
Labels: enhancement,documentation

Hey Team ! 

**TL;DR** : 
Started porting helpfiles to rst and md formats. Repo is at : https://github.com/Pychimp/neovim-docs

---
#### Better Explanation:

So, I have started to port the help files to both rst and md formats. 
I have cloned the main neovim/docs [repo](https://github.com/neovim/docs/commit/dc9d7ee48861a7102c50e4a34e2c7d39d5f20ade) (after @rjw57 latest PR was merged in)

As @tarruda had mentioned in #106, He wanted to keep the original format. So, what I plan to do, is to convert the help files to rst and md on seperate branches, and then send a PR to the main neovim/docs repo. 

(Meaning, Even after my PR would be merged (Hopefully ! :smile:), The original *.txt **will be** as they are on the master branch, while the converted ones will be on their **own and respective** branches)
## 

Reasons:
- The original help format used currently in vim (with `*<tag>*` and `|<tag>|`) is great, and _we_ can stick with those...
- Alternatively, as @Gaelan [mentioned](https://github.com/neovim/neovim/issues/106#issuecomment-35960969), neovim might be able to render out the docs easily (just the way, vim seems to do with the current help format). 

> Why two formats (rst and md), can't you make simply one and then, once that is approved merge it in to main ?

Well ... The thing is we had a (long) bit of discussion (like this: #207), and I didn't want to waste the team's time by having a flame war like that, which is why I'll make them into rst and md formats. After some time, Should the team decide to choose one format over the other, the rejected one can be dropped off, and the selected one will continue to develop. 

(Plus, I might have some time to kill, and I'm bad at C :sweat_smile: (the C code in this repo does look scary), So, I thought I might help out like this.)

Please feel free to discuss and let me know, what you guys think ! :smile: 

Link to my repo : https://github.com/Pychimp/neovim-docs
Repository: neovim
Issue: :source CRLF (fileformat=dos / ^M line endings) VimL on non-unix
Labels: enhancement,vimscript

I copied over my `.vimrc` to `.neovimrc` then git cloned @Shougo's NeoBundle for plugin management, which has files in it that are `fileformat=dos` and neovim throws these errors on startup:
http://hastebin.com/rixaxefofe.lua

For reference, here's the neobundle.vim file it mentions:
https://github.com/Shougo/neobundle.vim/blob/master/plugin/neobundle.vim

Basically, this is my `.vimrc` file:
https://gist.github.com/trusktr/6956110

The only change I made to it when copying to `.neovimrc` is to change .vim to .neovim on line 9.

The rc automatically creates the needed directories if they don't exist (e.g. `~/.neovim`, `~/.neovim/swap`, etc), clones NeoBundle, then let's NeoBundle install/initiate all the listed plugins, then sets some custom mappings and settings.

Works perfectly in Vim, but not NeoVim.

@Shougo, does NeoBundle work for you in NeoVim?
Repository: bitcoin
Issue: Clients leak IPs if they are recipients of a transaction
Labels: Wallet,Privacy

So, this paper http://ifca.ai/fc14/papers/fc14_submission_71.pdf got me thinking about the current rules for transaction rebroadcasting:

Once a transaction has been broadcast, you stop rebroadcasting. Unless you own txins or txouts in the transaction. 

So, you use the paper's techniques. But you can be much more speculative than they are, and get a low-likelihood but possible IP match for an address, connect your client up, and issue a transaction paying yourself and a small amount to the address you're interested in, just over the dust amount.

The transaction should be constructed so it's unlikely to be mined.

The transaction traverses the network, then it stops being rebroadcast, _except_ by the recipient and you. If your client is connected to the wallet that owns the address, it will see rebroadcasting for some time, providing a very strong link between the two.

This seems like a bad outcome. 

I speculate that the 1Sochi transactions may have this motivation -- mapping addresses to determine IPs at large in Bitcoin. 

It seems like the simplest thing would be to not re-re-broadcast to clients you've already spoken to, but I'll wait for smarter people than me to work out the right fix.
Repository: youtube-dl
Issue: Save source link in extended attribute (Mac)
Labels: request

Browsers on the Mac set a "Where From" attribute on downloaded files. Files also have a comments field, where some people put a URL.

I implemented the latter as an external tool, and would integrate it into youtube-dl _if it has any chance to be accepted_. The former wouldn't be a problem, either.
Repository: react
Issue: iframe contents cause invariant violation
Labels: Type: Bug,Component: DOM

When using server rendering, putting an `<img>` in an `<iframe>` seems to invariably cause an invariant violation (it can't find the image).

This is related to #1252, but not identical. In both cases, the browser isn't aware of the inner elements however, in this case, it's because browsers that support iframes are actually mutating the DOM (by replacing the contents with the document specified in the `src` attribute).
Repository: react
Issue: Stop doing data-*, aria-*, start using dataSet
Labels: Type: Feature Request,Component: DOM,Resolution: Backlog,Partner

The DOM already exposes `data-*` as `dataset` but it's doing transformation from hyphenated to camelCase. [From MDN](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement.dataset):

```
<div id="user" data-id="1234567890" data-user="johndoe" data-date-of-birth>John Doe
</div>

var el = document.querySelector('#user');

// el.id == 'user'
// el.dataset.id === '1234567890'
// el.dataset.user === 'johndoe'
// el.dataset.dateOfBirth === ''

el.dataset.dateOfBirth = '1960-10-03'; // set the DOB.

// 'someDataAttr' in el.dataset === false

el.dataset.someDataAttr = 'mydata';
// 'someDataAttr' in el.dataset === true
```

We should just start supporting `dataSet` (because camelCase). This will allow a couple things:
- easier reasoning about data attributes (`Object.keys(this.props.dataSet)`)
- easier merging (`<div dataSet={merge(this.props.dataSet, {extra: 'value', override: 'value'})} />`)
- easier (potentially faster?) updates (just modify `node.dataset`)

We'll want to do the reverse of what the DOM is doing. eg `<div dataSet={{dateOfBirth: 'val', foo: 'bar'}} />` becomes `<div data-date-of-birth="val" data-foo="bar"></div>`.

To the best of my knowledge, `aria-*` doesn't have a corresponding API, but we should make it work the same way. I think `ariaSet` makes sense.
Repository: rust
Issue: Private items with a public reexport could suggest the public path in privacy error message
Labels: C-enhancement,A-diagnostics,A-resolve,T-compiler

E.g. `use std::io::buffered::BufferedReader;` says `struct BufferedReader is private` but could say 

```
struct BufferedReader is private, but available publicly as `std::io::BufferedReader`
```

(This probably requires some significant work, for not a _huge_ benefit.)
Repository: youtube-dl
Issue: Suggestion option to dump only result, viz id, artist-title or error
Labels: request

While downloading a playlist one may encounter several issues such:
- one's artist-title does not correspond to the ouput
- errors

Those are very insteresting information, but a matching between the returned information from youtube-dl and your own can be lenghty process.

I propose to have an option (say -d summaryLog.txt) to dump a summary log unicode or UTF-8 text file with the following structure, for each videoID a single line as:
video_ID; either output name or occurred error

So instead of for instance:
F:\Youtube Extract\Russian>youtube-dl nG647q4Obds
[youtube] Setting language
[youtube] nG647q4Obds: Downloading webpage
[youtube] nG647q4Obds: Downloading video info webpage
[youtube] nG647q4Obds: Extracting video information
[youtube] nG647q4Obds: Encrypted signatures detected.
[download] Destination:  - -nG647q4Obds.mp4
[download] 100% of 5.08MiB in 00:05

One would have:
nG647q4Obds; Инфинити - Таю-nG647q4Obds

Thanks
Repository: youtube-dl
Issue: [FranceTV] france5.fr playlists
Labels: request

Hello,

Youtube-dl doesn't know what to do on a playlist/show page, because the URL does not contain an ID. We could add a way to download all the videos of the show.

```
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://www.france5.fr/emissions/l-oeil-et-la-main', '-v']
[debug] Encodings: locale 'UTF-8', fs 'UTF-8', out 'UTF-8', pref: 'UTF-8'
[debug] youtube-dl version 2014.03.27.1
[debug] Python version 2.7.3 - Linux-3.2.0-4-amd64-x86_64-with-debian-7.4
[debug] Proxy map: {}
[francetv] l-oeil-et-la-main: Downloading webpage
ERROR: Unable to extract video ID; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 509, in extract_info
    ie_result = ie.extract(url)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 161, in extract
    return self._real_extract(url)
  File "./youtube-dl/youtube_dl/extractor/francetv.py", line 166, in _real_extract
    video_id = self._html_search_regex(id_res, webpage, 'video ID')
  File "./youtube-dl/youtube_dl/extractor/common.py", line 369, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 359, in _search_regex
    raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video ID; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
```

Regards,
Repository: youtube-dl
Issue: Please support triart.se
Labels: site-support-request

$ youtube-dl --verbose http://www.triart.se/bio/article90562.ece
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.triart.se/bio/article90562.ece']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.03.30.1
[debug] Python version 2.7.6 - Linux-3.13-1-amd64-x86_64-with-debian-jessie-sid
[debug] Proxy map: {}
[generic] article90562: Requesting header
WARNING: Falling back on generic information extractor.
[generic] article90562: Downloading webpage
[generic] article90562: Extracting information
ERROR: Unsupported URL: http://www.triart.se/bio/article90562.ece; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 379, in _real_extract
    doc = parse_xml(webpage)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1315, in parse_xml
    return xml.etree.ElementTree.XML(s.encode('utf-8'), **kwargs)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1300, 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: mismatched tag: line 34, column 119
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 511, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 161, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 612, in _real_extract
    raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://www.triart.se/bio/article90562.ece; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Repository: rust
Issue: Tracking Issue for auto traits (auto_traits) -- formerly called opt-in built-in traits (optin_builtin_traits)
Labels: A-type-system,A-trait-system,P-medium,B-RFC-approved,T-lang,B-unstable,B-RFC-implemented,C-tracking-issue,F-auto_traits,S-tracking-perma-unstable,T-types

This is the tracking issue for [**RFC 19**](https://github.com/rust-lang/rfcs/blob/master/text/0019-opt-in-builtin-traits.md).

## Checklist

Here is a check-list of code to write and tricky scenarios to be sure we handle:
- [ ] forbid conditional negative impls [as described here](https://gist.github.com/nikomatsakis/bbe6821b9e79dd3eb477#negative-reasoning-from-oibit-and-rfc-586)
- [x] conditional negative impls not properly enforced https://github.com/rust-lang/rust/issues/23072
- [x] `impl !Pod for ..` should not be legal https://github.com/rust-lang/rust/issues/28475
- [x] fix feature-gate for `impl Foo for ..` https://github.com/rust-lang/rust/issues/23225
- [x] defaulted traits ought to be have more restrictive coherence rules https://github.com/rust-lang/rust/issues/22978
- [x] defaulted traits should have no methods #23080 / https://github.com/rust-lang/rust/pull/23117
- [x] Add parser support for `impl Foo for ..`
- [x] Port `Send/Sync` to use new infrastructure internally
- [x] Add `unsafe impl Send for ..` / `unsafe impl Sync for ..` 
- [x] Object types should never match against a defaulted trait (though the object type itself may add a candidate for traits that appear in the object type)
- [x] When a defaulted trait matches, it should impose any supertrait bounds on the matched type as nested obligations
- [x] Be wary of type inference -- if we haven't resolved a type yet, we have to be ambiguous
- [ ] Systematic testing for `constituent_types`
- [x] Coherence interaction: a defaulted trait can only be implemented for structs/enums
- [x] Coherence interaction: a trait can only be defaulted in the crate where it is defined
- [x] Coherence interaction: a trait can only be defaulted once
- [x] Coherence interaction: an auto-trait can be redundantly implemented for an object that has it - #56934
- [x] Defaulted impls cannot be generic
- [x] Fix the interaction with PhantomData. OIBIT should treat PhantomData<T> as if there were an instance of T reachable rather than breaking it down like it would a different struct. https://github.com/rust-lang/rust/pull/23091
- [x] Allow negative implementations for traits that have a default implementation (besides Send/Sync).
- [x] https://github.com/rust-lang/rust/issues/104808 lifetimes on auto traits are buggy
- [x] Coherence rules: is `impl AutoTrait for dyn Trait` legal? https://github.com/rust-lang/rust/issues/13231#issuecomment-1397480267
- [x] Interaction with dyn safety. https://github.com/rust-lang/rust/pull/107082
- [x] Do `[u8]` negative impls affect `str`. https://github.com/rust-lang/rust/issues/13231#issuecomment-1399386472
Repository: react
Issue: touchmove doesn't fire on removed element
Labels: Type: Enhancement,Component: DOM,Partner

If you have

```
{this.state.show &&
  <div onTouchStart={this.hideTheDiv} onTouchMove={...} />}
```

such that the onTouchStart handler removes the div (and maybe replaces it with another one in the same place, useful in certain draggable interactions), the onTouchMove handler doesn't fire because the events of a detached element no longer bubble to document. We should probably bind the touchmove handler when the element receives touchstart instead of delegating to document.

Sort of related to #1254.

cc @merbs @eater
Repository: electron
Issue: Headless version for testing
Labels: enhancement :sparkles:

@zcbenz how much work do you think it would be to create a headless version of atom-shell that could be used as a replacement for [phantomjs](http://phantomjs.org/)?

phantomjs is lagging behind more and more from what actual web browsers do today and it would be great to have something more up to date to use for headless testing.
Repository: nvm
Issue: reference $HOME in $PROFILE addition rather than hard-coding $NVM_DIR
Labels: feature requests,installing nvm: profile detection

I recently had to make this change when `$HOME` changed.

``` diff
-[ -s "/Users/michael/.nvm/nvm.sh" ] && . "/Users/michael/.nvm/nvm.sh" # This loads nvm
+[ -s "$HOME/.nvm/nvm.sh" ] && . "$HOME/.nvm/nvm.sh" # This loads nvm
```

Trying to reinstall nvm failed to fix the path differences because it simply looks for `nvm.sh` in `$PROFILE`.
Repository: rust
Issue: Line-based breakpoints in inline functions don't show correct source
Labels: A-debuginfo,P-medium,T-compiler,C-bug

``` rust
#[inline(always)]
fn bar() -> int {
    5
}

fn main() {
    let _ = bar();
}
```

```
(gdb) break inline.rs:3
Breakpoint 1 at 0x404e80: file inline.rs, line 3.
(gdb) r
Starting program: /tmp/inline 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Breakpoint 1, inline::main () at inline.rs:6
6   fn main() {
(gdb) 
```
Repository: rust
Issue: `-Zunpretty=expanded` does not preserve hygiene
Labels: A-pretty,P-low,T-compiler,C-feature-request,requires-nightly,A-hygiene

rustc internally converts `for val in iter { ... }` to:

``` Rust
match &mut iter {
    i =>
    loop  { match i.next() { None => break , Some(val) => { ... } } }
}
```

where `i` is created by `let local_ident = token::gensym_ident("i");`, so `i` does not clash with other local variables.

However, pprust just prints it as plain `i`. So the following code:

``` Rust
let mut i: int = 0;
for _ in iter {
    i += 1;
}
```

is prettified by rustc as:

``` Rust
let mut i: int = 0;
match &mut iter {
    i =>
    loop  { match i.next() { None => break , Some(_) => { i += 1; } } }
}
```

which is not correct anymore.
Repository: neovim
Issue: Bidi language support
Labels: enhancement,localization

The biggest problem with Vim for right-to-left languages like Persian(Farsi), Arabic, Hebrew and Urdu is that Vim doesn't support them! :( Please add some bidi to #Neovim and save us!
Repository: nvm
Issue: How to update nvm
Labels: feature requests

If nvm has a command that will update himself, it will be more awesome. Now the method i know is remove nvm and reinstall, but this will set all my node reinstall
Repository: rust
Issue: Consider aggressively avoiding generating memcpys for moves if we can avoid it
Labels: I-slow,C-enhancement,A-codegen,T-compiler,A-mir-opt,A-mir-opt-nrvo

Given that our assembler output tends to have a lot of moves in it and LLVM is bad at optimizing them out, I'm beginning to wonder if we shouldn't take more aggressive steps. For example:
- Convert (non-POD?) by-value move parameters in the Rust ABI to be passed by reference.
- Non-immediate values that go dead by dint of being moved into a new place should not be memcpy'd there.

Any others?
Repository: neovim
Issue: Improve large files support
Labels: enhancement,performance,needs:design,gsoc

Currently vim loads the whole file into memory, which is bad idea for some files. I think we should consider reworking memfile,regexp engine and all related code to allow editing files that do not fit into the available memory.
At this time it means that all API functions should be designed as if files are all impossible to load into memory (e.g. you cannot request a piece of file without specifying maximum length you can accept). On VimL side this will result in adding string-pretending lua objects that may be returned by getline()/@c/... and that actually use file positions + binary diffs (API must have FileChangeWritten hooks providing all necessary information) with a warning that editing file (but _not_ appending to it) outside of vim may result in changing some "strings". It is better to create infrastructure for handling this on new VimL side right now.

An idea for API: getline() C implementation should look like

```
typedef struct {
    fpos_t start;  // First byte position
    fpos_t end;    // Last byte position
    size_t len;    // Length of the next field
    char string[1];
} FileString;
```
Repository: rust
Issue: Compile ignored tests rather than skipping
Labels: A-testsuite,E-hard,C-enhancement,T-compiler,A-compiletest,E-tedious,E-needs-design

Ignored tests:

Lack of support in codegen for closures/generics are always inline:
 - [ ] `src/test/codegen-units/item-collection/cross-crate-closures.rs`
 - [ ] `src/test/codegen-units/item-collection/non-generic-closures.rs`
 - [ ] `src/test/codegen-units/partitioning/methods-are-with-self-type.rs`


This compile successfully, but it should fail:
 - [ ] `src/test/ui/lint/dead-code/closure-bang.rs`
Repository: neovim
Issue: Is the nfa regex engine slow?
Labels: performance

I'm not sure what's causing this, almost surely a plugin, but neovim freezes a lot for me. So I'm opening this issue here to get to the bottom of it when I have time. 

I tried looking at it through Xcode instruments. In these periods of heavy activity (i.e.: freezing), the nfa regex engine manages to allocate and free no less than 134GB of memory. $(deity) vim, have you never heard of a scratch buffer?!

I'm thinking the offending plugin is [vim-easytags](https://github.com/xolox/vim-easytags), which periodically runs ctags and highlights recognized symbols. This is some nice functionality that I don't want to give up, but it's triggering some pathological behaviour. Perhaps @xolox could chime in (for reference @xolox, neovim doesn't support python yet, that's going to come later). The freezing only happens whenever I move around in the buffer (which is one of the most useful things I do in vim).

Here's some screenshots of instruments measuring both CPU usage and memory, where we can see that one CPU side it's more `vim_free` having difficulty keeping up with the massive amount of free'ing going on:

![screen shot 2014-04-29 at 15 58 04](https://cloud.githubusercontent.com/assets/189413/2829704/7c0271b4-cfa6-11e3-805c-402380563d5f.png)
![screen shot 2014-04-29 at 15 51 44](https://cloud.githubusercontent.com/assets/189413/2829710/89fc0d34-cfa6-11e3-9dad-903484d52532.png)

<bountysource-plugin>

---

Want to back this issue? **[Place a bounty on it!](https://www.bountysource.com/issues/1892448-is-the-nfa-regex-engine-slow?utm_campaign=plugin&utm_content=tracker%2F461131&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F461131&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Repository: youtube-dl
Issue: Write to --download-archive if date is not in range or matched reject pattern
Labels: request

My proposal is to add some option like --write-anyway that would write the ID to the download archive folder. This way in future operations, would be processed faster because it would not need to open connection and would skip it locally.

Thank you for your great job