id
int64 393k
2.82B
| repo
stringclasses 68
values | title
stringlengths 1
936
| body
stringlengths 0
256k
⌀ | labels
stringlengths 2
508
| priority
stringclasses 3
values | severity
stringclasses 3
values |
|---|---|---|---|---|---|---|
213,971,283 | vscode | Add padding when pressing space between a pair of curly braces | When I type `{` to create a pair of curly braces:
```
{}
```
...and then when I press space, I would like 2 spaces to be inserted with the cursor in the middle:
```
{ | }
^ cursor
```
Currently it just inserts a single space, so getting the same result requires pressing space twice then the back arrow once. Or otherwise setting:
```
"javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": true
// or "typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": true
```
...then formatting the line once there's already stuff inside it.
I believe pressing space between a pair of brackets with nothing between them (`{}`) is more-or-less an unambiguous signal (in pretty much any language) that the user intends to have a padding space at both ends. It's also very similar to the already-covered case where someone instead presses enter to produce:
```
{
| <- cursor
}
```
In Sublime Text I was able to add the functionality myself using a keybinding that looked (in their format) like:
```
{ "keys": ["space"], "command": "insert_snippet", "args": {"contents": " $0 "}, "context":
[
{ "key": "selection_empty", "operator": "equal", "operand": true, "match_all": true },
{ "key": "preceding_text", "operator": "regex_contains", "operand": "\\{$", "match_all": true },
{ "key": "following_text", "operator": "regex_contains", "operand": "^\\}", "match_all": true }
]
}
```
...but in VS Code there doesn't seem to be enough functionality available to add a keybinding like this - I can insert a snippet but can't see anything that would allow me to limit the context to the inside of a pair of brackets.
If someone points me to the place in the codebase where the similar behavior for pressing "enter" is defined, I might be able to open a PR myself. | feature-request,editor-autoclosing | high | Critical |
213,998,156 | youtube-dl | Allow filtering out payment required videos | cannot download full video of http://www.le.com/ptv/vplay/2061436.html?ch=baiduald_ffdy
this is an vip video, youtube-dl can only download the first 10min of the video .
If cannot download the full video, then this behavior doesn't make much sense, better to remove the behavior . | request | low | Minor |
214,094,391 | youtube-dl | 3player error msg "Unsupported url" for various videos downloadable a few days ago | ## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.03.10*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.10**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [x] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
[C:\Documents and Settings\adult\Local Settings\Temp\6\wget-1.16]youtube-dl --ve
rbose http://www.tv3.ie/3player/show/1131/121878/0/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'http://www.tv3.ie/3player/show/1131/12
1878/0/']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.03.10
[debug] Python version 3.4.4 - Windows-XP-5.1.2600-SP3
[debug] exe versions: none
[debug] Proxy map: {}
[generic] 0: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 0: Downloading webpage
[generic] 0: Extracting information
ERROR: Unsupported URL: http://www.tv3.ie/3player/show/1131/121878/0/
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpj3l3ckzu\bu
ild\youtube_dl\YoutubeDL.py", line 761, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpj3l3ckzu\bu
ild\youtube_dl\extractor\common.py", line 427, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpj3l3ckzu\bu
ild\youtube_dl\extractor\generic.py", line 2648, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: http://www.tv3.ie/3player/sh
ow/1131/121878/0/
[C:\Documents and Settings\adult\Local Settings\Temp\6\wget-1.16]
### Description of your *issue*, suggested solution and other information
Hi
Last week I was able to download some videos from the 3player online catchup service for Ireland's tv3 free-to-air channel, but yesterday every link I tried (including some that worked perfectly last week) came back with the "unsupported url" error msg. The same error occurs now with the previously-successful versions of youtube-dl too so maybe in the last day or two tv3 / 3player have changed something to block it.
Thanks in advance for your help :)
| site-support-request | low | Critical |
214,153,091 | youtube-dl | Add support for TheSurfNetwork | ### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.03.10*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.10**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [x] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: http://www.thesurfnetwork.com/watch/75808a1a85aa339c85a5244386e6c82defb4b76458f9675f/trailer
- Single video: http://www.thesurfnetwork.com/detail/75808a1a85aa339c85a5244386e6c82defb4b76458f9675f/movie
---
### Description of your *issue*, suggested solution and other information
I'd like to make a request for thesurfnetwork.com please, thank you. It's account needed and pretty simple to download I think as I can download with Flash Video Downloader extension for Chrome. The reason I asking to download here is when I download with FVD the output file is not the best, but with youtube-dl the output file is perfect! | geo-restricted,account-needed | low | Critical |
214,189,787 | nvm | nvm install node error | When I input nvm install node
result is:
`grep: brackets ([ ]) not balanced
awk: nonterminated character class v0.12.18
input record number 1, file
source line number 3
Version 'node' not found - try nvm ls-remote to browse available versions.`
I uninstalled nvm and reinstalled it, no effect. I think it's a problem with grep.
I installed nvm with the curl command from their install guide. Using version 0.33.1
Seems to be same issue as #960 Thanks for your help!
##<!-- Thank you for being interested in nvm! Please help us by filling out the following form if you‘re having trouble. If you have a feature request, or some other question, please feel free to clear out the form. Thanks! -->
- Operating system and version: OSX Yosemite v. 10.10.5
- `nvm debug` output:
<details>
<!-- do not delete the following blank line -->
```sh
nvm --version: v0.33.1
$SHELL: /bin/bash
$HOME: /Users/MyUserName
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: 'https://nodejs.org/dist'
$NVM_IOJS_ORG_MIRROR: 'https://iojs.org/dist'
nvm current: system
which node: /usr/local/bin/node
which iojs:
which npm: /usr/local/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules
You have mail in /var/mail/MyUserName
```
</details>
- `nvm ls` output:
<details>
<!-- do not delete the following blank line -->
```sh
-> system
node -> stable (-> N/A) (default)
iojs -> N/A (default)
lts/* -> lts/boron (-> N/A)
lts/argon -> v4.8.0 (-> N/A)
lts/boron -> v6.10.0 (-> N/A)
```
</details>
- How did you install `nvm`? (e.g. install script in readme, homebrew):
Install script in readme: `curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash`
- What steps did you perform?
Ran install script, verified installation, ran `nvm install node`
- What happened?
Received the following output:
`grep: brackets ([ ]) not balanced
awk: nonterminated character class v0.12.18
input record number 1, file
source line number 3
Version 'node' not found - try `nvm ls-remote` to browse available versions.`
- What did you expect to happen?
I expected node to be installed on my machine.
- Is there anything in any of your profile files (`.bashrc`, `.bash_profile`, `.zshrc`, etc) that modifies the `PATH`?
Yes.
<!-- if this does not apply, please delete this section -->
- If you are having installation issues, or getting "N/A", what does `curl -v nodejs.org/dist/` print out?
<details>
<!-- do not delete the following blank line -->
```sh
* Trying 2400:cb00:2048:1::6814:162e...
* Connected to nodejs.org (2400:cb00:2048:1::6814:162e) port 80 (#0)
> GET /dist/ HTTP/1.1
> Host: nodejs.org
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Tue, 14 Mar 2017 19:57:38 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=dff4c9fd07cafd7a82e37f3f15f4fb0321489521458; expires=Wed, 14-Mar-18 19:57:38 GMT; path=/; domain=.nodejs.org; HttpOnly
< CF-Cache-Status: HIT
< Expires: Tue, 14 Mar 2017 23:57:38 GMT
< Cache-Control: public, max-age=14400
< Server: cloudflare-nginx
< CF-RAY: 33f9cd9d759e79ff-SEA
<
<html>
<head><title>Index of /dist/</title></head>
<body bgcolor="white">
<h1>Index of /dist/</h1><hr><pre><a href="../">../</a>
<a href="latest/">latest/</a> 08-Mar-2017 22:16 -
<a href="latest-argon/">latest-argon/</a> 22-Feb-2017 01:41 -
<a href="latest-boron/">latest-boron/</a> 22-Feb-2017 15:00 -
<a href="latest-v0.10.x/">latest-v0.10.x/</a> 18-Oct-2016 16:38 -
<a href="latest-v0.12.x/">latest-v0.12.x/</a> 22-Feb-2017 13:55 -
<a href="latest-v4.x/">latest-v4.x/</a> 22-Feb-2017 01:41 -
<a href="latest-v5.x/">latest-v5.x/</a> 23-Jun-2016 23:19 -
<a href="latest-v6.x/">latest-v6.x/</a> 22-Feb-2017 15:00 -
<a href="latest-v7.x/">latest-v7.x/</a> 08-Mar-2017 22:16 -
<a href="npm/">npm/</a> 23-May-2014 16:55 -
<a href="patch/">patch/</a> 30-Jul-2014 23:02 -
<a href="v0.1.100/">v0.1.100/</a> 17-Oct-2015 10:42 -
<a href="v0.1.101/">v0.1.101/</a> 17-Oct-2015 10:42 -
<a href="v0.1.102/">v0.1.102/</a> 17-Oct-2015 10:42 -
<a href="v0.1.103/">v0.1.103/</a> 17-Oct-2015 10:42 -
<a href="v0.1.104/">v0.1.104/</a> 17-Oct-2015 10:42 -
<a href="v0.1.14/">v0.1.14/</a> 17-Oct-2015 10:42 -
<a href="v0.1.15/">v0.1.15/</a> 17-Oct-2015 10:42 -
<a href="v0.1.16/">v0.1.16/</a> 17-Oct-2015 10:42 -
<a href="v0.1.17/">v0.1.17/</a> 17-Oct-2015 10:42 -
<a href="v0.1.18/">v0.1.18/</a> 17-Oct-2015 10:42 -
<a href="v0.1.19/">v0.1.19/</a> 17-Oct-2015 10:42 -
<a href="v0.1.20/">v0.1.20/</a> 17-Oct-2015 10:42 -
<a href="v0.1.21/">v0.1.21/</a> 17-Oct-2015 10:42 -
<a href="v0.1.22/">v0.1.22/</a> 17-Oct-2015 10:42 -
<a href="v0.1.23/">v0.1.23/</a> 17-Oct-2015 10:42 -
<a href="v0.1.24/">v0.1.24/</a> 17-Oct-2015 10:42 -
<a href="v0.1.25/">v0.1.25/</a> 17-Oct-2015 10:42 -
<a href="v0.1.26/">v0.1.26/</a> 17-Oct-2015 10:42 -
<a href="v0.1.27/">v0.1.27/</a> 17-Oct-2015 10:42 -
<a href="v0.1.28/">v0.1.28/</a> 17-Oct-2015 10:42 -
<a href="v0.1.29/">v0.1.29/</a> 17-Oct-2015 10:42 -
<a href="v0.1.30/">v0.1.30/</a> 17-Oct-2015 10:42 -
<a href="v0.1.31/">v0.1.31/</a> 17-Oct-2015 10:42 -
<a href="v0.1.32/">v0.1.32/</a> 17-Oct-2015 10:42 -
<a href="v0.1.33/">v0.1.33/</a> 17-Oct-2015 10:42 -
<a href="v0.1.90/">v0.1.90/</a> 17-Oct-2015 10:42 -
<a href="v0.1.91/">v0.1.91/</a> 17-Oct-2015 10:42 -
<a href="v0.1.92/">v0.1.92/</a> 17-Oct-2015 10:42 -
<a href="v0.1.93/">v0.1.93/</a> 17-Oct-2015 10:42 -
<a href="v0.1.94/">v0.1.94/</a> 17-Oct-2015 10:42 -
<a href="v0.1.95/">v0.1.95/</a> 17-Oct-2015 10:42 -
<a href="v0.1.96/">v0.1.96/</a> 17-Oct-2015 10:42 -
<a href="v0.1.97/">v0.1.97/</a> 17-Oct-2015 10:42 -
<a href="v0.1.98/">v0.1.98/</a> 17-Oct-2015 10:42 -
<a href="v0.1.99/">v0.1.99/</a> 17-Oct-2015 10:42 -
<a href="v0.10.0/">v0.10.0/</a> 19-Mar-2013 04:14 -
<a href="v0.10.1/">v0.10.1/</a> 21-Mar-2013 19:04 -
<a href="v0.10.10/">v0.10.10/</a> 12-Jun-2013 22:46 -
<a href="v0.10.11/">v0.10.11/</a> 13-Jun-2013 22:11 -
<a href="v0.10.12/">v0.10.12/</a> 19-Jun-2013 02:19 -
<a href="v0.10.13/">v0.10.13/</a> 13-Jul-2013 20:14 -
<a href="v0.10.14/">v0.10.14/</a> 01-Sep-2015 06:15 -
<a href="v0.10.15/">v0.10.15/</a> 12-Aug-2013 20:52 -
<a href="v0.10.16/">v0.10.16/</a> 16-Aug-2013 19:35 -
<a href="v0.10.16-isaacs-manual/">v0.10.16-isaacs-manual/</a> 16-Aug-2013 16:26 -
<a href="v0.10.17/">v0.10.17/</a> 22-Aug-2013 17:23 -
<a href="v0.10.18/">v0.10.18/</a> 09-Oct-2013 03:56 -
<a href="v0.10.19/">v0.10.19/</a> 09-Oct-2013 17:15 -
<a href="v0.10.2/">v0.10.2/</a> 03-Apr-2013 05:01 -
<a href="v0.10.20/">v0.10.20/</a> 09-Oct-2013 17:25 -
<a href="v0.10.21/">v0.10.21/</a> 21-Oct-2013 19:55 -
<a href="v0.10.22/">v0.10.22/</a> 02-Dec-2013 16:59 -
<a href="v0.10.23/">v0.10.23/</a> 21-Jan-2014 18:51 -
<a href="v0.10.24/">v0.10.24/</a> 21-Jan-2014 19:01 -
<a href="v0.10.25/">v0.10.25/</a> 11-Apr-2014 20:13 -
<a href="v0.10.26/">v0.10.26/</a> 11-Apr-2014 20:34 -
<a href="v0.10.27/">v0.10.27/</a> 07-Aug-2014 17:43 -
<a href="v0.10.28/">v0.10.28/</a> 07-Aug-2014 18:35 -
<a href="v0.10.29/">v0.10.29/</a> 09-Jun-2014 17:45 -
<a href="v0.10.3/">v0.10.3/</a> 26-Apr-2013 23:11 -
<a href="v0.10.30/">v0.10.30/</a> 31-Jul-2014 19:13 -
<a href="v0.10.31/">v0.10.31/</a> 19-Aug-2014 22:12 -
<a href="v0.10.32/">v0.10.32/</a> 16-Sep-2014 23:52 -
<a href="v0.10.33/">v0.10.33/</a> 23-Oct-2014 19:12 -
<a href="v0.10.34/">v0.10.34/</a> 17-Dec-2014 21:59 -
<a href="v0.10.35/">v0.10.35/</a> 22-Dec-2014 21:51 -
<a href="v0.10.36/">v0.10.36/</a> 26-Jan-2015 19:56 -
<a href="v0.10.37/">v0.10.37/</a> 12-Mar-2015 04:11 -
<a href="v0.10.38/">v0.10.38/</a> 23-Mar-2015 21:43 -
<a href="v0.10.39/">v0.10.39/</a> 22-Jun-2015 16:45 -
<a href="v0.10.4/">v0.10.4/</a> 26-Apr-2013 23:41 -
<a href="v0.10.40/">v0.10.40/</a> 09-Jul-2015 21:57 -
<a href="v0.10.41/">v0.10.41/</a> 04-Dec-2015 02:41 -
<a href="v0.10.42/">v0.10.42/</a> 09-Feb-2016 17:03 -
<a href="v0.10.43/">v0.10.43/</a> 04-Mar-2016 01:44 -
<a href="v0.10.44/">v0.10.44/</a> 01-Apr-2016 04:31 -
<a href="v0.10.45/">v0.10.45/</a> 06-May-2016 13:20 -
<a href="v0.10.46/">v0.10.46/</a> 23-Jun-2016 23:21 -
<a href="v0.10.47/">v0.10.47/</a> 28-Sep-2016 00:23 -
<a href="v0.10.48/">v0.10.48/</a> 18-Oct-2016 16:38 -
<a href="v0.10.5/">v0.10.5/</a> 13-May-2013 22:31 -
<a href="v0.10.6/">v0.10.6/</a> 15-May-2013 17:35 -
<a href="v0.10.7/">v0.10.7/</a> 24-May-2013 02:36 -
<a href="v0.10.8/">v0.10.8/</a> 12-Jun-2013 19:42 -
<a href="v0.10.9/">v0.10.9/</a> 12-Jun-2013 19:51 -
<a href="v0.11.0/">v0.11.0/</a> 03-Apr-2013 18:43 -
<a href="v0.11.1/">v0.11.1/</a> 15-May-2013 17:47 -
<a href="v0.11.10/">v0.11.10/</a> 21-Jan-2014 19:19 -
<a href="v0.11.11/">v0.11.11/</a> 11-Apr-2014 20:49 -
<a href="v0.11.12/">v0.11.12/</a> 11-Apr-2014 21:06 -
<a href="v0.11.13/">v0.11.13/</a> 02-May-2014 14:53 -
<a href="v0.11.14/">v0.11.14/</a> 16-Jan-2015 16:37 -
<a href="v0.11.15/">v0.11.15/</a> 20-Jan-2015 23:42 -
<a href="v0.11.16/">v0.11.16/</a> 30-Jan-2015 17:05 -
<a href="v0.11.2/">v0.11.2/</a> 15-May-2013 18:29 -
<a href="v0.11.3/">v0.11.3/</a> 27-Jun-2013 00:26 -
<a href="v0.11.4/">v0.11.4/</a> 13-Jul-2013 19:50 -
<a href="v0.11.5/">v0.11.5/</a> 12-Aug-2013 21:07 -
<a href="v0.11.6/">v0.11.6/</a> 22-Aug-2013 17:24 -
<a href="v0.11.7/">v0.11.7/</a> 09-Oct-2013 17:56 -
<a href="v0.11.8/">v0.11.8/</a> 02-Dec-2013 18:57 -
<a href="v0.11.9/">v0.11.9/</a> 02-Dec-2013 19:16 -
<a href="v0.12.0/">v0.12.0/</a> 06-Feb-2015 22:03 -
<a href="v0.12.1/">v0.12.1/</a> 24-Mar-2015 02:45 -
<a href="v0.12.10/">v0.12.10/</a> 09-Feb-2016 17:03 -
<a href="v0.12.11/">v0.12.11/</a> 03-Mar-2016 18:00 -
<a href="v0.12.12/">v0.12.12/</a> 09-Mar-2016 03:00 -
<a href="v0.12.13/">v0.12.13/</a> 01-Apr-2016 00:10 -
<a href="v0.12.14/">v0.12.14/</a> 06-May-2016 13:52 -
<a href="v0.12.15/">v0.12.15/</a> 23-Jun-2016 23:22 -
<a href="v0.12.16/">v0.12.16/</a> 28-Sep-2016 00:24 -
<a href="v0.12.17/">v0.12.17/</a> 18-Oct-2016 16:16 -
<a href="v0.12.18/">v0.12.18/</a> 22-Feb-2017 13:55 -
<a href="v0.12.2/">v0.12.2/</a> 31-Mar-2015 23:22 -
<a href="v0.12.3/">v0.12.3/</a> 14-May-2015 02:33 -
<a href="v0.12.4/">v0.12.4/</a> 23-May-2015 06:47 -
<a href="v0.12.5/">v0.12.5/</a> 22-Jun-2015 19:52 -
<a href="v0.12.6/">v0.12.6/</a> 04-Jul-2015 02:34 -
<a href="v0.12.7/">v0.12.7/</a> 09-Jul-2015 23:51 -
<a href="v0.12.8/">v0.12.8/</a> 24-Nov-2015 23:53 -
<a href="v0.12.9/">v0.12.9/</a> 04-Dec-2015 02:40 -
<a href="v0.2.0/">v0.2.0/</a> 17-Oct-2015 10:42 -
<a href="v0.2.1/">v0.2.1/</a> 17-Oct-2015 10:42 -
<a href="v0.2.2/">v0.2.2/</a> 17-Oct-2015 10:42 -
<a href="v0.2.3/">v0.2.3/</a> 17-Oct-2015 10:42 -
<a href="v0.2.4/">v0.2.4/</a> 17-Oct-2015 10:42 -
<a href="v0.2.5/">v0.2.5/</a> 17-Oct-2015 10:42 -
<a href="v0.2.6/">v0.2.6/</a> 17-Oct-2015 10:42 -
<a href="v0.3.0/">v0.3.0/</a> 17-Oct-2015 10:42 -
<a href="v0.3.1/">v0.3.1/</a> 17-Oct-2015 10:42 -
<a href="v0.3.2/">v0.3.2/</a> 17-Oct-2015 10:42 -
<a href="v0.3.3/">v0.3.3/</a> 17-Oct-2015 10:42 -
<a href="v0.3.4/">v0.3.4/</a> 17-Oct-2015 10:42 -
<a href="v0.3.5/">v0.3.5/</a> 17-Oct-2015 10:42 -
<a href="v0.3.6/">v0.3.6/</a> 17-Oct-2015 10:42 -
<a href="v0.3.7/">v0.3.7/</a> 17-Oct-2015 10:42 -
<a href="v0.3.8/">v0.3.8/</a> 17-Oct-2015 10:42 -
<a href="v0.4.0/">v0.4.0/</a> 17-Oct-2015 10:42 -
<a href="v0.4.1/">v0.4.1/</a> 17-Oct-2015 10:42 -
<a href="v0.4.10/">v0.4.10/</a> 17-Oct-2015 10:42 -
<a href="v0.4.11/">v0.4.11/</a> 17-Oct-2015 10:42 -
<a href="v0.4.12/">v0.4.12/</a> 17-Oct-2015 10:42 -
<a href="v0.4.2/">v0.4.2/</a> 17-Oct-2015 10:42 -
<a href="v0.4.3/">v0.4.3/</a> 17-Oct-2015 10:42 -
<a href="v0.4.4/">v0.4.4/</a> 17-Oct-2015 10:42 -
<a href="v0.4.5/">v0.4.5/</a> 17-Oct-2015 10:42 -
<a href="v0.4.6/">v0.4.6/</a> 17-Oct-2015 10:42 -
<a href="v0.4.7/">v0.4.7/</a> 17-Oct-2015 10:42 -
<a href="v0.4.8/">v0.4.8/</a> 17-Oct-2015 10:42 -
<a href="v0.4.9/">v0.4.9/</a> 17-Oct-2015 10:42 -
<a href="v0.5.0/">v0.5.0/</a> 17-Oct-2015 10:42 -
<a href="v0.5.1/">v0.5.1/</a> 14-Oct-2015 10:40 -
<a href="v0.5.10/">v0.5.10/</a> 14-Oct-2015 10:40 -
<a href="v0.5.2/">v0.5.2/</a> 14-Oct-2015 10:40 -
<a href="v0.5.3/">v0.5.3/</a> 14-Oct-2015 10:40 -
<a href="v0.5.4/">v0.5.4/</a> 14-Oct-2015 10:40 -
<a href="v0.5.5/">v0.5.5/</a> 14-Oct-2015 10:40 -
<a href="v0.5.6/">v0.5.6/</a> 14-Oct-2015 10:40 -
<a href="v0.5.7/">v0.5.7/</a> 14-Oct-2015 10:40 -
<a href="v0.5.8/">v0.5.8/</a> 14-Oct-2015 10:40 -
<a href="v0.5.9/">v0.5.9/</a> 14-Oct-2015 10:40 -
<a href="v0.6.0/">v0.6.0/</a> 14-Oct-2015 10:39 -
<a href="v0.6.1/">v0.6.1/</a> 14-Oct-2015 10:39 -
<a href="v0.6.10/">v0.6.10/</a> 14-Oct-2015 10:39 -
<a href="v0.6.11/">v0.6.11/</a> 14-Oct-2015 10:39 -
<a href="v0.6.12/">v0.6.12/</a> 14-Oct-2015 10:39 -
<a href="v0.6.13/">v0.6.13/</a> 14-Oct-2015 10:39 -
<a href="v0.6.14/">v0.6.14/</a> 14-Oct-2015 10:39 -
<a href="v0.6.15/">v0.6.15/</a> 14-Oct-2015 10:39 -
<a href="v0.6.16/">v0.6.16/</a> 14-Oct-2015 10:39 -
<a href="v0.6.17/">v0.6.17/</a> 14-Oct-2015 10:39 -
<a href="v0.6.18/">v0.6.18/</a> 14-Oct-2015 10:39 -
<a href="v0.6.19/">v0.6.19/</a> 14-Oct-2015 10:39 -
<a href="v0.6.2/">v0.6.2/</a> 14-Oct-2015 10:39 -
<a href="v0.6.20/">v0.6.20/</a> 14-Oct-2015 10:39 -
<a href="v0.6.21/">v0.6.21/</a> 14-Oct-2015 10:39 -
<a href="v0.6.3/">v0.6.3/</a> 14-Oct-2015 10:39 -
<a href="v0.6.4/">v0.6.4/</a> 14-Oct-2015 10:39 -
<a href="v0.6.5/">v0.6.5/</a> 14-Oct-2015 10:39 -
<a href="v0.6.6/">v0.6.6/</a> 14-Oct-2015 10:39 -
<a href="v0.6.7/">v0.6.7/</a> 14-Oct-2015 10:39 -
<a href="v0.6.8/">v0.6.8/</a> 14-Oct-2015 10:39 -
<a href="v0.6.9/">v0.6.9/</a> 14-Oct-2015 10:39 -
<a href="v0.7.0/">v0.7.0/</a> 14-Oct-2015 10:38 -
<a href="v0.7.1/">v0.7.1/</a> 14-Oct-2015 10:38 -
<a href="v0.7.10/">v0.7.10/</a> 14-Oct-2015 10:38 -
<a href="v0.7.11/">v0.7.11/</a> 14-Oct-2015 10:38 -
<a href="v0.7.12/">v0.7.12/</a> 14-Oct-2015 10:38 -
<a href="v0.7.2/">v0.7.2/</a> 14-Oct-2015 10:38 -
<a href="v0.7.3/">v0.7.3/</a> 14-Oct-2015 10:38 -
<a href="v0.7.4/">v0.7.4/</a> 14-Oct-2015 10:38 -
<a href="v0.7.5/">v0.7.5/</a> 14-Oct-2015 10:38 -
<a href="v0.7.6/">v0.7.6/</a> 14-Oct-2015 10:38 -
<a href="v0.7.7/">v0.7.7/</a> 14-Oct-2015 10:38 -
<a href="v0.7.8/">v0.7.8/</a> 14-Oct-2015 10:38 -
<a href="v0.7.9/">v0.7.9/</a> 14-Oct-2015 10:38 -
<a href="v0.8.0/">v0.8.0/</a> 06-Sep-2015 08:36 -
<a href="v0.8.1/">v0.8.1/</a> 06-Sep-2015 08:36 -
<a href="v0.8.10/">v0.8.10/</a> 06-Sep-2015 08:36 -
<a href="v0.8.11/">v0.8.11/</a> 06-Sep-2015 08:36 -
<a href="v0.8.12/">v0.8.12/</a> 06-Sep-2015 08:36 -
<a href="v0.8.13/">v0.8.13/</a> 06-Sep-2015 08:36 -
<a href="v0.8.14/">v0.8.14/</a> 06-Sep-2015 08:36 -
<a href="v0.8.15/">v0.8.15/</a> 06-Sep-2015 08:36 -
<a href="v0.8.16/">v0.8.16/</a> 06-Sep-2015 08:36 -
<a href="v0.8.17/">v0.8.17/</a> 06-Sep-2015 08:36 -
<a href="v0.8.18/">v0.8.18/</a> 06-Sep-2015 08:36 -
<a href="v0.8.19/">v0.8.19/</a> 06-Sep-2015 08:36 -
<a href="v0.8.2/">v0.8.2/</a> 06-Sep-2015 08:36 -
<a href="v0.8.20/">v0.8.20/</a> 06-Sep-2015 08:36 -
<a href="v0.8.21/">v0.8.21/</a> 06-Sep-2015 08:36 -
<a href="v0.8.22/">v0.8.22/</a> 06-Sep-2015 08:36 -
<a href="v0.8.23/">v0.8.23/</a> 09-Apr-2013 00:30 -
<a href="v0.8.24/">v0.8.24/</a> 04-Jun-2013 14:12 -
<a href="v0.8.25/">v0.8.25/</a> 13-Jun-2013 20:17 -
<a href="v0.8.26/">v0.8.26/</a> 23-Jun-2014 17:02 -
<a href="v0.8.27/">v0.8.27/</a> 23-Jun-2014 17:12 -
<a href="v0.8.28/">v0.8.28/</a> 31-Jul-2014 18:36 -
<a href="v0.8.3/">v0.8.3/</a> 06-Sep-2015 08:36 -
<a href="v0.8.4/">v0.8.4/</a> 06-Sep-2015 08:36 -
<a href="v0.8.5/">v0.8.5/</a> 06-Sep-2015 08:36 -
<a href="v0.8.6/">v0.8.6/</a> 06-Sep-2015 08:36 -
<a href="v0.8.7/">v0.8.7/</a> 06-Sep-2015 08:37 -
<a href="v0.8.8/">v0.8.8/</a> 06-Sep-2015 08:37 -
<a href="v0.8.9/">v0.8.9/</a> 06-Sep-2015 08:37 -
<a href="v0.9.0/">v0.9.0/</a> 14-Oct-2015 10:38 -
<a href="v0.9.1/">v0.9.1/</a> 14-Oct-2015 10:38 -
<a href="v0.9.10/">v0.9.10/</a> 14-Oct-2015 10:38 -
<a href="v0.9.11/">v0.9.11/</a> 14-Oct-2015 10:38 -
<a href="v0.9.12/">v0.9.12/</a> 14-Oct-2015 10:38 -
<a href="v0.9.2/">v0.9.2/</a> 14-Oct-2015 10:38 -
<a href="v0.9.3/">v0.9.3/</a> 14-Oct-2015 10:38 -
<a href="v0.9.4/">v0.9.4/</a> 14-Oct-2015 10:38 -
<a href="v0.9.5/">v0.9.5/</a> 14-Oct-2015 10:38 -
<a href="v0.9.6/">v0.9.6/</a> 14-Oct-2015 10:38 -
<a href="v0.9.7/">v0.9.7/</a> 14-Oct-2015 10:38 -
<a href="v0.9.8/">v0.9.8/</a> 14-Oct-2015 10:38 -
<a href="v0.9.9/">v0.9.9/</a> 14-Oct-2015 10:38 -
<a href="v4.0.0/">v4.0.0/</a> 08-Sep-2015 22:08 -
<a href="v4.1.0/">v4.1.0/</a> 18-Sep-2015 15:36 -
<a href="v4.1.1/">v4.1.1/</a> 24-Sep-2015 01:52 -
<a href="v4.1.2/">v4.1.2/</a> 05-Oct-2015 21:35 -
<a href="v4.2.0/">v4.2.0/</a> 13-Oct-2015 17:40 -
<a href="v4.2.1/">v4.2.1/</a> 14-Oct-2015 14:37 -
<a href="v4.2.2/">v4.2.2/</a> 03-Nov-2015 20:44 -
<a href="v4.2.3/">v4.2.3/</a> 04-Dec-2015 02:35 -
<a href="v4.2.4/">v4.2.4/</a> 23-Dec-2015 20:10 -
<a href="v4.2.5/">v4.2.5/</a> 20-Jan-2016 21:46 -
<a href="v4.2.6/">v4.2.6/</a> 21-Jan-2016 22:23 -
<a href="v4.3.0/">v4.3.0/</a> 09-Feb-2016 17:04 -
<a href="v4.3.1/">v4.3.1/</a> 17-Feb-2016 17:33 -
<a href="v4.3.2/">v4.3.2/</a> 02-Mar-2016 21:52 -
<a href="v4.4.0/">v4.4.0/</a> 09-Mar-2016 06:52 -
<a href="v4.4.1/">v4.4.1/</a> 22-Mar-2016 22:58 -
<a href="v4.4.2/">v4.4.2/</a> 01-Apr-2016 01:39 -
<a href="v4.4.3/">v4.4.3/</a> 12-Apr-2016 22:07 -
<a href="v4.4.4/">v4.4.4/</a> 06-May-2016 14:49 -
<a href="v4.4.5/">v4.4.5/</a> 24-May-2016 18:43 -
<a href="v4.4.6/">v4.4.6/</a> 23-Jun-2016 23:08 -
<a href="v4.4.7/">v4.4.7/</a> 10-Jan-2017 16:39 -
<a href="v4.5.0/">v4.5.0/</a> 16-Aug-2016 16:10 -
<a href="v4.6.0/">v4.6.0/</a> 28-Sep-2016 01:09 -
<a href="v4.6.1/">v4.6.1/</a> 18-Oct-2016 17:03 -
<a href="v4.6.2/">v4.6.2/</a> 05-Jan-2017 18:02 -
<a href="v4.7.0/">v4.7.0/</a> 05-Jan-2017 18:03 -
<a href="v4.7.1/">v4.7.1/</a> 05-Jan-2017 17:22 -
<a href="v4.7.2/">v4.7.2/</a> 05-Jan-2017 22:55 -
<a href="v4.7.3/">v4.7.3/</a> 01-Feb-2017 00:56 -
<a href="v4.8.0/">v4.8.0/</a> 22-Feb-2017 01:41 -
<a href="v5.0.0/">v5.0.0/</a> 29-Oct-2015 21:04 -
<a href="v5.1.0/">v5.1.0/</a> 18-Nov-2015 14:35 -
<a href="v5.1.1/">v5.1.1/</a> 04-Dec-2015 02:38 -
<a href="v5.10.0/">v5.10.0/</a> 01-Apr-2016 03:24 -
<a href="v5.10.1/">v5.10.1/</a> 05-Apr-2016 23:31 -
<a href="v5.11.0/">v5.11.0/</a> 21-Apr-2016 20:35 -
<a href="v5.11.1/">v5.11.1/</a> 05-May-2016 22:56 -
<a href="v5.12.0/">v5.12.0/</a> 23-Jun-2016 23:19 -
<a href="v5.2.0/">v5.2.0/</a> 09-Dec-2015 05:24 -
<a href="v5.3.0/">v5.3.0/</a> 16-Dec-2015 20:05 -
<a href="v5.4.0/">v5.4.0/</a> 06-Jan-2016 22:39 -
<a href="v5.4.1/">v5.4.1/</a> 12-Jan-2016 23:45 -
<a href="v5.5.0/">v5.5.0/</a> 21-Jan-2016 02:25 -
<a href="v5.6.0/">v5.6.0/</a> 10-Feb-2016 14:20 -
<a href="v5.7.0/">v5.7.0/</a> 23-Feb-2016 05:36 -
<a href="v5.7.1/">v5.7.1/</a> 02-Mar-2016 23:22 -
<a href="v5.8.0/">v5.8.0/</a> 09-Mar-2016 15:38 -
<a href="v5.9.0/">v5.9.0/</a> 16-Mar-2016 21:33 -
<a href="v5.9.1/">v5.9.1/</a> 23-Mar-2016 17:36 -
<a href="v6.0.0/">v6.0.0/</a> 27-Apr-2016 05:14 -
<a href="v6.1.0/">v6.1.0/</a> 06-May-2016 15:01 -
<a href="v6.10.0/">v6.10.0/</a> 22-Feb-2017 15:00 -
<a href="v6.2.0/">v6.2.0/</a> 17-May-2016 21:10 -
<a href="v6.2.1/">v6.2.1/</a> 02-Jun-2016 22:37 -
<a href="v6.2.2/">v6.2.2/</a> 17-Jun-2016 15:50 -
<a href="v6.3.0/">v6.3.0/</a> 06-Jul-2016 19:37 -
<a href="v6.3.1/">v6.3.1/</a> 21-Jul-2016 22:30 -
<a href="v6.4.0/">v6.4.0/</a> 16-Aug-2016 14:48 -
<a href="v6.5.0/">v6.5.0/</a> 29-Aug-2016 13:55 -
<a href="v6.6.0/">v6.6.0/</a> 15-Sep-2016 20:50 -
<a href="v6.7.0/">v6.7.0/</a> 28-Sep-2016 21:11 -
<a href="v6.8.0/">v6.8.0/</a> 12-Oct-2016 21:04 -
<a href="v6.8.1/">v6.8.1/</a> 15-Oct-2016 00:32 -
<a href="v6.9.0/">v6.9.0/</a> 18-Oct-2016 17:17 -
<a href="v6.9.1/">v6.9.1/</a> 25-Oct-2016 14:06 -
<a href="v6.9.2/">v6.9.2/</a> 05-Jan-2017 18:06 -
<a href="v6.9.3/">v6.9.3/</a> 05-Jan-2017 17:24 -
<a href="v6.9.4/">v6.9.4/</a> 05-Jan-2017 23:32 -
<a href="v6.9.5/">v6.9.5/</a> 31-Jan-2017 23:21 -
<a href="v7.0.0/">v7.0.0/</a> 25-Oct-2016 14:12 -
<a href="v7.1.0/">v7.1.0/</a> 08-Nov-2016 21:15 -
<a href="v7.2.0/">v7.2.0/</a> 06-Dec-2016 22:49 -
<a href="v7.2.1/">v7.2.1/</a> 06-Dec-2016 22:58 -
<a href="v7.3.0/">v7.3.0/</a> 20-Dec-2016 21:49 -
<a href="v7.4.0/">v7.4.0/</a> 04-Jan-2017 18:43 -
<a href="v7.5.0/">v7.5.0/</a> 01-Feb-2017 02:45 -
<a href="v7.6.0/">v7.6.0/</a> 22-Feb-2017 14:13 -
<a href="v7.7.0/">v7.7.0/</a> 01-Mar-2017 02:45 -
<a href="v7.7.1/">v7.7.1/</a> 02-Mar-2017 03:24 -
<a href="v7.7.2/">v7.7.2/</a> 08-Mar-2017 22:16 -
<a href="index.json">index.json</a> 08-Mar-2017 22:16 81233
<a href="index.tab">index.tab</a> 08-Mar-2017 22:16 47753
<a href="node-0.0.1.tar.gz">node-0.0.1.tar.gz</a> 26-Aug-2011 16:22 2846972
<a href="node-0.0.2.tar.gz">node-0.0.2.tar.gz</a> 26-Aug-2011 16:22 2847748
<a href="node-0.0.3.tar.gz">node-0.0.3.tar.gz</a> 26-Aug-2011 16:22 2891652
<a href="node-0.0.4.tar.gz">node-0.0.4.tar.gz</a> 26-Aug-2011 16:21 2891533
<a href="node-0.0.5.tar.gz">node-0.0.5.tar.gz</a> 26-Aug-2011 16:22 2926727
<a href="node-0.0.6.tar.gz">node-0.0.6.tar.gz</a> 26-Aug-2011 16:21 2952115
<a href="node-0.1.0.tar.gz">node-0.1.0.tar.gz</a> 26-Aug-2011 16:21 3331341
<a href="node-0.1.1.tar.gz">node-0.1.1.tar.gz</a> 26-Aug-2011 16:22 3390971
<a href="node-0.1.10.tar.gz">node-0.1.10.tar.gz</a> 26-Aug-2011 16:22 3674389
<a href="node-0.1.11.tar.gz">node-0.1.11.tar.gz</a> 26-Aug-2011 16:22 3683687
<a href="node-0.1.12.tar.gz">node-0.1.12.tar.gz</a> 26-Aug-2011 16:21 3699939
<a href="node-0.1.13.tar.gz">node-0.1.13.tar.gz</a> 26-Aug-2011 16:22 3718928
<a href="node-0.1.2.tar.gz">node-0.1.2.tar.gz</a> 26-Aug-2011 16:21 3516421
<a href="node-0.1.3.tar.gz">node-0.1.3.tar.gz</a> 26-Aug-2011 16:22 3527371
<a href="node-0.1.4.tar.gz">node-0.1.4.tar.gz</a> 26-Aug-2011 16:21 3567057
<a href="node-0.1.5.tar.gz">node-0.1.5.tar.gz</a> 26-Aug-2011 16:22 3598128
<a href="node-0.1.6.tar.gz">node-0.1.6.tar.gz</a> 26-Aug-2011 16:22 3598051
<a href="node-0.1.7.tar.gz">node-0.1.7.tar.gz</a> 26-Aug-2011 16:22 3599626
<a href="node-0.1.8.tar.gz">node-0.1.8.tar.gz</a> 26-Aug-2011 16:22 3639185
<a href="node-0.1.9.tar.gz">node-0.1.9.tar.gz</a> 26-Aug-2011 16:21 3639588
<a href="node-latest.tar.gz">node-latest.tar.gz</a> 08-Mar-2017 12:28 28087478
<a href="node-v0.1.100.tar.gz">node-v0.1.100.tar.gz</a> 26-Aug-2011 16:21 3813493
<a href="node-v0.1.101.tar.gz">node-v0.1.101.tar.gz</a> 26-Aug-2011 16:22 3825097
<a href="node-v0.1.102.tar.gz">node-v0.1.102.tar.gz</a> 26-Aug-2011 16:21 3847409
<a href="node-v0.1.103.tar.gz">node-v0.1.103.tar.gz</a> 26-Aug-2011 16:22 3843666
<a href="node-v0.1.104.tar.gz">node-v0.1.104.tar.gz</a> 26-Aug-2011 16:21 3859322
<a href="node-v0.1.14.tar.gz">node-v0.1.14.tar.gz</a> 26-Aug-2011 16:22 3736523
<a href="node-v0.1.15.tar.gz">node-v0.1.15.tar.gz</a> 26-Aug-2011 16:21 3766716
<a href="node-v0.1.16.tar.gz">node-v0.1.16.tar.gz</a> 26-Aug-2011 16:22 3827870
<a href="node-v0.1.17.tar.gz">node-v0.1.17.tar.gz</a> 26-Aug-2011 16:21 3826866
<a href="node-v0.1.18.tar.gz">node-v0.1.18.tar.gz</a> 26-Aug-2011 16:21 3537137
<a href="node-v0.1.19.tar.gz">node-v0.1.19.tar.gz</a> 26-Aug-2011 16:22 3574916
<a href="node-v0.1.20.tar.gz">node-v0.1.20.tar.gz</a> 26-Aug-2011 16:21 3575681
<a href="node-v0.1.21.tar.gz">node-v0.1.21.tar.gz</a> 26-Aug-2011 16:22 3597096
<a href="node-v0.1.22.tar.gz">node-v0.1.22.tar.gz</a> 26-Aug-2011 16:21 3604861
<a href="node-v0.1.23.tar.gz">node-v0.1.23.tar.gz</a> 26-Aug-2011 16:22 3605321
<a href="node-v0.1.24.tar.gz">node-v0.1.24.tar.gz</a> 26-Aug-2011 16:21 3649641
<a href="node-v0.1.25.tar.gz">node-v0.1.25.tar.gz</a> 26-Aug-2011 16:22 3666675
<a href="node-v0.1.26.tar.gz">node-v0.1.26.tar.gz</a> 26-Aug-2011 16:22 3704254
<a href="node-v0.1.27.tar.gz">node-v0.1.27.tar.gz</a> 26-Aug-2011 16:22 3766114
<a href="node-v0.1.28.tar.gz">node-v0.1.28.tar.gz</a> 26-Aug-2011 16:22 3804602
<a href="node-v0.1.29.tar.gz">node-v0.1.29.tar.gz</a> 26-Aug-2011 16:21 3807335
<a href="node-v0.1.30.tar.gz">node-v0.1.30.tar.gz</a> 26-Aug-2011 16:22 3912671
<a href="node-v0.1.31.tar.gz">node-v0.1.31.tar.gz</a> 26-Aug-2011 16:22 3933441
<a href="node-v0.1.32.tar.gz">node-v0.1.32.tar.gz</a> 26-Aug-2011 16:21 3984949
<a href="node-v0.1.33.tar.gz">node-v0.1.33.tar.gz</a> 26-Aug-2011 16:22 4016600
<a href="node-v0.1.90.tar.gz">node-v0.1.90.tar.gz</a> 26-Aug-2011 16:22 6452573
<a href="node-v0.1.91.tar.gz">node-v0.1.91.tar.gz</a> 26-Aug-2011 16:21 6488023
<a href="node-v0.1.92.tar.gz">node-v0.1.92.tar.gz</a> 26-Aug-2011 16:22 6535942
<a href="node-v0.1.93.tar.gz">node-v0.1.93.tar.gz</a> 26-Aug-2011 16:21 6528767
<a href="node-v0.1.94.tar.gz">node-v0.1.94.tar.gz</a> 26-Aug-2011 16:22 6691437
<a href="node-v0.1.95.tar.gz">node-v0.1.95.tar.gz</a> 26-Aug-2011 16:21 3691396
<a href="node-v0.1.96.tar.gz">node-v0.1.96.tar.gz</a> 26-Aug-2011 16:22 3697128
<a href="node-v0.1.97.tar.gz">node-v0.1.97.tar.gz</a> 26-Aug-2011 16:21 3725213
<a href="node-v0.1.98.tar.gz">node-v0.1.98.tar.gz</a> 26-Aug-2011 16:21 3770749
<a href="node-v0.1.99.tar.gz">node-v0.1.99.tar.gz</a> 26-Aug-2011 16:22 3796156
<a href="node-v0.10.14.tar.gz">node-v0.10.14.tar.gz</a> 25-Jul-2013 19:06 13782897
<a href="node-v0.2.0.tar.gz">node-v0.2.0.tar.gz</a> 26-Aug-2011 16:21 3869705
<a href="node-v0.2.1.tar.gz">node-v0.2.1.tar.gz</a> 26-Aug-2011 16:22 3874229
<a href="node-v0.2.2.tar.gz">node-v0.2.2.tar.gz</a> 26-Aug-2011 16:21 3876164
<a href="node-v0.2.3.tar.gz">node-v0.2.3.tar.gz</a> 26-Aug-2011 16:22 3877908
<a href="node-v0.2.4.tar.gz">node-v0.2.4.tar.gz</a> 26-Aug-2011 16:22 4002347
<a href="node-v0.2.5.tar.gz">node-v0.2.5.tar.gz</a> 26-Aug-2011 16:22 4008314
<a href="node-v0.2.6.tar.gz">node-v0.2.6.tar.gz</a> 26-Aug-2011 16:21 4010320
<a href="node-v0.3.0.tar.gz">node-v0.3.0.tar.gz</a> 26-Aug-2011 16:22 4054239
<a href="node-v0.3.1.tar.gz">node-v0.3.1.tar.gz</a> 26-Aug-2011 16:22 4147683
<a href="node-v0.3.2.tar.gz">node-v0.3.2.tar.gz</a> 26-Aug-2011 16:21 4433878
<a href="node-v0.3.3.tar.gz">node-v0.3.3.tar.gz</a> 26-Aug-2011 16:22 4582669
<a href="node-v0.3.4.tar.gz">node-v0.3.4.tar.gz</a> 26-Aug-2011 16:21 4610441
<a href="node-v0.3.5.tar.gz">node-v0.3.5.tar.gz</a> 26-Aug-2011 16:22 4655131
<a href="node-v0.3.6.tar.gz">node-v0.3.6.tar.gz</a> 26-Aug-2011 16:21 4727071
<a href="node-v0.3.7.tar.gz">node-v0.3.7.tar.gz</a> 26-Aug-2011 16:22 4748183
<a href="node-v0.3.8.tar.gz">node-v0.3.8.tar.gz</a> 26-Aug-2011 16:22 4779447
<a href="node-v0.4.0.tar.gz">node-v0.4.0.tar.gz</a> 26-Aug-2011 16:21 4827760
<a href="node-v0.4.1.tar.gz">node-v0.4.1.tar.gz</a> 26-Aug-2011 16:22 4855576
<a href="node-v0.4.10.tar.gz">node-v0.4.10.tar.gz</a> 26-Aug-2011 16:22 12410018
<a href="node-v0.4.11.tar.gz">node-v0.4.11.tar.gz</a> 26-Aug-2011 16:21 12419274
<a href="node-v0.4.12.tar.gz">node-v0.4.12.tar.gz</a> 15-Sep-2011 23:48 12421469
<a href="node-v0.4.2.tar.gz">node-v0.4.2.tar.gz</a> 26-Aug-2011 16:22 4922523
<a href="node-v0.4.3.tar.gz">node-v0.4.3.tar.gz</a> 26-Aug-2011 16:22 4991966
<a href="node-v0.4.4.tar.gz">node-v0.4.4.tar.gz</a> 26-Aug-2011 16:21 4995935
<a href="node-v0.4.5.tar.gz">node-v0.4.5.tar.gz</a> 26-Aug-2011 16:22 5001301
<a href="node-v0.4.6.tar.gz">node-v0.4.6.tar.gz</a> 26-Aug-2011 16:21 5008110
<a href="node-v0.4.7.tar.gz">node-v0.4.7.tar.gz</a> 26-Aug-2011 16:22 5011520
<a href="node-v0.4.8.tar.gz">node-v0.4.8.tar.gz</a> 26-Aug-2011 16:22 4991396
<a href="node-v0.4.9.tar.gz">node-v0.4.9.tar.gz</a> 26-Aug-2011 16:21 4994552
<a href="node-v0.4.tar.gz">node-v0.4.tar.gz</a> 26-Aug-2011 16:21 4991396
<a href="node-v0.5.0.tar.gz">node-v0.5.0.tar.gz</a> 26-Aug-2011 16:21 5357945
<a href="node-v0.6.1.tar.gz">node-v0.6.1.tar.gz</a> 14-Nov-2011 21:57 9276847
<a href="node-v0.6.10.tar.gz">node-v0.6.10.tar.gz</a> 15-Mar-2012 23:03 10545272
<a href="node-v0.6.11.tar.gz">node-v0.6.11.tar.gz</a> 15-Mar-2012 23:03 10555423
<a href="node-v0.6.12.tar.gz">node-v0.6.12.tar.gz</a> 15-Mar-2012 23:03 10452498
<a href="node-v0.6.13.tar.gz">node-v0.6.13.tar.gz</a> 15-Mar-2012 23:04 10757157
<a href="node-v0.6.2.tar.gz">node-v0.6.2.tar.gz</a> 18-Nov-2011 23:29 9286655
<a href="node-v0.6.3.tar.gz">node-v0.6.3.tar.gz</a> 15-Mar-2012 23:07 10048403
<a href="node-v0.6.4.tar.gz">node-v0.6.4.tar.gz</a> 02-Dec-2011 02:17 10195975
<a href="node-v0.6.5.tar.gz">node-v0.6.5.tar.gz</a> 15-Mar-2012 23:04 10195654
<a href="node-v0.6.6.tar.gz">node-v0.6.6.tar.gz</a> 15-Mar-2012 23:04 10446671
<a href="node-v0.6.7.tar.gz">node-v0.6.7.tar.gz</a> 15-Mar-2012 23:04 10473188
<a href="node-v0.6.8.tar.gz">node-v0.6.8.tar.gz</a> 20-Jan-2012 02:26 10488841
<a href="node-v0.6.9.tar.gz">node-v0.6.9.tar.gz</a> 15-Mar-2012 23:03 10544243
<a href="npm-versions.txt">npm-versions.txt</a> 27-Feb-2014 00:01 1676
</pre><hr></body>
</html>
* Connection #0 to host nodejs.org left intact
```
</details>
| needs followup | low | Critical |
214,224,697 | neovim | tui: S8C1T (8-bit) mode, v:termresponse | ## Problem
https://github.com/neovim/neovim/issues/25856 implemented `v:termresponse` but we don't yet use it to detect whether we can use 8-bit key sequences.
Related Vim help:
> > > > > > xterm-8bit xterm-8-bit
Xterm can be run in a mode where it uses 8-bit escape sequences. The CSI code
is used instead of <Esc>[. The advantage is that an <Esc> can quickly be
recognized in Insert mode, because it can't be confused with the start of a
special key.
For the builtin termcap entries, Vim checks if the 'term' option contains
"8bit" anywhere. It then uses 8-bit characters for the termcap entries, the
mouse and a few other things. You would normally set $TERM in your shell to
"xterm-8bit" and Vim picks this up and adjusts to the 8-bit setting
automatically.
When Vim receives a response to the t_RV (request version) sequence and it
starts with CSI, it assumes that the terminal is in 8-bit mode and will
convert all key sequences to their 8-bit variants.
## Expected behavior
Nvim should detect whether it can use 8-bit mode, via a "request version" `TermResponse` (aka "Primary Device Attributes"?). Unless there's a better way.
## Reference
- Vim in some cases does a synchronous timeout-based check, e.g.: https://github.com/vim/vim/commit/ba6ec182973af726ce9b7b7eb3753fc3a7ae7d1b#diff-366ece1c6e8026aed5df9c6ae82c3967R2622
- [S8C1T mode](http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-C1-_8-Bit_-Control-Characters) | enhancement,tui | low | Minor |
214,226,299 | rust | rustbuild: if stage0 binaries can't be run, kindly inform user | Hello!
I was trying to build rust within Alpine linux and since it comes with `musl` instead of `glibc` I've bumped into this confusing error message from rustbuild.
```
$ make check
Traceback (most recent call last):
File "/home/test/rust/src/bootstrap/bootstrap.py", line 614, in <module>
main()
File "/home/test/rust/src/bootstrap/bootstrap.py", line 602, in main
bootstrap()
File "/home/test/rust/src/bootstrap/bootstrap.py", line 587, in bootstrap
rb.build_bootstrap()
File "/home/test/rust/src/bootstrap/bootstrap.py", line 377, in build_bootstrap
self.run(args, env)
File "/home/test/rust/src/bootstrap/bootstrap.py", line 380, in run
proc = subprocess.Popen(args, env=env)
File "/usr/lib/python2.7/subprocess.py", line 390, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1024, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [Makefile:54: check] Error 1
```
`cargo` is there, in stage0 directory but since it's not compatible with `musl`. execution fails.
My proposal is (thanks @matt36 for the idea) that we should catch the error and inform the user with more context.
```
$ make check
/home/test/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo could not be executed.
You might want to check your internet connection stability since it might be preventing
you from getting stage0 packages correctly.
If the archives are intact, then please check your operating system compatibility on prebuilt
stage0 binaries.
Go to: http://docs.rust-lang.org/some/docs/here for more information.
Build completed unsuccessfully in 0:00:00
make: *** [Makefile:54: check] Error 127
```
(If you're wondering "why cargo is not found?" please refer to https://github.com/rust-lang/rust/issues/31322)
Thanks | T-bootstrap,C-feature-request | low | Critical |
214,235,466 | TypeScript | Shorten method signatures (aka "type madness") | Some of the types that make everything work behind the scenes are ridiculous. For example, from Vue.js:
For a Vue developer creating a new Vue instance in JavaScript, they will be exposed to this every time. If they already know what arguments to supply, this does not do a great job as a quick reminder. If they don't know what args to supply, this is probably not very helpful either. We should be able to give users an option to show a _concise_ method signature like the following.
In this example, the tildas indicate that there is "type madness" hidden below. If the user really wants to see the types, they can goToDefinition or maybe we could give them a way to expand the signature window.
We would need to pick some arbitrary line when to display type information and when to hide it. My initial thinking is something along the lines of:
- Hide all generic types, but leave angle brackets in
- Hide types when there are more than 2 unions or intersections
- Show string literals if less than 100 characters (roughly 2 lines?)
I would imagine we would also want to give JavaScript users the concise signature by default and TypeScript users the full signature by default, but give both the camps the ability to configure to their preference. | Suggestion,Needs Proposal,Domain: Signature Help,Domain: Type Display | medium | Major |
214,253,907 | rust | Dyn compatibility error when using an associated type as a type parameter in the super-trait listing | I tried this code:
```rust
trait Super<T> {}
trait Foo: Super<<Self as Foo>::Bar> { type Bar; }
type BoxFoo = Box<Foo<Bar = u8>>;
```
The code should compile since `Self::Bar` is the type parameter, not `Self`.
Instead, it will fail with the following message:
`the trait Foo cannot be made into an object`
`the trait cannot use Self as a type parameter in the supertrait listing`
FYI [the discussion that sparked this issue](https://www.reddit.com/r/rust/comments/5z3t5j/hey_rustaceans_got_an_easy_question_ask_here/dewgxlf/):
> So this has to do with object safety -- any trait that references Self is not object safe because the true Self type is erased. **However, the error doesn't seem appropriate in this case. I think this warrants a bug report at least to fix the error message, if not to relax the object safety check** (because there could be something I don't see preventing it still... can't say I fully understand object safety).
## Meta
`rustc --version --verbose`: **rustc 1.17.0-nightly (`b1e31766d` 2017-03-03)** | A-type-system,C-enhancement,A-trait-system,A-associated-items,T-compiler,T-types,A-trait-objects,A-dyn-compatibility | low | Critical |
214,356,102 | rust | Produce a warning when using `const` with interior mutability | Originally reported in https://users.rust-lang.org/t/broken-atomics-puzzle/9533
Consider this code
```rust
use std::sync::atomic::{AtomicBool, Ordering};
pub const A: AtomicBool = AtomicBool::new(false);
fn main() {
A.compare_exchange(false, true, Ordering::SeqCst, Ordering::SeqCst);
println!("A = {}", A.load(Ordering::SeqCst));
}
```
[Playground](https://play.integer32.com/?version=stable&mode=debug&edition=2015&gist=8f714787458e6a0a7eb96591cd0ce6b1)
It compiles and runs cleanly, but produces unexpected results because `const` is used instead of `static`.
It would be nice to somehow give a warning for `.compare_and_swap` call, but I am not sure it is possible.
| A-lints,T-compiler,C-feature-request | medium | Critical |
214,538,233 | youtube-dl | Feature Request: Alternate thumbnail embedder - tageditor | - [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.15**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [ ] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [x] Feature request (request for a new functionality)
---
### Description of your *issue*, suggested solution and other information
I'd like to propose an alternative to `atomicparsley` for thumbnail embedding: `tageditor` (https://github.com/Martchus/tageditor). It's supports mp4 *and* mkv embedding of cover images (among quite a lot of other things).
Example command line:
```
tageditor -set cover="foo.png" -f "foo.mp4" [--max-padding nnnn]
```
Might be able to resolve #10359.
If using an alternate external application for thumbnail embedding is already supported, at least `--help` doesn't mention it.
| request,postprocessors | low | Critical |
214,673,656 | neovim | :nineties mode: disable various settings for slow terminals | On slow connections, 'showcmd', 'ruler', etc. can cause bad performance. We can serve that use-case by providing a single built-in mapping (`{count}CTRL-L` ?) or command (`:ni[neties]`) that disables various settings known to cause extra redraws.
:ni[neties] Party like it's the 90s. Disable various features,
for slow environments. Ni!
So then we can have defaults that serve most users, but when using nvim on a slow connection, one can just hit a single mapping to make it faster.
List of effects:
```
set mouse=
set noshowcmd
set noruler
set nosmoothscroll
``` | enhancement,performance,tui | low | Major |
214,675,163 | go | plugin: requires CGO_ENABLED=1 | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
`go version go1.8 linux/amd64`
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN="/home/johan/gows/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/johan/gows"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build464530147=/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?
I tried to build a simple plugin with `CGO_ENABLED=0`. It builds fine, and at plugin load time you get an error `plugin: not implemented`. This is an intentional limitation at the moment, but I think it moves backwards in the general trend of the language development, which has been moving away from C dependencies. This should hopefully be a discussion around supporting plugins without the need for CGO.
### What did you expect to see?
I expected to be able to build and load plugins without CGO.
### What did you see instead?
I got an error saying `plugin: not implemented`. | compiler/runtime | medium | Critical |
214,721,571 | rust | Rust allows function argument names to shadow unit structs imported in function body | Assume that `foo::bar` is a unit struct in all these examples. This fails to compile:
```rust
use foo::bar;
fn foo(bar: i32) {}
```
As does this:
```rust
fn foo() {
use foo::bar;
let bar = 1;
}
```
However, this compiles successfully:
```rust
fn foo(bar: i32) {
use foo::bar;
}
```
It probably shouldn't. The local variable `bar` can never be accessed for the same reason as the first two. This has led to some confusion by users of Diesel, when they tried to write code like the following:
```rust
fn find_by_email(conn: &PgConnection, email: &str) -> QueryResult<User> {
use schema::users::dsl::*;
use schema::users;
users.filter(users::email.eq(email)).first(conn)
```
However, `users::email` and `email` are both that unit struct, so this code would return the first user in the database not the user with the given email as you'd expect. It does at least complain about the unused argument, but this should be a hard error. | A-resolve,T-lang,T-compiler,C-bug | low | Critical |
214,758,107 | go | x/build/cmd/gopherbot: ping a CL when it has +2 but OP can't submit | Have gopherbot ping a CL when it has +2 but OP can't submit.
| Builders,FeatureRequest | low | Major |
214,775,618 | go | runtime: performance problem with many Cgo calls | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
`go version go1.8 darwin/amd64`, though I've also verified this happens on Linux.
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/pmattis/Development/go"
GORACE=""
GOROOT="/Users/pmattis/Development/go-1.8"
GOTOOLDIR="/Users/pmattis/Development/go-1.8/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/qc/fpqpgdqd167c70dtc6840xxh0000gn/T/go-build085228252=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
```
### Background
CockroachDB internally uses RocksDB (a fork of LevelDB) for data storage. We access RocksDB via a small Cgo wrapper. All writes to RocksDB are performed using `WriteBatches` which are first written to a write-ahead-log and then inserted into the database. Internally, RocksDB "groups" multiple concurrent write batches together into a single append to the write-ahead-log. While investigating performance, we noticed that the size of the groups was smaller than expected.
### What did you do?
TL;DR? If write batch grouping is performed in Go performance is good. If it is performed in C++ (either by code that is nearly identical to the Go grouping or by RocksDB) performance is bad.
https://github.com/cockroachdb/cockroach/pull/14138 started as an experiment to replace the grouping of write batches in RocksDB with our own grouping in Go to try and understand the smaller than expected group sizes. In addition to fixing the group sizes, it improved performance on one experiment by 100% while reducing latencies. This was unexpected as the Cgo call overheads are negligible in comparison to the cost of committing the batch to RocksDB. In order to point the finger at RocksDB, we reimplemented the grouping of write batches in our Cgo RocksDB wrapper. Performance was equivalent to RocksDB performing the grouping.
I've provided a stripped down reproduction scenario at https://github.com/petermattis/batchtest. Running on my Mac laptop I see:
```
~ ./batchtest -t go
_elapsed____ops/sec
1s 8029.6
2s 8432.0
3s 8100.1
4s 8296.5
5s 8171.8
6s 8282.0
7s 8040.7
8s 8133.3
9s 8240.4
10s 8221.7
```
```
~ ./batchtest -t cgo
_elapsed____ops/sec
1s 5036.4
2s 2242.4
3s 1284.3
4s 1245.5
5s 1254.5
6s 1246.1
7s 1962.5
8s 4291.7
10s 2036.3
```
By default, `batchtest` uses 100 concurrent worker threads writing "batches". My suspicion is that `batchtest` and CockroachDB are tickling some badness in the Go scheduler. If I set `GOMAXPROCS` to the number of concurrent workers the cgo performance gets much closer to the Go performance:
```
~ GOMAXPROCS=100 ./batchtest -t cgo
_elapsed____ops/sec
1s 6943.9
2s 7252.0
3s 7090.4
4s 6810.8
5s 7326.4
6s 7758.9
7s 7897.7
8s 7893.2
9s 7022.5
10s 6875.9
```
https://github.com/cockroachdb/cockroach/pull/14138 is an acceptable workaround for committing batches, but it would be great to understand the performance discrepancy here. We're concerned about other Cgo operations in CockroachDB that don't have such easy workarounds. | Performance,compiler/runtime | medium | Critical |
214,789,045 | go | test: errorcheck support for intraline errors | Now that the compiler supports reporting column position for errors, we need a mechanism in test/run.go for testing this.
I propose we use `/* ERROR "foo" */` placed just before where we expect the error to be emitted, except to allow for white space in between.
E.g., for #19576, the test would be
package p
func f() int { /* ERROR "missing return" */ }
Rationale:
- run.go currently only looks for `// ERROR` annotations, which can only occur at the end of the line, so there's no risk of collision using `/* ERROR */` for column-precise error matching.
- Not explicitly having to write column numbers into the errors makes them easier to maintain, just like how we don't currently have to worry about line numbers.
- We emit errors at the start of tokens, so putting the error expectation before that lets us unambiguously match it to an expected column. Putting afterwards would require more complex logic for figuring out how many characters to rewind past.
- Allowing whitespace after the error comment allows the code to be gofmt'd.
/cc @griesemer @ianlancetaylor @bradfitz | help wanted,NeedsFix,FeatureRequest | low | Critical |
214,833,291 | rust | Specialization and lifetime dispatch | I see this briefly mentioned in #31844 but no existing issue tracking the incorrect behavior.
Something in the following code is unsound. It should not be possible to implement `make_static`.
```rust
#![feature(specialization)]
trait FromRef<'a, T: ?Sized> {
fn from_ref(r: &'a T) -> Self;
}
impl<'a, T: ?Sized> FromRef<'a, T> for &'a T {
fn from_ref(r: &'a T) -> Self {
r
}
}
impl<'a, T: ?Sized, R> FromRef<'a, T> for R {
default fn from_ref(_: &'a T) -> Self {
unimplemented!()
}
}
fn main() {
let s = "specialization".to_owned();
println!("{:?}", make_static(s.as_str()));
}
fn make_static<T: ?Sized>(data: &T) -> &'static T {
fn helper<T: ?Sized, R>(data: &T) -> R {
R::from_ref(data)
}
helper(data)
}
``` | P-medium,T-compiler,B-unstable,I-unsound,A-specialization,C-bug,requires-nightly,F-specialization,S-bug-has-test,T-types | low | Minor |
214,897,290 | rust | Overflow on requirement evaluation with associated types | ```rust
trait Foo { }
trait Bar<P> {
type X;
}
impl<T, U> Foo for (T, U)
where T: Bar<(T, U), X=U>
{ }
impl<T, P: Foo> Bar<P> for T {
type X = u32;
}
fn main() { }
```
produces on stable and nightly:
```
error[E0275]: overflow evaluating the requirement `<T as Bar<(T, U)>>::X`
--> src/lol.rs:7:1
|
7 | impl<T, U> Foo for (T, U)
| _^ starting here...
8 | | where T: Bar<(T, U), X=U>
9 | | { }
| |___^ ...ending here
|
= note: required because of the requirements on the impl of `Foo` for `(T, U)`
= note: required because of the requirements on the impl of `Bar<(T, U)>` for `T`
error: aborting due to previous error
```
The impl's compile individually but not together. I expect it to be able to compile. | A-type-system,T-compiler,C-bug,T-types | low | Critical |
214,926,877 | flutter | Color-code stack traces to ease interpretation of crash reports | There's been some discussion in `gitter` about how to pick out app-code/user-code from the super-long stack.
Simply put some symbols around the line numbers would've just done the job, say `# 52` for framework code and `#* 53` for user code.
Colored stacks may also be a good idea, though it involves much more work.
| c: new feature,c: crash,framework,a: quality,P3,team-framework,triaged-framework | low | Critical |
214,932,859 | node | Node.js' internal scripts should be hidden in the inspector. | Node.js' internal scripts are not distinguished from user scripts. So when debugging a user script, the inspector is polluted with these internal scripts.
This could be solved either by blackboxing internal scripts by default, or setting a different script kind in V8 internally for these scripts. The latter probably requires an API change in V8.
@ak239 @ofrobots
| module,feature request,inspector | high | Critical |
215,047,264 | opencv | OpenCL Kernel only takes up to 16 arguments |
##### System information (version)
- OpenCV => 3.2
- Operating System / Platform => Ubuntu 16.04
- Compiler => g++
##### Detailed description
cv::ocl::Kernel::args() only takes up to 16 arguments. This is hard-coded in the source (ocl.hpp). Presumably, the developer did not expect users to need more than that, but for my purposes, I need the option for more.
I would suggest either adding more overloads with more arguments (maybe a bit unflexible solution) or adding the option to add more arguments by calling the function again with some flag. The second option would require the index of the last added argument (i in the source) to be available from outside, so that the next call would be able to continue from that index, instead of overwriting previous arguments. | feature,category: ocl,category: t-api | low | Major |
215,058,511 | opencv | OpenCL kernel does not support user defined callback function | <!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).
This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->
##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
##### Detailed description
While the kernel is invoked to run asynchronously, it does not support user defined callback function,
instead it installs a fixed callback function `oclCleanupCallback`.
<!-- your description -->
<!-- to add code example fence it with triple backticks and optional file extension
```.cpp
// C++ code example
```
or attach as .txt or .zip file
--> | feature,category: ocl | low | Critical |
215,129,286 | create-react-app | Warn about duplicate dependencies | I haven’t tried this plugin, but it looks cool: https://github.com/darrenscerri/duplicate-package-checker-webpack-plugin.
Maybe we should do it? | issue: proposal | low | Minor |
215,168,677 | rust | `UnwindSafe` is unergonomic | As I expressed on IRC, I feel like, unless quickly taken care of, `UnwindSafe` is going to be a "failed feature". I've seen now quite a bit of people that told me that "they just wrap everything in `AssertUnwindSafe`" defeating the whole purpose of it. I've also seen comments that `UnwindSafe` is a PITA - sentiment that I'm beginning to share. I am tempted to ignore `UnwindSafe` completely as well, even though I'd like to do stuff properly. Please hear me out.
`UnwindSafe` and `RefUnwindSafe` are not too complicated, but they force people into writing a lot of boilerplate, and the worst part once used ... force that boilerplate on all other users, that might not even know what is it all about.
Static dispatch works OK, since similarly to `Send` and `Sync` any `struct` will get `UnwindSafe` and `RefUnwindSafe` if all fields of it satisfy it.
The problem is dynamic dispatch, trait object and trait bounds. Any time someone has to use eg. `Box<TraitObject>`, even if it's only due to lack of `impl Trait` on stable, that person most probably should have done `Box<Trait + RefUnwindSafe>`. Otherwise that `Box<Trait>` does not satisfy `SafeUnwind`, even though most probably that would be the intention. After all ["This trait is namely not implemented by UnsafeCell, the root of all interior mutability"](https://doc.rust-lang.org/std/panic/trait.RefUnwindSafe.html).
And even if that person is aware of "unwind safety", after putting `+RefUnwindSafe` it won't work because:
only Send/Sync traits can be used as additional traits in a trait object
To get this working a lot of boilerplate needs to be added. [Example in my code](https://github.com/slog-rs/slog/blob/0b4c3f2923c2f35f643f212d0dd8562af8dfd954/src/lib.rs#L1112) which is just a PITA. And the worst part: after putting `UnwindSafe` bound in types used in open-traits (to be implemented by users of a library), now all users have to satisfy that bound. They will have to remember about it, add blanket implementations adding `UnwindSafe` for every type used as trait object, and get libraries they might want to use it, to do the same...
I don't know. Maybe I'm missing something here, but I feel like at least `+UnwindSafe` should work just like `+Send` and `+Sync`.
Also, I think if the default would be different, there would be almost no problem. `Box<Trait>` should mean `Box<Trait + RefUnwindSafe>`, and users should be able to opt-out of it with `Box<Trait + !RefUnwindSafe>`. This way, unaware uses would get their types `UnwindSafe` without knowing it. | C-enhancement,T-lang | medium | Critical |
215,206,410 | go | x/net/idna: support label separators other than ASCII dot | ### What version of Go are you using (`go version`)?
```
go version go1.8 linux/amd64
```
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/admin/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build229576781=/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?
Passed a string `"example\u3002jp"` to `ToASCII()`.
### What did you expect to see?
The return value is `"example.jp"`
### What did you see instead?
The return value was `"xn--examplejp-ck3h"`
https://tools.ietf.org/html/rfc3490#section-3.1
```
3.1 Requirements
IDNA conformance means adherence to the following four requirements:
1) Whenever dots are used as label separators, the following
characters MUST be recognized as dots: U+002E (full stop), U+3002
(ideographic full stop), U+FF0E (fullwidth full stop), U+FF61
(halfwidth ideographic full stop).
```
I created a fix and add test cases at https://github.com/hnakamur/net/commit/bd2fe133f3df97090c43d065b739774b900f67c9
I also followed the steps at [Contribution Guide - The Go Programming Language](https://golang.org/doc/contribute.html) and am ready to run `git mail` if this fix looks good to reviewers.
Thanks! | NeedsInvestigation | low | Critical |
215,212,157 | rust | E0122 says bounds aren't enforced, but they actually are? | For [multistr](https://docs.rs/multistr) I've included trait bounds in type aliases so that it's clear in the documentation what should be passed to the generics for these aliases, e.g. [SliceArray5](https://docs.rs/multistr/latest/multistr/type.SliceArray5.html).
But because I've generated several of these aliases E0122 floods my error output and I don't see any way of turning it off:
```
warning[E0122]: trait bounds are not (yet) enforced in type definitions
--> src/array.rs:166:13
|
166 | pub type $slice_name<T: 'static + Copy> = $name<[T]>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
```
(× 17)
It'd be really nice if I could silence this error somehow, because while it's good to have the error by default, it's making debugging my code very hard when I have to scroll past a wall of these errors. | T-compiler,C-feature-request | low | Critical |
215,250,202 | youtube-dl | [vbox] Add support for authentication | ## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.03.16*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.16**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [x] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
$ youtube-dl -v https://www.vbox7.com/play:bcb87e7c29
C:\Users\Admin\Desktop>C:\Users\Admin\Desktop\youtube-dl.exe https://www.vbox7.c
om/play:bcb87e7c29
[Vbox7] bcb87e7c29: Downloading JSON metadata
ERROR: An extractor error has occurred. (caused by KeyError('title',)); please r
eport this issue on https://yt-dl.org/bug . Make sure you are using the latest v
ersion; type youtube-dl -U to update. Be sure to call youtube-dl with the --ve
rbose flag and include its complete output.
C:\Users\Admin\Desktop>C:\Users\Admin\Desktop\youtube-dl.exe -v https://www.vbox
7.com/play:bcb87e7c29 >> out.txt
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.vbox7.com/play:bcb87e7c29']
[debug] Encodings: locale cp1251, fs mbcs, out cp1251, pref cp1251
[debug] youtube-dl version 2017.03.16
[debug] Python version 3.4.4 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg 1.2
[debug] Proxy map: {}
ERROR: An extractor error has occurred. (caused by KeyError('title',)); please r
eport this issue on https://yt-dl.org/bug . Make sure you are using the latest v
ersion; type youtube-dl -U to update. Be sure to call youtube-dl with the --ve
rbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\extractor\common.py", line 427, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\extractor\vbox7.py", line 78, in _real_extract
KeyError: 'title'
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\extractor\common.py", line 427, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\extractor\vbox7.py", line 78, in _real_extract
KeyError: 'title'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\YoutubeDL.py", line 761, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpvd2cwzkd\bu
ild\youtube_dl\extractor\common.py", line 440, in extract
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by Key
Error('title',)); please report this issue on https://yt-dl.org/bug . Make sure
you are using the latest version; type youtube-dl -U to update. Be sure to cal
l youtube-dl with the --verbose flag and include its complete output.
...
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: https://www.vbox7.com/play:bcb87e7c29
---
### Description of your *issue*, suggested solution and other information
Cannot download from www.vbox7.com this url https://www.vbox7.com/play:bcb87e7c29
| nsfw | low | Critical |
215,265,738 | TypeScript | Type JSX elements based on createElement function | TypeScript currently uses a JSX namespace to type the props of JSX elements. This is customisable by modifying `JSX.IntrinsicElements`, `JSX.ElementClass`. However, the type of an element is always `JSX.Element`.
Of course more interfaces could be added to the `JSX` namespace. However, I think that with less effort, the compiler could be made more flexible. I'd propose to check JSX elements based on a (virtual) call to `JSX.createElement`. For instance, the current behaviour can approximately be written like this:
```typescript
namespace JSX {
// intrinsic elements
function createElement<K extends keyof JSX.IntrinsicElements>(tag: K, props: JSX.IntrinsicElements[K], children: JSX.Element[]): JSX.Element;
// class and functional components
function createElement<P>(component: (JSX.ElementClass & { new(): { props: P } }) | ((props: P) => JSX.Element), props: P, children: JSX.Element[]): JSX.Element;
}
```
Given that function signatures are well customisable with the use of generics for instance, most requests can be implemented this way. For instance, #13890 and #13618 would benefit from this change. Libraries that use JSX, but not on the React-way, will benefit from this too.
## Proposed semantics
For a JSX element, a virtual call to `JSX.createElement` is constructed. It is passed three arguments:
1. Tag name (string) in case of an intrinsic argument (`<div />`). Otherwise, the identifier is passed (`Foo` for `<Foo />`).
2. An object containing the props.
3. An array containing the children.
This should be roughly the same as the JSX transform used in the emitter phase. One notable difference is the following: in case of no properties or no children, an empty object or an empty array should be passed, instead ignoring the argument. This makes it easier to write `JSX.createElement` for library authors.
## Backwards compatibility
For backwards compatibility, one of the following approaches could be taken:
- Use old logic if `JSX.createElement` does not exist.
- If `JSX.createElement` does not exist, default it to (roughly) the definition above.
## Error reporting
When type checking the generated function call, the checker can give error messages like "Argument of type .. " or "Supplied parameters do not match any signature of call target". These messages should be replaced when checking JSX elements. | Suggestion,In Discussion,Fix Available | high | Critical |
215,433,319 | go | mime: BEncoding and QEncoding don't respect the 76 character line limit in RFC2047 | As a continuation of Issue #12300, mime: BEncoding and QEncoding don't respect the 76 character line limit in RFC2047.
Here is the relevant part from Section 2 of RFC2047. (emphasis mine)
> An 'encoded-word' may not be more than 75 characters long, including
> 'charset', 'encoding', 'encoded-text', and delimiters. If it is
> desirable to encode more text than will fit in an 'encoded-word' of
> 75 characters, multiple 'encoded-word's (**separated by CRLF SPACE**) may
> be used.
>
> While there is no limit to the length of a multiple-line header
> field, **each line of a header field that contains one or more
> 'encoded-word's is limited to 76 characters**.
### What version of Go are you using (`go version`)?
1.8
### What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=E:\gowork\
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\graj04\AppData\Local\Temp\go-build930053034=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1
### What did you do?
https://play.golang.org/p/vO6pcZgesh
### What did you expect to see?
```
=?utf-8?q?=C2=A1Hola,_se=C3=B1or_this_is_to_see_what_happens_if_the_test_?=
=?utf-8?q?is_really_long._ltkhetslk_lskthe_lt_slkth_sekltse_ltksht_lskejt?=
=?utf-8?q?_lsht_lsht_lht_lht_lsht_lhtlshtlsetlksje_tlsejt_lksetlkse_tlkse?=
=?utf-8?q?_tlkst_lkstlkst_lskht_lstlsht_lshtlshtlshtslhtlshtlstle_tlse_tl?=
=?utf-8?q?se_tlkse_tlkse_tlse_tlst_lsetlstlset_setsle_tlset_lst_lset_lskt?=
=?utf-8?q?_alkthalkht_alkth_aeklth_aeslth_aeslth_eajraoiflanvwoalnwoaiehf?=
=?utf-8?q?_awesi_leahr_aflhf_awelh_aweh_awelh_wahwe_!?=
```
### What did you see instead?
```
=?utf-8?q?=C2=A1Hola,_se=C3=B1or_this_is_to_see_what_happens_if_the_test_?= =?utf-8?q?is_really_long._ltkhetslk_lskthe_lt_slkth_sekltse_ltksht_lskejt?= =?utf-8?q?_lsht_lsht_lht_lht_lsht_lhtlshtlsetlksje_tlsejt_lksetlkse_tlkse?= =?utf-8?q?_tlkst_lkstlkst_lskht_lstlsht_lshtlshtlshtslhtlshtlstle_tlse_tl?= =?utf-8?q?se_tlkse_tlkse_tlse_tlst_lsetlstlset_setsle_tlset_lst_lset_lskt?= =?utf-8?q?_alkthalkht_alkth_aeklth_aeslth_aeslth_eajraoiflanvwoalnwoaiehf?= =?utf-8?q?_awesi_leahr_aflhf_awelh_aweh_awelh_wahwe_!?=
```
| help wanted,NeedsFix | medium | Critical |
215,470,602 | react | Compiler Optimization Umbrella | Spinoff from https://github.com/reactjs/react-future/issues/50
I wanted to create an umbrella task for when we start working on compiler level optimizations. We've had [a tag](https://github.com/facebook/react/issues?q=is%3Aopen+is%3Aissue+label%3A%22Component%3A+Optimizing+Compiler%22) open for a while but these are fairly primitive optimizations. We want to be able to go further.
I don't think we'll start this project immediately but soon after the Fiber stuff is in place.
__Compiler Infra__
- [ ] Base-line cross-module full JavaScript AOT compiler.
- [ ] Compiler infra structure that fits well into existing tooling at FB, Webpack, Rollup based ecosysem etc. Support parallelism and incremental builds.
- [ ] Solve things like what the npm ecosystem should do. Compile before publishing or after? Probably after.
__Optimizations__
- [ ] Enable multiple levels of host instances / DOM elements to be managed by a single Fiber. I think this is probably a key requirement for many optimizations. I'm not sure if that Fiber's children will have a single placement point (the parent that they get inserted into) or if it could have multiple insertion points. If it manually does the insertion of its children, then the later would work.
- [ ] Optimizing pure host/DOM elements ("string" components). Can be reasoned about at the core compiler level.
- [ ] Inlining pure functional components so that now the result can be reasoned about as a flat component.
- [ ] Basic constant folding for static configuration.
- [ ] Optimizing across component boundaries without inlining.
- [ ] Optimizing stateful functional components.
__Runtime Optimizations__
- [ ] Dead-code elimination of library code that isn't needed by a particular application. Such as certain events, controlled components or complex attributes.
__Stretch Goals__
- [ ] Computing delta updates after code changes and lets Service Workers update based on that.
More to come... | Type: Umbrella,React Core Team | medium | Critical |
215,471,600 | go | doc: Update documentation on cherry-picking | The current documentation on "Reviewing code by others" in the contribution guidelines is for the old Gerrit UI. The new Gerrit UI does not have the same "Download" button, and when one goes to More/Cherry Pick it appears it needs to be cherry-picked onto another branch on Gerrit. I was also unable to reverse engineer the provided `git` call to apply in a new situation.
It's reasonable to ask users to test if commits resolve issues, but it would be nice to provide clean documentation on how to do so. My recommendations:
- Making it its own section, possibly above Making a Contribution. Right now, the section is a tiny section at the bottom that is easy to miss.
- Update the documentation to the new Gerrit UI
- Some discussion on how to properly apply a patch given an issue, i.e. given an installation from source at current stable, list the correct steps. Checkout branch? Checkout master, then branch, then apply patch? | Documentation,help wanted,NeedsFix | low | Minor |
215,535,187 | go | proposal: spec: change int to be arbitrary precision | An idea that has been kicking around for years, but never written down:
The current definition of `int` (and correspondingly `uint`) is that it is either 32 or 64 bits. This causes a variety of problems that are small but annoying and add up:
- overflow when constants like math.MaxUint64 is automatically promoted to `int` type
- maximum size of a byte slice is only half the address space on a 32-bit machine
- `int` values can overflow silently, yet no one depends on this working. (Those who want overflow use sized types.)
- great care must be taken with conversion between potentially large values, as information can be lost silently
- many more
I propose that for Go 2 we make a profound change to the language and have `int` and `uint` be arbitrary precision. It can be done efficiently - many other languages have done so - and with the new compiler it should be possible to avoid the overhead completely in many cases. (The usual solution is to represent an integer as a word with one bit reserved; for instance if clear, the word points to a big.Int or equivalent, while if set the bit is just cleared or shifted out.)
The advantages are many:
- `int` (and `uint`, but I'll stop mentioning it now) become very powerful types
- overflow becomes impossible, simplifying and securing many calculations
- the default type for `len` etc. can now capture any size without overflow
- we could permit any integer type to be converted to `int` without ceremony, simplifying some arithmetical calculations
Most important, I think it makes Go a lot more interesting. No language in its domain has this feature, and the advantages of security and simplicity it would bring are significant. | LanguageChange,Proposal,Proposal-FinalCommentPeriod,LanguageChangeReview | high | Critical |
215,542,388 | kubernetes | Feature Request: enable user-managed Pod Migration | A user wants to extend Kubernetes to allow for application-specific migration in response to pod deletion events, whenever possible.
1. Normally, there should be 1 instance of a pod -- call it `pod-1`.
1. However, something (usually the system, e.g. rescheduler or node upgrades) wants to delete `pod-1`, then a replica, `pod-2` should be created.
1. Before `pod-1` is actually terminated, it will discover `pod-2` and they will do an application-level handoff of state.
1. After handoff, scale down to just 1 pod, for economy.
This issue is created to suggest possible ways to implement this pattern.
| sig/scheduling,sig/apps,lifecycle/frozen | low | Major |
215,572,529 | vscode | `editor.fontFamily` in settings should suggest list of available monospace fonts | _From @letientai299 on March 16, 2017 9:57_
_Copied from original issue: Microsoft/vscode-docs#889_ | feature-request,settings-editor | medium | Critical |
215,677,062 | rust | refactor the `AssociatedItem` structures | During the work on https://github.com/rust-lang/rust/pull/40668, there was some discussion about refactoring the `ty::AssociatedItem` and `hir::{Impl,Trait}ItemRef` data structures. The precise plan is a *bit* unclear, so I'm opening this issue to try and discuss and lay it out.
Observations:
- Although `ty::AssociatedItem` lives in `ty`, it has no real dependencies and is based entirely on the HIR, so it would better live in HIR.
- The existing `ImplItemRef` and `TraitItemRef` are basically specialized variants of `AssociatedItem`, though they add a `Span` and use local-ids (`ImplItemId`) rather than a `DefId`.
- There is a need for a query that given a `DefId` gives you back the `AssociatedItem` (including across crates). The local-crate portion of this query seems like it could live in `hir::map` quite nicely.
- Some of this setup is carefully crafted to avoid incorrect incremental dependencies and can change as we progress on the proposed red/green changes (in particular, the current query goes to some lengths to avoid reading from `Hir(X)` when computing `AssociatedItem(X)`, instead reading from the containing impl/trait; this is because we don't want to require everything that needed even basic information about `X` to have to change when `X` changes).
cc @eddyb @cramertj | C-cleanup,A-associated-items,T-compiler | low | Minor |
215,720,084 | go | encoding/base64: decoding is slow | ### What version of Go are you using (`go version`)?
Go 1.8
### What operating system and processor architecture are you using (`go env`)?
amd64
### What did you do?
On my slow computer, using encoding/base64, I can decode data at ~100MB/s.
It should be much faster as shown by https://github.com/aklomp/base64
I'm planning to work on this in my spare time. This issue tracks this effort. | Performance | medium | Major |
215,743,325 | TypeScript | raise a type error on attempt to strict-equal-compare a value of string | null to undefined | the following examples are almost certainly bugs:
```typescript
declare var one: string | undefined;
// expected a type error: Operator '===' cannot be applied to types 'string | undefined' and 'null'
// actual no problem
if (one === null) {
// unreachable, because one can't ever be null, undefined was likely meant instead
}
```
```typescript
declare var another: string | null;
// expected a type error: Operator '===' cannot be applied to types 'string | null' and 'undefined'
// actual no problem
if (another === undefined) {
// unreachable, because one can't ever be undefined, null was likely meant instead
}
```
consider raising a type error for the above situations
| Suggestion,Awaiting More Feedback | medium | Critical |
215,831,991 | angular | There is no way to access inputs or outputs of Components created by NgComponentOutlet | **I'm submitting a ...** (check one with "x")
```
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```
**Current behavior**
There is no way to set @Inputs or subscribe to @Output events of the Component created by `NgComponentOutlet`.
**Expected behavior**
I expect some to set values and to subscribe events.
**What is the motivation / use case for changing the behavior?**
At least, we should have the same level of functionality as `ViewContainerRef.createComponent()` which is roughly the programatic equivalent of `NgComponentOutlet`. That function returns a `ComponentRef<any>` which provides an instance property that allows direct access to the class instance of the Component. The original feature request for `NgComponentOutlet` defined an event on the directive that would fire and pass this `ComponentRef` object after creation. This did not make it into the current implementation and I see no other alternatives to access inputs/outputs.
Supporting only Components with no inputs or outputs severely limits the usefulness of `NgComponentOutlet`.
* **Angular version:** 4.0.0-rc.1
| feature,area: common,feature: under consideration | high | Critical |
215,872,016 | rust | Switch `run-make` tests from Makefiles to rust | Rust currently has a suite of [`run-make`](https://github.com/rust-lang/rust/tree/master/src/test/run-make) tests, which generally test specific `rustc` invocations or behaviour, or require external tools (eg. `grep` or `nm`).
The goal of this issue is to rewrite these `run-make` tests, which are currently written as Makefiles, in rust to a) get rid of the dependency on external tools such as `make` and b) make them more accessible to rust contributors by not requiring arcane knowledge of the `make` tool.
The transition will require at least the following steps:
* [ ] Survey the existing `run-make` tests with regard to what they actually do / which programs they use (and how). I assume the programs will likely fall into one of three categories:
* Rust tools (`rustc`, `rustdoc`)
* Utilities easily replaceable by rust code, eg. `grep`
* Complex utilities, eg. `nm`, which cannot be easily rewritten in rust
* [ ] Design and (partially) implement a support library, which makes the actions identified above easily possible. For example I imagine a test should look something like this:
```rust
extern crate support;
fn main() {
let s = support::init();
let lib = s.rustc().compile("file1.rs").output_rlib();
assert!(s.nm(lib).filter_lines("some_symbol").count() == 2);
}
```
* [ ] Add a new mode to [`compile-test`](https://github.com/rust-lang/rust/tree/master/src/tools/compiletest), maybe `run-rmake`, which runs the new rust-based `run-make` tests. This will either include compiling the support library, or receiving the support library from a previous build stage.
* [ ] Start porting the actual `run-make` tests, which may involve adding additional functionality to the support library. At that time this issue, or another, will track the state of all the existing tests and include some detailed instruction to allow people to easily contributing by porting one of the existing tests.
---
There are some open questions:
* Should the support library allow execution of arbitrary commands? Limiting commands to only those explicitly added to the support library would mean that there is a single place which lists the external tools we depend on.
* Is the proposed integration with `compiletest` the correct choice? For example the support library itself may have external dependencies (maybe `regex` or `gcc-rs`) which means we should probably use cargo to compile the actual tests. At which point it may be worth considering if `compile-test` is needed at all or if cargo is enough (Have the support library in `src/lib.rs`, the new `run-make` tests in `tests/*.rs` and auxiliary files in subdirectories of `tests/` named after the main test file).
---
If anyone wants to get involved in the process, please leave a comment on this issue or ping me on IRC.
---
<details><summary>Original Issue Description</summary>
Based on a short experiment, it looks like rust on msvc only has five build dependencies: Visual Studio, Git, Python, CMake and make, where make is only used for the `run-make` tests as far as I can tell.
Of those five, the first four are easily installable natively on windows, whereas make wasn't as straight forward to installe when I tried and required msys2 / mingw.
The questions the are:
* Is there any interest in performing such a conversion?
* If so, then which language should those tests be migrated to? Python or Rust seem like the logical choices.
* How should the switch happen? We'll probably want some kind of incremental strategy, since there are quite a few `run-make` tests.
</details> | A-testsuite,E-hard,C-enhancement,E-help-wanted,T-bootstrap,T-infra,A-compiletest,A-run-make | medium | Major |
215,891,093 | go | cmd/compile: use FP-based frame zeroing outside of package runtime on plan9 | In 039d455f9d3d5d5109424f15d86b7f9b63768b42, we changed cmd/compile to avoid using DUFFZERO and other FP-based frame zeroing methods, because they're not permitted within note handlers.
I think this is overly conservative. It should still be safe to use DUFFZERO on plan9 when we're compiling non-runtime packages, because functions from those packages will never be called by sigtramp. This is probably as simple as changing
var isPlan9 = obj.GOOS == "plan9"
to
var isPlan9 = obj.GOOS == "plan9" && compiling_runtime
in cmd/compile/internal/amd64/ggen.go.
Just pointing out since I was looking at related code. Will let some of the plan9 folks decide if this is worth pursuing.
/cc @0intro | Performance,OS-Plan9,NeedsInvestigation,compiler/runtime | low | Minor |
215,893,524 | go | x/build/kubernetes/gke: use non-deprecated auth | We're currently using `clusters.list` to get the certificate pair used to authenticate to the Kubernetes API. This is deprecated (and very confusing to set up in a new project). The docs say we should switch to just using OAuth directly with the API (which has the advantage that we don't need to also grant the coordinator permission to create new clusters).
/cc @bradfitz | Builders,NeedsFix | low | Minor |
215,902,659 | rust | Type inference incorrectly selects specialized instance of type parameter | ```rust
#![feature(specialization)]
use std::vec;
struct Foo<T>(T);
impl<T> Foo<T> {
fn foo<I: IntoIterator<Item = T>>(it: I) -> Foo<T> {
<Self as SpecExtend<_, _>>::from_iter(it.into_iter())
}
}
trait SpecExtend<T, I> {
fn from_iter(iter: I) -> Self;
}
impl<T, I> SpecExtend<T, I> for Foo<T>
where I: Iterator<Item = T>
{
default fn from_iter(iter: I) -> Self {
panic!()
}
}
impl<T> SpecExtend<T, vec::IntoIter<T>> for Foo<T> {
fn from_iter(iter: vec::IntoIter<T>) -> Self {
panic!()
}
}
fn main() {}
```
```
rustc 1.17.0-nightly (134c4a0f0 2017-03-20)
error[E0308]: mismatched types
--> <anon>:8:47
|
8 | <Self as SpecExtend<_, _>>::from_iter(it.into_iter())
| ^^^^^^^^^^^^^^ expected struct `std::vec::IntoIter`, found associated type
|
= note: expected type `std::vec::IntoIter<T>`
found type `<I as std::iter::IntoIterator>::IntoIter`
error: aborting due to previous error
```
@aturon | T-compiler,A-specialization,A-inference,C-bug,F-specialization | low | Critical |
215,935,876 | opencv | Stitcher not working on the real Windows Phone (Lumia 950) but works fine on emulator | ## System information (version)
- OpenCV => 3.0.0-dev (master)
- Operating System / Platform => Windows Phone 8.1
- Compiler => Visual Studio 2013
## Detailed description
Stitcher.stitch() function works pretty fine on Windows Phone emulators (x86 code, checked both WP8.1 and W10M) but fails on the real device (I used Microsoft Lumia 950 for development). From my code trace, I found that call of `matcher->knnMatch(features1.descriptors, features2.descriptors, pair_matches, 2);` in the **matchers.cpp** produces different **pair_matches** on emulator and real handset. Sorry, I can't trace this sophisticated code too deep.
I'm using [this picture set](https://www.dropbox.com/s/qwx5x8knyv6ob7x/test_images.zip?dl=0); for the test app, I've modified slightly (for simplicity) **opencv_perf_stitching** project by this way (added these lines at the beginning:
```
Mat pano;
vector<Mat> imgs;
imgs.push_back( imread( "1.jpg" ) );
imgs.push_back( imread( "2.jpg" ) );
imgs.push_back( imread( "3.jpg" ) );
Stitcher stitcher = Stitcher::createDefault();
auto result = stitcher.stitch(imgs, pano);
```
**Could you please fix this issue as soon as you can (or suggest workaround)? It's a real showstopper for me now :(**
## Steps to reproduce
- download and unzip [this picture set](https://www.dropbox.com/s/qwx5x8knyv6ob7x/test_images.zip?dl=0)
- open solution **OpenCV.sln**
- set active project **opencv_perf_stitching**
- modify source file **perf_stitch.cpp** as described above
- add images 1.jpg, 2.jpg, 3.jpg as a Content to the project
- build project on **x86** platform and run on emulator, **status** will be 0 (normal situation, panorama built)
- build project on **arm** platform and run on real phone, **status** will be 1, i.e. ERR_NEED_MORE_IMGS (matcher not found points) | bug,category: stitching,platform: winrt/uwp | medium | Critical |
215,979,030 | TypeScript | Allow an interface in the JSX namespace to specify the element class type | We're writing a non-react library that uses TS's JSX support with custom interfaces defined in the JSX namespace. Unless we are very much mistaken (The documentation seems a little out-of-date in this area? Most of our current understanding comes from reading through issues on here, we may have missed something.) it seems that while ElementClass can be used to define the type of the _element instance type_ there is no interface to limit the members of the _element class type_.
We have a custom component base-class and an equivalent to React's createElement function. Our createElement function needs to be able to create instances of the component classes. To be able to do this in a type-safe manner, we need to be able to specify an interface for the _element class type_ that can require a specific constructor signature.
This feels like an oversight in the current implementation TBH. With React itself it's even possible to create components with incompatible constructors that would fail at runtime. | Suggestion,In Discussion | low | Major |
216,002,644 | youtube-dl | Hallmark Channel | ## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.03.22*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.22**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [x] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
~$ youtube-dl http://www.hallmarkchanneleverywhere.com/Series/Episode/Words+from+the+Heart -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'http://www.hallmarkchanneleverywhere.com/Series/Episode/Words+from+the+Heart', u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.03.22
[debug] Python version 2.7.9 - Linux-3.16.0-4-686-pae-i686-with-debian-8.7
[debug] exe versions: avprobe 11.8-6, ffmpeg N-83692-gb8a7dcbde2-static, ffprobe N-83692-gb8a7dcbde2-static, rtmpdump 2.4
[debug] Proxy map: {}
[generic] Words+from+the+Heart: Requesting header
WARNING: Falling back on generic information extractor.
[generic] Words+from+the+Heart: Downloading webpage
[generic] Words+from+the+Heart: Extracting information
ERROR: Unsupported URL: http://www.hallmarkchanneleverywhere.com/Series/Episode/Words+from+the+Heart
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 1790, in _real_extract
doc = compat_etree_fromstring(webpage.encode('utf-8'))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2526, in compat_etree_fromstring
doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2515, 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: not well-formed (invalid token): line 20, column 31
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 761, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 428, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2653, in _real_extract
raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://www.hallmarkchanneleverywhere.com/Series/Episode/Words+from+the+Heart
<end of log>
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: http://www.hallmarkchanneleverywhere.com/Series/Episode/Words+from+the+Heart
- Single video: http://www.hallmarkchanneleverywhere.com/Series/Episode/5132
- Single video: http://www.hallmarkchanneleverywhere.com/Movies/Details/All%2527s%2bFair%2bin%2bLove%2band%2bAdvertising#
---
### Description of your *issue*, suggested solution and other information
Please add support for The Hallmark Channel (http://www.hallmarkchannel.com/)
| site-support-request,tv-provider-account-needed | low | Critical |
216,147,084 | flutter | iOS build fails with "SecKey API returned: -25308" "codesign failed with exit code 1" | ## Steps to Reproduce
Follow Getting started guide to create to create default "myapp"
Able to launch against simulator, but get following error against real iDevice
first run i get the standard message:
```
Could not build the precompiled application for the device.
══════════════════════════════════════════════════════════════════
Building an iOS app requires a selected Development Team with a Provisioning Profile
Please ensure that a Development Team is selected by:
1- Opening the Flutter project's Xcode target with
open ios/Runner.xcworkspace
2- Select the 'Runner' project in the navigator then the 'Runner' target
in the project settings
3- In the 'General' tab, make sure a 'Development Team' is selected
For more information, please visit:
https://flutter.io/setup/#deploy-to-ios-devices
```
I open the workspace as suggested and add my team. (Xcode set for automatic management of signing, I have a a valid wildcard provisioning profile)
i run flutter run again and get this error
```
/usr/bin/codesign --force --sign 7D8FC5A3FC9ADE6BFAA1B387E733C232D239A97F --preserve-metadata=identifier,entitlements --timestamp=none /Users/jeffa/Documents/myapp/build/ios/Release-iphoneos/Runner.app/Frameworks/Flutter.framework
SecKey API returned: -25308, (null)/Users/jeffa/Documents/myapp/build/ios/Release-iphoneos/Runner.app/Frameworks/Flutter.framework: unknown error -1=ffffffffffffffff
Command /usr/bin/codesign failed with exit code 1
Could not build the precompiled application for the device.
```
If I build/run the target from inside Xcode it launches on the device and runs.
Please tell us what you were doing and what went wrong. If you are running flutter tools from the command line, please try adding the `-v` or `--verbose` option to gather more information.
```
myapp $ flutter doctor -v
[[1m +178 ms[0m] /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[ +95 ms] Exit code 0 from: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[ ] 2.3
[ +12 ms] [/Users/jeffa/Documents/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[ +10 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[ ] origin/master
[ ] [/Users/jeffa/Documents/flutter/] git ls-remote --get-url origin
[ +9 ms] Exit code 0 from: git ls-remote --get-url origin
[ ] https://github.com/flutter/flutter.git
[ ] [/Users/jeffa/Documents/flutter/] git log -n 1 --pretty=format:%H
[ +12 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[ ] 15e51a9e3ed59b70605629b8bab1106b22354472
[ ] [/Users/jeffa/Documents/flutter/] git log -n 1 --pretty=format:%ar
[ +7 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[ ] 17 hours ago
[ +50 ms] [1m[‚úì] Flutter (on Mac OS X 10.12.3 16D32, channel master)[0m
[ ] [1m • Flutter at /Users/jeffa/Documents/flutter[0m
[ ] [1m • Framework revision 15e51a9e3e (17 hours ago), 2017-03-22 01:42:40[0m
[ ] [1m • Engine revision 6b9eda4a40[0m
[ ] [1m • Tools Dart version 1.23.0-dev.9.0[0m
[ +28 ms] [1m[‚úì] Host Executable Compatibility[0m
[ ] [1m • Downloaded executables execute on host[0m
[ +2 ms] /usr/libexec/java_home
[ +30 ms] Exit code 0 from: /usr/libexec/java_home
[ +1 ms] java -version
[[1m +288 ms[0m] [1m[‚úì] Android toolchain - develop for Android devices (Android SDK 25.0.2)[0m
[ ] [1m • Android SDK at /Users/jeffa/Library/Android/sdk[0m
[ ] [1m • Platform android-25, build-tools 25.0.2[0m
[ ] [1m • Java binary at: /Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/bin/java[0m
[ ] [1m • Java version: Java(TM) SE Runtime Environment (build 1.8.0_77-b03)[0m
[ +2 ms] xcode-select --print-path
[ +7 ms] Exit code 0 from: xcode-select --print-path
[ ] /Applications/Xcode.app/Contents/Developer
[ ] xcodebuild -version
[ +81 ms] Exit code 0 from: xcodebuild -version
[ ] Xcode 8.2.1
Build version 8C1002
[ ] xcrun clang
[ +12 ms] python -c import six
[ +99 ms] ideviceinstaller -h
[ +11 ms] ios-deploy --version
[ +17 ms] ios-deploy --version
[ +10 ms] Exit code 0 from: ios-deploy --version
[ ] 1.9.1
[ ] idevice_id -h
[ +6 ms] ios-deploy --version
[ +9 ms] ios-deploy --version
[ +8 ms] Exit code 0 from: ios-deploy --version
[ ] 1.9.1
[ +1 ms] idevice_id -l
[ +15 ms] 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ ] ideviceName
[[1m +103 ms[0m] pod --version
[[1m +429 ms[0m] pod --version
[[1m +421 ms[0m] Exit code 0 from: pod --version
[ ] 1.2.0
[ ] pod --version
[[1m +413 ms[0m] Exit code 0 from: pod --version
[ ] 1.2.0
[ ] [1m[‚úì] iOS toolchain - develop for iOS devices (Xcode 8.2.1)[0m
[ ] [1m • Xcode at /Applications/Xcode.app/Contents/Developer[0m
[ ] [1m • Xcode 8.2.1, Build version 8C1002[0m
[ ] [1m • ios-deploy 1.9.1[0m
[ ] [1m • CocoaPods version 1.2.0[0m
[ +1 ms] [1m[‚úì] Android Studio (version 2.3)[0m
[ ] [1m • Android Studio at /Applications/Android Studio.app/Contents[0m
[ ] [1m • Gradle version 3.2[0m
[ +3 ms] /Users/jeffa/Library/Android/sdk/platform-tools/adb devices -l
[ +14 ms] Exit code 0 from: /Users/jeffa/Library/Android/sdk/platform-tools/adb devices -l
[ ] List of devices attached
[ +16 ms] idevice_id -h
[ +6 ms] which idevice_id
[ +4 ms] Exit code 0 from: which idevice_id
[ ] /usr/local/bin/idevice_id
[ ] /usr/local/bin/idevice_id -l
[ +6 ms] Exit code 0 from: /usr/local/bin/idevice_id -l
[ ] 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ ] which ideviceinfo
[ +3 ms] Exit code 0 from: which ideviceinfo
[ ] /usr/local/bin/ideviceinfo
[ ] /usr/local/bin/ideviceinfo -k DeviceName -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ +91 ms] Exit code 0 from: /usr/local/bin/ideviceinfo -k DeviceName -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ ] JPHONE
[ ] which ideviceinstaller
[ +4 ms] Exit code 0 from: which ideviceinstaller
[ ] /usr/local/bin/ideviceinstaller
[ ] which idevice_id
[ +3 ms] Exit code 0 from: which idevice_id
[ ] /usr/local/bin/idevice_id
[ ] which ideviceinfo
[ +3 ms] Exit code 0 from: which ideviceinfo
[ ] /usr/local/bin/ideviceinfo
[ ] which iproxy
[ +3 ms] Exit code 0 from: which iproxy
[ ] /usr/local/bin/iproxy
[ ] which idevicedebug
[ +3 ms] Exit code 0 from: which idevicedebug
[ ] /usr/local/bin/idevicedebug
[ ] which idevicesyslog
[ +3 ms] Exit code 0 from: which idevicesyslog
[ ] /usr/local/bin/idevicesyslog
[ ] which idevicescreenshot
[ +4 ms] Exit code 0 from: which idevicescreenshot
[ ] /usr/local/bin/idevicescreenshot
[ ] which ios-deploy
[ +4 ms] Exit code 0 from: which ios-deploy
[ ] /usr/local/bin/ios-deploy
[ +2 ms] /usr/bin/xcrun simctl list --json devices
[[1m +106 ms[0m] which ideviceinfo
[ +4 ms] Exit code 0 from: which ideviceinfo
[ ] /usr/local/bin/ideviceinfo
[ ] /usr/local/bin/ideviceinfo -k ProductVersion -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ +51 ms] Exit code 0 from: /usr/local/bin/ideviceinfo -k ProductVersion -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ ] 10.2.1
[ ] which ideviceinfo
[ +4 ms] Exit code 0 from: which ideviceinfo
[ ] /usr/local/bin/ideviceinfo
[ ] /usr/local/bin/ideviceinfo -k BuildVersion -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ +46 ms] Exit code 0 from: /usr/local/bin/ideviceinfo -k BuildVersion -u 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a
[ ] 14D27
[ +2 ms] [1m[‚úì] Connected devices[0m
[ ] [1m • JPHONE • 3d8b0e4ef50ee06b16f82dbef3f7c8af20df310a • ios • iOS 10.2.1 (14D27)[0m
[ ] [1m • iPhone 6 • 19D068F4-F0DA-4F31-8FA3-A52546429DB1 • ios • iOS 10.2 (simulator)[0m
[ ] 'flutter doctor' took 2765ms.
[[1m +260 ms[0m] ensureAnalyticsSent: 258ms
[ +2 ms] exiting with code 0
```
myapp $ flutter analyze
Analyzing lib/main.dart...
No analyzer warnings! (ran in 6.0s) | platform-ios,tool,t: xcode,P2,team-ios,triaged-ios | low | Critical |
216,177,507 | TypeScript | Improve feedback for abstract class instantiation error messages | <!-- BUGS: Please use this template. -->
<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->
<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->
**SUGGESTION**
Recently, I was trying to use a library written in ES2015 in an Ionic 2 project, and kept getting a `Cannot instantiate abstract class 'Foo'`. `Foo` is a concrete class that extends abstract class `Bar`, which extends abstract class `Baz`. The problem turned out to be a typo in `Bar.d.ts` (see below), which (I believe) made Typescript think that `Foo` did not implement some abstract methods of `Bar` and/or `Baz` (I'm still not sure which), but it took me a day and half to figure out what was going on. This error message should have more information about why `Foo` is abstract: `Foo is declared as abstract` or `Foo does not implement abstract methods ...`
**TypeScript Version:** 2.0.9
**Code**
**`Baz.d.ts`**
```ts
export as namespace Baz;
declare abstract class Baz {
abstract baz(): string;
}
```
**`Bar.d.ts`**
```ts
export as namespace BarTypo;
declare abstract class Bar extends Baz {
abstract foo(): void;
abstract bar(): string;
baz(): string;
}
export { Bar };
```
**`Foo.d.ts`**
```ts
import { Bar } from './bar.d';
export as namespace Foo;
declare class Foo extends Bar {
constructor(opts?);
foo(): void;
bar(a: string): string;
}
export { Foo };
```
**`otherProject.ts`**
```ts
import { Foo } from 'library';
export class Service {
foo: Foo;
constructor() {
this.foo = new Foo({ opt: true });
}
}
```
**Expected behavior:**
`Error: Cannot instantiate abstract class 'Foo'. It does not implement abstract method(s): baz.`
OR
`Error: Cannot instantiate abstract class 'Foo'. It does not implement abstract method(s): foo, bar.`
OR
`Error: Cannot instantiate abstract class 'Foo'. It does not implement abstract method(s): baz (from Baz); foo, bar (from Bar).`
**Actual behavior:**
`Error: Cannot instantiate abstract class 'Foo'.`
| Suggestion,Help Wanted,Effort: Moderate,Experience Enhancement | low | Critical |
216,237,392 | go | x/build: make trybots refuse to test a commit that's too old | Make trybots refuse to test a commit with a git parent over N commits or days old.
Related to but different than #9858 | Builders | low | Major |
216,310,498 | go | x/tools/go/ssa: docs describe a non-existent DebugRef.Object method | The documentation for the [DebugRef type](https://godoc.org/golang.org/x/tools/go/ssa#DebugRef) describes the possible values returned by the Object method. However, no such method exists.
As far as I can tell, the method has never existed; the comment, however, dates back to at least 2013. Should the method be added, or the comment removed?
/cc @alandonovan @griesemer | Documentation,NeedsInvestigation,Tools | low | Critical |
216,339,417 | go | html/template: dynamic substrings in HTML tags or attributes can result in unsafe HTML output | The following template:
```html
<s{{.X}}>alert('pwned')</script>
```
produces the following HTML output when executed with `X = "cript"`:
```html
<script>alert('pwned')</script>
```
This happens because:
* **During HTML parsing/escaping time**, the parser interprets "s" as the tag name, since the rest of the tagname will only be evaluated at execution-time. This causes the escaper to transition into the plain-text state, rather than the JS state, inside the script element body.
* **During execution time**, the htmlNameFilter inserted into `{{.X}}` (i.e. `{{.X | _html_template_htmlnamefilter`) sees the text value `"cript"`, deems that it is a safe HTML tag/attribute name, and renders it as-is.
In general, allowing dynamic substrings in HTML tags or attributes may confuse the parser and escaper, since the static and dynamic parts of the name are handled in different phases.
**Suggested solution:** disallow dynamic substrings in HTML tags or attributes completely.
| help wanted,NeedsFix | low | Major |
216,349,717 | go | x/tools/go/ssa: make opaqueType less annoying to use | The ssa package defines an opaqueType, which is an "opaque and degenerate" type, currently used by the Range instruction. It truly is degenerate, embedding a nil types.Type, causing a call to types.Type.Underlying to panic.
Code that wants to operate on the types of instructions needs to specifically check for the Range instruction and skip it. There doesn't seem to be a way to check for this degenerate type specifically, which would at least permit passing types around without having to keep track of the originating instruction.
The simplest solution that I can think of is to implement Underlying as the identity function. However I suspect that this hasn't been done for a good reason?
/cc @alandonovan | Tools | low | Minor |
216,415,498 | go | x/image/webp: issue with colors contrast when converting to jpeg/png | When i try to convert a webp image to a PNG image doing like that: https://play.golang.org/p/yAGNTfQrx2
The converted PNG dont keep the same "contrast" as the source webp image, while it's ok when converting the webp image with:
`dwebp in.webp -o out.png`
The same thing occurs when i convert a WEBP to JPEG.
- webp image (in.webp) : https://files.fm/f/dygrmekf
- png image (converted with dwebp cmd) : https://files.fm/f/hx2thfdn
- png image (converted with webp.Decode()->png.Encode()) : https://files.fm/f/2hws9psu
Im using go1.8 darwin/amd64
| NeedsInvestigation | low | Minor |
216,445,813 | vscode | Add dropdown for search input history | - VSCode Version: 1.10
- OS Version: Windows 10
Very closely related to https://github.com/Microsoft/vscode/issues/18735
This is a feature request. The UX around `find` is the one place where VS Code is not quite perfect - which speaks volumes to how wonderful this editor is. Wonderful job.
Basically, it would be great if, inside the `Find` box you could hit the down arrow and get a dropdown of prior searches which you could navigate between to re-search. | feature-request,search,editor-find | high | Critical |
216,474,539 | create-react-app | Show a transparent overlay with development warnings | As proposed [here](https://github.com/facebookincubator/create-react-app/issues/1873#issuecomment-288726204), maybe we should have a transparent "warning overlay" which is dismiss-able. | issue: proposal | low | Major |
216,481,410 | vscode | Allow to configure editor auto reload behaviour | **VSCode Version:** 1.10.2
**OS Version:** macOS 10.12.3
**Steps to Reproduce:**
1. Open editor
2. Modify a file in your git repository, but don't save it
3. Checkout a different branch that touches the same file
4. Go back to the editor and try to save
5. ERROR: "Failed to save 'file1': The content on disk is newer. Click on Compare to compare your version with the one on disk."
Personally I would like to see the files being reload from the disk every time without prompt. With git I don't have to worry about losing history. Similar to how SublimeText works. When the files change in disk (ex: change of branches), they get automatically reloaded, independently of their current state in the editor. I prefer this behaviour, rather than having to confirm reloads.
With that said however, **there must be options for all the use cases**. Many people prefer to be notified of changes in their files!
Suggestion to add an `editor.autoReload` parameter in order to control this behaviour. Possible values:
* `Always` - reload from disk without prompt
* `Confirm` - show a prompt confirmation to either accept or discard the changes
* `Backup` - show the file with the new changes automatically, but always backup the old state to 'filename.bak'
* `Never` - current behaviour?
Evolved the idea from @rmunn on [#23043](https://github.com/Microsoft/vscode/issues/23043#issuecomment-288601201) issue. Decided it was best to create a separate issue for this.
EDIT: Made it clear that it is mandatory to implement this feature with all the use cases in mind, and added new options. | feature-request,workbench-editors,keep | high | Critical |
216,583,890 | go | cmd/compile: eliminate base.Pos and ir.CurFunc | This is an umbrella issue for eliminating the global `lineno` variable from package gc. Filing as a HelpWanted issue because I think it's a relatively low-barrier-to-entry issue that people can usefully contribute to the compiler with small incremental improvements.
Here's the general algorithm:
1. Identify a function `Bar` that uses lineno.
2. Split it into two functions `Bar` and `Barl`; `Barl` takes an additional `pos src.XPos` parameter, and `Bar` just calls `Barl` with `lineno`.
3. Change callers of `Bar` to use `Barl`. Ideally, the caller can supply the position information directly (e.g., via `n.Pos` or something); but if necessary, just use `lineno` and later we'll recursively apply this procedure on the caller function.
An example of this is `yyerror` and `Warn` now have `yyerrorl` and `Warnl' functions that we're trying to use instead.
Note: sometimes uses of lineno should just go away entirely (e.g., CL 38393 / 80c4b53e1e5159cc440e52c906583edc1eb79abc). I suggest pinging here to discuss instances and/or express interest in working on this to avoid duplicating work (e.g., @josharian and I are looking at this in the backend for #15756). | help wanted,NeedsFix,compiler/runtime | medium | Critical |
216,585,386 | rust | No unused import for std::f64 if only f64 types used | I recently came across several instances of the following problem in a code base:
```rust
use std::f64; // No warning.
fn main() {
let x: f64 = 0.0;
println!("{}", x);
}
```
Why this didn't cause a warning baffled me for a while, until I realize that it was actually imported the *type* `f64`, even though I had been using it up until that point as a module like:
```rust
use std::f64;
fn main() {
println!("{}", f64::consts::PI);
}
```
Then later, when I refactored the code (more complex than this toy example), something like this was left:
```rust
use std::f64; // No warning for "unused" import, but it is not necessary.
use std::f64::consts::PI;
fn main() {
let x: f64 = 0.0;
println!("{}", PI + x);
}
```
In this final case, it would be great if `rustc` warned about this since `f64` is always implicitly in scope as a primitive type (I didn't think you could actually import it?).
Is this a case where the unused import lint got confused incorrectly? | A-lints,A-resolve,T-compiler,C-bug | low | Minor |
216,633,140 | TypeScript | TypeScripts Type System is Turing Complete | This is not really a bug report and I certainly don't want TypeScripts type system being restricted due to this issue. However, I noticed that the type system in its current form (version 2.2) is turing complete.
Turing completeness is being achieved by combining mapped types, recursive type definitions, accessing member types through index types and the fact that one can create types of arbitrary size.
In particular, the following device enables turing completeness:
```typescript
type MyFunc<TArg> = {
"true": TrueExpr<MyFunction, TArg>,
"false": FalseExpr<MyFunc, TArg>
}[Test<MyFunc, TArg>];
```
with `TrueExpr`, `FalseExpr` and `Test` being suitable types.
Even though I didn't formally prove (edit: in the meantime, I did - see below) that the mentioned device makes TypeScript turing complete, it should be obvious by looking at the following code example that tests whether a given type represents a prime number:
```typescript
type StringBool = "true"|"false";
interface AnyNumber { prev?: any, isZero: StringBool };
interface PositiveNumber { prev: any, isZero: "false" };
type IsZero<TNumber extends AnyNumber> = TNumber["isZero"];
type Next<TNumber extends AnyNumber> = { prev: TNumber, isZero: "false" };
type Prev<TNumber extends PositiveNumber> = TNumber["prev"];
type Add<T1 extends AnyNumber, T2> = { "true": T2, "false": Next<Add<Prev<T1>, T2>> }[IsZero<T1>];
// Computes T1 * T2
type Mult<T1 extends AnyNumber, T2 extends AnyNumber> = MultAcc<T1, T2, _0>;
type MultAcc<T1 extends AnyNumber, T2, TAcc extends AnyNumber> =
{ "true": TAcc, "false": MultAcc<Prev<T1>, T2, Add<TAcc, T2>> }[IsZero<T1>];
// Computes max(T1 - T2, 0).
type Subt<T1 extends AnyNumber, T2 extends AnyNumber> =
{ "true": T1, "false": Subt<Prev<T1>, Prev<T2>> }[IsZero<T2>];
interface SubtResult<TIsOverflow extends StringBool, TResult extends AnyNumber> {
isOverflowing: TIsOverflow;
result: TResult;
}
// Returns a SubtResult that has the result of max(T1 - T2, 0) and indicates whether there was an overflow (T2 > T1).
type SafeSubt<T1 extends AnyNumber, T2 extends AnyNumber> =
{
"true": SubtResult<"false", T1>,
"false": {
"true": SubtResult<"true", T1>,
"false": SafeSubt<Prev<T1>, Prev<T2>>
}[IsZero<T1>]
}[IsZero<T2>];
type _0 = { isZero: "true" };
type _1 = Next<_0>;
type _2 = Next<_1>;
type _3 = Next<_2>;
type _4 = Next<_3>;
type _5 = Next<_4>;
type _6 = Next<_5>;
type _7 = Next<_6>;
type _8 = Next<_7>;
type _9 = Next<_8>;
type Digits = { 0: _0, 1: _1, 2: _2, 3: _3, 4: _4, 5: _5, 6: _6, 7: _7, 8: _8, 9: _9 };
type Digit = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9;
type NumberToType<TNumber extends Digit> = Digits[TNumber]; // I don't know why typescript complains here.
type _10 = Next<_9>;
type _100 = Mult<_10, _10>;
type Dec2<T2 extends Digit, T1 extends Digit>
= Add<Mult<_10, NumberToType<T2>>, NumberToType<T1>>;
function forceEquality<T1, T2 extends T1>() {}
function forceTrue<T extends "true">() { }
//forceTrue<Equals< Dec2<0,3>, Subt<Mult<Dec2<2,0>, _3>, Dec2<5,7>> >>();
//forceTrue<Equals< Dec2<0,2>, Subt<Mult<Dec2<2,0>, _3>, Dec2<5,7>> >>();
type Mod<TNumber extends AnyNumber, TModNumber extends AnyNumber> =
{
"true": _0,
"false": Mod2<TNumber, TModNumber, SafeSubt<TNumber, TModNumber>>
}[IsZero<TNumber>];
type Mod2<TNumber extends AnyNumber, TModNumber extends AnyNumber, TSubtResult extends SubtResult<any, any>> =
{
"true": TNumber,
"false": Mod<TSubtResult["result"], TModNumber>
}[TSubtResult["isOverflowing"]];
type Equals<TNumber1 extends AnyNumber, TNumber2 extends AnyNumber>
= Equals2<TNumber1, TNumber2, SafeSubt<TNumber1, TNumber2>>;
type Equals2<TNumber1 extends AnyNumber, TNumber2 extends AnyNumber, TSubtResult extends SubtResult<any, any>> =
{
"true": "false",
"false": IsZero<TSubtResult["result"]>
}[TSubtResult["isOverflowing"]];
type IsPrime<TNumber extends PositiveNumber> = IsPrimeAcc<TNumber, _2, Prev<Prev<TNumber>>>;
type IsPrimeAcc<TNumber, TCurrentDivisor, TCounter extends AnyNumber> =
{
"false": {
"true": "false",
"false": IsPrimeAcc<TNumber, Next<TCurrentDivisor>, Prev<TCounter>>
}[IsZero<Mod<TNumber, TCurrentDivisor>>],
"true": "true"
}[IsZero<TCounter>];
forceTrue< IsPrime<Dec2<1,0>> >();
forceTrue< IsPrime<Dec2<1,1>> >();
forceTrue< IsPrime<Dec2<1,2>> >();
forceTrue< IsPrime<Dec2<1,3>> >();
forceTrue< IsPrime<Dec2<1,4>>>();
forceTrue< IsPrime<Dec2<1,5>> >();
forceTrue< IsPrime<Dec2<1,6>> >();
forceTrue< IsPrime<Dec2<1,7>> >();
```
Besides (and a necessary consequence of being turing complete), it is possible to create an endless recursion:
```
type Foo<T extends "true", B> = { "true": Foo<T, Foo<T, B>> }[T];
let f: Foo<"true", {}> = null!;
```
Turing completeness could be disabled, if it is checked that a type cannot use itself in its definition (or in a definition of an referenced type) in any way, not just directly as it is tested currently. This would make recursion impossible.
//edit:
A proof of its turing completeness can be found [here](https://gist.github.com/hediet/63f4844acf5ac330804801084f87a6d4) | Discussion | high | Critical |
216,637,497 | rust | To debug cargo project cause lots of 'symbol not found' problems on OSX | My workspace is on OSX. If I `touch hello.rs`, `rustc -g hello.rs` and then `gdb -q hello` of a single .rs file, there won't be any problem and it will load symbols successfully. However, when I use `cargo new hello --bin`, `cd hello`, then `cargo build` and then `gdb -q target/debug/hello`, it will be a blast on my iterm full of messages as follows:
```
>gdb -q target/debug/hello
Reading symbols from target/debug/hello...
warning: `/Users/zhengxiaolin/Documents/eclipse/hello/target/debug/deps/hello-aa762faea86652ac.0.o': can't open to read symbols: No such file or directory.
warning: can't find symbol '_ZN104_$LT$$RF$$u27$b$u20$collections..string..String$u20$as$u20$core..str..pattern..Pattern$LT$$u27$a$GT$$GT$13into_searcher17h12b3d7238e011a15E' in minsymtab
warning: can't find symbol '_ZN116_$LT$collections..borrow..Cow$LT$$u27$a$C$$u20$str$GT$$u20$as$u20$core..ops..AddAssign$LT$$RF$$u27$a$u20$str$GT$$GT$10add_assign17hdd8b6423379d7623E' in minsymtab
warning: can't find symbol '_ZN11collections3fmt6format17h622e78b799d1c558E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$10trim_right17ha60cffd510213a23E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$11into_string17h77e8e55aae74110bE' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$12encode_utf1617h4b31c1b570b71bf6E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$12escape_debug17h6eadad2fa42faab1E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$12to_lowercase17hdfeeabf72d2d11edE' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$12to_uppercase17hf48dd8c27a89e68dE' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$14escape_default17h52d3319153d73dafE' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$14escape_unicode17h116b615659071afdE' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$4trim17hbce03c1a35407699E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$6repeat17h6fe0557d17b09553E' in minsymtab
warning: can't find symbol '_ZN11collections3str21_$LT$impl$u20$str$GT$9trim_left17h015cef6fe5ab820fE' in minsymtab
warning: can't find symbol '_ZN11collections5btree3map16unwrap_unchecked28_$u7b$$u7b$closure$u7d$$u7d$14_MSG_FILE_LINE17he2a66a8a2be2ef68E' in minsymtab
warning: can't find symbol '_ZN11collections5slice10merge_sort14_MSG_FILE_LINE17h71c2ec20d499b44fE' in minsymtab
```
and so on.. My paste is only a small part. The no-symbol message has a lot..
Hope to solve the problem~ :) | A-linkage,O-macos,T-compiler,C-bug | medium | Critical |
216,642,394 | rust | Weird error message for missing symbol if module name is the same as a macro | ```
mod format {
mod sub {
pub fn foobar() { }
}
}
fn main() {
format::foobar();
}
```
```
$ rustc a.rs
error[E0423]: expected function, found macro `format::foobar`
--> a.rs:8:5
|
8 | format::foobar();
| ^^^^^^^^^^^^^^ did you mean `format::foobar!(...)`?
|
= help: possible better candidate is found in another module, you can import it into scope:
`use format::sub::foobar;`
error: aborting due to previous error
```
```
$ rustc --version
rustc 1.17.0-nightly (134c4a0f0 2017-03-20)
```
The weird thing is "expected function, found macro". `format::foobar` doesn't look like a macro. This also happens without the submodule `sub` (i.e. with an empty module `format`), the only difference is that no other candidate is suggested. | C-enhancement,A-diagnostics,A-resolve,A-macros,T-compiler | low | Critical |
216,652,325 | kubernetes | [Storage] Add support for capacity isolation of shared partitions | Based on https://github.com/kubernetes/community/pull/306
This issue is meant to track work items and help collaboration between the community on adding support for capacity isolation of shared partitions.
Note: Priority of these features can change based on the number of collaborators.
**v1.7**
Note: @jingxu97 has already been making progress on some of the items for v1.7.
- [x] Extend EmptyDir API Spec to include `SizeLimit` (Owner: @jingxu97) #45686
- [x] Define new resources in the API to surface node storage capacity (Owner: @jingxu97 ) #44785
- [x] Define new resources in the API to consume local storage (Owner: @jingxu97 ) #44785
- [x] Gate local storage as a resource with an alpha feature gate (Owner: @jingxu97 ) #44785
- [x] Kubelet expose local storage capacity for the primary partitions (Owner: @jingxu97) #46456
- [x] Kubelet supports & enforces storage reservation in Node Allocatable (Owner: @jingxu97) #46456
- [x] Kubelet enforces local storage limits by running a control loop that evicts pods that exceed their storage limits (Owner: @jingxu97) #45686
- [x] Kubelet specifies container overlay limits and enforces them by evicting pods (Owner: @jingxu97) #45686
- [x] Add a scheduler predicate that ensures that local storage is available while binding pods to nodes (Owner: @jingxu97 ) #46456
- [x] Add node e2es to ensure storage limit enforcement (Owner: @jingxu97) #46456 #45686
-------
**v1.8**
- [x] Add cluster e2es to verify scheduler local storage support (Owner: nickren) #51070
- [x] Require storage limits for all pods (or for Gu and Bu pods). Decision TBD (Owner: jingxu97)
- [x] Add local storage to downwards API (Owner: nickren) #49610 #50435
- [x] Extend Quota and Limitranges to support storage (Owner: nickren) #50757
- [x] Extend Metrics API to include storage and expose storage usage (Owner: jingxu97)
------
**v1.9**
- [ ] Introduce global limit ranges (Owner: jingxu97)
- [ ] Add default I/O rate limits for logs from containers (Owner: )
- [ ] Minimize disk metrics update latency by introducing support for project quota (Owner: )
- [ ] Extend Node Problem Detector to expose shared partition failures (Owner: )
cc @jingxu97 @kubernetes/sig-node-feature-requests @kubernetes/sig-storage-feature-requests | priority/important-soon,sig/scheduling,sig/storage,sig/node,kind/feature,milestone/removed,lifecycle/frozen | medium | Critical |
216,676,959 | opencv | Setting GPhoto camera widgets (properties) fails due to supplying an incorrect pointer to GPhoto library | - OpenCV => 3.2.0
- Operating System / Platform => Ubuntu/Linux
- Compiler => g++ 5.4.0
- GPhoto2 => version 2.5.9-3
##### Detailed description
Hello,
While using a GPhoto camera through the VideoCapture interface I noticed that it is not possible to set the values of text widgets in the camera.
While requesting the value of a widget of the type 'text', the getProperty function returns a double, which is actually a pointer to a char array.
Supplying this same value back to the camera's widget results in the failure of the setProperty call (the function returns 'false'). This also happens if pointers to a char array are provided. Because of this, it seems to be impossible to set text-based values for a GPhoto camera through openCV.
While looking at openCV's implementation it seems that instead of passing the pointer to the data, which is the 'double value' argument of setProperty, a pointer to the value argument is passed on to the GPhoto library. So in essence a pointer to a pointer to the data is passed on. This happens on line 793 in opencv/modules/videoio/src/cap_gphoto2.cpp
```.cpp
CR(gp_widget_set_value(widget, (void* )(intptr_t )&value));
```
Replacing it with
```.cpp
CR(gp_widget_set_value(widget, (void* )(intptr_t )value));
```
allows setting the text properties. Now a pointer to the actual data is passed on to the gp_widget_set_value call and the changes are visible after requesting the values through CV_CAP_PROP_GPHOTO2_WIDGET_ENUMERATE.
Also: providing a string to a function by casting its pointer to a double does look a bit strange. I'm also not even sure if it is safe: the double is converted to an int-like type (intptr_t), so can't this result in errors due to rounding? Maybe implementing setProperty functions for other types than 'double' would be better in the future? And also easier to understand?
| feature,category: videoio | low | Critical |
216,791,411 | rust | Mac lldb debuginfo behavior differs based on abs/rel input source path (?!) | I am observing varying behavior on my Mac depending on whether the input source files to `rustc` are denoted via an absolute source path or a relative one.
The test where I am seeing varying behavior is the `cross-crate-spans.rs` debuginfo test: https://github.com/rust-lang/rust/blob/master/src/test/debuginfo/cross-crate-spans.rs
In a nutshell: when I need to make a breakpoint for a line in the auxiliary crate (the `auxiliary/cross_crate_spans.rs` in the test in question), I am seeing the breakpoint get hit twice (as expected) when I use a relative paths, but the breakpoint gets hit only once when I use absolute paths to compile the same input files.
----
I have made a shell script to establish the context for the problem:
```sh
set -e
# set -x
RUSTC=rustc
# We'll set up and run the test in an isolated directory just to be safe.
# (Note: needs to be an absolute path for the rest of the script to make sense...)
WORKING_DIR=/tmp/work
mkdir -p $WORKING_DIR
cd $WORKING_DIR
# The behavior we observe will vary depending on the value of
# `$SRC_DIR`. The bad behavior seems to arise whenever SRC_DIR is an
# absolute directory (i.e. whenever it leads with the '/' character.)
case $1 in
abs) SRC1_DIR=$WORKING_DIR/abs/source ; echo "Aux in absolute source path: $SRC1_DIR" ;;
rel) SRC1_DIR=rel/source ; echo "Aux in relative source path: $SRC1_DIR" ;;
*) echo "You need to pass 'abs' or 'rel' as first input to script."; exit 1;
esac
case $2 in
abs) SRC2_DIR=$WORKING_DIR/abs/source ; echo "Main in absolute source path: $SRC2_DIR" ;;
# (switching to the below fixes things on my host system.)
rel) SRC2_DIR=rel/source ; echo "Main in relative source path: $SRC2_DIR" ;;
*) echo "You need to pass 'abs' or 'rel' as second input to script."; exit 1;
esac
mkdir -p $SRC1_DIR
mkdir -p $SRC2_DIR
# (I renamed the aux file because the dash/underscore differentiating
# convention drove me crazy. However, I have observed that reproducing
# tne bug *also* is sensitive to maintaining the specific filename
# `cross-crate-spans.rs` for the main file. Perhaps there is something
# with how we pun dash and underscore when inferring crate names from
# file names?)
AUX_FILE=$SRC1_DIR/aux.rs
MAIN_FILE=$SRC2_DIR/cross-crate-spans.rs
# Move the files into the source area. (You don't have to use `curl`;
# you can just copy it from your own repository...)
curl -s -o $AUX_FILE -O https://raw.githubusercontent.com/rust-lang/rust/8b1941a7831d715e36a414668a0b23146ff9cc2c/src/test/debuginfo/auxiliary/cross_crate_spans.rs
curl -s -o $MAIN_FILE -O https://raw.githubusercontent.com/rust-lang/rust/8b1941a7831d715e36a414668a0b23146ff9cc2c/src/test/debuginfo/cross-crate-spans.rs
LIB_DIR=$WORKING_DIR/libs
mkdir -p $LIB_DIR
MAIN_BIN=cross-crate-spans
# (Show how the compiler is being invoked in each case.)
set -x
$RUSTC -C opt-level=0 -g $AUX_FILE --crate-name cross_crate_spans --out-dir $LIB_DIR
$RUSTC -C opt-level=0 -g $MAIN_FILE -L $LIB_DIR -C prefer-dynamic -C rpath -o $MAIN_BIN
# $RUSTC -C opt-level=0 -g $MAIN_FILE -L $LIB_DIR -o $MAIN_BIN
lldb $MAIN_BIN
```
----
After invoking the above script (e.g. via `sh /tmp/script abs abs`), you then interact with `lldb` to finish reproducing the bug.
```
% rm -rf /tmp/work/ && sh /tmp/script rel rel
Aux in relative source path: rel/source
Main in relative source path: rel/source
+ rustc -C opt-level=0 -g rel/source/aux.rs --crate-name cross_crate_spans --out-dir /tmp/work/libs
+ rustc -C opt-level=0 -g rel/source/cross-crate-spans.rs -L /tmp/work/libs -C prefer-dynamic -C rpath -o cross-crate-spans
+ lldb cross-crate-spans
(lldb) target create "cross-crate-spans"
Current executable set to 'cross-crate-spans' (x86_64).
(lldb) b aux.rs:24
Breakpoint 1: 2 locations.
(lldb) r
Process 4893 launched: '/private/tmp/work/cross-crate-spans' (x86_64)
Process 4893 stopped
* thread #1: tid = 0xad2057, 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.2
frame #0: 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4893 resuming
Process 4893 stopped
* thread #1: tid = 0xad2057, 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4893 resuming
(lldb) Process 4893 exited with status = 0 (0x00000000)
(lldb) q
% rm -rf /tmp/work/ && sh /tmp/script rel abs
Aux in relative source path: rel/source
Main in absolute source path: /tmp/work/abs/source
+ rustc -C opt-level=0 -g rel/source/aux.rs --crate-name cross_crate_spans --out-dir /tmp/work/libs
+ rustc -C opt-level=0 -g /tmp/work/abs/source/cross-crate-spans.rs -L /tmp/work/libs -C prefer-dynamic -C rpath -o cross-crate-spans
+ lldb cross-crate-spans
(lldb) target create "cross-crate-spans"
Current executable set to 'cross-crate-spans' (x86_64).
(lldb) b aux.rs:24
Breakpoint 1: 2 locations.
(lldb) r
Process 4913 launched: '/private/tmp/work/cross-crate-spans' (x86_64)
Process 4913 stopped
* thread #1: tid = 0xad20ff, 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.2
frame #0: 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4913 resuming
Process 4913 stopped
* thread #1: tid = 0xad20ff, 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4913 resuming
(lldb) Process 4913 exited with status = 0 (0x00000000)
(lldb) q
% rm -rf /tmp/work/ && sh /tmp/script abs rel
Aux in absolute source path: /tmp/work/abs/source
Main in relative source path: rel/source
+ rustc -C opt-level=0 -g /tmp/work/abs/source/aux.rs --crate-name cross_crate_spans --out-dir /tmp/work/libs
+ rustc -C opt-level=0 -g rel/source/cross-crate-spans.rs -L /tmp/work/libs -C prefer-dynamic -C rpath -o cross-crate-spans
+ lldb cross-crate-spans
(lldb) target create "cross-crate-spans"
Current executable set to 'cross-crate-spans' (x86_64).
(lldb) b aux.rs:24
Breakpoint 1: 2 locations.
(lldb) r
Process 4933 launched: '/private/tmp/work/cross-crate-spans' (x86_64)
Process 4933 stopped
* thread #1: tid = 0xad2163, 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.2
frame #0: 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4933 resuming
Process 4933 stopped
* thread #1: tid = 0xad2163, 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x0000000100000b4f cross-crate-spans`cross_crate_spans::generic_function<i16>(val=1212) + 127 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4933 resuming
(lldb) Process 4933 exited with status = 0 (0x00000000)
(lldb) q
% rm -rf /tmp/work/ && sh /tmp/script abs abs
Aux in absolute source path: /tmp/work/abs/source
Main in absolute source path: /tmp/work/abs/source
+ rustc -C opt-level=0 -g /tmp/work/abs/source/aux.rs --crate-name cross_crate_spans --out-dir /tmp/work/libs
+ rustc -C opt-level=0 -g /tmp/work/abs/source/cross-crate-spans.rs -L /tmp/work/libs -C prefer-dynamic -C rpath -o cross-crate-spans
+ lldb cross-crate-spans
(lldb) target create "cross-crate-spans"
Current executable set to 'cross-crate-spans' (x86_64).
(lldb) b aux.rs:24
Breakpoint 1: 2 locations.
(lldb) r
Process 4955 launched: '/private/tmp/work/cross-crate-spans' (x86_64)
Process 4955 stopped
* thread #1: tid = 0xad21fe, 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x0000000100000c43 cross-crate-spans`cross_crate_spans::generic_function<u32>(val=17) + 115 at aux.rs:24
21 let result = (val.clone(), val.clone());
22 let a_variable: u32 = 123456789;
23 let another_variable: f64 = 123456789.5;
-> 24 zzz();
25 result
26 }
27
(lldb) c
Process 4955 resuming
(lldb) Process 4955 exited with status = 0 (0x00000000)
(lldb) q
%
```
The transcript above shows that the number of times we hit the breakpoint varies depending on how the source file path was provided.
----
The results are as follows when you vary the absolute/relative nature of each of the two source inputs in the script. (For some period of time, I thought I was observing that problem occurred just based on the main input, but by the time I firmed up the script above, I no longer was seeing that: I had to pass both the aux and the main input as absolute paths in order to reproduce the bug.)
| Aux Input | Main Input | Breakpoint Hit Count | Expected Result?
| --- | --- | --- | --- |
| rel | rel | 2 | (good)
| rel | abs | 2 | (good)
| abs | rel | 2 | (good)
| abs | abs | 1 | *bad*
----
One more observation: By chance, I decided while looking into this to also try varying the input file names. This led to a new bit of data: reproducing the bug requires the main file keep the source `cross-crate-spans.rs` (and do not pass a `--crate-name` argument to it).
* If you rename it to `main.rs` (and do not otherwise muck with its crate name), the bug will not reproduce.
* If you rename it to `main.rs` but also pass `--crate-name cross_crate_spans` (the crate name derived from "cross-crate-spans.rs") when compiling `main.rs`, then the bug *will* reproduce.
* This leads me to wonder: Is the real bug here that we are blithely allowing multiple crates with the same name to be linked together, and even treating it like a scenario that needs to be part to our *test suite*?
----
My `lldb` reports that it is version `lldb-360.1.70`, and my Xcode (according to `xcodebuild`) is Xcode 8.2.1, Build version 8C1002. | A-testsuite,A-debuginfo,P-low,T-compiler,C-bug | low | Critical |
216,821,144 | TypeScript | Autocompletion for mapped type with inferred keys and values all the same. | **TypeScript Version:** nightly 2.3.0-dev.20170324
**Code**
```ts
declare function f<T extends { [P in keyof T]: { x: number } }>(t: T): void;
f({
arbitraryKey: {
/*Here*/
}
});
```
**Expected behavior:**
Autocomplete gives `x`.
**Actual behavior:**
Don't get useful autocomplete. | Suggestion,Domain: Completion Lists,Experience Enhancement | low | Minor |
216,829,119 | go | x/sys/unix: add missing values from syscall pkg to enable complete migration | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go tip
### What operating system and processor architecture are you using (`go env`)?
Ubuntu 16.04 and Fedora22, Red Hat 7.x on ppc64le & ppc64
### What did you do?
Trying to migrate Go code from syscall to sys/unix as described in the golang syscall package documentation https://golang.org/pkg/syscall/. This was the suggested solution for issue https://github.com/golang/go/issues/19560. While it is possible to fix just the case that is described in this issue, that is not a complete solution. We want to avoid hitting another issue because of using syscall, so we'd like to migrate use of syscall to sys/unix. Also having a mixture of references to syscall and sys/unix is confusing since then it is not clear when to use which one.
Issues with migrating from syscall to sys/unix:
1) syscall.Signal and syscall.Errno need to have a type defined within sys/unix so user code doesn't need to use these to convert signals and errnos to the appropriate integer type for the platform.
I was going to try a change for this based on a suggestion by Ian, but I'm not able to get the generator scripts in sys/unix to work. I get these errors:
GOOS=linux GOARCH=ppc64le ./mkall.sh
could not determine kind of name for C.TIOCGETC
could not determine kind of name for C.TIOCGETP
could not determine kind of name for C.TIOCGLTC
could not determine kind of name for C.TIOCSETC
could not determine kind of name for C.TIOCSETN
could not determine kind of name for C.TIOCSETP
could not determine kind of name for C.TIOCSLTC
This happened on Fedora22 and Ubuntu 16.04. If I could get some direction on what this might be that would help.
2) The structure SysProcAttr is defined in syscall but not in sys/unix. It is used in the os package, so I don't think it should be moved to sys/unix. Seems like it needs an equivalent declaration in os.
| compiler/runtime | low | Critical |
216,846,705 | rust | Move libm bindings into separate crate | It is a followup for https://github.com/rust-lang/rust/issues/39473
There is Rust cleanup activity that aims to move complex, platform-specific dependencies outside of `std`. For examples `libc` bindings were moved to its own crate and `std` links to it.
It worth checking if similar thing can be done for `libm` dependency. Decoupling `libm` library from `std` has advantages:
- clear interface between the libraries
- external `libm` will have its own release cycle independent of the Rust one. If there is a bug in `libm` crate then it can be released separately without waiting for a new Rust release.
- external `libm` has more freedom over its implementation. Initially `libm` is going to be just a wrapper over system shared library. But it is be possible to create a version that statically links to openlibm and avoid dynamic linking. It would be great to see a libm version implemented fully in Rust, similar to what [math.rs](https://github.com/nagisa/math.rs) tries to achieve. And users could switch between libm implementation depending on their requirements.
Another question - do math functions like hyperbolic cosine need to be part of std at all? Would it make more sense to remove `libm` dependency from std completely and let users plug math crate manually instead? | C-cleanup,T-compiler | low | Critical |
216,861,514 | flutter | How to open the Scaffold's drawer using Flutter Driver? | I'm logging this because someone asked and I don't know the answer. I should try it myself and fix it if it's not currently possible. | a: tests,tool,framework,t: flutter driver,P3,team-framework,triaged-framework | medium | Critical |
216,875,954 | go | proposal: time: add civil time package | I propose a package with minimal implementations of the types Date, Time and DateTime, which represent times without a corresponding location.
A civil time or date does not represent a point or interval of time, but they are useful for representing events transpiring between humans. For example, your birthday begins at midnight on your birthdate regardless of where you are in the world. If you're turning 21, you can buy a drink in New York at midnight, but teleport instantaneously to San Francisco and you'll be denied, because it is 9 PM the day before.
In practice, the main motivation for these types is to represent values in database-like storage systems, like BigQuery and Spanner (and other, non-Google products).
The package currently exists at cloud.google.com/go/civil, and has been in use by the BigQuery and Spanner client libraries for a few months. For now, I'd like to move it to golang.org/x/time/civil. It is probably too esoteric to be worth including in the standard library, but if there were ever a "second-tier" set of packages that augmented the standard library, it could live there. (See #17244.)
A CL is in progress at https://go-review.googlesource.com/c/38571.
| Proposal | high | Critical |
216,943,287 | angular | Child routes disappear immediately instead of playing :leave animation | <!--
IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING
-->
**I'm submitting a ...** (check one with "x")
```
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```
**Current behavior**
Child routes disappear immediately without playing animations when the parent route changes.
**Expected behavior**
Either all child routes play their :leave animation, or child routes don't get deleted until the parent route's :leave animation is done).
**Minimal reproduction of the problem with instructions**
Here's a version of the crisis center with animations added to all components to show the issue:
https://plnkr.co/edit/QKdb7ucKDX5JX4kKiOJ1?p=preview
Animating from Heroes > Crisis Center works smoothly, however when animating from Crisis Center > Heroes, the list disappears immediately without playing the ':leave' animation.
**What is the motivation / use case for changing the behavior?**
Smoothly animating nested routing.
**Please tell us about your environment:**
<!-- Operating system, IDE, package manager, HTTP server, ... -->
Windows 10, node, asp.net core, Visual Studio (or just plunkr).
* **Angular version:** 4.0.0
<!-- Check whether this is still an issue in the most recent Angular version -->
* **Browser:** all
* **Language:** TypeScript 2.2
| type: bug/fix,area: animations,freq2: medium,P3 | medium | Critical |
216,986,242 | go | cmd/compile: Unnecessary register high-bytes rezeroing after unsigned right shift | Please answer these questions before submitting your issue. Thanks!
#### What did you do?
Hello up there. Please consider the following function:
```go
package xxx
const hextable = "0123456789abcdef"
func HexHi(v byte) byte {
return hextable[v>>4]
}
```
(https://play.golang.org/p/6t7Bq7lw2k)
it compiles to the following assembly:
```
#include "funcdata.h"
TEXT ·HexHi(SB), $0-16 // bbb.go:5
NO_LOCAL_POINTERS
// FUNCDATA $0, gclocals·f207267fbf96a0178e8758c6e3e0ce28(SB) (args)
// FUNCDATA $1, gclocals·33cdeccccebe80329f1fdbee7f5874cb(SB) (no locals)
MOVBLZX v+0(FP), AX // bbb.go:6
SHRB $4, AL
MOVBLZX AL, AX <-- NOTE
LEAQ go.string."0123456789abcdef"(SB), CX
MOVBLZX (CX)(AX*1), AX
MOVB AL, _r1+8(FP)
RET
```
where:
1. `v` was byte-zero-extend loaded from stack argument `MOVBLZX v+0(FP), AX`
2. `v` was shifted right by 4 `SHRB $4, AL`
and then
3. compiler makes sure that higher bytes of AX are zero `MOVBLZX AL, AX`
Step 3 is not neccessary since original `MOVBLZX v+0(FP), AX` is zero-extend move and after it AX[31:8] is zero and logical right shifts preserve that property (even more: for unsigned v, i if we know at some time that v is <= A, for v>>i we can know that it is <= A/2^i).
#### What did you expect to see?
No high-bytes rezeroing after right shift on zero-extended byte-loaded register.
#### What did you see instead?
Unneccessary high-bytes rezeroing instruction emitted.
#### Does this issue reproduce with the latest release (go1.8)?
Yes.
#### Possibly related issues
#18575
#### System details
```
go version devel +ecc6a81617 Sat Mar 25 00:35:35 2017 +0000 linux/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/kirr/go"
GORACE=""
GOROOT="/home/kirr/src/tools/go/go"
GOTOOLDIR="/home/kirr/src/tools/go/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build279220346=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOROOT/bin/go version: go version devel +ecc6a81617 Sat Mar 25 00:35:35 2017 +0000 linux/amd64
GOROOT/bin/go tool compile -V: compile version devel +ecc6a81617 Sat Mar 25 00:35:35 2017 +0000 X:framepointer
uname -sr: Linux 4.9.0-2-amd64
Distributor ID: Debian
Description: Debian GNU/Linux 9.0 (stretch)
Release: 9.0
Codename: stretch
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Debian GLIBC 2.24-9) stable release version 2.24, by Roland McGrath et al.
gdb --version: GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
```
Thanks beforehand,
Kirill
/cc @randall77 | Performance,compiler/runtime | low | Critical |
216,995,030 | go | cmd/compile: arm64: emit double-register loads and stores in lowering | ARMv8 has "double-register" loads and stores (`ldp` and `stp`), which the present SSA backend does not emit.
Since these instructions can accept any general-purpose register (unlike the corresponding ARMv7 instructions `ldrd` and `strd`), they shouldn't require any changes to the register allocator in order to get them working. I think things will "just work" if `ldp` returns a tuple of the loaded values.
In particular, I'd expect this change to make the sequence of instructions preceding and following a call op (with the existing ABI) to be reduced by up to a factor of 2. We can also use `stp` to zero 16 bytes at once.
The `stp` rule should be expressible with the existing SSA rewrite rule infrastructure. The `ldp` rule is more challenging, because there is no way to iterate the uses of a memory value in the rewrite rules. We may have to introduce an architecture-dependent pass just before lower to combine adjacent 4- and 8-byte loads into paired 8- and 16-byte loads.
CC: @williamweixiao I'm happy to take this on, but please let me know if you have similar work planned. | Performance,NeedsFix,compiler/runtime | low | Minor |
217,038,999 | opencv | Provide centroids and areas of new markers returned by watershed | ##### System information (version)
- OpenCV => ALL
- Operating System / Platform => ALL
- Compiler => ALL
##### Detailed description
Current implementation of `cv::watershed()` only updates the input labels, but does not report the new centroids or areas. Although it can be computed externally through extra iterations, it is redundant to perform these operations as it can be carried out in parallel while updating the labels with less cost.
##### Current signature
```.cpp
void watershed(InputArray image, InputOutputArray markers);
```
##### Desired signature
```.cpp
void watershed(InputArray image, InputOutputArray markers, InputOutputArray centroids = noArray(), InputOutputArray stats = noArray());
```
OR
```.cpp
void watershed(InputArray image, InputOutputArray markers, OutputArray centroids = noArray(), OutputArray stats = noArray());
``` | feature,category: imgproc | low | Minor |
217,048,010 | youtube-dl | Site Request: DisneyLife.com | - [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.24**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
- [x] Site support request (request for adding support for a new site)
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
youtube-dl.exe -v https://disneylife.com/view/the-lion-king
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://disneylife.com/view/the-lion-king']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2017.03.24
[debug] Python version 3.4.4 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-83410-gb1e2192, ffprobe N-83410-gb1e2192
[debug] Proxy map: {}
[generic] the-lion-king: Requesting header
WARNING: Falling back on generic information extractor.
[generic] the-lion-king: Downloading webpage
[generic] the-lion-king: Extracting information
ERROR: Unsupported URL: https://disneylife.com/view/the-lion-king
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7c11i4w7\bu
ild\youtube_dl\YoutubeDL.py", line 761, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7c11i4w7\bu
ild\youtube_dl\extractor\common.py", line 428, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7c11i4w7\bu
ild\youtube_dl\extractor\generic.py", line 2653, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: https://disneylife.com/view/
the-lion-king
...
<end of log>
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: https://disneylife.com/view/the-lion-king
---
### Description of your *issue*, suggested solution and other information
Hi, please can support for disneylife.com be added, thank you.
| account-needed | low | Critical |
217,095,635 | youtube-dl | Support for KTLA videos | ---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.03.26*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [X] I've **verified** and **I assure** that I'm running youtube-dl **2017.03.26**
### Before submitting an *issue* make sure you have:
- [ ] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [X] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [X] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### Description of your *issue*, suggested solution and other information
Can you please add support for ktla.com videos
Example: http://ktla.com/2017/03/26/mother-and-her-2-children-among-4-people-killed-in-sacramento-home/
Currently it gives this error:
```
[generic] ...: Requesting header
WARNING: Falling back on generic information extractor.
[generic] ...: Downloading webpage
[generic] ...: Extracting information
ERROR: Unsupported URL: ...
```
| site-support-request | low | Critical |
217,155,887 | youtube-dl | Gaana Support | It would be nice to have Gaana.com support.
Song urls :
http://gaana.com/share/titemI21309714
http://gaana.com/song/do-naina-male
Album urls:
http://gaana.com/share/AitemI1863456
http://gaana.com/album/angamaly-diaries
Thank you | site-support-request | low | Minor |
217,161,128 | go | proposal: introduce new html meta tag for issue trackers | For the users of the packages with vanity import paths uses, it is often impossible to find the package's issue tracker to file an issue. The package maintainers often have to manually add a link to the package comment to ensure that users will be able to find the package's issue tracker. This process is tedious and adding more noise to the godoc.
I propose to introduce a new meta tag for our vanity URL redirect pages, so that the package owners can set the location of the package's issue tracker.
```
<meta name="go-import" content="cloud.google.com/go git https://code.googlesource.com/gocloud">
<meta name="go-source" content="cloud.google.com/go https://github.com/GoogleCloudPlatform/gcloud-golang https://github.com/GoogleCloudPlatform/gcloud-golang/tree/master{/dir} https://github.com/GoogleCloudPlatform/gcloud-golang/tree/master{/dir}/{file}#L{line}">
<meta name="go-issues" content="cloud.google.com/go https://github.com/GoogleCloudPlatform/gcloud-golang/issues">
```
Once a meta tag is introduced, the Go tools (such as godoc.org) can display a link to the issue tracker on the package page. | Proposal,Proposal-Hold | low | Minor |
217,178,741 | go | proposal: cmd/vet: missing error assignment check | I noticed a mistake during a code review that I think could be automatically detected. The idea is to detect code which looks like:
```
if f(); err != nil {
...
}
```
which should instead assign the return value of f()
```
if err := f(); err != nil {
...
}
```
For the code to compile at all, err must be declared in the outer scope.
### Correctness:
This check detects code that the programmer didn't intend to write. In some instances the mistake is caused by what I personally might call a readability issue, such as when f() is a multi-line func literal that obscures the if statement. Nevertheless, this reports on the missing assignment, not the style.
### Frequency:
A number of these have been detected at Google. The check is lightweight. I did not do a large review of open-source Go, but examples can be seen at:
https://github.com/golang/crypto/blob/459e26527287adbc2adcc5d0d49abff9a5f315a7/acme/acme.go#L157
https://github.com/tensorflow/tensorflow/blob/c44601f5411408c324c81dd38bc8686cbd2568aa/tensorflow/go/tensor.go#L101
### Precision:
It is difficult to define a false negative for this test, but for my particular implementation perhaps errors that are not called "err", and are not checked against nil. Others implementations may be able to increase the scope.
False positives seem rare, though it is possible to write code like:
```
var err error
f := func() {
mu.Lock()
defer mu.Unlock()
err = g()
}
if f(); err != nil {
```
I do not think it would any less clear for f() to return err in that case though.
A false positive of my initial implementation is
https://github.com/ziutek/mymysql/blob/0582bcf675f52c0c2045c027fd135bd726048f45/autorc/autorecon.go#L124
this could be eliminated by looking for err (or &err) being passed as a parameter, though that function could avoid modifying its input parameter and instead return an error.
A more thorough check for if conditions that are always true/false would detect some of these situations, especially if a previous check for nil caused a return. But it would miss some, so I think a simple check is worth introducing. Some mistakes occur in tests:
```
if err := f(); err != nil {
t.Error(err)
}
if g(); err != nil {
t.Error(err)
}
```
whilst others aggregate errors rather than returning:
```
for x := range xs {
if f(x); err != nil {
errs = append(errs, err)
}
}
```
An initial implementation is here: https://go-review.googlesource.com/c/38631/ | Proposal,Proposal-Hold,Analysis | low | Critical |
217,188,048 | rust | Indexing tuple warning misleading | The following rust snippet:
```rust
fn main() {
let x = (0u32, 1u64, 2isize);
for i in 0..3 {
println!("{}\n", x[i]);
// ERROR: to access tuple elements,
// use tuple indexing syntax (e.g. `tuple.0`)
// println!("{}\n", x.i); // This doesn't obviously work
}
}
```
produces a warning that recommends using `.0` to index the tuple, but what it should recommend is to `match` on the index. | C-enhancement,A-diagnostics,P-low,T-compiler,A-suggestion-diagnostics,D-newcomer-roadblock,D-terse | low | Critical |
217,204,798 | flutter | Doctor should check for hardware VM accelleration | If a developer is configured for Android, then we should check if they have hardware acceleration configured. If not, Flutter will run very slow.
The command is:
```
$ ./emulator -accel-check
accel:
0
HAXM version 6.0.1 (3) is installed and usable.
accel
```
When the check fails, we should point developers at this URL:
https://developer.android.com/studio/run/emulator-acceleration.html
| platform-android,tool,t: flutter doctor,P3,team-android,triaged-android | low | Major |
217,223,909 | angular | Implement --help for compiler-cli tools | **I'm submitting a ...** (check one with "x")
```
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```
**Current behavior**
`ngc --help` and `ng-xi18n --help` do not display help text, instead it does the usual action.
**Expected behavior**
`ngc --help` and `ng-xi18n --help` should display the command line and modifiers supported by the tools.
**Minimal reproduction of the problem with instructions**
Run `ngc --help` in a terminal
**What is the motivation / use case for changing the behavior?**
Most command line tools implement `--help` and `-h` flags to display some help text (with the various supported modifiers) and the version. The `compiler-cli` tools should do the same as it provides an easy way to figure out how to tweak command line and scripts to get the expected behaviours.
See for instance `npm --help`, `yarn --help`, `tsc --help` or `webpack --help` for similar help texts.
`--version` would also be a nice to have but not as critical I guess.
* **Angular version:** 2.4.9
* **Browser:** n/a
* **Language:** n/a
* **Node (for AoT issues):** `node --version` = 4.7.2
| feature,hotlist: error messages,area: compiler,feature: under consideration | low | Critical |
217,296,587 | TypeScript | Unable to access ServiceWorkerGlobalScope via `self.` | <!-- BUGS: Please use this template. -->
<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->
<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->
Since `ServiceWorker` related types sit in `lib.webworker.d.ts`, `webworker` lib need to be added to `tsconfig.json`.
```json
{
"compilerOptions": {
"lib": [
"es2017",
"webworker"
]
}
}
```
But in current [`lib.webworker.d.ts`](https://github.com/Microsoft/TypeScript/blob/v2.2.2/lib/lib.webworker.d.ts#L1718), it `declare var self: WorkerGlobalScope;`, so we can't access ServiceWorkerGlobalScope via `self.`
---
**TypeScript Version:** 2.2.1
**Expected behavior:**
Can access ServiceWorkerGlobalScope via `self.`(like [`self.clients`](https://github.com/Microsoft/TypeScript/blob/v2.2.2/lib/lib.webworker.d.ts#L1375))
**Actual behavior:**
Access with error.
| Bug,Help Wanted,Domain: lib.d.ts | high | Critical |
217,324,749 | electron | Method to get/set file pointers in clipboard | There is currently no mechanism to get/set file pointers from/to clipboard.
File pointers: The stuff in clipboard when you copy (`ctrl+c`) selected files in your OS file explorer.
After ~15 min research, there was #2244 issue which went a different direction and than got closed. Also there are some projects on hold waiting for this kind of functionality, such as https://github.com/bertofer/quercus/issues/1. | enhancement :sparkles:,component/clipboard | high | Critical |
217,349,941 | flutter | RepaintBoundaries should notice that they are next to each other | It seems like we should remove one of the following boundaries, and that the logic should complain that one of them is redundant. Maybe if the parent is a RenderRepaintBoundary, then it should always diagnose as redundant?
```
│
└─child 1: RenderRepaintBoundary#699402239
│ creator: RepaintBoundary-[<1>] ← SliverFillViewport ← Viewport ←
│ IgnorePointer-[GlobalKey#991626018] ← Listener ←
│ _GestureSemantics ←
│ RawGestureDetector-[LabeledGlobalKey<RawGestureDetectorState>#486348456]
│ ← RepaintBoundary ← CustomPaint ← RepaintBoundary ←
│ NotificationListener<ScrollNotification> ←
│ GlowingOverscrollIndicator ← ⋯
│ parentData: index=1; layoutOffset=411.4
│ constraints: BoxConstraints(w=411.4, h=663.4)
│ size: Size(411.4, 663.4)
│ metrics: 99.9% useful (1 bad vs 1152 good)
│ diagnosis: this is an outstandingly useful repaint boundary and
│ should definitely be kept
│
└─child: RenderRepaintBoundary#127255144
│ creator: RepaintBoundary ←
│ NotificationListener<ScrollNotification> ←
│ GlowingOverscrollIndicator ← Scrollable ←
│ PrimaryScrollController ← ListView ← RepaintBoundary-[<1>] ←
│ SliverFillViewport ← Viewport ←
│ IgnorePointer-[GlobalKey#991626018] ← Listener ←
│ _GestureSemantics ← ⋯
│ parentData: <none>
│ constraints: BoxConstraints(w=411.4, h=663.4)
│ size: Size(411.4, 663.4)
│ metrics: 100.0% useful (1 bad vs 2112 good)
│ diagnosis: this is an outstandingly useful repaint boundary and
│ should definitely be kept
│
``` | framework,c: performance,c: proposal,P3,team-framework,triaged-framework | low | Minor |
217,362,112 | flutter | Highlight draws above Splash (which when opaque causes Splash to disappear) | Re: InkWell (and everything that uses it).
If you use opaque (alpha = 255) colors or trigger multiple highlight events then the highlight layer will be rendered above the splash (or previous splash). I spoke briefly to @Hixie about it and the solution is probably to create a hierarchy or manager to ensure that the layers are always rendered in the correct order.
It is easy to test using this code:
```dart
final Color highlightColor = new Color(0xFFFF0000);
final Color splashColor = new Color(0xFF0000FF);
var mainWidget = new Material(
child: new Center(
child: new Container(
width: 200.0,
height: 60.0,
child: new InkWell(
highlightColor: highlightColor,
splashColor: splashColor,
onTap: () {},
),
),
),
);
```
You will see that the highlight will fade in over the top of the splash.
| framework,f: material design,customer: posse (eap),P3,team-design,triaged-design | low | Major |
217,395,212 | flutter | Add description for why some dependencies are needed in doctor | We're asking users to install more and more stuff. Some are more self evident like xcode. But why the user needs the six python module and cocoapods are a bit more obscure. We should probably explain why they're needed on the website or in doctor and what happens if they don't have them. | tool,t: flutter doctor,P3,team-tool,triaged-tool | low | Minor |
217,428,328 | go | cmd/compile: clumsy rematerialization in mapassign_fast* | On 73912a1b91
If you disassemble `runtime.mapassign_fast32` on ARM, you'll find the following code generated for the bucket probing loop:
```
0.34 │ d4: cmp ip, #8
│ ↓ bcs 1a0
│ ldrsb fp, [r2]
│ add lr, r2, ip
│ ldrb r0, [lr]
│ and r3, r5, #255
│ cmp r3, r0
│ ↓ beq 13c
│ cmp r0, #0
39.68 │ ↓ bne 104
│ cmp r7, #0
│ ↓ beq 114 ; jumps just past this loop
│104: add ip, ip, #1
0.20 │ ldr r0, [sp, #28] ; <-- clobbered in loop
│ mov r3, #1 ; <-- clobbered in loop
│ ↑ b d4
```
(The `ldr r0, [sp, #28]` is reloading a spill of the variable `bucket`.)
The `beq 114` branch jumps forwards to a block that uses `r0` and `r3`. I'd expect the values in those registers to be rematerialized in that block, rather than in the body of a loop. (They don't appear to be live on any other edges out of this loop.)
Found while investigating #19495 | Performance,compiler/runtime | low | Minor |
217,461,197 | electron | Allow specifying udp port range for webrtc | It would be good to be able to provide some values for the policies that can be found here:
chrome://policy/
(Tick the box "Show policies with no value set")
For instance, this will allow a developer to set a particular range of UDP port for WebRTC (policy named WebRtcUdpPortRange) and avoid issue with some firewall restrictions. | enhancement :sparkles:,beginner friendly | medium | Major |
217,470,423 | go | x/mobile: gobind reverse bindings mistakes struct fields with embedding a java class | ### What version of Go are you using (`go version`)?
go version go1.8 linux/amd64
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/micro/Workspace"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build006260206=/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"
### x/mobile version
my x/mobile is updated to the latest commit in Date: Tue Feb 21 21:57:37 2017 +0100
### What did you do?
I've created an `MainActivity` and embedded `android.app.Activity`. Then I added a `android.webkit.WebView` field to the struct and ran `./gradlew assembleDebug`.
Here is the [code](https://play.golang.org/p/mB8gNDgxyG) and [build.gradle](https://pastebin.com/ATxqqfV4)
### What did you expect to see?
Successfully compile and build an apk.
### What did you see instead?
```
:preBuild UP-TO-DATE
:preDebugBuild UP-TO-DATE
:checkDebugManifest
:preReleaseBuild UP-TO-DATE
:prepareComAndroidDatabindingAdapters121Library UP-TO-DATE
:prepareComAndroidDatabindingLibrary121Library UP-TO-DATE
:prepareComAndroidSupportSupportV42103Library UP-TO-DATE
:prepareDebugDependencies
:compileDebugRenderscript UP-TO-DATE
:generateDebugResValues UP-TO-DATE
:generateDebugResources UP-TO-DATE
:mergeDebugResources UP-TO-DATE
:dataBindingProcessLayoutsDebug UP-TO-DATE
:compileDebugAidl UP-TO-DATE
:generateDebugBuildConfig UP-TO-DATE
:gobindDebug
type test1.MainActivity struct{Java/android/app.Activity; MyWebView Java/android/webkit.WebView} embeds more than one Java class; only one is allowed.
type test1.MainActivity struct{Java/android/app.Activity; MyWebView Java/android/webkit.WebView} embeds more than one Java class; only one is allowed.
type test1.MainActivity struct{Java/android/app.Activity; MyWebView Java/android/webkit.WebView} embeds more than one Java class; only one is allowed.
type test1.MainActivity struct{Java/android/app.Activity; MyWebView Java/android/webkit.WebView} embeds more than one Java class; only one is allowed.
:gobindDebug FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':gobindDebug'.
> Process 'command '/home/micro/Workspace/bin/gobind'' finished with non-zero exit value 1
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
```
I think that `gobind` mistakes the struct fields with embedding a java class. | mobile | low | Critical |
217,619,686 | go | runtime: redirect println(runtime.writeErr) to NSLog(asl_log) on iOS | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go version go1.7.5 darwin/amd64
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH=""
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/m9/qtbxkp6s3p96fk54rln7qhj80000gp/T/go-build412033723=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
### What did you do?
Get a uncatch panic on ios in network extension process.As I can not attach xcode to that process.I can only use devices window of xcode to view the NSLog output from that process.
### What did you expect to see?
See panic message in NSLog output of that network extension process.
### What did you see instead?
Nothing.
| Proposal,Proposal-Accepted,compiler/runtime | low | Critical |
217,639,492 | opencv | Mac crash in cvWaitKey after setting POS_FRAMES on file | ##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->
- OpenCV => 3.2.0
- Operating System / Platform => Mac OS Yosemite/Sierra (verified on both)
- Compiler => Apple LLVM version 7.0.2 (clang-700.1.81)
##### Detailed description
After opening a file, stepping forward, then stepping backward, there is a reproducible crash. This is a regression from OpenCV 3.0.0. (I was not able to test 3.1.0.)
The file is in format "ISO Media, Apple QuickTime movie" according to the "file" program. It was created with:
```
cv::VideoWriter outputVideo;
int codec = CV_FOURCC('r', 'a', 'w', ' ');
outputVideo.open(filename, codec, 30, cv::Size(640, 480));
```
##### Steps to reproduce
Here is a (lightly edited) backtrace from CoreGraphics, showing "current", "creation", and "destruction":
```
<Warning>: Invalid Connection ID 170963
PScurrentwindowbounds: CGSGetWindowBounds returned error (1000)
<Warning>: CGSConnection: serious error: CID 170963 is dead.
<Warning>: Backtrace (at 11562.2):
<Warning>: CGSConnection: current backtrace:: 0 CoreGraphics 0x00007fff8e2d4266 CGSBacktraceCreate + 112
<Warning>: CGSConnection: current backtrace:: 1 CoreGraphics 0x00007fff8e3bddde CGSLogBacktrace + 15
<Warning>: CGSConnection: current backtrace:: 2 CoreGraphics 0x00007fff8e2d46b2 (anonymous namespace)::Registry::zombie_check(unsigned int) + 56
<Warning>: CGSConnection: current backtrace:: 3 CoreGraphics 0x00007fff8e2d461b CGSConnectionRegistryCheckConnectionID + 55
<Warning>: CGSConnection: current backtrace:: 4 CoreGraphics 0x00007fff8e2d4543 CGSConnectionByID + 160
<Warning>: CGSConnection: current backtrace:: 5 CoreGraphics 0x00007fff8e3268b0 CGSDisableUpdateToken + 9
<Warning>: CGSConnection: current backtrace:: 6 AppKit 0x00007fff978592ea -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 1832
<Warning>: CGSConnection: current backtrace:: 7 AppKit 0x00007fff978111ae -[NSView displayIfNeeded] + 1876
<Warning>: CGSConnection: current backtrace:: 8 AppKit 0x00007fff97810a09 -[NSWindow displayIfNeeded] + 236
<Warning>: CGSConnection: current backtrace:: 9 AppKit 0x00007fff97810672 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 936
<Warning>: CGSConnection: current backtrace:: 10 AppKit 0x00007fff97f46171 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1540 + 46
<Warning>: CGSConnection: current backtrace:: 11 CoreFoundation 0x00007fff95734127 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
<Warning>: CGSConnection: current backtrace:: 12 CoreFoundation 0x00007fff95734080 __CFRunLoopDoObservers + 368
<Warning>: CGSConnection: current backtrace:: 13 CoreFoundation 0x00007fff95726188 __CFRunLoopRun + 872
<Warning>: CGSConnection: current backtrace:: 14 CoreFoundation 0x00007fff95725bd8 CFRunLoopRunSpecific + 296
<Warning>: CGSConnection: current backtrace:: 15 HIToolbox 0x00007fff9471c56f RunCurrentEventLoopInMode + 235
<Warning>: CGSConnection: current backtrace:: 16 HIToolbox 0x00007fff9471c1ee ReceiveNextEventCommon + 179
<Warning>: CGSConnection: current backtrace:: 17 HIToolbox 0x00007fff9471c12b _BlockUntilNextEventMatchingListInModeWithFilter + 71
<Warning>: CGSConnection: current backtrace:: 18 AppKit 0x00007fff9780d8ab _DPSNextEvent + 978
<Warning>: CGSConnection: current backtrace:: 19 AppKit 0x00007fff9780ce58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
<Warning>: CGSConnection: current backtrace:: 20 libopencv_highgui.3.2.dylib 0x000000010093acce cvWaitKey + 285
<Warning>: CGSConnection: current backtrace:: 21 libopencv_highgui.3.2.dylib 0x00000001009386b3 cv::waitKey(int) + 11
...
<Warning>: Backtrace (at 11560.7):
<Warning>: CGSConnection: creation backtrace:: 0 CoreGraphics 0x00007fff8e2d4266 CGSBacktraceCreate + 112
<Warning>: CGSConnection: creation backtrace:: 1 CoreGraphics 0x00007fff8e2d4008 CGSConnectionRegistryAddConnectionID + 398
<Warning>: CGSConnection: creation backtrace:: 2 CoreGraphics 0x00007fff8e2d3402 CGSNewConnection + 1058
<Warning>: CGSConnection: creation backtrace:: 3 AppleGVA 0x00000001050b8ee4 AVF_CreateMediaAcceleratorInterface + 183728
<Warning>: CGSConnection: creation backtrace:: 4 VideoToolbox 0x00007fff8af60972 VTGetGVADecoderAvailability + 2666
<Warning>: CGSConnection: creation backtrace:: 5 VideoToolbox 0x00007fff8aed5b62 VTDecompressionSessionCreateWithOptions + 2181
<Warning>: CGSConnection: creation backtrace:: 6 MediaToolbox 0x00007fff93e2e6ca VMC2CreateWithQueues + 7737
<Warning>: CGSConnection: creation backtrace:: 7 MediaToolbox 0x00007fff93e2c7b3 VMC2CreateWithCallbacks + 1452
<Warning>: CGSConnection: creation backtrace:: 8 MediaToolbox 0x00007fff93e2c1b9 VMC2CreateWithQueues2 + 559
<Warning>: CGSConnection: creation backtrace:: 9 MediaToolbox 0x00007fff93ef486f FigVideoRenderPipelineCreateWithFigImageQueueArray + 1390
<Warning>: CGSConnection: creation backtrace:: 10 MediaToolbox 0x00007fff93ef4ba0 FigVideoRenderPipelineCreateWithVisualContext + 238
<Warning>: CGSConnection: creation backtrace:: 11 MediaToolbox 0x00007fff93fc4a7e FigAssetWriterCreateWithURL + 54804
<Warning>: CGSConnection: creation backtrace:: 12 AVFoundation 0x00007fff92318db4 -[AVAssetReaderTrackOutput _enableTrackExtractionReturningError:] + 1085
<Warning>: CGSConnection: creation backtrace:: 13 AVFoundation 0x00007fff922af8c1 -[AVAssetReader startReading] + 323
<Warning>: CGSConnection: creation backtrace:: 14 libopencv_videoio.3.2.dylib 0x000000010235b4b3 CvCaptureFile::setupReadingAt(CMTime) + 789
<Warning>: CGSConnection: creation backtrace:: 15 libopencv_videoio.3.2.dylib 0x000000010235c1d1 CvCaptureFile::setProperty(int, double) + 601
<Warning>: CGSConnection: creation backtrace:: 16 libopencv_videoio.3.2.dylib 0x00000001023511f3 cv::VideoCapture::set(CV_CAP_PROP_POS_FRAMES, 0) + 31
...
<Warning>: Backtrace (at 11562.1):
<Warning>: CGSConnection: destruction backtrace:: 0 CoreGraphics 0x00007fff8e2d4266 CGSBacktraceCreate + 112
<Warning>: CGSConnection: destruction backtrace:: 1 CoreGraphics 0x00007fff8e3ab5bd CGSConnectionRegistryRemoveConnectionID + 74
<Warning>: CGSConnection: destruction backtrace:: 2 CoreGraphics 0x00007fff8e3ab38b CGSReleaseConnection + 103
<Warning>: CGSConnection: destruction backtrace:: 3 AppleGVA 0x00000001050b7589 AVF_CreateMediaAcceleratorInterface + 177237
<Warning>: CGSConnection: destruction backtrace:: 4 AppleGVA 0x00000001050ba42e AVF_CreateMediaAcceleratorInterface + 189178
<Warning>: CGSConnection: destruction backtrace:: 5 VideoToolbox 0x00007fff8af61d7c VTGetGVADecoderAvailability + 7796
<Warning>: CGSConnection: destruction backtrace:: 6 CoreMedia 0x00007fff8fed7111 FigBaseObjectFinalize + 73
<Warning>: CGSConnection: destruction backtrace:: 7 CoreFoundation 0x00007fff956cce8e CFRelease + 526
<Warning>: CGSConnection: destruction backtrace:: 8 VideoToolbox 0x00007fff8aed4f4b VTDecompressionSessionInvalidate + 94
<Warning>: CGSConnection: destruction backtrace:: 9 MediaToolbox 0x00007fff93e2bc17 VMC2WaitUntilCompletelyStopped + 171
<Warning>: CGSConnection: destruction backtrace:: 10 MediaToolbox 0x00007fff93e2b8ab VMC2Invalidate + 103
<Warning>: CGSConnection: destruction backtrace:: 11 MediaToolbox 0x00007fff93ef507c FigVideoRenderPipelineCreateWithVisualContext + 1482
<Warning>: CGSConnection: destruction backtrace:: 12 MediaToolbox 0x00007fff93fc1bc4 FigAssetWriterCreateWithURL + 42842
<Warning>: CGSConnection: destruction backtrace:: 13 MediaToolbox 0x00007fff93fc30af FigAssetWriterCreateWithURL + 48197
<Warning>: CGSConnection: destruction backtrace:: 14 AVFoundation 0x00007fff922b1e6d -[AVAssetReader cancelReading] + 336
<Warning>: CGSConnection: destruction backtrace:: 15 libopencv_videoio.3.2.dylib 0x000000010235b1f0 CvCaptureFile::setupReadingAt(CMTime) + 82
<Warning>: CGSConnection: destruction backtrace:: 16 libopencv_videoio.3.2.dylib 0x000000010235c1d1 CvCaptureFile::setProperty(int, double) + 601
<Warning>: CGSConnection: destruction backtrace:: 17 libopencv_videoio.3.2.dylib 0x00000001023511f3 cv::VideoCapture::set(CV_CAP_PROP_POS_FRAMES, 2) + 31
...
``` | bug,category: videoio,platform: ios/osx | low | Critical |
217,717,260 | go | cmd/compile: slow to compile large map literals containing dynamic elements | ### What version of Go are you using (`go version`)?
`go version go1.8 darwin/amd64`
### What operating system and processor architecture are you using (`go env`)?
```
$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/afisk/gopath"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_q/9g3l6s7x3v92ws74nng9g2g00000gn/T/go-build418677857=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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?
Used `text/template` to generate a very large go file to embed data, and then just ran `go build`
```
$ git clone https://github.com/getlantern/httpseverywhere.git
$ cd httpseverywhere
$ git checkout too-large-for-go
$ go build
```
### What did you expect to see?
A successfully built binary
### What did you see instead?
```
$ go build
# github.com/getlantern/httpseverywhere
panic: runtime error: makeslice: len out of range
goroutine 1 [running]:
cmd/compile/internal/gc.newliveness(0xc4272221b0, 0xc42011c238, 0xc49bc7e000, 0x4a651, 0x5ac00, 0xc4da1da000, 0x832c, 0x9800, 0xc48ef5f898)
/usr/local/go/src/cmd/compile/internal/gc/plive.go:717 +0x145
cmd/compile/internal/gc.liveness(0xc4272221b0, 0xc42011c238, 0xc4c21321c0, 0xc4c2132230)
/usr/local/go/src/cmd/compile/internal/gc/plive.go:1740 +0x14f
cmd/compile/internal/gc.genssa(0xc45d30b440, 0xc42011c238, 0xc4c21321c0, 0xc4c2132230)
/usr/local/go/src/cmd/compile/internal/gc/ssa.go:4500 +0x77c
cmd/compile/internal/gc.compile(0xc4272221b0)
/usr/local/go/src/cmd/compile/internal/gc/pgen.go:443 +0x707
cmd/compile/internal/gc.funccompile(0xc4272221b0)
/usr/local/go/src/cmd/compile/internal/gc/dcl.go:1292 +0xdc
cmd/compile/internal/gc.fninit(0xc420115c00, 0x3b, 0x70)
/usr/local/go/src/cmd/compile/internal/gc/init.go:164 +0xb8d
cmd/compile/internal/gc.Main()
/usr/local/go/src/cmd/compile/internal/gc/main.go:471 +0x23b1
main.main()
/usr/local/go/src/cmd/compile/main.go:50 +0xfe
```
| ToolSpeed,compiler/runtime | medium | Critical |
217,738,555 | kubernetes | Recommended liveness check for kube-apiserver | For 1.6, what is the healthz endpoint / recommended liveness check for a secure setup (RBAC, kubeadm discovery not enabled, insecure port disabled)?
`curl https://127.0.0.1/healthz` is returning a 401 for me.
Edit: What I originally called "kubeadm discovery not enabled" is now more commonly / correctly called "setting --anonymous-auth=false on apiserver". | area/security,sig/api-machinery,kind/feature,lifecycle/frozen | medium | Critical |
217,797,421 | go | cmd/go: document that generate processes packages in command line order | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
```
go version go1.8 linux/amd64
```
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/myitcv/mgo/src/modelogiq.com/g/_vendor:/home/myitcv/mgo"
GORACE=""
GOROOT="/home/myitcv/gos"
GOTOOLDIR="/home/myitcv/gos/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build675075507=/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?
`go generate` accepts a number of packages as arguments, packages on which to run `go generate`. `go generate -help` makes no mention of the order in which those packages will be `go generate`-d
The lack of any mention on the order of execution might well be intentional...
But in any case I'd like to propose we define the order and document it (this issue could conceivably be a proposal, very happy to redo as such)
The use case stems a use case where `go generate`-ors end up parsing dependencies in order to make decisions on their output. In this context, having `go generate` run in reverse dependency order (there's probably a more precise term?) on the set of packages provided as arguments avoids the need to re-run `go generate` multiple times (which incidentally is the current alternative, clearly not ideal)
### What did you expect to see?
"Expect" is not the correct word here... because the order is unspecified I can't reasonably have an expectation. More a "hope" perhaps that:
`go generate` should run in reverse-dependency order on the set of packages passed to it as arguments.
### What did you see instead?
It runs in an unspecified order.
cc @robpike perhaps? | Suggested,Documentation,help wanted,NeedsFix | low | Critical |
217,844,148 | angular | broken animations in angular4 | [X ] bug report
**Current behavior**
I have animation on routerTransition and it is breaking my app. the error is like this
> ERROR Error: Uncaught (in promise): Error: The provided animation trigger "c12#routeAnimation" has not been registered!
> Error: The provided animation trigger "c12#routeAnimation" has not been registered!
> at InjectableAnimationEngine.DomAnimationEngine.setProperty (browser.es5.js:1354) [angular]
> at AnimationRenderer.setProperty (animations.es5.js:226) [angular]
```
The only thing changed is i have upgraded angular to 4. Previously is was working just fine. This is how i used routerTransitions in my component
> animations: [routerTransition],
> host: '[@routeAnimation]': ''
```
**Expected behavior**
It should work as it is been working in previous version
**Minimal reproduction of the problem with instructions**
in a ts file add this
```
import { animate, state, style, transition, trigger } from '@angular/animations';`
export const routerTransition =
trigger('routerAnimations', [
state('void', style({position: 'absolute', overflow: 'hidden', width: '100%', top: '50px', left: '20px'})),
state('*', style({position: 'absolute', overflow: 'hidden', width: '100%', top: '50px', left: '20px'})),
transition(':enter', [
style({transform: 'translateX(100%)'}),
animate('0.5s ease-in-out', style({transform: 'translateX(0%)'}))
]),
transition(':leave', [
style({transform: 'translateX(0%)'}),
animate('0.5s ease-out', style({transform: 'translateX(-100%)'}))
])
]);
```
And then inject it into a component like this
```
host: '[@routeAnimation]': 'true'
animations: [routerTransition],
```
**What is the motivation / use case for changing the behavior?**
<!-- Describe the motivation or the concrete use case -->
**Please tell us about your environment:**
<!-- Operating system, IDE, package manager, HTTP server, ... -->
Window 10
* **Angular version:** 4
* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
<!-- All browsers where this could be reproduced -->
Chrome
* **Language:** [all | TypeScript X.X | ES6/7 | ES5]
Typescript 2.2.2
* **Node (for AoT issues):** `node --version` =
6.9 | type: bug/fix,area: animations,freq3: high,P3 | low | Critical |
217,886,045 | TypeScript | add a constraint for immutable types | say, i have a generic function that by design requires that its parameters may only take immutable arguments, i wish i could get such guarantee from TS by declaring my function as follows:
```typescript
function doThings<readonly T>(value: T): Result<T> {
// ...
}
```
as far as how to make an interface immutable:
```typescript
readonly interface Point {
readonly x: number;
readonly y: number;
}
```
so the problem being solve here is to make sure that the caller won't mutate the argument after it is passed to the function
**simple use case**: a hash-based data container, which calculates a hash of a given value, and will store it at that hash, and it all will work until the value is mutated outside and tha stored hash is no longer valid, so the container doesn't really work anymore
**another use case**: a cache or object pool or any other situation when there are many parties involved in taking hold of the same object, which must be guaranteed from being mutated by one party to prevent spooky action at a distance for all other parties
| Suggestion,Awaiting More Feedback | low | Major |
217,895,869 | rust | Rustdoc incorrectly orders trait impls | Documentation for `Rc`: https://doc.rust-lang.org/nightly/std/rc/struct.Rc.html
Source code: https://doc.rust-lang.org/nightly/src/alloc/rc.rs.html#263-265
In the source impls for `!Send` and `!Sync` come one after another. In the generated documentation they don't.
The docs should respect the order of impls in the source - that's what I've been told in the `#rust-docs` channel. In fact, other impls for `Rc` apparently don't follow the order from the source either. What order *do* they follow? :) | T-rustdoc,C-bug | low | Minor |
217,951,855 | opencv | [Feature Request] VResizeLanczos4Vec_32s8u | Hi :)
I was testing out some image resizing with opencv and I realized that Lanczos4 ran substantially slower than bicubic. I was curious why this was, so I went digging, and found out that the bicubic resampler engages a vectorized implementation `VResizeCubicVec_32s8u`, which I believe operates on 4, 8-bit unsigned ints. Lanczos seems to have some vectorized implementations, but none for this particular configuration. I can confirm from profiling that the Lanczos resampler is running non-vectorized code.
It'd be great to add this vectorized codepath to imgwarp.cpp. I've done a little SSE work before but even still it's pretty tricky, so I'm not sure if the other vectorized implementations can be modified to work for Lanczos. Hopefully this won't be a lot of work :) | feature,category: imgproc | low | Major |
217,984,525 | go | gccgo: unneeded hash/equal functions emitted for runtime types | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
gccgo trunk/tip
go version devel +7e817859b3 Mon Mar 27 18:51:42 2017 +0000 linux/amd64
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOOS="linux"
### What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
https://play.golang.org/p/tl4iNxoar6
### What did you expect to see?
This program compiles and builds with gccgo, however I note that the compiler is generating more hash/equal functions that it needs to. In particular, it seems to have decided that it should generate hash/equal functions for the anonymous type corresponding to the BySize field in runtime.MemStats, along with a few other runtime types. This is not a bad thing from a correctness point of view, but it results in extra wasted work at compile time and link time, as well as object file bloat.
### What did you see instead?
I would expect that the compiler would be able to recognize that the type in question is in an external package and that the hash/equal functions can be picked up externally.
| NeedsInvestigation | low | Critical |
218,002,500 | rust | Add explicit or zero constructor for `std::time::Instant` | **Updated: [see below](https://github.com/rust-lang/rust/issues/40910#issuecomment-1015362071)**
----
I'd like to be able to construct an `Instant` with value 0 (whatever epoch that is, I don't care).
Motivation: we have code to schedule timeouts taking a `Duration`. We have a mock version of the same scheduler which doesn't use real time but has the same API, and uses `Instant` internally (simply because converting between `Instant` and `Duration` is convenient and gives us mock code closer to the real code). Since the only way of constructing an `Instant` at the moment is `Instant::now()`, we currently store a "start time" when constructing the scheduler and compare all times to that; this would be simpler if we could simply use zero. | T-libs-api | low | Major |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.