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 |
|---|---|---|---|---|---|---|
266,607,291 | rust | optimisation opportunity missed due to `assert!` | I have noticed interesting behaviour regarding `assert!` which was unexpected. I am not sure if this is a LLVM or Rust issue.
in the following code (See godbolt link below) I have a vec like structure `OwnedRegion`.
I want to iterate over the region (implemented as `slice::IterMut`) and populate an array.
I expect LLVM to do loop unrolling and loop vectorisation. If you place
the necessary `intrinsics::assume` to trick llvm into removing the bound check you do
indeed get the optimisations. However I wanted to replace the `assume` with an `assert!`
but that removes the optimisation even if combined with an `assume`! What I think is happening
is the bounds check is being reintroduced because the length check in the `assert!` is being moved into the for loop or elided completely because it duplicates the length check in the index operation.
What should happen is the bounds check in the for loop should be lifted/elided because of the `assert!`
```
fn main() {
let mut region: OwnedRegion<usize> = test::black_box(OwnedRegion::empty());
let mut my_array: [usize; 128] = [0;128];
// !!! The following assert blocks the loop vectorization optimization !!!
// !!! remove the following line to enable Loop vectorization !!!
assert!(region.len > 128 );
// I know this assume is unsafe given that we created an empty OwnedRegion.
// I am only looking at the output assembly to see if optimization is run
unsafe { assume(region.len() > 128) };
for i in 0..128 {
my_array[i] = region[i];
}
println!("{:?}", &my_array[..32]);
}
```
with `assert!` and `assume`:
inner loops is:
```asm
cmp r15, rcx
jbe .LBB6_5
lea rcx, [rax - 2]
mov rdx, qword ptr [rbx + 8*rax - 24]
mov qword ptr [rbp + 8*rax - 1152], rdx
cmp r15, rcx
jbe .LBB6_4
lea rcx, [rax - 1]
mov rdx, qword ptr [rbx + 8*rax - 16]
mov qword ptr [rbp + 8*rax - 1144], rdx
cmp r15, rcx
jbe .LBB6_8
mov rcx, qword ptr [rbx + 8*rax - 8]
mov qword ptr [rbp + 8*rax - 1136], rcx
cmp r15, rax
jbe .LBB6_10
add rsi, 4
mov rcx, qword ptr [rbx + 8*rax]
mov qword ptr [rbp + 8*rax - 1128], rcx
```
where LBB6_4, LBB6_5, LBB6_8, and LBB6_10 jump to `std::panic`
with just `assume`:
inner loops is:
```asm
.LBB3_3:
movups xmm0, xmmword ptr [rbx + 8*rax]
movups xmm1, xmmword ptr [rbx + 8*rax + 16]
movups xmmword ptr [rbp + 8*rax - 1120], xmm0
movups xmmword ptr [rbp + 8*rax - 1104], xmm1
movups xmm0, xmmword ptr [rbx + 8*rax + 32]
movups xmm1, xmmword ptr [rbx + 8*rax + 48]
movups xmmword ptr [rbp + 8*rax - 1088], xmm0
movups xmmword ptr [rbp + 8*rax - 1072], xmm1
movups xmm0, xmmword ptr [rbx + 8*rax + 64]
movups xmm1, xmmword ptr [rbx + 8*rax + 80]
movups xmmword ptr [rbp + 8*rax - 1056], xmm0
movups xmmword ptr [rbp + 8*rax - 1040], xmm1
movups xmm0, xmmword ptr [rbx + 8*rax + 96]
movups xmm1, xmmword ptr [rbx + 8*rax + 112]
movups xmmword ptr [rbp + 8*rax - 1024], xmm0
movups xmmword ptr [rbp + 8*rax - 1008], xmm1
add rax, 16
cmp rax, 128
jne .LBB3_3
```
here is a [godbolt link](https://rust.godbolt.org/#z:OYLghAFBqd5QCxAYwPYBMCmBRdBLAF1QCcAaPECAKxAEZSBnVAV2OUxAHIBSAJgGYwYbgFYAQgDNMAQwKtM0TADtMxPMgD6AB2nFpAWw2yCxBgEpRAEW4AGAIJ9Bw8VNnyI6Yqi3IA1hswAT0wdAmQECxFre0chUUkZOWIFBgRdTHRIywBqWwcBOJdE9zRkjTwlEwqGdXMrPNjnBLdkiAJMBgIshoKm1ySFCuQAG2YagDdMDT0lYExu%2B0wAD3biJWzkPXbs9s7ufjEG%2BzHMbM70EBAtE0uAZTTk9H3D44ZT88v9XV9VS4AFNKVVD6SyyaTPPInM4EC4gCpVJQ1ZAMS7SBgMZj6TAQ17vGGXbwokDcADsYjewwkpGyllUmCpNLpEgAsswCNSAJJKLBLTnc5asgik6wHSFvaGwtKpS6k8mYSnUgASaIQwpxDnsWmYACNocRmMgCNkAPIAdxU6AASphgHhUEp9gBhMCcNSzakAFRA2RdbuA%2B2wuTJeWyoey12I3vu6Se/EdHoDpBDYeGym9YzwAC9MEn7GHsgB6AvZAByqHa3o9CDwDGyX2IP2I2Sl2SUqA29reAEdmMp2LWJCQO%2BNdHhpEp2Nk8AA6TDTk3mjLW232qe1tAjtTjo2r7gANhsCYP0%2BToaL2SrNbX2WYSjGzGkw2y2swyGkUNNpzSkzrbOk2tTbJpGQftayIC9nzZICzGyS0KmAbVmAkKQm2qeQwIQU422IL5hlPQti1SGNsgADWNS1fwIf9AP1VNa1QCRYLGI1x3QZ8YLsP4OWyZQMWSWt9D/bU8GGQhAmve1hnErRUHRPAANOU1CAQID8PPQSqIU7JkhQvtTnA/cbDNC1lztB0D2yU1q3CHilEHNgOinJRNzHCdsQOM520IM5MEwfRa2SNF7Wo/TUDU4tP2kH51gqFzx0neydmrMDAi0OdwuyZlvlUa8VFA3RxMSzxvHCXxsggT9slQc1cgPI8bBg1idnbYTuSS05DN9eDDOyUSpAIPAsRPPMww0etG29AFt2BUEqKdPg9y62YLwDBoSWiDU7EGrQ8LjF1pE9b19oDBcTJtMynX2z0TtlfDHHiCpRJUeoRtDLVdQkdZUyUCAFopCQYIAWhOjNsyDF47HzfN/unb67vWu7XtyAQHqUJ7sSifD3uyT6eP0a5AggIGTtueVGNupH82Mpdzt3YNKaht6bmyaNHkuPyCaJ3NIcZqHvu9Gxud5qGxuyyNsimoEQTBfD8zVJH5YcBGYnsbbdudV14MOn1NdmE7aR0nGh2pq1aYdPbdeAa7%2BEDCmedDAhUtOD1dDmI19hyeIE0x0UVft5H%2BFR9GXv93GsB037eD3f7iZt5G91JylLhd4g3fB2Ww1vBhpCkdOGcZ1MjQjXJ%2BByGGI2nNFtBMIn1WF/M0QxLEICECuaw0O9hmGImLF9/3hcuD4QAYUT2EuCQvEMPRTW0XQCAYCAI2pGHvosfOgw2uXlaVja8jVy7Le1pb/Tjg36UFI2mxN0z7QPv1rdt%2Bn/fu8RHoqDHN7DMOmTGtlI73DSPlKSx1tlHQBicJDJ1dpgd2T9hZZxzh1OB9dQyF3DCYEuZcybTgrlXCMtc%2B4oNDI3TEChW4mGnO3Tu3czC9whkQ7Ig98TD1HhwEAE9gTTGkDPHQxB56/wIIvEwy9sGrwzqGRWW9d7bz3vjdWx8j6WxOnYBg1oJDzXEN7EUgZErXzNnfLWK0452zlijV%2BaN34h3zLjKuEc/pkxAfHL2Vg879zDP9eG0jd6qzkQY90F4jpKLjiowUGixBaJOroxcpsVzmw1vfIxj96FhhfmIN%2Bz1MZIxsQwAR/9AEx2yMDYxYCoLOKiK44WHiFYyJkT4naB8DoBOyI6YY9p3KBhaW0y%2Bp0aaxIaQ/CpX91gjDaf/ApRTAx6L6RbRpCZjHIMZreNWfllDtHQEIWu1TvGh2Ga0lQGgOH6DyVBf61JyyYXFgtKZF0ZkPxgiY3mSy5ErMqBkDZa9n41O2fvW5TTlSpBOv8lSUSzrTI1rMm6CyA5B0sZknZzYVROkVN6KUSAQBAtUAGMZZNl5UQrPHQBip7lQvzECy4qL/4ACpKWnOhLIeYni1rfN8b8uZgYuQ8idKDdp3Trm31ZZC5JDsnYmjZFqd2pcjEQzumYtJFiMmf1DLjCoPJsUKicjydMNRsyOIWh6QZjNzwljEJBESBBAYVA1cseC2RxhjlqjYBaZTrAHnERIqOEBqUx1RpyuFUimVHC2iy8FAyOUCjZFy7VPKQW9JuSGxJBroXmODn6oZVqli5IWvknF6atVZnmIUm6JSjT6oeYa4sxrTXDHNZalV1rlp2ukA6rNpTNH1FdevFtRpPU0ocT65YViUlfMDbI%2BpAq46EkuGGpYTpJ0gEtOOOYkb82rTjjGmJcaroJrLTsEVxoxWlMlc69UMrA7JthYqnGMV%2BRLDVQyOtSxvRzoXbMdyjpuUBl1VHZ1ib8zTsuA%2Bqlvb1UPo%2Bf6mI28fnxrZVVLQRJp2zrg5cF9cwPRhTjB%2Bm2kTjbRJvnErdMGd2OzSqKgg4rMG5DbT7aVCtZXpI/vhZVN673UgfU%2BpD87F2YDQ8u7Mn7C3FL3D%2Bndf6b0AeYwtL1ObQOMogxtKDBGTpzoQ3GZ9XGABik9ePtOw1fXD%2Bjx1JPwsR04%2B6yOHs9lRkUNHn50flQxrJ17VX2JA2J2DRIUOYE08CbT/GJlOKs7%2BsM/64QSajlJ1zPIwNDq8aO%2BRnAIUTo4ypx0anX3qeYF3XTPSN38ug4K4ze6D0Sss%2BE%2BofdT0woVYxpzywWPZHKG5tLcwMtdy/UJwLIn3Fk1kzvOL/SE3KZvYhjzXGuQjAzJMXzWG104dBZuhLAyiNFfMyVyjZXqOBtMWeuVKbL1Mec1HWlbH3PIbGxOUYEw32YewO14TJLgtidC4dvcEX703uixI4ddT4uJcDENzlqmOOebQ%2BNy7eApsYajaunRc3Y15cU/MoVu6SNmfIx7dbESKu0Z2/RwdSrau3pc%2B9zVp3OOvtBxdyb13oc2zu51h7oYQuAck8BknyxPsbwDX7BTi3BvJZvaEoHo3X3TewNlvl%2BG%2BeEahakvHqaCfpszcWoB7PH1k882L9rgD7vI9EzyQU4meTK4AVBN7rGPu9cVv1wzZPp1C9S8DrjPGocrpm7DvT82EfS4KzjqrDn4UPpN9myLyx2Mi9Q%2Bh99tPbsCdAab92DO9ePYN2yI3yxg9m7ZxbqLVvIPBsR/9gXqehTC7O%2BlrTru%2BPu95fpsFhfE1y/s/jq9SuNLHKNMdprTuK8%2Bar%2B07XraNue0Z9ke3afnsZ/b127I5v02c%2Bt/nsd%2BWkvwcFxGsv5OWuZd2h7nLeGBsy%2BR03vbNW29/xn7SxrpPmteZ34PxPw%2BguhiqZ82LP3D9KeL%2BG0vjuI%2BYDB2pzFwlzrwWz%2B0bzs1P0c3P0EUv2k273/0AKuy1zjwJSHy0WfzH3XwIHTwzWnxVznxky2W5yDWXwbwBx/xG3L0jyQIhxpzd3F1m093hyl3AJ3RPwvTPyD3wIT1VxzzDw12d1QFoMh2jwYIf0xxcS6yZ2wNwMzyNEIMt2ILkxHXsFxi%2BAqCJkTTQUAWSFiW9ElzFwo12BwJAAAmAn8G1FQFvUl3Znxkdh7jrhTBgUom0jNl4AMNALyxu2MI6FMPML8A0CsJsK8KUDsM5loScNQRcMAX0ECCMGID0ECG9HiEwxNVoF4AAA4pCj1xBHUDgMjsjNskZzwhAyiwALxMIjYu5qobVG5VAjQAJUA/AMJThWlvBbVXwiA1BMxZAzJYMBp9Asw%2BjVxyi4gSjiwxiKjkh9BUAfwCAqjBwailJlp0ZmpbIQpsgAAZVADoyYQ0EgYYgaUYsY/CeovhDZPQsyWGZQEuQMQo7IOhLbMMc8biXwNsU0JKK8EhLEa8BBXOW0SYdYBY2QSyU4TYRIDIICdYDmR2ffM2ecDKbiAwKqNGcSdo3wOoo0BY04FgVbICdEPyACcScCN4U4PARibwQYo4/oq8fUdYfCf4pBE1AkpuBQK4%2B0G4n6e5OOQo4lazRjIcPAJybIGwacacB46QuIhIpIh6HInIDkh0V%2BcrY/daXIJGLQN0AgYYJQDZPgXgWUYkfgdTNUXgXgakLNeI3QWU8QcU/gA0qIJ4uTTgMwUgYYLgEQTgUgMIzgGwL01ALgS0ZiTyVgScRwWgL0nA30l0103wEAfgfgacAATgABZMi9wUyRBaB%2BAbASQRB%2BASQSQ3SuAUyvSfS/TSAAzOAvSURBYoy/TXS4BYAkA0B8YRJVByBKBWytB2zIwlA8BgAEBtTAhSAJAzVVAUQIBtQuAKzWoCouAIzSBWysRKhjQ0SZyvSsAvhZhUwNzSB8BkhDQ6CURozSBlhXw2QOBOBFz4R5Q9yqh9ANzXTRJtQURIBXSqSzITzClAZNh6VAYTNnxLVAZHQBjAZUxJhdpLB%2BAayWAHI6BnyPSyy9yqz9ROhkBWwByhypJypcBCAhxwzqRUs2zUwmxwyzBIynzYz4zeBpwSRaBMibBeBaB8yRAkyMikzzT3TOBSzvSUKuAayQA6ynzSAmzEAQA8TxVOyIBuzey6Azz8BuiELizOBPS%2BLTyqzwzLJlJtJmIML%2BzBzhzKLozaFSA4yEzpwEyrLrKbKVLeLyz/SBLGAhLSB6yYyVLeBkKNKnK3LTLJhTAzIQAUygA%3D) | A-LLVM,C-enhancement,T-compiler,C-optimization | low | Major |
266,616,854 | vscode | Support fontName in textMateRules | This is a feature request, and I am not sure how it will be received. Probably not overwhelmingly positive, but nonetheless:
I would like to have support to change font family in my textmate theme. Right now you support `fontStyle`, `fontSize` and `foreground`. I believe the correct term is `fontName` as per https://github.com/textmate/markdown.tmbundle/issues/7 which would control the css `font-family` property,
E g something like
```
"editor": {
"fontFamily": "Fira Code",
"fontSize": "16",
"tokenColorCustomizations": {
"textMateRules": [
{
"name": "Variables",
"scope": "variable",
"settings": {
"fontName": "Script12 BT",
}
}
]
}
}
```
This would be in order to conditionally change font-family and be able to support more creative themes.
| feature-request,editor-theming | high | Critical |
266,652,489 | bitcoin | Block Re-announcement post-compact-fast-announcement after a GETHEADERS or GETBLOCKS request | BIP 152, in the "Pre-Validation Relay and Consistency Considerations" section, point 3, suggests that nodes "SHOULD re-announce" a "block using the associated announcement methods after validation has completed if it is not included in the original response [to a GETHEADERS/GETBLOCKS message]". This is a pretty strange requirement that we currently do not meet (it implies that, if you announce a compact block to a peer using HB mode, and it then requests the header/block inv from you, and you do not supply it as you have not yet finished connecting the block, you need to, once you finish connecting the block, send the header/inv. Because this requirement is not there for GETDATA messages directly (BIP 152 instead requires that the message-processing-pipline stall until you've connected the block), this does not effect our usage of compact blocks, but technically we are not faithfully implementing BIP 152.
Adding a check for this case and handle it explicitly (by watching for GETHEADERS/GETBLOCKS and then setting pindexBestHeaderSent back if we have a most_recent_block which is not included but which has more work than our tip) is doable, but somewhat gross. Personally, I'd prefer that BIP 152 either be changed to drop this SHOULD, or make a note that Bitcoin Core does not meet this SHOULD and implementations SHOULD NOT rely on this behavior. | P2P | low | Minor |
266,661,027 | TypeScript | Anonymous function expressions aren't covered for 'infer from usage' | I'm not getting any codefixes on the parameters in the following example:
```ts
var f = function(x, y, z) {
return 0 + x + y + z;
}
f(1, 2, 3)
```
At the very least, `x`, `y`, and `z` should infer from their bodies.
Optimally, we should climb up looking for `PropertyAssignment`s, `PropertyDeclaration`s, and `BinaryExpression`s (with `=` tokens), and `VariableDeclarations`. For those, we should find all references and figure out the type there.
Should also test for default exports as well. | Bug,Domain: Quick Fixes | low | Minor |
266,687,541 | go | cmd/gofmt: unexpected formatting of comments | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
`go version go1.9.1 linux/amd64`
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/xxx/go"
GORACE=""
GOROOT="/usr/lib64/go"
GOTOOLDIR="/usr/lib64/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="x86_64-pc-linux-gnu-gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build052197988=/tmp/go-build -gno-record-gcc-switches"
CXX="x86_64-pc-linux-gnu-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"
```
### What did you do?
The following code (https://play.golang.org/p/yWr8ET9ZUg) is laid out with comments as I would expect:
```
package main
import "os/exec"
func main() {
exec.Command("nmap",
"-sV", // Get version information
"-oA", "blah", // Save all versions as output
"-oG", "-", // Output Greppable format to stdout
"-Pn", // Skip Ping scan to force scanning everything
"-p-", // Scan all ports
"-v", // Increase verbosity (shows down hosts now)
)
}
```
However, the output of `gofmt` gives the following (https://play.golang.org/p/My_W9bkZrY):
```
package main
import "os/exec"
func main() {
exec.Command("nmap",
"-sV", // Get version information
"-oA", "blah", // Save all versions as output
"-oG", "-", // Output Greppable format to stdout
"-Pn", // Skip Ping scan to force scanning everything
"-p-", // Scan all ports
"-v", // Increase verbosity (shows down hosts now)
)
}
```
It seems to appear that the first two lines are treated as one block, the third line by itself, and the last three lines are treated as another block.
### What did you expect to see?
I would expect no change in the formating of the comments
### What did you see instead?
The comments changed, as shown above.
First time bug for me, so hopefully this is OK. Let me know if there is anything more you need. I'm also keen to help fix it, but I'm also new to go so may take a while :)
Cheers,
Hugh | NeedsInvestigation | low | Critical |
266,698,369 | go | x/crypto/ocsp: the responder cert is not provided along with the OCSP response signature | The docs on [`ocsp.CreateResponse`](https://github.com/golang/crypto/blob/ed5229da99e3a6df35c756cd64b6982d19505d86/ocsp/ocsp.go#L658) state that:
```
// The responder cert is used to populate the responder's name field, and the
// certificate itself is provided alongside the OCSP response signature.
```
But in the [code](https://github.com/golang/crypto/blob/ed5229da99e3a6df35c756cd64b6982d19505d86/ocsp/ocsp.go#L727), the responder cert is only used to populate the `rawResponderID`.
The certificate provided with the OCSP response signature seem to come from [`template.Certificate`](https://github.com/golang/crypto/blob/ed5229da99e3a6df35c756cd64b6982d19505d86/ocsp/ocsp.go#L761-L765) instead of the responder cert.
Is this an error in the docs/code or am I missing something?
| NeedsInvestigation | low | Critical |
266,831,072 | pytorch | Add safety checks in `index_add`/`scatter_add` | Consider this snippet:
```python
a = torch.ones(5)
i = torch.ones(5)
a.index_add_(0, i, a)
```
Idk if we support repeated indices in `i` (we should), but we definitely shouldn't support adding to itself, as the result depends on the order of processing the additions. | triaged | low | Minor |
266,844,994 | opencv | setMouseCallback core dumped | ##### System information (version)
- OpenCV => 3.3
- Operating System / Platform => Ubuntu 16.04
- Compiler => gcc
##### Detailed description
Core dumped when setMouseCallback added.
##### Steps to reproduce
```
import cv2
point = [0,0]
def on_mouse(event,x,y,flags,params):
global point
if event == cv2.EVENT_LBUTTONDOWN:
point[0] = x
point[1] = y
cap = cv2.VideoCapture('video.mp4')
waitTime = 50
(grabbed, frame) = cap.read()
while(cap.isOpened()):
cv2.namedWindow('frame')
cv2.setMouseCallback('frame', on_mouse)
cv2.imshow('frame',frame)
key = cv2.waitKey(waitTime)
if key == 27:
break
cap.release()
cv2.destroyAllWindows()
``` | incomplete | low | Minor |
266,981,357 | youtube-dl | Unable to download uuid | ## 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 this: `[x]`)
- Use the *Preview* tab to see what your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.10.15.1*. 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.10.15.1**
### Before submitting an *issue* make sure you have:
- [x ] At least skimmed through the [README](https://github.com/rg3/youtube-dl/blob/master/README.md), **most notably** the [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:
`# youtube-dl --verbose --username xxx --password xxxx https://hrti.hrt.hr/#/video/show/3970749/eko-zona-18-listopada-2017
[debug] System config: [u'-o', u'/home/nginx/domains/xxx/videoup/%(title)s.%(ext)s', u'--ffmpeg-location', u'/home/nginx/domains/xxx/staticffmpeg/']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'--username', u'PRIVATE', u'--password', u'PRIVATE', u'https://hrti.hrt.hr/#/video/show/3970749/eko-zona-18-listopada-2017']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.10.15.1
[debug] Python version 2.7.5 - Linux-3.10.0-693.2.2.el7.x86_64-x86_64-with-centos-7.4.1708-Core
[debug] exe versions: ffmpeg N-85581-ge22d495538-static, ffprobe N-85581-ge22d495538-static
[debug] Proxy map: {}
[HRTi] Downloading uuid
ERROR: Unable to download uuid: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/lib/python2.7/site-packages/youtube_dl/extractor/common.py", line 503, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/lib/python2.7/site-packages/youtube_dl/YoutubeDL.py", line 2195, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib64/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib64/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/usr/lib64/python2.7/urllib2.py", line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)`
| account-needed | low | Critical |
267,019,638 | flutter | Align the Hero widget API doc with the Hero animation tutorial | Please update the [Hero widget API doc](https://docs.flutter.io/flutter/widgets/Hero-class.html) to reflect terminology used in the new [Hero animations tutorial](https://flutter.io/animations/hero-animations/). Specifically, mention that the Hero widget implements a style of animation also known as Shared Element Transitions.
In addition, it would be helpful to add a link to the tutorial from the API doc and a snippet of sample usage.
Cc: @HansMuller @Sfshaza
| framework,a: animation,d: api docs,f: routes,c: proposal,P2,team-framework,triaged-framework | low | Major |
267,033,186 | kubernetes | Subresource for metadata | This is a tracker to consider the idea of a subresource for object metadata. In particular, for Secrets, you may want to grant a controller permission to read/edit metadata without granting access to the data.
Forked from https://github.com/kubernetes/community/pull/1163/files#r143342579:
@smarterclayton wrote:
> Somewhat of a red flag in that it gives those controllers access to all secrets in the system.
@bgrant0607 wrote:
> If we're concerned about permissions, we could create a subresource for updating ownerReferences, finalizers, and possibly other metadata in order to facilitate lifecycle management without privilege escalation. | sig/api-machinery,kind/feature,lifecycle/frozen | low | Major |
267,071,959 | rust | Rust compiler has unintuitive lifetime for returned mutable borrow in loops | Pardon if I have an incorrect view of how the borrow/lifetime system works.
Compiler complains about multiple mutable borrows in a loop, if a mutable borrow can be returned from the function.
Consider the following:
```
use std::collections::VecDeque;
struct Something;
struct Struct1 {
list: VecDeque<usize>,
thing: Something,
}
impl Struct1 {
fn get_mut(&mut self) -> &mut Something {
for _ in self.list.iter() {
let a = &mut self.thing;
if true {
return a;
}
}
panic!("hi");
}
}
```
I get the following compilation
```
error[E0499]: cannot borrow `self.thing` as mutable more than once at a time
--> src/main.rs:20:26
|
20 | let a = &mut self.thing;
| ^^^^^^^^^^ mutable borrow starts here in previous iteration of loop
...
27 | }
| - mutable borrow ends here
...
error: aborting due to previous error
```
It is not expected to me that the lifetime of the mutable reference would clash. It seems that the only reason the lifetime of a is considered so long is because it can be returned. However, if it is being returned, I don't see why it should be considered a conflict, as it won't continue with the loop.
I'm not familiar with the details of the compiler, but I would expect, and I would want, the compiler to end the lifetime of the mutable borrow at the end of the loop. Or at the end of containing braces if there are any. | A-lifetimes,A-borrow-checker,T-compiler,C-bug | low | Critical |
267,098,937 | rust | Add suggestion/explanation to error on trying to mutably borrow immutable reference | ```rust
let mut mem_buffer : &[u8] = &b"foo"[..];
let mut reader = &mut mem_buffer as &std::io::Read;
let mut read_buffer = [0u8, 10];
reader.read(&mut read_buffer);
```
reports
```
error[E0596]: cannot borrow immutable borrowed content `*reader` as mutable
--> src/main.rs:5:5
|
5 | reader.read(&mut read_buffer);
| ^^^^^^ cannot borrow as mutable
```
Which is correct, but the fix is to modify the creation of the `reader` variable. While this case is easy, it's probably less so in the general case. Possible avenues of improvement:
1. The easy way this error message can be improved is to mention that the type is `&T`, but should be `&mut T`.
2. If there are explicit type annotations on the variable, a note should point to it
3. If the variable's type is inferred, a note should point to its initializer and maybe even do some primitive checks that can lead the developer towards the solution. | C-enhancement,A-diagnostics,P-low,T-compiler,WG-diagnostics | low | Critical |
267,132,908 | electron | Per monitor DPI awareness causes issues with window positioning and sizing | As per https://github.com/electron/electron/issues/9560 where previous issues regarding this were collapsed into.
If you have one monitor with non-100% scaling and one monitor with 100% scaling both `setSize` and `setPosition` do not act as expected (they always set incorrectly by a factor exactly equal to the scale factor of the screen)
A proposed workaround is #9708 but that simply reverts the addition of the feature instead of fixing the underlying cause.
All future issues regarding DPI scaling and window positioning / sizing should be merged into this one. | platform/windows,machine-dependent,bug :beetle:,bug/regression :leftwards_arrow_with_hook:,2-0-x,5-0-x,component/BrowserWindow | high | Critical |
267,136,076 | flutter | secondaryAnimation in Router buildTransitions is never started | I’m trying to run second example from: https://docs.flutter.io/flutter/widgets/ModalRoute/buildTransitions.html
But it seems that `secondaryAnimation` is not started, it’s in `dismissed` state. When I print `secondaryAnimation.toString()` I’m getting
`kAlwaysDismissedAnimation➩ProxyAnimation➩ProxyAnimation`
From the sources of `animation.dart` I can read:
```
// An animation that is always dismissed.
//
// Using this constant involves less overhead than building an
// [AnimationController] with an initial value of 0.0. This is useful when an
// API expects an animation but you don't actually want to animate anything.
const Animation<double> kAlwaysDismissedAnimation = const _AlwaysDismissedAnimation();
```
And in `routes.dart` it’s indeed initialized to `final ProxyAnimation _secondaryAnimation = new ProxyAnimation(kAlwaysDismissedAnimation);`
Maybe I'm doing something wrong but I couldn't find a way to initialize `secondaryAnimation` with different value.
| framework,d: api docs,f: routes,P2,team-framework,triaged-framework | low | Major |
267,156,695 | angular | Leave animation triggers child ngOnDestroy immediately | <!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>
## Current behavior
<!-- Describe how the issue manifests. -->
`ngOnDestroy` is called when the `:leave` animation starts.
## Expected behavior
<!-- Describe what the desired behavior would be. -->
`ngOnDestroy` should be called after the `:leave` animation finishes.
## Minimal reproduction of the problem with instructions
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-->
[Reproduction plunkr](http://plnkr.co/edit/RL8FsFb0WtbTIuMAQGbq?p=preview)
1. Wait for the `:enter` animation to finish. The element background is red during the whole duration of the animation.
2. Click the "Hide" button. The red background is removed immediately when the animation starts.
If replays are necessary, use the "Show" button to restart the reproduction.
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
If the destroy method makes visual changes to the component or directive, these will be visible during the leave animation. This results in unexpected behavior for the user.
## Environment
<pre><code>
Angular version: 4.4.6
Also reproducible in 5.0.0-rc.3
<!-- Check whether this is still an issue in the most recent Angular version -->
Browser:
- all
</code></pre>
| type: bug/fix,area: animations,freq2: medium,P3 | medium | Critical |
267,210,903 | rust | Failing tests for x86_64-unknown-linux-gnux32 | As can see [here](https://travis-ci.org/rust-lang/rust/jobs/290436965), the are failing tests for x86_64-unknown-linux-gnux32
[run-pass](https://travis-ci.org/rust-lang/rust/jobs/290436965#L5218):
- `lto-unwind.rs`
- `backtrace-debuginfo.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `backtrace.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `command-before-exec.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `command-exec.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `out-of-stack.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `stack-probes-lto.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `stack-probes.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
- `wait-forked-but-failed-child.rs` (Fixed by https://github.com/rust-lang/rust/pull/45652)
@alexcrichton [suggests](https://github.com/rust-lang/rust/pull/45391#issuecomment-338087194) that it is a problem with stack walk.
libstd:
- `net::tcp::tests::timeouts`
- `net::udp::tests::timeout`
- `sys::imp::ext::net::test::timeouts`
- `io::cursor::tests::test_box_slice_writer` (segfault)
The timeout are related with `timeval`, `setsockopt` and `SO_RCVTIMEO`.
Edit 1: update to include https://github.com/rust-lang/rust/pull/45652 fixes | O-linux,C-bug,O-x32 | low | Critical |
267,221,295 | TypeScript | Compiler gives two different errors for wrong number of type arguments | ```ts
class B<T, U = number> {
t: T
u: U
}
class D extends B<string, string, string> {
~
Generic type B<T, U> requires between 1 and 2 type arguments.
d: number
}
let b = new B<string, string, string>()
~~~
Expected 1-2 type arguments, but got 3.
```
**Expected behavior:**
You get a wordier, less helpful message when incorrectly extending a base class. You get a terser, more detailed, message when incorrectly creating an instance of the base class.
**Actual behavior:**
Both messages should be the new terse, detailed message. I forgot to change this when I added the new message. | Bug,Domain: Error Messages | low | Critical |
267,263,860 | TypeScript | Bug(?): Using attribute type of extended generic param and an intersection type | **TypeScript Version:** 2.7.0-dev.20171020
**Code**
```ts
interface Container {
foo: Foo;
}
interface Foo {
a: string;
}
interface Bar {
b: string;
}
function example<T extends Container>(): T['foo'] & Bar {
return {
a: 'foo',
b: 'bar',
};
}
```
**Expected behavior:**
I expect the code to compile. `T` extends `Container`, so it knows `T['foo']` must be assignable to `Foo`, even if the interface is extended, as the function signature allows. Replacing `T['foo'] & Bar` in the function's return type with `Foo & Bar` works fine.
**Actual behavior:**
Compile error:
```
index.ts(15,5): error TS2322: Type '{ a: string; b: string; }' is not assignable to type 'T["foo"] & Bar'.
Object literal may only specify known properties, but 'a' does not exist in type 'T["foo"] & Bar'. Did you mean to write 'a'?
``` | Bug | low | Critical |
267,311,041 | go | go/ast: trailing func comments mishandled in CommentMap | Working example: https://play.golang.org/p/TlsDxVbGow
Prints: `g: "trailing comment in f\n"`
Seems like the correct output should either be nothing (if it is associated with `_ = x`), or `f: "trailing comment in f\n"`.
What's currently happening is that the "_ = x" in func f is the most recent "important" node when we encounter the comment. Since the comment isn't on the line immediately following "_ = x", it doesn't
get associated with it. We don't look further up the "important nodes" stack to notice that it's within the bounds of f. Instead, we just give up and associate it with g.
/cc @griesemer | help wanted,NeedsFix | low | Minor |
267,316,634 | vscode | Explore improving GDPR annotations | The current GDPR annotations are comment based. Thus, if we are not careful, they can easily go out of sync with the actual code. Scope of this exploration:
- using interfaces and types
- listing rules and quick fixes | plan-item | low | Minor |
267,345,241 | vue | Asset support for functional components | ### What problem does this feature solve?
Functional components with templates allow users to improve performance without sacrificing readability or ease of use. However, currently these do not support the "components" option. This limits this feature a lot, to a very limited set of use cases.
### What does the proposed API look like?
Simply support the components option just like non-functional components
<!-- generated by vue-issues. DO NOT REMOVE --> | intend to implement,feature request,improvement,has PR | medium | Major |
267,354,869 | TypeScript | Polymorphic `this` breaks when a module exports a variable and interface with the same name | Importing a variable that has a corresponding interface of the same name from a module causes unexpected behavior.
In the screenshot below, the function, doSomething, should return the type `Model<number>` due to polymorphic `this`; however, it returns `Model<T>`, which is unusable.
<img width="1270" alt="screen shot 2017-10-20 at 11 02 03 pm" src="https://user-images.githubusercontent.com/9221137/31848679-40fae1ca-b5ec-11e7-9db3-bb8b250e2c95.png">
Here is an easy way to reproduce this behavior:
1) `npm install -g @types/sequelize sequelize`
2) Replace `node_modules/@types/sequelize/index.d.ts` with the following
```ts
declare namespace sequelize {
interface Model<T> {
doSomething(arg: T): this;
}
}
declare var sequelize: { Model: sequelize.Model<any> };
export = sequelize;
```
3) create a file with the following contents:
```ts
import { Model } from 'sequelize';
let a: Model<number> = null as any;
a.doSomething(5).doSomething();
```
Workaround:
Use `import * as ...` syntax and the names will resolve correctly.
<img width="611" alt="screen shot 2017-10-20 at 11 22 28 pm" src="https://user-images.githubusercontent.com/9221137/31848782-9950104c-b5ed-11e7-8766-cbc1c95d9939.png">
| Bug | low | Minor |
267,379,740 | vue | Alert (possibly fix) SSR Mismatch in Production | ### What problem does this feature solve?
Currently there is no way to receive alerts (and possibly rerender) in production concerning SSR vs VDom mismatch.
This is critical because different browsers will handle this in unexpected ways. For instance, I just finished trouleshooting an issue that is specific to Windows 10 and IE11 where a rendered vdom tree does not match ssr rendered html and causes a white screen. Chrome and other browsers were able to recover. The mismatch renders fine when navigating to this from an already rendered vue. Just not when the initial rendering happens with a specific page.
Discussion in forum.
https://forum.vuejs.org/t/ssr-render-mismatch-error-emit-in-production/20083
### What does the proposed API look like?
I think the bulk of code currently lives here.
https://github.com/vuejs/vue/blob/adff0084e1b7bc4b8ffa2b87390c66afbc435582/src/core/vdom/patch.js#L662
I think during initial ssr render we need more granular flags to opt in to alerts on this behavior. Currently it is only NODE_ENV
Initial (maybe too verbose) thoughts would be.
WARN_ON_SSR_MISMATCH
RECOVER_ON_SSR_MISMATCH
Then if those are true we can change behavior.
I understand that this is performance critical so am very open to suggestions. I would be willing to implement this myself in a PR.
<!-- generated by vue-issues. DO NOT REMOVE --> | improvement | low | Critical |
267,387,195 | rust | RawVec stores a capacity field even if T is zero-sized | When `std::mem::size_of::<T>() == 0` `RawVec<T>` has always a capacity equal to `std::usize::MAX` elements. It currently stores a `cap: usize` that always contains this value but doing so is unnecessary in this case.
@withoutboats this would be a not so far fetched case for allowing `struct` specialization like @arielb1 proposed. | I-slow,T-libs-api,A-specialization,C-feature-accepted,I-heavy,A-layout,A-zst | medium | Major |
267,411,018 | TypeScript | Suggestion: Allow merging of a wildcard import alias with a compile-time-only type alias of the same name | For projects with a lot of types with their own sets of functions, namespacing is of course a standard technique in programming to resolve naming conflicts between the functions of those types. The problem with namespacing in TypeScript (and JavaScript, by extension) is that it introduces an object-property hierarchy that can't be easily normalized to eliminate dead code and unused functions and classes.
ES2015 module syntax provided a nice solution for this - wildcard imports - but unfortunately that doesn't play nicely with TypeScript's merging of namespaces with types. I'd love to see a way to associate a module with an interface or type alias without introducing the compiled output overhead of TypeScript namespaces when those namespaces exist only to associate some functions with a related type name.
### Proposal
If a compile-time-only type is imported with the same alias as the wildcard alias, either as `default` or otherwise, that type name would automatically merge with the wildcard alias, allowing the wildcard alias to also be used to reference the merged type alias:
```ts
// foo.ts
export interface Foo { /* ... */ }
export function create(): Foo { /* ... */ }
export default Foo;
// bar.ts
import Foo, * as Foo from './foo';
const foo: Foo = Foo.create();
// ------
// or:
// bar.ts
import * as Foo from './foo';
import { Foo } from './foo';
const foo: Foo = Foo.create();
```
### Rationale
This is sort of already supported with TypeScript namespace merging, but TypeScript namespaces generate extra boilerplate that can't be easily tree-shaken at build time, and for which the indirection is baked into the final output, unlike wildcard imports, the indirection of which is discarded at build time by modern bundlers.
I can't do this:
```ts
import * as SortedSet from '@collectable/sorted-set';
// redundant/contrived, just for explanation purposes:
function add<T>(value: T, set: SortedSet<T>): SortedSet<T> {
return SortedSet.add(value, set);
}
```
or this:
```ts
// ... the names can't be merged here:
import SortedSet, * as SortedSet from '@collectable/sorted-set';
// or here:
import * as SortedSet from '@collectable/sorted-set';
import SortedSet from '@collectable/sorted-set';
// or here:
import * as SortedSet from '@collectable/sorted-set';
import { SortedSet } from '@collectable/sorted-set';
```
Instead, I'd have to do this:
```ts
import * as SortedSet from '@collectable/sorted-set';
function add<T>(value: T, set: SortedSet.SortedSet<T>): SortedSet.SortedSet<T> {
return SortedSet.add(value, set);
}
```
Or I could give SortedSet some kind of general type name, but this would then be too abstract if not performing a wildcard import:
```ts
import * as SortedSet from '@collectable/sorted-set';
function add<T>(value: T, set: SortedSet.Type<T>): SortedSet.Type<T> {
return SortedSet.add(value, set);
}
// but now I'm forced to manually alias the type at the point of consumption:
import {Type as SortedSet, add} from '@collectable/sorted-set';
function add<T>(value: T, set: SortedSet<T>): SortedSet<T> {
return add(value, set);
}
```
Alternatively I could export an alias of the `SortedSet` type as `Type`, but now I'm confusing the issue by having two different type names that mean the same thing.
I'm open to any solution which lets me associate a module with an interface or type alias; I just want the output to be optimal for ES2015, rather than optimal for TypeScript. For libraries that export a number of different type modules, where those modules implement common function names, this would be a very useful addition. | Suggestion,Awaiting More Feedback | low | Major |
267,425,694 | youtube-dl | Dramafever - Unable to login | ## 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 this: `[x]`)
- Use the *Preview* tab to see what your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.10.20*. 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.10.20**
### Before submitting an *issue* make sure you have:
- [X ] At least skimmed through the [README](https://github.com/rg3/youtube-dl/blob/master/README.md), **most notably** the [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 the `-v` flag to **your command line** you run youtube-dl with (`youtube-dl -v <your command line>`), copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'--dump-pages', u'--proxy', u'socks5://192.168.1.1:1000/', u'-u', u'PRIVATE', u'-p', u'PRIVATE', u'-f', u'list', u'--playlist-items', u'1', u'--write-sub', u'--sub-lang', u'English', u'https://www.dramafever.com/drama/5040/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.10.20
[debug] Python version 2.7.13 - Linux-4.9.0-4-amd64-x86_64-with-debian-9.2
[debug] exe versions: ffmpeg 3.2.8-1, ffprobe 3.2.8-1
[debug] Proxy map: {u'http': u'socks5://192.168.1.1:1000/', u'https': u'socks5://192.168.1.1:1000/'}
[debug] Using fake IP 3.90.100.148 (US) as X-Forwarded-For.
[dramafever:series] Logging in as **redacted**
[dramafever:series] Dumping request to https://www.dramafever.com/accounts/login/
<!doctype html>
<html ng-app="dramafever" ng-controller="DFApplicationController as rm">
<head>
  <meta charset="utf-8">
  <title ng-bind="rm.meta().title">Watch Korean Drama Free | Korean Movies Online & Telenovela | DramaFever | KDrama</title>

  <!-- build:base -->
  <base href="/">
  <!-- endbuild -->

  <meta name="description" content="{{rm.meta().description}}">
  <meta name="keywords" content="{{ rm.meta().keywords }}">

  <meta name="viewport" content="width=device-width">
  <meta name="dramafever:health" content="good">

  <!-- Twitter Card Information -->
  <meta name="twitter:card" content="summary_large_image">
  <meta name="twitter:title" content="{{rm.meta().title}}">
  <meta name="twitter:site" content="Dramafever">
  <meta name="twitter:description" content="{{rm.meta().description}}">
  <meta name="twitter:creator" content="Dramafever">
  <meta name="twitter:image:src" content="{{rm.meta().image | buildPath: true}}">

  <!-- Open-Graph Information -->
  <meta property="og:type" content="article">
  <meta property="og:title" content="{{rm.meta().title}}">
  <meta property="og:site_name" content="Dramafever">
  <meta property="og:description" content="{{rm.meta().description}}">
  <meta property="og:image" content="{{rm.meta().image | buildPath: true}}">
  <meta property="og:url" content="{{rm.absUrl()}}">
  <meta property="og:locale" content="{{rm.UrlLanguage.activeLanguage}}">
  <meta property="fb:app_id" content="@@facebook.app_id">
  <meta property="fb:admins" content="725041423,503879685,769413503,120959,1157251270">


  <meta property="og:video" content="{{rm.absUrl()}}" ng-if="rm.meta().hasVideo">

  <meta property="og:video:url" content="{{rm.absUrl()}}" ng-if="rm.meta().hasVideo">
  <meta property="og:video:type" content="video/mp4" ng-if="rm.meta().hasVideo">
  <meta property="og:video:width" content="640" ng-if="rm.meta().hasVideo">
  <meta property="og:video:height" content="375" ng-if="rm.meta().hasVideo">
  <meta name="video_type" content="video/mp4" ng-if="rm.meta().hasVideo">
  <meta name="medium" content="video" ng-if="rm.meta().hasVideo">
  <meta name="video_width" content="100%" ng-if="rm.meta().hasVideo">
  <meta name="video_height" content="100%" ng-if="rm.meta().hasVideo">

  <link rel="apple-touch-icon-precomposed" sizes="152x152" href="{{'images/favicon-152x152.png' | buildPath}}">
  <link rel="apple-touch-icon-precomposed" sizes="144x144" href="{{'images/favicon-144x144.png' | buildPath}}">
  <link rel="apple-touch-icon-precomposed" sizes="120x120" href="{{'images/favicon-120x120.png' | buildPath}}">
  <link rel="apple-touch-icon-precomposed" sizes="114x114" href="{{'images/favicon-114x114.png' | buildPath}}">
  <link rel="apple-touch-icon-precomposed" sizes="72x72" href="{{'images/favicon-72x72.png' | buildPath}}">
  <link rel="apple-touch-icon-precomposed" href="{{'images/favicon-57x57.png' | buildPath}}">
  <link rel="icon" href="{{'images/favicon-32x32.png' | buildPath}}" sizes="32x32">

  <link ng-href="{{'styles/fontastic.css' | buildPath}}" rel="stylesheet" type="text/css">
  <link href="https://fonts.googleapis.com/css?family=Open+Sans:400,700|Raleway:400,700,800" rel="stylesheet">

  <!-- bower:css -->
  <link rel="stylesheet" href="builds/57/libs.min.css">
  <!-- endinject -->

  <!-- inject:css -->
  <link rel="stylesheet" href="builds/57/dramafever.min.css">
  <!-- endinject -->

  <script>window.appConfig = { "application":{"storage":"local","id":"www","url":"https://www.dramafever.com"},"raven":{"dsn":"https://9b205aae68ae49a089cb4f3edda971c5@sentry.io/160215"}, "swiftype":{"engineKey":"CywzyscJAHKCwrezfzpN"}, "build": {"id":"57","destination":"dist/builds/57","destOnly":"/builds/57"}, "facebookPixel": {"id":"111244061120"}, "freewheel": {"url":"https://5e0d2.v.fwmrm.net/ad/g/1","nw":"385234","prof":"385234:df_html5_desktop_live","resp":"vast3","csid":"df_desktop_episode_html5","asnw":"385234","ssnw":"385234","flag":"+amcb+exvt+emcr+aeti+sltp","metr":"1023","platform":"web","env":"prod","nielson":"Y0g5NDJxZVFiQzJvOm0zdnN5M3g5OXR3ODY3eUdqVTNQ","iOS":{"prof":"385234:df_iosweb_live","csid":"df_mobileweb_ios_video"},"android":{"prof":"385234:df_androidweb_live","csid":"df_mobileweb_android_video"},"timeout":1}, "comScore": {"c2":"14909701","stationTitle":"DRAMAFEVER","dictionary":"DRAMAFEVER"}, "youbora": {"accountCode":"dramafever","enableAnalytics":true,"channel":"dramafever"} };</script>

  <!-- Facebook Pixel Code not ideal place but this is where Facebook wants the script to be.-->
  <script>
  !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod?
  n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n;
  n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0;
  t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window,
  document,'script','https://connect.facebook.net/en_US/fbevents.js');

  fbq('init', '111244061120');
  </script>
  <noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=111244061120&ev=PageView&noscript=1"></noscript>
  <!-- End Facebook Pixel Code -->

  <!-- wb dfp override -->
  <script async src="//js-sec.indexww.com/ht/htw-wb.js" type="text/javascript"></script>
  <script type="text/javascript">
      window.googletag = window.googletag || {};
      googletag.cmd = window.googletag.cmd || [];
      googletag.cmd.push(function() {
          if (typeof window.headertag === 'undefined' || window.headertag.apiReady !== true) {
              window.headertag = googletag;
          }
      });
  </script>
  <!-- end wb dfp override -->
</head>
<body>
  <div ng-include="'partials/header/mobile-nav.html'"></div>
  <div class="site-container" ui-view autoscroll="true" ng-class="{openburger:rm.activeMobileMenu }"></div>
  <search:overlay></search:overlay>

  <!-- bower:js -->
  <script src="builds/57/libs.min.js"></script>
  <!-- endinject -->

  <!-- inject:modules -->
  <script src="builds/57/dramafever-bundle.js"></script>
  <!-- endinject -->

  <!-- inject:js -->
  <script src="builds/57/dramafever.min.js"></script>
  <!-- endinject -->

  <!-- inject:partials -->
  <script src="builds/57/dramafever.templates.js"></script>
  <!-- endinject -->

  <script type="text/javascript">
    //Sentry Config
    Raven.config('https://9b205aae68ae49a089cb4f3edda971c5@sentry.io/160215', {
      release: '57'
    }).install();
    //Google Analytics
    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
    (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
    m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
    })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');

    ga('create', 'UA-5254737-1', 'auto');
  </script>

  <div id="fb-root"></div>
  <script>(function(d, s, id) {
    var js, fjs = d.getElementsByTagName(s)[0];
    if (d.getElementById(id)) return;
    js = d.createElement(s); js.id = id;
    js.src = "//connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.7";
    fjs.parentNode.insertBefore(js, fjs);
  }(document, 'script', 'facebook-jssdk'));</script>

  <!-- Google Tag Manager -->
  <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
  new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
  j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
  'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
  })(window,document,'script','dataLayer','GTM-THVVLPD');</script>
  <!-- End Google Tag Manager -->

  <!-- Segment Analytics -->
  <script>
    !function(){var analytics=window.analytics=window.analytics||[];if(!analytics.initialize)if(analytics.invoked)window.console&&console.error&&console.error("Segment snippet included twice.");else{analytics.invoked=!0;analytics.methods=["trackSubmit","trackClick","trackLink","trackForm","pageview","identify","reset","group","track","ready","alias","debug","page","once","off","on"];analytics.factory=function(t){return function(){var e=Array.prototype.slice.call(arguments);e.unshift(t);analytics.push(e);return analytics}};for(var t=0;t<analytics.methods.length;t++){var e=analytics.methods[t];analytics[e]=analytics.factory(e)}analytics.load=function(t){var e=document.createElement("script");e.type="text/javascript";e.async=!0;e.src=("https:"===document.location.protocol?"https://":"http://")+"cdn.segment.com/analytics.js/v1/"+t+"/analytics.min.js";var n=document.getElementsByTagName("script")[0];n.parentNode.insertBefore(e,n)};analytics.SNIPPET_VERSION="4.0.0";
    analytics.load("aNZXYivtZIfyATXSjd2ajH4kjUNDq2yI");
    }}();
  </script>
  <!-- End Segment Analytics -->

</body>
</html>

ERROR: Unable to log in; 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 call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 784, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 433, in extract
self.initialize()
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 391, in initialize
self._real_initialize()
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/dramafever.py", line 41, in _real_initialize
self._login()
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/dramafever.py", line 66, in _login
raise ExtractorError('Unable to log in')
ExtractorError: Unable to log in; 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 call youtube-dl with the --verbose flag and include its complete output.
### Description of your *issue*, suggested solution and other information
While trying to grab a video from dramafever, it is now saying it is unable to login. I can still login using this username and password on the main site through a browser.
This issue occurs with or without the socks5 proxy enabled.
Explanation of your *issue* in arbitrary form goes here. Please make sure the [description is worded well enough to be understood](https://github.com/rg3/youtube-dl#is-the-description-of-the-issue-itself-sufficient). Provide as much context and examples as possible.
If work on your *issue* requires account credentials please provide them or explain how one can obtain them.
| cant-reproduce | low | Critical |
267,442,742 | rust | likely/unlikely intrinsics fail to propagate through inline functions | [See it live](https://godbolt.org/g/WhPRDs):
```rust
#![feature(core_intrinsics)]
extern crate core;
use core::intrinsics::unlikely;
#[inline(always)]
fn test(x: bool) -> bool {
unsafe {
unlikely(x)
}
}
pub fn foo(x: u32) -> u32 {
if test(x == 0) { 1 } else { x * 2 }
}
pub fn foo2(x: u32) -> u32 {
unsafe {
let c = unlikely(x == 0);
if c { 1 } else { x * 2 }
}
}
pub fn bar(x: u32) -> u32 {
if x == 0 { 1 } else { x * 2 }
}
```
`foo2` generates:
```asm
push rbp
mov rbp, rsp
test edi, edi
je .LBB1_1
add edi, edi
.LBB1_3:
mov eax, edi
pop rbp
ret
.LBB1_1:
mov edi, 1
jmp .LBB1_3
```
but `foo` generates the same assembly as `bar` instead of the same assembly as `foo2`:
```asm
push rbp
mov rbp, rsp
lea ecx, [rdi + rdi]
test edi, edi
mov eax, 1
cmovne eax, ecx
pop rbp
ret
``` | A-LLVM,T-compiler,C-bug | low | Minor |
267,444,620 | vue | Mouse button modifiers for "v-on" should have more precise aliases | ### What problem does this feature solve?
Currently mouse button modifiers, introduced in #4866, are `left`, `middle`, `right` for `$event.button` values `0`, `1`, `2` correspondingly. But that is only correct for the "default" right-handed layout. In the left-handed mode (when the buttons are switched in the OS) the right button has `0` value and the left button - `2`. Besides, also some right-handed users may reverse or remap the mouse buttons. And working with code with these names for mouse buttons may lead to confusion and bugs among developers not familiar with the "default" right-handed mode being the target for these modifiers.
### What does the proposed API look like?
Keep `left` and `right` as deprecated and add `main` and `secondary` as their aliases.
<!-- generated by vue-issues. DO NOT REMOVE --> | feature request,has PR | low | Critical |
267,453,604 | vscode | Allow to open two distinct editors side by side in one group | VsCode has the ability to horizonatally split an editor window. When you execute `code --diff file1 file2` both files are opened side by side in a single editor window with a single header tab. A similar view is presented when you edit the VsCode settings.
This is splitting. It would be nice to be able to do this for my own files to have multiple views of the same file. What would make it actually usable would be the following three enhancements.
1. The option to split either horizontally or vertically.
1. The ability to move focus from one split pane to another.
1. The ability to unsplit (revert the editor back to a single pane).
What we currently have is a keyboard shortcut "workbench.action.splitEditor" which doesn't actually split an editor at all, instead it just opens the same file in another editor in a different editor group. This is not editor splitting which by definition should occur in the same editor tab.
Calling opening a file in another editor group 'splitting' when there is already nascent functionality to support proper splitting is a pointless ambiguity that serves only to reduce the possibility that the editor will ever support proper splitting any time in the near future.
Proposal:
1. Rename "workbench.action.splitEditor" to "workbench.action.openInNewEditorGroup"
2. Make the VsCode diff view usable by adding a keyboard shortcut to permit cycling focus from one editor pane to the other.
3. Add support to split open editor vertically or horizontally by the addition of the additional keyboard shortcuts "editor.action.splitHorizontal", "editor.action.splitVertical" and "editor.action.unsplit".
| feature-request,workbench-editors | high | Critical |
267,463,356 | rust | Document arithmetic operations on Instant | Some questions that have come up about using Instants:
1. What meaning does `Instant -= Duration` have?
2. What are the preconditions on the instant and the duration, so that it does not panic or cause arithmetic overflow assertions? One user noticed that `instant -= duration` can trip this assertion (specifically on Windows). | C-enhancement,P-medium,T-libs-api,A-time | low | Minor |
267,476,594 | angular | Sorting an array displayed with ngForOf applies void animation state to some elements | ## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>
## Current behavior
When displaying elements of an array using ngForOf and animations are defined for those elements, after sorting the array using Array.prototype.sort the void animation state is applied to some of the elements.
## Expected behavior
The void state should not be applied to elements that are being displayed.
## Minimal reproduction of the problem with instructions
~https://plnkr.co/edit/MPAQhIlOXeyHv3HX66C5
Click "Create" to display a list of items, which are configured through the animations API to be colored blue in the "1" state and red in the void state, and to transition between the two. The items correctly transition from red to blue upon creation. Click "Sort" to sort the list. After it is sorted you will see some of the items transition from blue to red, indicating the void state even though all of the items are still displayed (as they should be).~
The original reproduction above no longer exhibits the issue, but using a Material Stepper you can see what appears to be the same bug.
https://stackblitz.com/edit/angular-zzcx1r?file=src%2Fmain.ts
## What is the motivation / use case for changing the behavior?
## Environment
<pre><code>
Angular version: 4.4.6
Browser:
- [x] Chrome (desktop) version 61.0.3163.91
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [x] Firefox version 56.0
- [x] Safari (desktop) version 11.0
- [ ] Safari (iOS) version XX
- [x] IE version 11.674.15063.0
- [x] Edge version 40.15063.674.0
</code></pre>
| type: bug/fix,area: animations,freq2: medium,P3 | low | Critical |
267,502,957 | neovim | VimL: string(): E724 with obj.func = obj.func | ```vim
let obj = {}
function obj.func()
endfunction
let obj.func = obj.func
echom string(obj)
```
Throws, but still displays:
```
E724: unable to correctly dump variable with self-referencing container
{'func': function('31', {E724@0})}
```
`let obj.func = get(obj, 'func')` seems to work around this.
Shouldn't this behave the same, and be a no-operation after all?
It works in Vim.
Related issues:
https://github.com/neovim/neovim/issues/5902#issuecomment-293622862 links to https://github.com/neovim/neovim/pull/5529#issuecomment-271541590.
Version v0.2.1-1057-ge35a66d39
Version v0.3.0-1029-g48967695c | vimscript,compatibility | low | Major |
267,507,547 | godot | Issue with flipping 2D characters (non uniform scaling) | Hello, so I wanted to try out 3.0 and began porting a game prototype I had in godot 2.1.4 and got a ridiculous "bug?"
This was working fine in godot 2.1.4. Flipping the main node of the character (AKA KinematicBody2D).
but why like that? so all the stuff that are child of the character will flip with the character too, like weapons scenes with its own hitbox and script, particle effects, more sprites, etc. In Godot 2.1.4 actually worked really well without any physics problem as long as you don't use weird numbers.
the way I did it was changing the node scale of the main node (KinematicBody2D) from (1, 1) facing right to (-1, 1) facing left.
Feature Request: this is not crazy needed but maybe a Flip H and Flip V checkbox in the physicsbodies like in the Sprite node. that way you don't have to flip every single child on the character and you don't mess with the scale numbers. at be able of doing it of code or fixing the bug I'm having
I know you guys will say you're not supposed to change the scale of a physicsbody but to me it makes
more sense to flip the main node of the character instead of the sprite node or any other node.
having all the weapons and stuff as a child of the sprite node doesn't feel right and at the same time even if thats the way of doing it, you have to tell new people that that's the way of doing it.
**Issue description:**
the characters goes crazy and flips H and V very fast when flipping the character (that didn't happen in 2.1.4)
**Steps to reproduce:**
when moving to the left flip the main node with set_scale((-1,1) in script then ingame move to the left and it happens
**Link to minimal example project:**
[platformTEST.zip](https://github.com/godotengine/godot/files/1405432/platformTEST.zip)
godot 3.0 build 2017-10-22
| discussion,topic:physics | medium | Critical |
267,515,208 | opencv | Build issue with VS2017 and Cuda 9.0 | ##### System information
- OpenCV => 3.3 main branch snapshot
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
CMake config output:
```
found Intel IPP (ICV version): 2017.0.3 [2017.0.3]
at: C:/Users/C/Documents/OpenCV/opencv-master/build/3rdparty/ippicv/ippicv_win
found Intel IPP IW sources: 2017.0.3
at: C:/Users/C/Documents/OpenCV/opencv-master/build/3rdparty/ippicv/ippiw_win
CUDA detected: 9.0
CUDA NVCC target flags: -gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_52,code=sm_52;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-D_FORCE_INLINES
Could not find OpenBLAS include. Turning OpenBLAS_FOUND off
Could not find OpenBLAS lib. Turning OpenBLAS_FOUND off
A library with BLAS API not found. Please specify library location.
LAPACK requires BLAS
A library with LAPACK API not found. Please specify library location.
Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Could NOT find Pylint (missing: PYLINT_EXECUTABLE)
VTK is not found. Please set -DVTK_DIR in CMake to VTK build directory, or to VTK install subdirectory with VTKConfig.cmake file
Caffe: NO
Protobuf: NO
Glog: NO
Looking for tiny_dnn.h
Looking for tiny_dnn.h - found
Found tiny-dnn in: C:/Users/C/Documents/OpenCV/opencv-master/build/3rdparty/tinydnn/tiny-dnn-1.0.0a3
The protocol buffer compiler is not found (PROTOBUF_PROTOC_EXECUTABLE='')
freetype2: NO
harfbuzz: NO
CMake Warning at C:/Users/C/Documents/OpenCV/opencv_contrib-master/modules/matlab/CMakeLists.txt:54 (message):
A required dependency of the matlab module (Python Jinja2 package) was not
found (installation command: "pip install jinja2"). Disabling Matlab
bindings...
No preference for use of exported gflags CMake configuration set, and no hints for include/library directories provided. Defaulting to preferring an installed/exported gflags CMake configuration if available.
Failed to find installed gflags CMake configuration, searching for gflags build directories exported with CMake.
Failed to find gflags - Failed to find an installed/exported CMake configuration for gflags, will perform search for installed gflags components.
Failed to find gflags - Could not find gflags include directory, set GFLAGS_INCLUDE_DIR to directory containing gflags/gflags.h
Failed to find glog - Could not find glog include directory, set GLOG_INCLUDE_DIR to directory containing glog/logging.h
Module opencv_sfm disabled because the following dependencies are not found: Eigen Glog/Gflags
Excluding from source files list: C:/Users/C/Documents/OpenCV/opencv-master/build/modules/imgproc/accum.neon.cpp
Torch importer has been enabled. To run the tests you have to install Torch ('th' executable should be available) and generate testdata using opencv_extra/testdata/dnn/generate_torch_models.py script.
Tesseract: NO
General configuration for OpenCV 3.3.0-dev =====================================
Version control: unknown
Extra modules:
Location (extra): C:/Users/C/Documents/OpenCV/opencv_contrib-master/modules
Version control (extra): unknown
Platform:
Timestamp: 2017-10-23T01:04:20Z
Host: Windows 10.0.15063 AMD64
CMake: 3.9.0
CMake generator: Visual Studio 15 2017 Win64
CMake build tool: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community/MSBuild/15.0/Bin/MSBuild.exe
MSVC: 1911
CPU/HW features:
Baseline: SSE SSE2 SSE3
requested: SSE3
Dispatched code generation: SSE4_1 SSE4_2 FP16 AVX AVX2
requested: SSE4_1 SSE4_2 AVX FP16 AVX2
SSE4_1 (3 files): + SSSE3 SSE4_1
SSE4_2 (1 files): + SSSE3 SSE4_1 POPCNT SSE4_2
FP16 (2 files): + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 AVX
AVX (5 files): + SSSE3 SSE4_1 POPCNT SSE4_2 AVX
AVX2 (8 files): + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 FMA3 AVX AVX2
C/C++:
Built as dynamic libs?: YES
C++11: YES
C++ Compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe (ver 19.11.25547.0)
C++ flags (Release): /DWIN32 /D_WINDOWS /W4 /GR /EHa /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi /wd4251 /wd4324 /wd4275 /wd4512 /wd4589 /MP8 /MD /O2 /Ob2 /DNDEBUG /Zi
C++ flags (Debug): /DWIN32 /D_WINDOWS /W4 /GR /EHa /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi /wd4251 /wd4324 /wd4275 /wd4512 /wd4589 /MP8 /MDd /Zi /Ob0 /Od /RTC1
C Compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/Hostx86/x64/cl.exe
C flags (Release): /DWIN32 /D_WINDOWS /W3 /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi /MP8 /MD /O2 /Ob2 /DNDEBUG /Zi
C flags (Debug): /DWIN32 /D_WINDOWS /W3 /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D _SCL_SECURE_NO_WARNINGS /Gy /bigobj /Oi /MP8 /MDd /Zi /Ob0 /Od /RTC1
Linker flags (Release): /machine:x64 /INCREMENTAL:NO /debug
Linker flags (Debug): /machine:x64 /debug /INCREMENTAL
ccache: NO
Precompiled headers: YES
Extra dependencies: cudart.lib nppc.lib nppial.lib nppicc.lib nppicom.lib nppidei.lib nppif.lib nppig.lib nppim.lib nppist.lib nppisu.lib nppitc.lib npps.lib cublas.lib cufft.lib -LIBPATH:C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v9.0/lib/x64
3rdparty dependencies:
OpenCV modules:
To be built: cudev core cudaarithm flann imgproc ml objdetect phase_unwrapping plot reg surface_matching video xphoto bgsegm cudabgsegm cudafilters cudaimgproc cudawarping dnn face fuzzy img_hash imgcodecs photo shape videoio xobjdetect cudacodec highgui ts bioinspired dpm features2d line_descriptor saliency text calib3d ccalib cudafeatures2d cudalegacy cudaobjdetect cudaoptflow cudastereo datasets rgbd stereo structured_light superres tracking videostab xfeatures2d ximgproc aruco optflow stitching python3
Disabled: js world contrib_world
Disabled by dependency: -
Unavailable: java python2 viz cnn_3dobj cvv dnn_modern freetype hdf matlab sfm
Windows RT support: NO
GUI:
QT: NO
Win32 UI: YES
OpenGL support: NO
VTK support: NO
Media I/O:
ZLib: build (ver 1.2.8)
JPEG: build (ver 90)
WEBP: build (ver encoder: 0x020e)
PNG: build (ver 1.6.24)
TIFF: build (ver 42 - 4.0.2)
JPEG 2000: build (ver 1.900.1)
OpenEXR: build (ver 1.7.1)
GDAL: NO
GDCM: NO
Video I/O:
Video for Windows: YES
DC1394 1.x: NO
DC1394 2.x: NO
FFMPEG: YES (prebuilt binaries)
avcodec: YES (ver 57.89.100)
avformat: YES (ver 57.71.100)
avutil: YES (ver 55.58.100)
swscale: YES (ver 4.6.100)
avresample: YES (ver 3.5.0)
GStreamer: NO
OpenNI: NO
OpenNI PrimeSensor Modules: NO
OpenNI2: NO
PvAPI: NO
GigEVisionSDK: NO
DirectShow: YES
Media Foundation: NO
XIMEA: NO
Intel PerC: NO
Intel Media SDK: NO
Parallel framework: Concurrency
Trace: YES (with Intel ITT)
Other third-party libraries:
Use Intel IPP: 2017.0.3 [2017.0.3]
at: C:/Users/C/Documents/OpenCV/opencv-master/build/3rdparty/ippicv/ippicv_win
Use Intel IPP IW: sources (2017.0.3)
at: C:/Users/C/Documents/OpenCV/opencv-master/build/3rdparty/ippicv/ippiw_win
Use Lapack: NO
Use Eigen: NO
Use Cuda: YES (ver 9.0)
Use OpenCL: YES
Use OpenVX: NO
Use custom HAL: NO
NVIDIA CUDA
Use CUFFT: YES
Use CUBLAS: YES
USE NVCUVID: YES
NVIDIA GPU arch: 50 52 60 61 70
NVIDIA PTX archs:
Use fast math: NO
OpenCL: <Dynamic loading of OpenCL library>
Include path: C:/Users/C/Documents/OpenCV/opencv-master/3rdparty/include/opencl/1.2
Use AMDFFT: NO
Use AMDBLAS: NO
Python 2:
Interpreter: C:/Python27/python.exe (ver 2.7.10)
Python 3:
Interpreter: C:/Users/C/AppData/Local/Programs/Python/Python35/python.exe (ver 3.5)
Libraries: C:/Users/C/AppData/Local/Programs/Python/Python35/libs/python35.lib (ver 3.5.0)
numpy: C:/Users/C/AppData/Local/Programs/Python/Python35/lib/site-packages/numpy/core/include (ver 1.12.0)
packages path: C:/Users/C/AppData/Local/Programs/Python/Python35/Lib/site-packages
Python (for build): C:/Python27/python.exe
Java:
ant: NO
JNI: C:/Program Files/Java/jdk1.8.0_111/include C:/Program Files/Java/jdk1.8.0_111/include/win32 C:/Program Files/Java/jdk1.8.0_111/include
Java wrappers: NO
Java tests: NO
Matlab:
mex: C:/Program Files/MATLAB/MATLAB Production Server/R2015a/bin/mex.bat
Compiler/generator: Not working (bindings will not be generated)
Documentation:
Doxygen: NO
Tests and samples:
Tests: YES
Performance tests: YES
C/C++ Examples: NO
Install path: C:/Users/C/Documents/OpenCV/opencv-master/build/install
cvconfig.h is in: C:/Users/C/Documents/OpenCV/opencv-master/build
-----------------------------------------------------------------
Configuring done
```
VS2017 build output log:
```
Severity Code Description Project File Line Suppression State
Error MSB6006 "cmd.exe" exited with code 1. opencv_core C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_core330d.lib' opencv_ml C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ml\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_core330d.lib' opencv_flann C:\Users\C\Documents\OpenCV\opencv-master\build\modules\flann\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_core330d.lib' opencv_imgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_flann330d.lib' opencv_surface_matching C:\Users\C\Documents\OpenCV\opencv-master\build\modules\surface_matching\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudawarping C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_plot C:\Users\C\Documents\OpenCV\opencv-master\build\modules\plot\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_phase_unwrapping C:\Users\C\Documents\OpenCV\opencv-master\build\modules\phase_unwrapping\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudafilters C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error MSB6006 "cmd.exe" exited with code 1. opencv_photo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_img_hash C:\Users\C\Documents\OpenCV\opencv-master\build\modules\img_hash\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_fuzzy C:\Users\C\Documents\OpenCV\opencv-master\build\modules\fuzzy\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_objdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\objdetect\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_video C:\Users\C\Documents\OpenCV\opencv-master\build\modules\video\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_xphoto C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xphoto\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_imgcodecs C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgcodecs\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_reg C:\Users\C\Documents\OpenCV\opencv-master\build\modules\reg\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudabgsegm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_face C:\Users\C\Documents\OpenCV\opencv-master\build\modules\face\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_video330d.lib' opencv_bgsegm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\bgsegm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_video330d.lib' opencv_shape C:\Users\C\Documents\OpenCV\opencv-master\build\modules\shape\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgcodecs330d.lib' opencv_videoio C:\Users\C\Documents\OpenCV\opencv-master\build\modules\videoio\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudacodec C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_videoio330d.lib' opencv_highgui C:\Users\C\Documents\OpenCV\opencv-master\build\modules\highgui\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_version C:\Users\C\Documents\OpenCV\opencv-master\build\apps\version\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_visualisation C:\Users\C\Documents\OpenCV\opencv-master\build\apps\visualisation\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_annotation C:\Users\C\Documents\OpenCV\opencv-master\build\apps\annotation\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_xobjdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xobjdetect\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_imgproc330d.lib' opencv_dnn C:\Users\C\Documents\OpenCV\opencv-master\build\modules\dnn\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_bioinspired C:\Users\C\Documents\OpenCV\opencv-master\build\modules\bioinspired\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_dpm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\dpm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_flann330d.lib' opencv_features2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\features2d\LINK 1
Error LNK1104 cannot open file '..\..\..\..\lib\Debug\opencv_highgui330d.lib' opencv_waldboost_detector C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xobjdetect\tools\waldboost_detector\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudafeatures2d C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_ml330d.lib' opencv_text C:\Users\C\Documents\OpenCV\opencv-master\build\modules\text\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_features2d330d.lib' opencv_saliency C:\Users\C\Documents\OpenCV\opencv-master\build\modules\saliency\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_features2d330d.lib' opencv_line_descriptor C:\Users\C\Documents\OpenCV\opencv-master\build\modules\line_descriptor\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_perf_videoio C:\Users\C\Documents\OpenCV\opencv-master\build\modules\videoio\LINK 1
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_histogram.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_histogram.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_histogram.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_histogram.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_blend.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_blend.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_blend.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaimgproc\perf\perf_blend.cpp) opencv_perf_cudaimgproc C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_xphoto330d.lib' opencv_perf_xphoto C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xphoto\LINK 1
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudawarping\perf\perf_warping.cpp) opencv_perf_cudawarping C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudawarping\perf\perf_warping.cpp) opencv_perf_cudawarping C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudawarping\perf\perf_warping.cpp) opencv_perf_cudawarping C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudawarping\perf\perf_warping.cpp) opencv_perf_cudawarping C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error D8040 error creating or communicating with child process opencv_perf_cudaimgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaimgproc\cl 1
Error D8040 error creating or communicating with child process opencv_perf_cudawarping C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudawarping\cl 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_bioinspired330d.lib' opencv_perf_bioinspired C:\Users\C\Documents\OpenCV\opencv-master\build\modules\bioinspired\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_features2d330d.lib' opencv_calib3d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\calib3d\LINK 1
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_core.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_core.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_core.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_core.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_element_operations.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_element_operations.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_element_operations.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_element_operations.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_reductions.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_reductions.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth,perf::`anonymous-namespace'::MatCn> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_reductions.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudaarithm\perf\perf_reductions.cpp) opencv_perf_cudaarithm C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error MSB6006 "cmd.exe" exited with code 1. opencv_xfeatures2d C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudalegacy C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error D8040 error creating or communicating with child process opencv_perf_cudaarithm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaarithm\cl 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudabgsegm330d.lib' opencv_perf_cudabgsegm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudabgsegm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_text330d.lib' opencv_datasets C:\Users\C\Documents\OpenCV\opencv-master\build\modules\datasets\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudacodec330d.lib' opencv_perf_cudacodec C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudacodec\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudaoptflow C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudafeatures2d330d.lib' opencv_perf_cudafeatures2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudafeatures2d\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_superres C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_stereo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\stereo\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_videostab C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_phase_unwrapping330d.lib' opencv_structured_light C:\Users\C\Documents\OpenCV\opencv-master\build\modules\structured_light\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_stitching C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_aruco C:\Users\C\Documents\OpenCV\opencv-master\build\modules\aruco\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudaobjdetect C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_ximgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ximgproc\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_cudastereo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_perf_core C:\Users\C\Documents\OpenCV\opencv-master\build\modules\core\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_plot330d.lib' opencv_tracking C:\Users\C\Documents\OpenCV\opencv-master\build\modules\tracking\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_ccalib C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ccalib\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_createsamples C:\Users\C\Documents\OpenCV\opencv-master\build\apps\createsamples\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_video330d.lib' opencv_optflow C:\Users\C\Documents\OpenCV\opencv-master\build\modules\optflow\LINK 1
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudastereo\perf\perf_stereo.cpp) opencv_perf_cudastereo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 535
Error C2610 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::tuple(std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &&)': is not a special member function which can be defaulted (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudastereo\perf\perf_stereo.cpp) opencv_perf_cudastereo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 536
Error C2535 'std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth>::operator =(const std::tuple<cv::Size,perf::`anonymous-namespace'::MatDepth> &)': member function already defined or declared (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudastereo\perf\perf_stereo.cpp) opencv_perf_cudastereo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error C1903 unable to recover from previous error(s); stopping compilation (compiling source file C:\Users\C\Documents\OpenCV\opencv-master\modules\cudastereo\perf\perf_stereo.cpp) opencv_perf_cudastereo C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\include\tuple 674
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_traincascade C:\Users\C\Documents\OpenCV\opencv-master\build\apps\traincascade\LINK 1
Error D8040 error creating or communicating with child process opencv_perf_cudastereo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudastereo\cl 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_aruco330d.lib' opencv_interactive-calibration C:\Users\C\Documents\OpenCV\opencv-master\build\apps\interactive-calibration\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaoptflow330d.lib' opencv_perf_cudaoptflow C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaoptflow\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_rgbd C:\Users\C\Documents\OpenCV\opencv-master\build\modules\rgbd\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_xfeatures2d330d.lib' opencv_perf_xfeatures2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xfeatures2d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaobjdetect330d.lib' opencv_perf_cudaobjdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaobjdetect\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_perf_calib3d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\calib3d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudafilters330d.lib' opencv_perf_cudafilters C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudafilters\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_perf_objdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\objdetect\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_ximgproc330d.lib' opencv_perf_ximgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ximgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_line_descriptor330d.lib' opencv_perf_line_descriptor C:\Users\C\Documents\OpenCV\opencv-master\build\modules\line_descriptor\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_photo330d.lib' opencv_perf_photo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\photo\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_reg330d.lib' opencv_perf_reg C:\Users\C\Documents\OpenCV\opencv-master\build\modules\reg\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudalegacy330d.lib' opencv_perf_cudalegacy C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudalegacy\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_perf_imgcodecs C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgcodecs\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_stereo330d.lib' opencv_perf_stereo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\stereo\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_optflow330d.lib' opencv_perf_optflow C:\Users\C\Documents\OpenCV\opencv-master\build\modules\optflow\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_tracking330d.lib' opencv_perf_tracking C:\Users\C\Documents\OpenCV\opencv-master\build\modules\tracking\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_aruco330d.lib' opencv_test_aruco C:\Users\C\Documents\OpenCV\opencv-master\build\modules\aruco\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_video330d.lib' opencv_test_video C:\Users\C\Documents\OpenCV\opencv-master\build\modules\video\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_superres330d.lib' opencv_perf_superres C:\Users\C\Documents\OpenCV\opencv-master\build\modules\superres\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_stitching330d.lib' opencv_perf_stitching C:\Users\C\Documents\OpenCV\opencv-master\build\modules\stitching\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_bgsegm330d.lib' opencv_test_bgsegm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\bgsegm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_reg330d.lib' opencv_python3 C:\Users\C\Documents\OpenCV\opencv-master\build\modules\python3\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_bioinspired330d.lib' opencv_test_bioinspired C:\Users\C\Documents\OpenCV\opencv-master\build\modules\bioinspired\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_calib3d330d.lib' opencv_test_calib3d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\calib3d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_video330d.lib' opencv_perf_video C:\Users\C\Documents\OpenCV\opencv-master\build\modules\video\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_perf_imgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudabgsegm330d.lib' opencv_test_cudabgsegm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudabgsegm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudacodec330d.lib' opencv_test_cudacodec C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudacodec\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudafeatures2d330d.lib' opencv_test_cudafeatures2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudafeatures2d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaarithm330d.lib' opencv_test_cudaarithm C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaarithm\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudafilters330d.lib' opencv_test_cudafilters C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudafilters\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaimgproc330d.lib' opencv_test_cudaimgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaimgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaobjdetect330d.lib' opencv_test_cudaobjdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaobjdetect\LINK 1
Error MSB6006 "cmd.exe" exited with code 1. opencv_test_cudev C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets 171
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudalegacy330d.lib' opencv_test_cudalegacy C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudalegacy\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudastereo330d.lib' opencv_test_cudastereo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudastereo\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_test_core C:\Users\C\Documents\OpenCV\opencv-master\build\modules\core\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudawarping330d.lib' opencv_test_cudawarping C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudawarping\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_dnn330d.lib' opencv_test_dnn C:\Users\C\Documents\OpenCV\opencv-master\build\modules\dnn\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_face330d.lib' opencv_test_face C:\Users\C\Documents\OpenCV\opencv-master\build\modules\face\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_cudaoptflow330d.lib' opencv_test_cudaoptflow C:\Users\C\Documents\OpenCV\opencv-master\build\modules\cudaoptflow\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_flann330d.lib' opencv_test_flann C:\Users\C\Documents\OpenCV\opencv-master\build\modules\flann\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_features2d330d.lib' opencv_perf_features2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\features2d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_test_highgui C:\Users\C\Documents\OpenCV\opencv-master\build\modules\highgui\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_img_hash330d.lib' opencv_test_img_hash C:\Users\C\Documents\OpenCV\opencv-master\build\modules\img_hash\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_test_imgcodecs C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgcodecs\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_line_descriptor330d.lib' opencv_test_line_descriptor C:\Users\C\Documents\OpenCV\opencv-master\build\modules\line_descriptor\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_phase_unwrapping330d.lib' opencv_test_phase_unwrapping C:\Users\C\Documents\OpenCV\opencv-master\build\modules\phase_unwrapping\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_fuzzy330d.lib' opencv_test_fuzzy C:\Users\C\Documents\OpenCV\opencv-master\build\modules\fuzzy\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_optflow330d.lib' opencv_test_optflow C:\Users\C\Documents\OpenCV\opencv-master\build\modules\optflow\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_objdetect330d.lib' opencv_test_objdetect C:\Users\C\Documents\OpenCV\opencv-master\build\modules\objdetect\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_ml330d.lib' opencv_test_ml C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ml\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_photo330d.lib' opencv_test_photo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\photo\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_reg330d.lib' opencv_test_reg C:\Users\C\Documents\OpenCV\opencv-master\build\modules\reg\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_structured_light330d.lib' opencv_test_structured_light C:\Users\C\Documents\OpenCV\opencv-master\build\modules\structured_light\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_stereo330d.lib' opencv_test_stereo C:\Users\C\Documents\OpenCV\opencv-master\build\modules\stereo\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_shape330d.lib' opencv_test_shape C:\Users\C\Documents\OpenCV\opencv-master\build\modules\shape\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_stitching330d.lib' opencv_test_stitching C:\Users\C\Documents\OpenCV\opencv-master\build\modules\stitching\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_superres330d.lib' opencv_test_superres C:\Users\C\Documents\OpenCV\opencv-master\build\modules\superres\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_text330d.lib' opencv_test_text C:\Users\C\Documents\OpenCV\opencv-master\build\modules\text\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_rgbd330d.lib' opencv_test_rgbd C:\Users\C\Documents\OpenCV\opencv-master\build\modules\rgbd\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_features2d330d.lib' opencv_test_features2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\features2d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_videostab330d.lib' opencv_test_videostab C:\Users\C\Documents\OpenCV\opencv-master\build\modules\videostab\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_test_videoio C:\Users\C\Documents\OpenCV\opencv-master\build\modules\videoio\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_tracking330d.lib' opencv_test_tracking C:\Users\C\Documents\OpenCV\opencv-master\build\modules\tracking\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_xphoto330d.lib' opencv_test_xphoto C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xphoto\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_xfeatures2d330d.lib' opencv_test_xfeatures2d C:\Users\C\Documents\OpenCV\opencv-master\build\modules\xfeatures2d\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_ximgproc330d.lib' opencv_test_ximgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\ximgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_highgui330d.lib' opencv_test_imgproc C:\Users\C\Documents\OpenCV\opencv-master\build\modules\imgproc\LINK 1
Error LNK1104 cannot open file '..\..\lib\Debug\opencv_dnn330d.lib' opencv_perf_dnn C:\Users\C\Documents\OpenCV\opencv-master\build\modules\dnn\LINK 1
``` | bug,category: build/install,category: gpu/cuda (contrib) | low | Critical |
267,516,056 | rust | Unnecessary compares and branches in asm output | https://godbolt.org/g/62GNZf
```rust
pub fn f1(v: &mut Vec<f32>) {
v.clear();
}
pub fn f2(v: &mut Vec<f32>) {
unsafe { v.set_len(0); }
}
```
```asm
example::f1:
push rbp
mov rbp, rsp
cmp qword ptr [rdi + 16], 0
je .LBB0_2
mov qword ptr [rdi + 16], 0
.LBB0_2:
pop rbp
ret
example::f2:
push rbp
mov rbp, rsp
mov qword ptr [rdi + 16], 0
pop rbp
ret
```
In f1, the lines `cmp qword ptr [rdi + 16], 0` and `je .LBB0_2` should be optimized away, but aren't, why?
(It sets the len to 0 if it's not 0, otherwise leaves it at 0. The len will be 0 afterwards either way, so it should eliminate the check and just set it to 0 like `set_len(0)`.)
I thought I'd open this issue because I don't think such optimization opportunities should be left on the table because it accumulatively affects a lot of code. | I-slow,C-enhancement,C-optimization | low | Minor |
267,518,454 | go | cmd/link: optimize init code, make it generate less asm code and make binary smaller and faster | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go version go1.9 darwin/amd64
### Does this issue reproduce with the latest release?
yes
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/a/go"
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/m9/qtbxkp6s3p96fk54rln7qhj80000gp/T/go-build753370285=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
### What did you do?
https://play.golang.org/p/Ia27Pa9Gxs
### What did you expect to see?
The init call tree should be ordered and flat.
The empty init functions should be remove.
main.Init direct call all init functions in the correct order(this one can be compute from import tree):
```
runtime/internal/sys.init()
unicode/utf8.init()
internal/cpu.init()
unsafe.init()
internal/race.init()
errors.init()
math.init()
sync/atomic.init()
strconv.init()
runtime/internal/atomic.init()
runtime.init()
sync.init()
syscall.init()
time.init()
io.init()
internal/poll.init()
os.init()
```
### What did you see instead?
main.Init() just call strconv.init() os.init() which are defined in main package.
os.init call io.init, runtime.init, sync.init, time.init, internal/poll.init .
The panic message stack in some deep package like `runtime.init` also complex with os.init and main.Init(I just found why it is from this asm code)
```
TEXT os.init(SB) <autogenerated>
<autogenerated>:1 0x1063dc0 65488b0c25a0080000 MOVQ GS:0x8a0, CX
<autogenerated>:1 0x1063dc9 483b6110 CMPQ 0x10(CX), SP
<autogenerated>:1 0x1063dcd 0f861a040000 JBE 0x10641ed
<autogenerated>:1 0x1063dd3 4883ec38 SUBQ $0x38, SP
<autogenerated>:1 0x1063dd7 48896c2430 MOVQ BP, 0x30(SP)
<autogenerated>:1 0x1063ddc 488d6c2430 LEAQ 0x30(SP), BP
<autogenerated>:1 0x1063de1 0fb605dec50800 MOVZX 0x8c5de(IP), AX
<autogenerated>:1 0x1063de8 3c01 CMPL $0x1, AL
<autogenerated>:1 0x1063dea 760a JBE 0x1063df6
<autogenerated>:1 0x1063dec 488b6c2430 MOVQ 0x30(SP), BP
<autogenerated>:1 0x1063df1 4883c438 ADDQ $0x38, SP
<autogenerated>:1 0x1063df5 c3 RET
<autogenerated>:1 0x1063df6 7507 JNE 0x1063dff
<autogenerated>:1 0x1063df8 e803fafbff CALL runtime.throwinit(SB)
<autogenerated>:1 0x1063dfd 0f0b UD2
<autogenerated>:1 0x1063dff c605c0c5080001 MOVB $0x1, 0x8c5c0(IP)
<autogenerated>:1 0x1063e06 e8e503ffff CALL io.init(SB)
<autogenerated>:1 0x1063e0b e86069feff CALL runtime.init(SB)
<autogenerated>:1 0x1063e10 e86b31ffff CALL syscall.init(SB)
<autogenerated>:1 0x1063e15 e82603ffff CALL sync.init(SB)
<autogenerated>:1 0x1063e1a e8f1abffff CALL time.init(SB)
<autogenerated>:1 0x1063e1f e81cccffff CALL internal/poll.init(SB)
<autogenerated>:1 0x1063e24 488d054c410200 LEAQ 0x2414c(IP), AX
error.go:13 0x1063e2b 48890424 MOVQ AX, 0(SP)
error.go:13 0x1063e2f 48c744240810000000 MOVQ $0x10, 0x8(SP)
error.go:13 0x1063e38 e8a3f1feff CALL errors.New(SB)
error.go:13 0x1063e3d 488b442418 MOVQ 0x18(SP), AX
error.go:13 0x1063e42 488b4c2410 MOVQ 0x10(SP), CX
error.go:13 0x1063e47 48890d52e20600 MOVQ CX, 0x6e252(IP)
error.go:13 0x1063e4e 8b0dacc70800 MOVL 0x8c7ac(IP), CX
error.go:13 0x1063e54 85c9 TESTL CX, CX
error.go:13 0x1063e56 0f8577030000 JNE 0x10641d3
error.go:13 0x1063e5c 48890545e20600 MOVQ AX, 0x6e245(IP)
error.go:13 0x1063e63 488d058f430200 LEAQ 0x2438f(IP), AX
error.go:14 0x1063e6a 48890424 MOVQ AX, 0(SP)
error.go:14 0x1063e6e 48c744240811000000 MOVQ $0x11, 0x8(SP)
error.go:14 0x1063e77 e864f1feff CALL errors.New(SB)
error.go:14 0x1063e7c 488b442418 MOVQ 0x18(SP), AX
error.go:14 0x1063e81 488b4c2410 MOVQ 0x10(SP), CX
error.go:14 0x1063e86 48890d33e20600 MOVQ CX, 0x6e233(IP)
error.go:14 0x1063e8d 8b0d6dc70800 MOVL 0x8c76d(IP), CX
error.go:14 0x1063e93 85c9 TESTL CX, CX
error.go:14 0x1063e95 0f851e030000 JNE 0x10641b9
error.go:14 0x1063e9b 48890526e20600 MOVQ AX, 0x6e226(IP)
error.go:14 0x1063ea2 488d05cd460200 LEAQ 0x246cd(IP), AX
error.go:15 0x1063ea9 48890424 MOVQ AX, 0(SP)
error.go:15 0x1063ead 48c744240813000000 MOVQ $0x13, 0x8(SP)
error.go:15 0x1063eb6 e825f1feff CALL errors.New(SB)
error.go:15 0x1063ebb 488b442410 MOVQ 0x10(SP), AX
error.go:15 0x1063ec0 488b4c2418 MOVQ 0x18(SP), CX
error.go:15 0x1063ec5 488905c4e10600 MOVQ AX, 0x6e1c4(IP)
error.go:15 0x1063ecc 8b052ec70800 MOVL 0x8c72e(IP), AX
error.go:15 0x1063ed2 85c0 TESTL AX, AX
error.go:15 0x1063ed4 0f85c5020000 JNE 0x106419f
error.go:15 0x1063eda 48890db7e10600 MOVQ CX, 0x6e1b7(IP)
error.go:15 0x1063ee1 488d05a1460200 LEAQ 0x246a1(IP), AX
error.go:16 0x1063ee8 48890424 MOVQ AX, 0(SP)
error.go:16 0x1063eec 48c744240813000000 MOVQ $0x13, 0x8(SP)
error.go:16 0x1063ef5 e8e6f0feff CALL errors.New(SB)
error.go:16 0x1063efa 488b442410 MOVQ 0x10(SP), AX
error.go:16 0x1063eff 488b4c2418 MOVQ 0x18(SP), CX
error.go:16 0x1063f04 488905a5e10600 MOVQ AX, 0x6e1a5(IP)
error.go:16 0x1063f0b 8b05efc60800 MOVL 0x8c6ef(IP), AX
error.go:16 0x1063f11 85c0 TESTL AX, AX
error.go:16 0x1063f13 0f856c020000 JNE 0x1064185
error.go:16 0x1063f19 48890d98e10600 MOVQ CX, 0x6e198(IP)
error.go:16 0x1063f20 488d053c460200 LEAQ 0x2463c(IP), AX
error.go:17 0x1063f27 48890424 MOVQ AX, 0(SP)
error.go:17 0x1063f2b 48c744240813000000 MOVQ $0x13, 0x8(SP)
error.go:17 0x1063f34 e8a7f0feff CALL errors.New(SB)
error.go:17 0x1063f39 488b442410 MOVQ 0x10(SP), AX
error.go:17 0x1063f3e 488b4c2418 MOVQ 0x18(SP), CX
error.go:17 0x1063f43 48890536e10600 MOVQ AX, 0x6e136(IP)
error.go:17 0x1063f4a 8b05b0c60800 MOVL 0x8c6b0(IP), AX
error.go:17 0x1063f50 85c0 TESTL AX, AX
error.go:17 0x1063f52 0f8513020000 JNE 0x106416b
error.go:17 0x1063f58 48890d29e10600 MOVQ CX, 0x6e129(IP)
error.go:17 0x1063f5f 488d05a55d0200 LEAQ 0x25da5(IP), AX
exec_unix.go:53 0x1063f66 48890424 MOVQ AX, 0(SP)
exec_unix.go:53 0x1063f6a 48c74424081c000000 MOVQ $0x1c, 0x8(SP)
exec_unix.go:53 0x1063f73 e868f0feff CALL errors.New(SB)
exec_unix.go:53 0x1063f78 488b442410 MOVQ 0x10(SP), AX
exec_unix.go:53 0x1063f7d 488b4c2418 MOVQ 0x18(SP), CX
exec_unix.go:53 0x1063f82 48890547e10600 MOVQ AX, 0x6e147(IP)
exec_unix.go:53 0x1063f89 8b0571c60800 MOVL 0x8c671(IP), AX
exec_unix.go:53 0x1063f8f 85c0 TESTL AX, AX
exec_unix.go:53 0x1063f91 0f85ba010000 JNE 0x1064151
exec_unix.go:53 0x1063f97 48890d3ae10600 MOVQ CX, 0x6e13a(IP)
executable_darwin.go:9 0x1063f9e e80de6ffff CALL os.Getwd(SB)
executable_darwin.go:9 0x1063fa3 488b0424 MOVQ 0(SP), AX
executable_darwin.go:9 0x1063fa7 488b4c2408 MOVQ 0x8(SP), CX
executable_darwin.go:9 0x1063fac 488b542410 MOVQ 0x10(SP), DX
executable_darwin.go:9 0x1063fb1 488b5c2418 MOVQ 0x18(SP), BX
executable_darwin.go:9 0x1063fb6 48890d3be10600 MOVQ CX, 0x6e13b(IP)
executable_darwin.go:9 0x1063fbd 8b0d3dc60800 MOVL 0x8c63d(IP), CX
executable_darwin.go:9 0x1063fc3 85c9 TESTL CX, CX
executable_darwin.go:9 0x1063fc5 0f8558010000 JNE 0x1064123
executable_darwin.go:9 0x1063fcb 4889051ee10600 MOVQ AX, 0x6e11e(IP)
executable_darwin.go:9 0x1063fd2 48891527e10600 MOVQ DX, 0x6e127(IP)
executable_darwin.go:9 0x1063fd9 8b0521c60800 MOVL 0x8c621(IP), AX
executable_darwin.go:9 0x1063fdf 85c0 TESTL AX, AX
executable_darwin.go:9 0x1063fe1 0f8522010000 JNE 0x1064109
executable_darwin.go:9 0x1063fe7 48891d1ae10600 MOVQ BX, 0x6e11a(IP)
file.go:56 0x1063fee 488b05bbc50800 MOVQ 0x8c5bb(IP), AX
file.go:56 0x1063ff5 48890424 MOVQ AX, 0(SP)
file.go:56 0x1063ff9 488d0524350200 LEAQ 0x23524(IP), AX
file.go:56 0x1064000 4889442408 MOVQ AX, 0x8(SP)
file.go:56 0x1064005 48c74424100a000000 MOVQ $0xa, 0x10(SP)
file.go:56 0x106400e e8eddcffff CALL os.NewFile(SB)
file.go:56 0x1064013 488b442418 MOVQ 0x18(SP), AX
file.go:56 0x1064018 8b0de2c50800 MOVL 0x8c5e2(IP), CX
file.go:56 0x106401e 85c9 TESTL CX, CX
file.go:56 0x1064020 0f85c9000000 JNE 0x10640ef
file.go:56 0x1064026 488905fbde0600 MOVQ AX, 0x6defb(IP)
file.go:57 0x106402d 488b0524c00600 MOVQ 0x6c024(IP), AX
file.go:57 0x1064034 48890424 MOVQ AX, 0(SP)
file.go:57 0x1064038 488d0547360200 LEAQ 0x23647(IP), AX
file.go:57 0x106403f 4889442408 MOVQ AX, 0x8(SP)
file.go:57 0x1064044 48c74424100b000000 MOVQ $0xb, 0x10(SP)
file.go:57 0x106404d e8aedcffff CALL os.NewFile(SB)
file.go:57 0x1064052 488b442418 MOVQ 0x18(SP), AX
file.go:57 0x1064057 8b0da3c50800 MOVL 0x8c5a3(IP), CX
file.go:57 0x106405d 85c9 TESTL CX, CX
file.go:57 0x106405f 7574 JNE 0x10640d5
file.go:57 0x1064061 488905c8de0600 MOVQ AX, 0x6dec8(IP)
file.go:58 0x1064068 488b05e1bf0600 MOVQ 0x6bfe1(IP), AX
file.go:58 0x106406f 48890424 MOVQ AX, 0(SP)
file.go:58 0x1064073 488d0501360200 LEAQ 0x23601(IP), AX
file.go:58 0x106407a 4889442408 MOVQ AX, 0x8(SP)
file.go:58 0x106407f 48c74424100b000000 MOVQ $0xb, 0x10(SP)
file.go:58 0x1064088 e873dcffff CALL os.NewFile(SB)
file.go:58 0x106408d 488b442418 MOVQ 0x18(SP), AX
file.go:58 0x1064092 8b0d68c50800 MOVL 0x8c568(IP), CX
file.go:58 0x1064098 85c9 TESTL CX, CX
file.go:58 0x106409a 7522 JNE 0x10640be
file.go:58 0x106409c 4889057dde0600 MOVQ AX, 0x6de7d(IP)
<autogenerated>:1 0x10640a3 e808f0ffff CALL os.init.0(SB)
<autogenerated>:1 0x10640a8 e853f1ffff CALL os.init.1(SB)
<autogenerated>:1 0x10640ad c60512c3080002 MOVB $0x2, 0x8c312(IP)
<autogenerated>:1 0x10640b4 488b6c2430 MOVQ 0x30(SP), BP
<autogenerated>:1 0x10640b9 4883c438 ADDQ $0x38, SP
<autogenerated>:1 0x10640bd c3 RET
<autogenerated>:1 0x10640be 488d0d5bde0600 LEAQ 0x6de5b(IP), CX
file.go:58 0x10640c5 48890c24 MOVQ CX, 0(SP)
file.go:58 0x10640c9 4889442408 MOVQ AX, 0x8(SP)
file.go:58 0x10640ce e8ed95faff CALL runtime.writebarrierptr(SB)
file.go:58 0x10640d3 ebce JMP 0x10640a3
file.go:58 0x10640d5 488d0d54de0600 LEAQ 0x6de54(IP), CX
file.go:57 0x10640dc 48890c24 MOVQ CX, 0(SP)
file.go:57 0x10640e0 4889442408 MOVQ AX, 0x8(SP)
file.go:57 0x10640e5 e8d695faff CALL runtime.writebarrierptr(SB)
file.go:57 0x10640ea e979ffffff JMP 0x1064068
file.go:57 0x10640ef 488d0d32de0600 LEAQ 0x6de32(IP), CX
file.go:56 0x10640f6 48890c24 MOVQ CX, 0(SP)
file.go:56 0x10640fa 4889442408 MOVQ AX, 0x8(SP)
file.go:56 0x10640ff e8bc95faff CALL runtime.writebarrierptr(SB)
file.go:56 0x1064104 e924ffffff JMP 0x106402d
file.go:56 0x1064109 488d05f8df0600 LEAQ 0x6dff8(IP), AX
executable_darwin.go:9 0x1064110 48890424 MOVQ AX, 0(SP)
executable_darwin.go:9 0x1064114 48895c2408 MOVQ BX, 0x8(SP)
executable_darwin.go:9 0x1064119 e8a295faff CALL runtime.writebarrierptr(SB)
executable_darwin.go:9 0x106411e e9cbfeffff JMP 0x1063fee
executable_darwin.go:9 0x1064123 4889542428 MOVQ DX, 0x28(SP)
executable_darwin.go:9 0x1064128 48895c2420 MOVQ BX, 0x20(SP)
executable_darwin.go:9 0x106412d 488d0dbcdf0600 LEAQ 0x6dfbc(IP), CX
executable_darwin.go:9 0x1064134 48890c24 MOVQ CX, 0(SP)
executable_darwin.go:9 0x1064138 4889442408 MOVQ AX, 0x8(SP)
executable_darwin.go:9 0x106413d e87e95faff CALL runtime.writebarrierptr(SB)
executable_darwin.go:9 0x1064142 488b542428 MOVQ 0x28(SP), DX
executable_darwin.go:9 0x1064147 488b5c2420 MOVQ 0x20(SP), BX
executable_darwin.go:9 0x106414c e981feffff JMP 0x1063fd2
executable_darwin.go:9 0x1064151 488d0580df0600 LEAQ 0x6df80(IP), AX
exec_unix.go:53 0x1064158 48890424 MOVQ AX, 0(SP)
exec_unix.go:53 0x106415c 48894c2408 MOVQ CX, 0x8(SP)
exec_unix.go:53 0x1064161 e85a95faff CALL runtime.writebarrierptr(SB)
exec_unix.go:53 0x1064166 e933feffff JMP 0x1063f9e
exec_unix.go:53 0x106416b 488d0516df0600 LEAQ 0x6df16(IP), AX
error.go:17 0x1064172 48890424 MOVQ AX, 0(SP)
error.go:17 0x1064176 48894c2408 MOVQ CX, 0x8(SP)
error.go:17 0x106417b e84095faff CALL runtime.writebarrierptr(SB)
error.go:17 0x1064180 e9dafdffff JMP 0x1063f5f
error.go:17 0x1064185 488d052cdf0600 LEAQ 0x6df2c(IP), AX
error.go:16 0x106418c 48890424 MOVQ AX, 0(SP)
error.go:16 0x1064190 48894c2408 MOVQ CX, 0x8(SP)
error.go:16 0x1064195 e82695faff CALL runtime.writebarrierptr(SB)
error.go:16 0x106419a e981fdffff JMP 0x1063f20
error.go:16 0x106419f 488d05f2de0600 LEAQ 0x6def2(IP), AX
error.go:15 0x10641a6 48890424 MOVQ AX, 0(SP)
error.go:15 0x10641aa 48894c2408 MOVQ CX, 0x8(SP)
error.go:15 0x10641af e80c95faff CALL runtime.writebarrierptr(SB)
error.go:15 0x10641b4 e928fdffff JMP 0x1063ee1
error.go:15 0x10641b9 488d0d08df0600 LEAQ 0x6df08(IP), CX
error.go:14 0x10641c0 48890c24 MOVQ CX, 0(SP)
error.go:14 0x10641c4 4889442408 MOVQ AX, 0x8(SP)
error.go:14 0x10641c9 e8f294faff CALL runtime.writebarrierptr(SB)
error.go:14 0x10641ce e9cffcffff JMP 0x1063ea2
error.go:14 0x10641d3 488d0dcede0600 LEAQ 0x6dece(IP), CX
error.go:13 0x10641da 48890c24 MOVQ CX, 0(SP)
error.go:13 0x10641de 4889442408 MOVQ AX, 0x8(SP)
error.go:13 0x10641e3 e8d894faff CALL runtime.writebarrierptr(SB)
error.go:13 0x10641e8 e976fcffff JMP 0x1063e63
<autogenerated>:1 0x10641ed e82e6cfeff CALL runtime.morestack_noctxt(SB)
<autogenerated>:1 0x10641f2 e9c9fbffff JMP os.init(SB)
TEXT strconv.init(SB) <autogenerated>
<autogenerated>:1 0x1053770 65488b0c25a0080000 MOVQ GS:0x8a0, CX
<autogenerated>:1 0x1053779 483b6110 CMPQ 0x10(CX), SP
<autogenerated>:1 0x105377d 0f86ed000000 JBE 0x1053870
<autogenerated>:1 0x1053783 4883ec28 SUBQ $0x28, SP
<autogenerated>:1 0x1053787 48896c2420 MOVQ BP, 0x20(SP)
<autogenerated>:1 0x105378c 488d6c2420 LEAQ 0x20(SP), BP
<autogenerated>:1 0x1053791 0fb6054bcc0900 MOVZX 0x9cc4b(IP), AX
<autogenerated>:1 0x1053798 3c01 CMPL $0x1, AL
<autogenerated>:1 0x105379a 760a JBE 0x10537a6
<autogenerated>:1 0x105379c 488b6c2420 MOVQ 0x20(SP), BP
<autogenerated>:1 0x10537a1 4883c428 ADDQ $0x28, SP
<autogenerated>:1 0x10537a5 c3 RET
<autogenerated>:1 0x10537a6 7507 JNE 0x10537af
<autogenerated>:1 0x10537a8 e85300fdff CALL runtime.throwinit(SB)
<autogenerated>:1 0x10537ad 0f0b UD2
<autogenerated>:1 0x10537af c6052dcc090001 MOVB $0x1, 0x9cc2d(IP)
<autogenerated>:1 0x10537b6 e8b5f7ffff CALL math.init(SB)
<autogenerated>:1 0x10537bb 488d05394c0300 LEAQ 0x34c39(IP), AX
atoi.go:10 0x10537c2 48890424 MOVQ AX, 0(SP)
atoi.go:10 0x10537c6 48c744240812000000 MOVQ $0x12, 0x8(SP)
atoi.go:10 0x10537cf e80cf8ffff CALL errors.New(SB)
atoi.go:10 0x10537d4 488b442410 MOVQ 0x10(SP), AX
atoi.go:10 0x10537d9 488b4c2418 MOVQ 0x18(SP), CX
atoi.go:10 0x10537de 4889053be90700 MOVQ AX, 0x7e93b(IP)
atoi.go:10 0x10537e5 8b0515ce0900 MOVL 0x9ce15(IP), AX
atoi.go:10 0x10537eb 85c0 TESTL AX, AX
atoi.go:10 0x10537ed 756a JNE 0x1053859
atoi.go:10 0x10537ef 48890d32e90700 MOVQ CX, 0x7e932(IP)
atoi.go:10 0x10537f6 488d0550440300 LEAQ 0x34450(IP), AX
atoi.go:13 0x10537fd 48890424 MOVQ AX, 0(SP)
atoi.go:13 0x1053801 48c74424080e000000 MOVQ $0xe, 0x8(SP)
atoi.go:13 0x105380a e8d1f7ffff CALL errors.New(SB)
atoi.go:13 0x105380f 488b442410 MOVQ 0x10(SP), AX
atoi.go:13 0x1053814 488b4c2418 MOVQ 0x18(SP), CX
atoi.go:13 0x1053819 48890510e90700 MOVQ AX, 0x7e910(IP)
atoi.go:13 0x1053820 8b05dacd0900 MOVL 0x9cdda(IP), AX
atoi.go:13 0x1053826 85c0 TESTL AX, AX
atoi.go:13 0x1053828 7518 JNE 0x1053842
atoi.go:13 0x105382a 48890d07e90700 MOVQ CX, 0x7e907(IP)
<autogenerated>:1 0x1053831 c605abcb090002 MOVB $0x2, 0x9cbab(IP)
<autogenerated>:1 0x1053838 488b6c2420 MOVQ 0x20(SP), BP
<autogenerated>:1 0x105383d 4883c428 ADDQ $0x28, SP
<autogenerated>:1 0x1053841 c3 RET
<autogenerated>:1 0x1053842 488d05efe80700 LEAQ 0x7e8ef(IP), AX
atoi.go:13 0x1053849 48890424 MOVQ AX, 0(SP)
atoi.go:13 0x105384d 48894c2408 MOVQ CX, 0x8(SP)
atoi.go:13 0x1053852 e8699efbff CALL runtime.writebarrierptr(SB)
atoi.go:13 0x1053857 ebd8 JMP 0x1053831
atoi.go:13 0x1053859 488d05c8e80700 LEAQ 0x7e8c8(IP), AX
atoi.go:10 0x1053860 48890424 MOVQ AX, 0(SP)
atoi.go:10 0x1053864 48894c2408 MOVQ CX, 0x8(SP)
atoi.go:10 0x1053869 e8529efbff CALL runtime.writebarrierptr(SB)
atoi.go:10 0x105386e eb86 JMP 0x10537f6
<autogenerated>:1 0x1053870 e8ab75ffff CALL runtime.morestack_noctxt(SB)
<autogenerated>:1 0x1053875 e9f6feffff JMP strconv.init(SB)
TEXT main.init(SB) <autogenerated>
<autogenerated>:1 0x1064c90 65488b0c25a0080000 MOVQ GS:0x8a0, CX
<autogenerated>:1 0x1064c99 483b6110 CMPQ 0x10(CX), SP
<autogenerated>:1 0x1064c9d 764a JBE 0x1064ce9
<autogenerated>:1 0x1064c9f 4883ec08 SUBQ $0x8, SP
<autogenerated>:1 0x1064ca3 48892c24 MOVQ BP, 0(SP)
<autogenerated>:1 0x1064ca7 488d2c24 LEAQ 0(SP), BP
<autogenerated>:1 0x1064cab 0fb60511b70800 MOVZX 0x8b711(IP), AX
<autogenerated>:1 0x1064cb2 3c01 CMPL $0x1, AL
<autogenerated>:1 0x1064cb4 7609 JBE 0x1064cbf
<autogenerated>:1 0x1064cb6 488b2c24 MOVQ 0(SP), BP
<autogenerated>:1 0x1064cba 4883c408 ADDQ $0x8, SP
<autogenerated>:1 0x1064cbe c3 RET
<autogenerated>:1 0x1064cbf 7507 JNE 0x1064cc8
<autogenerated>:1 0x1064cc1 e83aebfbff CALL runtime.throwinit(SB)
<autogenerated>:1 0x1064cc6 0f0b UD2
<autogenerated>:1 0x1064cc8 c605f4b6080001 MOVB $0x1, 0x8b6f4(IP)
<autogenerated>:1 0x1064ccf e89ceafeff CALL strconv.init(SB)
<autogenerated>:1 0x1064cd4 e8e7f0ffff CALL os.init(SB)
<autogenerated>:1 0x1064cd9 c605e3b6080002 MOVB $0x2, 0x8b6e3(IP)
<autogenerated>:1 0x1064ce0 488b2c24 MOVQ 0(SP), BP
<autogenerated>:1 0x1064ce4 4883c408 ADDQ $0x8, SP
<autogenerated>:1 0x1064ce8 c3 RET
<autogenerated>:1 0x1064ce9 e83261feff CALL runtime.morestack_noctxt(SB)
<autogenerated>:1 0x1064cee eba0 JMP main.init(SB)
```
ps: This program import tree map from go1.9:
```
"ImportPathMap": {
"errors": null,
"internal/cpu": null,
"internal/poll": [
"errors",
"io",
"sync",
"sync/atomic",
"syscall",
"time",
"unsafe"
],
"internal/race": [
"unsafe"
],
"io": [
"errors",
"sync"
],
"main": [
"os",
"strconv"
],
"math": [
"internal/cpu",
"unsafe"
],
"os": [
"errors",
"internal/poll",
"io",
"runtime",
"sync",
"sync/atomic",
"syscall",
"time"
],
"runtime": [
"runtime/internal/atomic",
"runtime/internal/sys",
"unsafe"
],
"runtime/internal/atomic": [
"unsafe"
],
"runtime/internal/sys": null,
"strconv": [
"errors",
"math",
"unicode/utf8"
],
"sync": [
"internal/race",
"runtime",
"sync/atomic",
"unsafe"
],
"sync/atomic": [
"unsafe"
],
"syscall": [
"errors",
"internal/race",
"runtime",
"sync",
"unsafe"
],
"time": [
"errors",
"runtime",
"sync",
"syscall"
],
"unicode/utf8": null,
"unsafe": null
}
}
``` | Suggested,NeedsInvestigation,compiler/runtime | low | Critical |
267,536,684 | rust | Inference worse in method signature using associated type than with new generic type parameter eq-constrained to the associated type | With this signature
```rust
fn try_fold<F, T: Try>(self, init: T::Ok, mut f: F) -> T where
Self: Sized, F: FnMut(T::Ok, Self::Item) -> T
```
This code
```rust
let a = [1, 2, 3];
let sum = a.iter().try_fold(0i8, |acc, &x| acc.checked_add(x));
```
Gets `error[E0619]: the type of this value must be known in this context`.
But it works fine with the seemingly-equivalent signature
```rust
fn try_fold<F, U, T: Try<Ok=U>>(self, init: U, mut f: F) -> T where
Self: Sized, F: FnMut(U, Self::Item) -> T
```
Since `acc` and `init` must have the same type in both cases, shouldn't both signatures work?
Full repro: https://play.rust-lang.org/?gist=f8d2baeae64b17344e1cf27673a2e905&version=nightly | C-enhancement,A-associated-items,A-inference,T-types | low | Critical |
267,560,855 | opencv | Using WINDOW_OPENGL on QT window (MacOS) causes WINDOW_KEEPRATIO to not work | ##### System information (version)
- OpenCV => 3.3.0
- Operating System / Platform => MacOS 10.12.6
- Compiler => XCode 9.0.0.9000038
[Complete build information](https://drive.google.com/open?id=0B7qnSeyFcPCPbXBicERtQ242RVk)
##### Detailed description
When using `cv2.namedWindow` `WINDOW_KEEPRATIO` was working for me fine. As I resize the window borders are added to keep the image aspect ratio. I then compiled `WITH_QT=ON` and again it still keep the image aspect ratio using the new QT window. However, if I also flag `WINDOW_OPENGL` to `cv2.namedWindow` then the window no longer keeps its aspect ratio.
Here are two images ([1](https://drive.google.com/open?id=0B7qnSeyFcPCPaTJVM21rRUVKbEk), [2](https://drive.google.com/open?id=0B7qnSeyFcPCPN2dYdk0tcXJIRDQ)) showing the same window resized to two very different sizes and the image being squished.
##### Steps to reproduce
```python
cv2.namedWindow(WINDOW_NAME, cv2.WINDOW_NORMAL | cv2.WINDOW_KEEPRATIO | cv2.WINDOW_GUI_EXPANDED | cv2.WINDOW_OPENGL)
```
| feature,category: highgui-gui | low | Minor |
267,572,944 | kubernetes | [Feature Request] Support disk quota for docker runtime | As docker already support `docker run --storage-opt size=1G xxx` such way to limit container disk usage, it would be better if k8s introduced this feature.
On the other hand, it also would be OK if k8s support pass `--storage-opt` in `containers` spec.
Thanks. | area/reliability,sig/storage,sig/node,kind/feature,lifecycle/frozen,needs-triage | medium | Critical |
267,593,482 | angular | Can't pass parameters in template to animation | I have written a small animation which doesn't do much
my-animations.ts
```
export const leavingTowardsTop =
trigger('leavingTowardsTop', [
transition(':leave', [
style({position: 'relative'}),
animate("250ms ease-in", keyframes([
style({top: 0}),
style({top: "{{topPixels}}"})
]))
], {params : { topPixels: "-3000px" }})
])
```
I have registered the animation in a component and in its template I am trying to do :
` <div [@leavingTowardsTop]="{params : { topPixels: '-30px' }}">
`
which works but ignore the specified value for topPixels (so it still takes -3000)
I also tried :
`[@leavingTowardsTop]="{ pixels: '-30px' }"`
but the -30 is still ignored
Am I missing something here ?
I am on Angular 4.4.6 for all modules.
| type: bug/fix,area: animations,freq1: low,P4 | medium | Critical |
267,625,496 | opencv | calibrateCamera fails for random-pattern input and fix focal length aspect ratio | OpenCV 3.3dev, Windows 10 x64, Visual Studio 2017
Problem:
`calibrateCamera` computes bad instrinsics and extrinsics when used with object and image point generated from random-pattern input, and fix focal length aspect ratio (CALIB_FIX_ASPECT_RATIO) flag.
Details:
`random_pattern_calibration.cpp` sample code is used here; command line `random_pattern_calibration.exe -pw 800 -ph 600 -mm 25 images.xml`; when running the original code (flags = 0) the estimated intrinsics are close to real values (though still not perfect: small fx/fy ratio and big p1,p2):
```
<flags>0</flags>
<camera_matrix type_id="opencv-matrix">
<rows>3</rows>
<cols>3</cols>
<dt>d</dt>
<data>
1.2810242855539684e+03 0. 9.4337871627044819e+02 0.
1.7160871348449657e+03 8.2035160399464769e+02 0. 0. 1.</data></camera_matrix>
<distortion_coefficients type_id="opencv-matrix">
<rows>1</rows>
<cols>5</cols>
<dt>d</dt>
<data>
9.0157476710754948e-03 -3.0376368347694447e-02
6.9050641321461419e-03 1.1583844483554158e-02 1.3193574069120802e-02</data></distortion_coefficients>
<rms>3.0258671922648297e+00</rms>
```
but when the flag is set to CALIB_FIX_ASPECT_RATIO and activated for `calibrateCamera` the estimated instrinsics are very far from the real values:
```
<flags>2</flags>
<camera_matrix type_id="opencv-matrix">
<rows>3</rows>
<cols>3</cols>
<dt>d</dt>
<data>
3.8147470141808649e+03 0. -4.7988364085335263e+02 0.
3.8147470141808649e+03 8.7325109000495343e+02 0. 0. 1.</data></camera_matrix>
<camera_distortion type_id="opencv-matrix">
<rows>5</rows>
<cols>1</cols>
<dt>d</dt>
<data>
-2.0394850680235380e-01 7.6372079248181979e-01
-5.4861356671901031e-03 -1.7419167799241686e-01
-4.8816620467613397e-01</data></camera_distortion>
<rms>1.3788212655961322e+01</rms>
```
The real values are:
```
<f>1539.41527989211615</f>
<cx>0.8411201250105462</cx>
<cy>-1.5852183416687927</cy>
<k1>0.0058501330927213891</k1>
<k2>-0.08160902608395923</k2>
<k3>0.12641783193454889</k3>
<p1>-0.00063976203947559184</p1>
<p2>-0.00025905208594043203</p2>
```
Here is the test data used:
[CalibNexus5X.zip](https://github.com/opencv/opencv/files/1406767/CalibNexus5X.zip)
| category: calib3d | low | Minor |
267,660,561 | go | proposal: os: add a package to atomically create or replace a file | I propose adding a package to atomically create or replace a file to the golang.org/x/ namespace.
Moving the required logic into a Go package slightly reduces code length and duplication across programs, but more importantly documents the intricacies of this pattern in a central place.
An implementation of such a package can be found at https://go-review.googlesource.com/c/exp/+/72379 | Proposal | medium | Critical |
267,671,251 | go | cmd/compile: generate correct DW_AT_external flag |
The current (1.9) Go compiler emits DWARF records for subprograms and variables that contain the "DW_AT_external" attribute, a flag which DWARF defines as:
_If the name of the subroutine described by an entry with the tag ... is visible
outside of its containing compilation unit, that entry has a DW_AT_external attribute,
which is a flag._
The compiler is assigning a value to DW_AT_external based on whether the LSym in question is marked as static (AttrStatic), which I don't think is the same as the definition above. When I look at the generated DWARF for things like the Go compiler, the only things being marked as non-external are a small number of vars and functions from assembly files.
Not sure this makes a huge amount of difference (as far as I can tell there is no degradation to the debugging experience as a result of package-local functions being marked as external), but it might be worth fixing this up just for consistency / POLA.
| NeedsFix,Debugging,compiler/runtime | low | Critical |
267,735,421 | angular | Support lazy-loaded event plugins | Currently all event plugins must be loaded at bootstrap. This can be an issue with lazy-loading, when only some subset of the application would need a certain plugin to be loaded. | feature,area: core | low | Major |
267,776,259 | vscode | Support envfile for tasks.json | The node and Go debuggers both support specifying an env file for environment variables instead of the `env` hash. It would be great if we could use the same file in tasks.json to have a single source of truth that can also be used by non-vscode scripts | feature-request,tasks | high | Critical |
267,780,047 | rust | Rustdoc doesn't show re-exports randomly | Some re-exports seem to not be shown in the rustc output. This is especially evident in the [amethyst](https://www.amethyst.rs/) crate.
Examples:
`amethyst_core::transform::bundle::TransformBundle` is re-exported as:
- `amethyst_core::transform::TransformBundle`
- `amethyst_core::TransformBundle`
- `amethyst::core::TransformBundle`
- `amethsyt::core::transform::TransformBundle`
- `amethsyt::core::transform::bundle::TransformBundle`
Yet none of these show up in the [generated documentation](https://www.amethyst.rs/doc/develop/doc/amethyst/index.html).
`amethyst::State` is re-exported as `ametyst::prelude::State`, and this _does_ show in the generated documentation.
This might also be the cause of https://github.com/rust-lang-nursery/rls/issues/505. | T-rustdoc,C-bug | low | Minor |
267,819,348 | flutter | Merge custom TextStyle with Theme.of by default across all material widgets | A number of our widgets take `TextStyle` to allow developers customize the look of text. For example, `InputDecoration` takes `labelStyle`, `helperStyle`, `hintStyle`, etc. It is desirable that the least path of resistance for developers using these options lead to reasonable results.
Currently we expect that the developer supplies a `TextStyle` that has _all_ the required style properties. That requires that either they call the default `TextStyle` constructor passing all the properties, ensure that the text they are styling appears under a `DefaultTextStyle` that supplies the missing properties, or they create a copy of another style (e.g. from `Theme.of`) replacing a subset of properties. Neither of the options are along the path of least resistance. Developers want to use the default constructor and pass a subset of properties, like so:
```dart
new InputDecoration(
labelText: new TextStyle(fontSize: 5.0),
)
```
This leads to broken behavior. The text style is incomplete (e.g. its missing `fontFamily`). Lerping this style with a style that comes from `Theme.of` results in an error, because this style's `inherit: true` while `Theme.of` has its set to `false`. There are probably other bugs that we haven't observed yet.
## Proposal
Classes that take `TextStyle` as arguments should `TextStyle.merge` it with `Theme.of`. This would fill in the gaps in the passed style, but also retains the option of allowing the developer to do the merging manually or supply their own complete text style. All they need to do is pass a `TextStyle` with `inherit: false`, which will just use the style the developer set. Of course, in that case it is up to the developer to make sure their style is complete.
### Widgets to revise
Material: many of the material widgets already use `DefaultTextStyle` populated from `Theme.of` and should behave correctly, but it's worth reviewing them and adding missing tests.
- `InputDecoration`
- `InputDecorator`
- `Material`
- `Chip`
- `DropdownButton`
- `TabBar`
- `TextField`
Widgets: these are tricky because `Theme` is part of the material library, not widgets. So perhaps widgets should either assume they are under a `DefaultTextStyle` or the received `TextStyle` is self-sufficient.
- `WidgetsApp`
- `BannerPainter`
- `EditableText`
- `AnimatedDefaultTextStyle`
/cc @mehmetf @Hixie | framework,f: material design,c: API break,c: proposal,P2,team-design,triaged-design | low | Critical |
267,866,855 | angular | HttpClientXsrfModule breaks compatibility with HttpModule by not handling GET requests | <!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>
## Current behavior
<!-- Describe how the issue manifests. -->
In `HttpModule` you could use XSRF support for GET requests. It added the XSRF header for all requests including GET requests
But `HttpClientModule` does not send the XSRF header for GET requests.
I understand why it's implemented this way, but in corporate world you might want to protect everything as well. This is not the point though.
The point is that this is an undocumented breaking change when moving from `HttpModule` to `HttpClientModule`, that could cost a lot of debugging time if you had code depending on old behaviour.
You can only tell the problem by looking at source code
https://github.com/angular/angular/blob/master/packages/common/http/src/xsrf.ts#L81-L82
if (req.method === 'GET' || req.method === 'HEAD' || lcUrl.startsWith('http://') ||
lcUrl.startsWith('https://')) {
Which I only did by accident after long debugging and then googling and seeing https://github.com/angular/angular/issues/18859#issuecomment-333844607
## Expected behavior
<!-- Describe what the desired behavior would be. -->
Either:
- Document the different behaviour
- Allow overriding it with options
- Or just keep it as before
## Minimal reproduction of the problem with instructions
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-->
For a server that supports XSRF, create a GET Api call with `HttpModule`.
Observe the call working fine.
Change `HttpModule` to ``HttpClientModule` and ``HttpClientXsrfModule`.
See the call fail.
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
Because it was working before and now it breaks.
## Environment
<pre><code>
Angular version: 4.3+
<!-- Check whether this is still an issue in the most recent Angular version -->
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX <!-- run `node --version` -->
- Platform: <!-- Mac, Linux, Windows -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
| feature,freq3: high,area: common/http,state: needs eng input,type: use-case,design complexity: low-hanging,P4,feature: under consideration | medium | Critical |
267,887,341 | vue | Functional components data merging util | ### What problem does this feature solve?
Hi! Components have the extend feature, but there is nothing similar for functional components. The problem and the solution is well explained at https://github.com/alexsasharegan/vue-functional-data-merge and while that works fine and I am very grateful to the author, I would like to request an official in core solution.
Why? Because there are edge situations or new features that 3rd party solutions will have a difficult time to be on top.
### What does the proposed API look like?
Similar as done by @alexsasharegan
<!-- generated by vue-issues. DO NOT REMOVE --> | feature request | low | Major |
267,902,244 | react | RFC: Plan for custom element attributes/properties in React 19 | This is meant to address #7249. The doc outlines the pros and cons of various approaches React could use to handle attributes and properties on custom elements.
# TOC/Summary
- Background
- Proposals
* Option 1: Only set properties
+ Pros
- Easy to understand/implement
- Avoids conflict with future global attributes
- Takes advantage of custom element "upgrade"
- Custom elements treated like any other React component
+ Cons
- Possibly a breaking change
- Need ref to set attribute
- Not clear how server-side rendering would work
* Option 2: Properties-if-available
+ Pros
- Non-breaking change
+ Cons
- Developers need to understand the heuristic
- Falling back to attributes may conflict with future globals
* Option 3: Differentiate properties with a sigil
+ Pros
- Non-breaking change that developers can opt-in to
- Similar to how other libraries handle attributes/properties
- The system is explicit
+ Cons
- It’s new syntax
- Not clear how server-side rendering would work
* Option 4: Add an attributes object
+ Pros
- The system is explicit
- Extending syntax may also solve issues with event handling
+ Cons
- It’s new syntax
- It may be a breaking change
- It may be a larger change than any of the previous proposals
* Option 5: An API for consuming custom elements
+ Pros
- The system is explicit
- Non-breaking change
- Idiomatic to React
+ Cons
- Could be a lot of work for a complex component
- May bloat bundle size
- Config needs to keep pace with the component
# Background
When React tries to pass data to a custom element it always does so using HTML attributes.
```jsx
<x-foo bar={baz}> // same as setAttribute('bar', baz)
```
Because attributes must be serialized to strings, this approach creates problems when the data being passed is an object or array. In that scenario, we end up with something like:
```html
<x-foo bar="[object Object]">
```
The workaround for this is to use a `ref` to manually set the property.
```jsx
<x-foo ref={el => el.bar = baz}>
```
This workaround feels a bit unnecessary as the majority of custom elements being shipped today are written with libraries which automatically generate JavaScript properties that back all of their exposed attributes. And anyone hand-authoring a vanilla custom element is [encouraged to follow this practice](https://developers.google.com/web/fundamentals/web-components/best-practices#attributes-properties) as well. We'd like to ideally see runtime communication with custom elements in React use JavaScript properties by default.
This doc outlines a few proposals for how React could be updated to make this happen.
# Proposals
## Option 1: Only set properties
Rather than try to decide if a property or attribute should be set, React could *always* set properties on custom elements. React would **NOT** check to see if the property exists on the element beforehand.
**Example:**
```jsx
<x-foo bar={baz}>
```
The above code would result in React setting the `.bar` property of the `x-foo` element equal to the value of `baz`.
For camelCased property names, React could use the same style it uses today for properties like `tabIndex`.
```jsx
<x-foo squidInk={pasta}> // sets .squidInk = pasta
```
### Pros
#### Easy to understand/implement
This model is simple, explicit, and dovetails with React’s ["JavaScript-centric API to the DOM"](https://reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html#why-are-we-changing-this).
Any element created with libraries like Polymer or Skate will automatically generate properties to back their exposed attributes. These elements should all "just work" with the above approach. Developers hand-authoring vanilla components are encouraged to [back attributes with properties](https://developers.google.com/web/fundamentals/web-components/best-practices#always-accept-primitive-data-strings-numbers-booleans-as-either-attributes--or-properties) as that mirrors how *modern* (i.e. not oddballs like `<input>`) HTML5 elements (`<video>`, `<audio>`, etc.) have been implemented.
#### Avoids conflict with future global attributes
When React sets an attribute on a custom element there’s always the risk that a future version of HTML will ship a similarly named attribute and break things. This concern was [discussed with spec authors](https://github.com/w3c/webcomponents/issues/654) but there is no clear solution to the problem. Avoiding attributes entirely (except when a developer explicitly sets one using `ref`) may sidestep this issue until the browsers come up with a better solution.
#### Takes advantage of custom element "upgrade"
Custom elements can be lazily [upgraded](https://developers.google.com/web/fundamentals/web-components/customelements#upgrades) on the page and some PRPL patterns rely on this technique. During the upgrade process, a custom element can access the properties passed to it by React—even if those properties were set before the definition loaded—and use them to render initial state.
#### Custom elements treated like any other React component
When React components pass data to one another they already use properties. This would just make custom elements behave the same way.
### Cons
#### Possibly a breaking change
If a developer has been hand-authoring vanilla custom elements which only have an attributes API, then they will need to update their code or their app will break. The fix would be to use a `ref` to set the attribute (explained below).
#### Need ref to set attribute
By changing the behavior so properties are preferred, it means developers will need to use a `ref` in order to explicitly set an attribute on a custom element.
```jsx
<custom-element ref={el => el.setAttribute('my-attr', val)} />
```
This is just a reversal of the current behavior where developers need a `ref` in order to set a property. Since developers should rarely need to set attributes on custom elements, this seems like a reasonable trade-off.
#### Not clear how server-side rendering would work
It's not clear how this model would map to server-side rendering custom elements. React could assume that the properties map to similarly named attributes and attempt to set those on the server, but this is far from bulletproof and would possibly require a heuristic for things like camelCased properties -> dash-cased attributes.
## Option 2: Properties-if-available
At runtime React could attempt to detect if a property is present on a custom element. If the property is present React will use it, otherwise it will fallback to setting an attribute. This is the model Preact uses to deal with custom elements.
**Pseudocode implementation:**
```js
if (propName in element) {
element[propName] = value;
} else {
element.setAttribute(propName.toLowerCase(), value);
}
```
**Possible steps:**
* If an element has a defined property, React will use it.
* If an element has an undefined property, and React is trying to pass it primitive data (string/number/boolean), it will use an attribute.
* Alternative: Warn and don’t set.
* If an element has an undefined property, and React is trying to pass it an object/array it will set it as a property. This is because some-attr="[object Object]” is not useful.
* Alternative: Warn and don’t set.
* If the element is being rendered on the server, and React is trying to pass it a string/number/boolean, it will use an attribute.
* If the element is being rendered on the server, and React is trying to pass it a object/array, it will not do anything.
### Pros
#### Non-breaking change
It is possible to create a custom element that only uses attributes as its interface. This authoring style is **NOT** encouraged, but it may happen regardless. If a custom element author is relying on this behavior then this change would be non-breaking for them.
### Cons
#### Developers need to understand the heuristic
Developers might be confused when React sets an attribute instead of a property depending on how they’ve chosen to load their element.
#### Falling back to attributes may conflict with future globals
Sebastian [raised a concern](https://github.com/facebook/react/issues/10399#issuecomment-320847065) that using `in` to check for the existence of a property on a custom element might accidentally detect a property on the superclass (HTMLElement).
There are also other potential conflicts with global attributes [discussed previously](#avoids-conflict-with-future-global-attributes) in this doc.
## Option 3: Differentiate properties with a sigil
React could continue setting attributes on custom elements, but provide a sigil that developers could use to explicitly set properties instead. This is similar to [the approach used by Glimmer.js](https://www.emberjs.com/blog/2017/10/10/glimmer-progress-report.html#toc_component-attributes).
**Glimmer example:**
```html
<custom-img @src="corgi.jpg" @hiResSrc="[email protected]" width="100%">
```
In the above example, the @ sigil indicates that `src` and `hiResSrc` should pass data to the custom element using properties, and `width` should be serialized to an attribute string.
Because React components already pass data to one another using properties, there would be no need for them to use the sigil (although it would work if they did, it would just be redundant). Instead, it would primarily be used as an explicit instruction to pass data to a custom element using JavaScript properties.
*h/t to @developit of Preact for suggesting this approach :)*
### Pros
#### Non-breaking change that developers can opt-in to
All pre-existing React + custom element apps would continue to work exactly as they have. Developers could choose if they wanted to update their code to use the new sigil style.
#### Similar to how other libraries handle attributes/properties
Similar to Glimmer, both Angular and Vue use modifiers to differentiate between attributes and properties.
**Vue example:**
```html
<!-- Vue will serialize `foo` to an attribute string, and set `squid` using a JavaScript property -->
<custom-element :foo="bar” :squid.prop=”ink”>
```
**Angular example:**
```html
<!-- Angular will serialize `foo` to an attribute string, and set `squid` using a JavaScript property -->
<custom-element [attr.foo]="bar” [squid]=”ink”>
```
#### The system is explicit
Developers can tell React exactly what they want instead of relying on a heuristic like the [properties-if-available](#option-2--properties-if-available) approach.
### Cons
#### It’s new syntax
Developers need to be taught how to use it and it needs to be thoroughly tested to make sure it is backwards compatible.
#### Not clear how server-side rendering would work
Should the sigil switch to using a similarly named attribute?
## Option 4: Add an attributes object
React could add additional syntax which lets authors explicitly pass data as attributes. If developers do not use this attributes object, then their data will be passed using JavaScript properties.
**Example:**
```jsx
const bar = 'baz';
const hello = 'World';
const width = '100%';
const ReactElement = <Test
foo={bar} // uses JavaScript property
attrs={{ hello, width }} // serialized to attributes
/>;
```
This idea was [originally proposed](https://gist.github.com/treshugart/2fb509a8828adf7fee5245bfa2a54ba7) by @treshugart, author of Skate.js, and is implemented in the [val](https://github.com/skatejs/val) library.
### Pros
#### The system is explicit
Developers can tell React exactly what they want instead of relying on a heuristic like the [properties-if-available](#option-2--properties-if-available) approach.
#### Extending syntax may also solve issues with event handling
*Note: This is outside the scope of this document but maybe worth mentioning :)*
Issue [#7901](https://github.com/facebook/react/issues/7901) requests that React bypass its synthetic event system when declarative event handlers are added to custom elements. Because custom element event names are arbitrary strings, it means they can be capitalized in any fashion. To bypass the synthetic event system today will also mean needing to come up with a heuristic for mapping event names from JSX to `addEventListener`.
```js
// should this listen for: 'foobar', 'FooBar', or 'fooBar'?
onFooBar={handleFooBar}
```
However, if the syntax is extended to allow attributes it could also be extended to allow events as well:
```js
const bar = 'baz';
const hello = 'World';
const SquidChanged = e => console.log('yo');
const ReactElement = <Test
foo={bar}
attrs={{ hello }}
events={{ SquidChanged}} // addEventListener('SquidChanged', …)
/>;
```
In this model the variable name is used as the event name. No heuristic is needed.
### Cons
#### It’s new syntax
Developers need to be taught how to use it and it needs to be thoroughly tested to make sure it is backwards compatible.
#### It may be a breaking change
If any components already rely on properties named `attrs` or `events`, it could break them.
#### It may be a larger change than any of the previous proposals
For React 17 it may be easier to make an incremental change (like one of the previous proposals) and position this proposal as something to take under consideration for a later, bigger refactor.
## Option 5: An API for consuming custom elements
*This proposal was offered by @sophiebits and @gaearon from the React team*
React could create a new API for consuming custom elements that maps the element’s behavior with a configuration object.
**Pseudocode example:**
```js
const XFoo = ReactDOM.createCustomElementType({
element: ‘x-foo’,
‘my-attr’: // something that tells React what to do with it
someRichDataProp: // something that tells React what to do with it
});
```
The above code returns a proxy component, `XFoo` that knows how to pass data to a custom element depending on the configuration you provide. You would use this proxy component in your app instead of using the custom element directly.
**Example usage:**
```jsx
<XFoo someRichDataProp={...} />
```
### Pros
#### The system is explicit
Developers can tell React the exact behavior they want.
#### Non-breaking change
Developers can opt-in to using the object or continue using the current system.
#### Idiomatic to React
This change doesn’t require new JSX syntax, and feels more like other APIs in React. For example, PropTypes (even though it’s being moved into its own package) has a somewhat similar approach.
### Cons
#### Could be a lot of work for a complex component
Polymer’s [paper-input](https://www.webcomponents.org/element/PolymerElements/paper-input/elements/paper-input) element has 37 properties, so it would produce a very large config. If developers are using a lot of custom elements in their app, that may equal a lot of configs they need to write.
#### May bloat bundle size
Related to the above point, each custom element class now incurs the cost of its definition + its config object size.
*Note: I'm not 100% sure if this is true. Someone more familiar with the React build process could verify.*
#### Config needs to keep pace with the component
Every time the component does a minor version revision that adds a new property, the config will need to be updated as well. That’s not difficult, but it does add maintenance. Maybe if configs are generated from source this is less of a burden, but that may mean needing to create a new tool to generate configs for each web component library.
cc @sebmarkbage @gaearon @developit @treshugart @justinfagnani | Component: DOM,Type: Discussion | high | Minor |
267,903,960 | go | x/mobile: exp/sprite lacks point -> sprite mapping function? | ### What version of Go are you using (`go version`)?
1.9
### What did you do?
Played with the exp/sprite package
### What did you expect to see?
A mechanism for taking a point (e.g., from touch.Event) and identifying a sprite or list of sprites which contain that point.
### What did you see instead?
No mention of such a thing in the documentation or code. Seems like 50% of the functionality of a sprite engine?
| mobile | low | Minor |
267,914,135 | TypeScript | HTMLCollection should be string indexable | <!-- BUGS: Please use this template. -->
According to [MDN](https://developer.mozilla.org/en-US/docs/Web/API/HTMLCollection), HTMLCollection should be string indexable:
> HTMLCollection also exposes its members directly as properties by both name and index. HTML IDs may contain : and . as valid characters, which would necessitate using bracket notation for property access. Currently HTMLCollections does not recognize purely numeric IDs, which would cause conflict with the array-style access, though HTML5 does permit these.
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** master
**Code**
```ts
declare const elements: HTMLCollection;
elements['myId'] // implicit any error, where it should be the same type as elements[0].
```
| Suggestion,Domain: lib.d.ts,Awaiting More Feedback | low | Critical |
267,923,538 | opencv | cv::cuda::stream Lag | <!--
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)
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
##### Detailed description
I meet a case it's hard to understand,As needed, I need to be able to transplant all of the image enhancement operations to GPU.I want to use cuda::stream to accelerate,but I found that takes a lot of time to initialize a stream array, which implements many times stream in the later code(about 100s) while without implementing it takes 1s.I'm not sure if it's a bug of opencv.
clock_t t1 = clock();
cv::cuda::Stream st_i[10];
clock_t t2 = clock();
cout << 2 << " " << t2 << " " << t2 - t1 << endl;//it takes 100s
fun(st_i);
clock_t t1 = clock();
cv::cuda::Stream st_i[10];
clock_t t2 = clock();
cout << 2 << " " << t2 << " " << t2 - t1 << endl;//it takes 1s
//fun(st_i);
| priority: low,category: gpu/cuda (contrib),RFC | low | Critical |
267,927,231 | neovim | dynamic --headless, nvim_ui_builtin() | I would like to request a vimscript function or api function that should negate the effect of the `--headless` command line switch. Lets call it `nvim_launch_builtin_tui()` for now. I imagine something like this:
```vim
if My_condition()
call nvim_launch_builtin_tui()
" now it looks as if we did start nvim without --headless
else
" this text will go directly to stdout
echo "running headless"
endif'
```
and then one would do `nvim --headless -S above-file.vim`. Depending on the user function `My_condition` one would effectively end up in a "normal" TUI nvim instance or in a headless nvim.
If I can express the logic of the `My_condition()` vimscript function in the `my_condition` shell command/function I can currently do something similar with this shell script:
```sh
if my_condition; then
# this now *is* a nvim without --headless
nvim
else
# this text will go directly to stdout
nvim --headless --cmd 'echo "running headless"'
fi
```
| enhancement,ui,tui,ui-extensibility,remote | low | Minor |
267,947,353 | create-react-app | Add preload to script and link tags in production builds | I want to preload styles and main script. But the current config generates the .html without preload support. So is there any way to make that happens? | contributions: up for grabs!,tag: enhancement,difficulty: medium | medium | Critical |
267,963,512 | angular | NoopAnimationsModule animation callbacks NOT in right order | <!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.
ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->
## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>
## Current behavior
<!-- Describe how the issue manifests. -->
In BrowserAnimationsModule mode, animation callbacks order is correct. `(@flyInOut.start)` would be fired before `(@flyInOut.done)`.
But in NoopAnimationsModule mode, animation callbacks order is NOT correct. `(@flyInOut.done)` would be fired before `(@flyInOut.start)`.
You could see it in the demo's console message.
Demo is [here](https://plnkr.co/edit/vADlYPwJYHbQzGdwgegn?p=preview)
## Expected behavior
<!-- Describe what the desired behavior would be. -->
`(@flyInOut.start)` should be fired before `(@flyInOut.done)`.
## Minimal reproduction of the problem with instructions
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-->
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Environment
<pre><code>
Angular version: 4.4.6
<!-- Check whether this is still an issue in the most recent Angular version -->
Browser:
- [ X] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX <!-- run `node --version` -->
- Platform: <!-- Mac, Linux, Windows -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
| type: bug/fix,area: animations,freq2: medium,P4 | low | Critical |
267,974,919 | kubernetes | 100th percentile of e2e latency metrics are always zero | /kind bug
**What happened**:
```
Oct 24 10:01:56.171: INFO: Top latency metric: {Resource:pods Subresource: Verb:LIST Scope:namespace Latency:{Perc50:8.089ms Perc90:16.1ms Perc99:65.268ms Perc100:0s} Count:225}
Oct 24 10:01:56.171: INFO: Top latency metric: {Resource:pods Subresource: Verb:DELETE Scope:namespace Latency:{Perc50:5.031ms Perc90:9.949ms Perc99:49.37ms Perc100:0s} Count:6200}
Oct 24 10:01:56.171: INFO: Top latency metric: {Resource:nodes Subresource:status Verb:PATCH Scope:cluster Latency:{Perc50:2.977ms Perc90:6.228ms Perc99:30.601ms Perc100:0s} Count:6583}
Oct 24 10:01:56.171: INFO: Top latency metric: {Resource:endpoints Subresource: Verb:PUT Scope:namespace Latency:{Perc50:1.605ms Perc90:4.363ms Perc99:21.734ms Perc100:0s} Count:570}
Oct 24 10:01:56.171: INFO: Top latency metric: {Resource:nodes Subresource: Verb:LIST Scope:cluster Latency:{Perc50:11.345ms Perc90:17.721ms Perc99:21.563ms Perc100:0s} Count:86}
```
Note the **Perc100:0s** in each of the above.
**What you expected to happen**:
Either a useful number to shown (e.g. the max value across all the samples, or 99.9th percentile, in case 100th percentile's definition such that it's guaranteed to be zero).
Or the 100th percentile skipped altogether from the summary, since it's just noise.
**How to reproduce it (as minimally and precisely as possible)**:
`kubetest -v --up && kubetest -v --test '--test_args=--ginkgo.focus=\[Feature:Performance\]'`
**Anything else we need to know?**:
**Environment**:
- Kubernetes version (use `kubectl version`): master
- Cloud provider or hardware configuration: gce
@kubernetes/sig-scalability-bugs | kind/bug,sig/scalability,lifecycle/frozen | low | Critical |
267,977,259 | vscode | Have Shift+Tab remove whitespace within a line | Extracted from https://github.com/Microsoft/vscode/issues/32280#issuecomment-333843440
From @martinsuchan
---
Shift+Tab does not outdent. Tested in *.ps1 files. No idea if this has worked in previous versions, just noticed it now.
Edit it works when I'm on the start of the line, but not in between strings. In VS2017 it works even between strings. Not sure it this is native VS behavior or ReSharper, but I use it a lot.
- VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
- OS Version: Windows_NT x64 10.0.15063
- Extensions:
Kotlin|mat|1.3.0
csharp|ms-|1.12.1
PowerShell|ms-|1.4.3
java|red|0.11.0 | feature-request,editor-core | medium | Major |
268,014,467 | opencv | imwrite/imencode fails with image higher than 8192 pixels width JP2 (JPEG 2000) | When compressing an image higher than 8192 pixels (by any width) the function imwrite generates an access violation (while using JP2 (JPEG 2000) encoding).
First-chance exception at 0x000007FED04A97A8 (opencv_imgcodecs300.dll) in FTIImagesHelpers_TestUnit-x64.exe: 0xC0000005: Access violation writing location 0x0000000002218000.
I have looked at Jasper encoder and found the following definition in [opencv/jas_stream.h](https://github.com/opencv/opencv/blob/master/3rdparty/libjasper/jasper/jas_stream.h)
128: /* The default buffer size (for fully-buffered operation). */
129: #define JAS_STREAM_BUFSIZE 8192
Link : (https://github.com/opencv/opencv/blob/master/3rdparty/libjasper/jasper/jas_stream.h#L159)
I don't much time to investigate more, but this is probably linked to this exception.
Thanks for the fix,
Patrick | bug,priority: low,category: imgcodecs | low | Minor |
268,063,394 | vue | TypeScript: add Props type to component constructor | ### What problem does this feature solve?
It would be useful if we can infer Props type from component (`ExtendedVue`).
For example, we can write type safe wrapper of `CreateElement` with it (or improve interface of `CreateElement` directly).
```typescript
function renderComponent<Props>(
h: CreateElement,
component: ExtendedVue<Vue, {}, {}, {}, Props>,
data: VNodeData & { props: Partial<Props> },
children?: VNodeChildren): VNode {
return h(component, data, children);
}
const MyComponent = Vue.extend({
props: { foo: String },
render(h) { return h("div", this.foo) };
});
const Parent = Vue.extend({
render(h) {
return renderComponent(h, MyComponent, { props: { foo: 0 } }); // error: type of property 'foo' are imcompatible
}
});
```
### What does the proposed API look like?
Now, `ExtendedVue<Vue, {}, {}, {}, { foo: string }>` and `ExtendedVue<Vue, {}, {}, { foo: string }, {}>` generate same type.
This means we can't determine `Props` type from `ExtendedVue` object.
I think, easiest (and most reasonable) way to achieve this is adding types to `$props` and `$data`
```diff
- export type CombinedVueInstance<Instance extends Vue, Data, Methods, Computed, Props> = Instance & Data & Methods & Computed & Props;
+ export type CombinedVueInstance<Instance extends Vue, Data, Methods, Computed, Props> = Instance & Data & Methods & Computed & Props & { $data: Data, $props: Props };
```
<!-- generated by vue-issues. DO NOT REMOVE --> | improvement,typescript | low | Critical |
268,102,850 | go | os: Add example showing how to read data from stdin | A pretty common task, especially for new programmers, is to ask the user to type in some value at the command line and then have the program act on it. (think "interactive maze game", "determine if word is palindrome", etc). It would be nice if we had an example in the `os` package showing how to do this. | Documentation,help wanted,NeedsInvestigation | low | Minor |
268,116,773 | rust | Tails calls are not being emitted as such | The following rust code should get tail calls:
```rust
pub fn moo() -> String {
goo()
}
#[inline(never)]
pub fn goo() -> String {
"https://".to_string()
}
```
Instead we get:
```assembly
example::moo:
push rbp
mov rbp, rsp
push rbx
push rax
mov rbx, rdi
call example::goo@PLT
mov rax, rbx
add rsp, 8
pop rbx
pop rbp
ret
example::goo:
push rbp
mov rbp, rsp
push rbx
push rax
mov rbx, rdi
lea rsi, [rip + str.0]
mov edx, 8
call <alloc::string::String as core::convert::From<&'a str>>::from@PLT
mov rax, rbx
add rsp, 8
pop rbx
pop rbp
ret
str.0:
.ascii "https://"
``` | A-LLVM,T-compiler,C-bug | low | Minor |
268,164,854 | kubernetes | Increase test coverage for HA failure modes | Issues such as #47131 suggest our test coverage of failure modes for HA kubernetes configurations is insufficient.
This is a placeholder issue to review our existing test coverage, identify our most critical blind spots and propose a set of changes to improve our test coverage of HA failure modes.
The etcd team has written up a [summary of potential test cases](https://github.com/coreos/etcd/issues/8711)
cc @xiang90 | area/test,kind/cleanup,sig/api-machinery,sig/cluster-lifecycle,kind/feature,lifecycle/frozen | medium | Critical |
268,182,397 | rust | Compilation Error when Mixing Line and Block comment | I have written a [small program](https://play.rust-lang.org/?gist=fb8ae0872ee993a786443f3a9900a5ec&version=stable).
```rust
fn main() {
println!("Hello, one!");
//*
println!("Hello, two!");
//*/
println!("Hello, three!");
}
```
The above program compiles and runs successfully. But.
```rust
fn main() {
println!("Hello, one!");
/*
println!("Hello, two!");
//*/
println!("Hello, three!");
}
```
The above program does not compiles and produces this `error: unterminated block comment`.
But as you can see the block comment is terminated.
This is a small trick to toggle comment a large group of statements by addition and removal of a `/`.
C language, javascript and Rust Lang share the same type of commenting style ( `//` and `/* */` ).
This trick works in C lang ( I tried gcc and clang compiler) and javascript as well, but currently it is not working in Rust Lang.
| A-diagnostics,A-parser,T-compiler | low | Critical |
268,204,145 | TypeScript | Array.prototype.filter doesn't require callback to return | I dig a bit and found out in #5850 and subsequently in #7779 the signature of filter has been changed not to return a boolean, so that people could return a truthy value in the implementation of the filter.
While I undertand the _convenience_ in terms of ease of use, this as far as I observed puts developers at risk of simple bugs like the following:
```typescript
const even = [1,2,3].filter(x => {
x % 2 == 0
})
```
Notice the missing `return` statement means the function returns `undefined`, which translates to `false`, which filters all the items out. This applies also in the case of `noImplicitReturns` set to true, since the function return type is `any`, thus it could be a void function for what the compiler knows.
I believe TypeScript's job should be to put this kind of cases in check actually, so that things like truthy values (which sometimes aren't as obvious as we might think and introduce bugs we don't really understand) can be better taken care of.
One solution to make both parties happy would be to optionally support truthy values (maybe an extra compiler flag? Another `truthy` type to allow for more relaxed checking?) and reintroduce the original signature of filter. | Suggestion,Domain: lib.d.ts,Awaiting More Feedback | low | Critical |
268,221,520 | kubernetes | Control plane bootstrapping order AKA we need a run-level concept | ### Background:
We are adding extension mechanisms to the Kubernetes control plane, initializers and admission webhooks. If e.g. the webhooks are configured but not actually running in the cluster, then the cluster is broken until an administrator can fix it. To make it possible to avoid this situation, we're going to let the webhook be gated on a selector matching the labels on the namespace containing the item under consideration. This should make it possible to construct a set of labels on namespaces that will allow the namespaces hosting the critical webhooks to be operational when the webhooks aren't running. (I will add a link to the design when it is published.)
### What we need:
We're looking for documented best practices around this. We imagined building a "run level" system in labels on namespaces out of this. A complete solution should
* Cover how many run levels there are
* Cover what components go in which run level
* Analyze the functionality of the current controller-manager; it may need to be split into binaries or modes that are in different run levels
* Draw some inspiration from Brian's [layers doc](https://docs.google.com/document/d/1XkjVm4bOeiVkj-Xt1LgoGiqWsBfNozJ51dyI-ljzt1o/edit).
We think cluster lifecycle SIG is probably the best place for this to be worked out.
(This is from a meeting between myself, @cheftako, @deads2k, @smarterclayton, @liggitt, @caesarxuchao, and @jagosan. ) | area/controller-manager,sig/api-machinery,sig/cluster-lifecycle,kind/feature,area/admin,area/admission-control,priority/important-longterm,lifecycle/frozen | low | Critical |
268,258,563 | youtube-dl | Google Play Music support | ## 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 this: `[x]`)
- Use the *Preview* tab to see what your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.10.20*. 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.10.20**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through the [README](https://github.com/rg3/youtube-dl/blob/master/README.md), **most notably** the [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**):
This is based on the `right click` -> `share` -> `copy link` functionality of items in google play music.
- Single video: https://play.google.com/music/m/Tg5o46ybbyflzb3epfxzr22za64?t=Asian_Jake_Paul_feat_Boyinaband_-_Idubbbz
- Single video: https://play.google.com/music/m/Tli62dsrjbu4b3paiux5uzp5rxq?t=Thats_What_I_Like_-_Bruno_Mars
- Playlist: https://play.google.com/music/playlist/AMaBXykOn9WLvry7WvNVB-721RkJthw2YC4qCLUngsHdXNoOc4W52UzzTH6EEgZipurK_2GXTDWMN6GOvZAs_VKvlfL4vvYNCQ%3D%3D
- Album: https://play.google.com/music/m/Bkgg5do3ni6nyae3hvn6ngtia2e?t=Astro_Lounge_-_Smash_Mouth
Note that **youtube-dl does not support sites dedicated to [copyright infringement](https://github.com/rg3/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free)**. In order for site support request to be accepted all provided example, URLs should not violate any copyrights.
---
### Description of your *issue* suggested solution and other information
Site support for Google Play Music. Hopefully, audio-only services are welcome here. This does require a youtube red/GPM subscription to support non-user uploaded songs.
| geo-restricted,account-needed | low | Critical |
268,297,986 | TypeScript | No compile error for satisfying function signature of only one branch of union of two | <!-- 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 -->
<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:** What the playground uses today (October 25th)
**Code**
```ts
class Henk {
giveMe<T>(valueWhere: T & { henk: string }) {
}
}
class Piet {
giveMe<T>(valueWhere: T & { piet: number }) {
}
}
const henkOrPiet: Piet | Henk = null
henkOrPiet.giveMe({
henk: ''
})
```
**Expected behavior:**
I would expect a compile error, because `henkOrPiet.giveMe(...)` should accept only a `T` that matches both `T & { henk: string }` and `T & { piet: number }`, which should (ideally) be `{ henk: string, piet: number }`. Instead it compiles if we only satisfy the first.
**Apparently this has to do with the order in which `Henk` and `Piet` are defined, because if I switch them, `henkOrPiet.giveMe({ piet: 4 })` will compile.
**Actual behavior:**
No compile error. | Bug | low | Critical |
268,352,388 | pytorch | DataLoader "casting" non statndard objects to lists | **The Problem:**
Currently if you implement a nonstandard collate function which, for example returns a namedtuple and set pin_memory=True the namedtuple would be "casted" to a list by the following [code](https://github.com/pytorch/pytorch/blob/23a3f78988aeeaf3ca193ec0b03fd755ddbcdd49/torch/utils/data/dataloader.py#L116).
**Proposed Approach:**
Add another argument to the data loader constructor `DataLoader(batch_type_ctor=bt_ctor)`, where bt_ctor is a callable returning a constructed object. The result of pin_memory_batch should be passed to bt_ctor, and so should be the result of collate_fn if collate_fn is default_collate.
This approach might seem to add complexity to DataLoader since the connection between batch_type_ctor and collate_fn is non trivial if you don't read the code and may result in some code duplication.
For example if you implement a nonstandard collate_fn which returns a namedtuple then the return value of the collate_fn should be resupplied via batch_type_ctor if pin_memory is used.
But this approach seems to result in the most simple api and simple implementation.
**PS**
I would enjoy contributing to the project.
cc @SsnL | module: dataloader,triaged | low | Major |
268,358,392 | vscode | Git - Support to compare with arbitrary commit instead of the current HEAD | Currently numerous places (explorer, gutters, etc.) will display changes since the last commit. I believe it would be useful to allow to show the same annotations but related to a different branch or tag. I am currently working on a large pull request and find myself constantly running `git diff master` in a console. | feature-request,git | high | Critical |
268,382,699 | nvm | nvm uninstall... doesn't | - Operating system and version:
Ubuntu 14.04.3 LTS
- `nvm debug` output:
<details>
<!-- do not delete the following blank line -->
```
nvm --version: v0.31.0
$SHELL: /bin/bash
$HOME: /home/ubuntu
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: v6.11.5
which node: $NVM_DIR/versions/node/v6.11.5/bin/node
which iojs:
which npm: $NVM_DIR/versions/node/v6.11.5/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v6.11.5
npm root -g: $NVM_DIR/versions/node/v6.11.5/lib/node_modules
```
</details>
- `nvm ls` output:
<details>
<!-- do not delete the following blank line -->
```
v6.10.0
-> v6.11.5
system
default -> 6.11.5 (-> v6.11.5)
node -> stable (-> v6.11.5) (default)
stable -> 6.11 (-> v6.11.5) (default)
iojs -> N/A (default)
```
</details>
- How did you install `nvm`? (e.g. install script in readme, homebrew):
Pre-installed on Cloud 9.
- What steps did you perform?
```
$ nvm ls
v6.10.0
-> v6.11.5
system
default -> 6.11.5 (-> v6.11.5)
node -> stable (-> v6.11.5) (default)
stable -> 6.11 (-> v6.11.5) (default)
iojs -> N/A (default)
$ node -v
v6.11.5
$ nvm uninstall 6.10.0
Uninstalled node v6.10.0
$ nvm ls
v6.10.0
-> v6.11.5
system
default -> 6.11.5 (-> v6.11.5)
node -> stable (-> v6.11.5) (default)
stable -> 6.11 (-> v6.11.5) (default)
iojs -> N/A (default)
```
- What happened?
As above.
- What did you expect to happen?
I expected v6.10.0 to be uninstalled. It was reported as being deleted, but it wasn't.
- Is there anything in any of your profile files (`.bashrc`, `.bash_profile`, `.zshrc`, etc) that modifies the `PATH`?
No.
| uninstalling,bugs,pull request wanted | low | Critical |
268,481,772 | vue | Request: add v-model.lazy for components | ### What problem does this feature solve?
v-model for components already supports .trim and .number.
Lazy modifier support for components would make it more uniform across the platform.
### What does the proposed API look like?
The only change (backwards compatible) would be to add a new property to model definition:
```
model: {
prop: 'value',
event: 'input',
eventLazy: 'change'
}
```
<!-- generated by vue-issues. DO NOT REMOVE --> | feature request,has PR | medium | Critical |
268,486,228 | go | x/build/cmd/coordinator: staging environment doesn’t run current version | When running coordinator on the `go-dashboard-dev` project (our staging environment), it panics:
```
2017/10/25 17:24:24 Running in prod mode
panic: unknown builder "windows-386-gce"
goroutine 1 [running]:
main.stagingClusterBuilders(0x8)
/go/src/golang.org/x/build/cmd/coordinator/coordinator.go:396 +0x527
main.main()
/go/src/golang.org/x/build/cmd/coordinator/coordinator.go:318 +0xc50
```
This appears to be an issue with the environment and not the binary logic.
/cc @adams-sarah | Builders | low | Minor |
268,495,799 | go | cmd/compile: escape analysis loopdepth should reset when blocks end | Compiling the package below with compile -m shows that `new(int)` escapes to heap:
package p
func g() bool
//go:noescape
func h(*int)
func f() {
var p *int
if g() {
x:
goto x
} else {
p = new(int)
}
h(p)
}
After replacing `x: goto x` with `for {}`, it no longer escapes.
The issue is `x` is considered a looping label, so `(*EscState).esc` increments `e.loopdepth` when visiting it. However, loopdepth is never decremented again at the end of its enclosing block, so loopdepth is still incremented when visiting the `p = new(int)` assignment. | NeedsInvestigation,compiler/runtime | low | Major |
268,583,775 | go | cmd/dist: feature request: control over maximum number of CPUs used during build and test | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go version
go version devel +a31e0a4aac Sat Oct 21 11:32:53 2017 +0000 darwin/amd64
### Does this issue reproduce with the latest release?
Yes
### 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/sean/go"
GORACE=""
GOROOT="/Users/sean/goLang/go"
GOTOOLDIR="/Users/sean/goLang/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/75/tsmllrjr8xl81b0059bfyyd00000gs/T/go-build923680158=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
### What did you do?
Invoke `all.bash` after updating with `git fetch` and `git pull`.
### What did you expect to see?
No more than `$GOMAXPROCS` used during the build and testing process.
### What did you see instead?
Every processor available being utilized.
I really like to be able to limit the number of logical processors that the build and test process Go uses. The logical choice would be for the process to respect the environment variable `GOMAXPROCS`. The reason for wanting to impose this limit is to manage the amount of heat produced on my system during the process.
| NeedsInvestigation | low | Critical |
268,594,175 | rust | Specialization: cannot specialize an impl of a local trait when the default impl is a blanket impl bounded by a non-local trait | Found this in the Chucklefish AMA thread, [in the subthread](https://www.reddit.com/r/rust/comments/78bowa/hey_this_is_kyren_from_chucklefish_we_make_and/dow4br2/?context=3) about working around the lack of `Ord` on floats.
This code compiles:
```rust
#![feature(specialization)]
trait Foo { fn foo(&self); }
impl<T: Ord> Foo for T { default fn foo(&self) {} }
```
...But adding a specialized impl fails:
```rust
#![feature(specialization)]
trait Foo { fn foo(&self); }
impl<T: Ord> Foo for T { default fn foo(&self) {} }
impl Foo for f64 { fn foo(&self) {} }
```
Error message:
```
error[E0119]: conflicting implementations of trait `Foo` for type `f64`:
--> src/main.rs:7:1
|
5 | impl<T: Ord> Foo for T { default fn foo(&self) {} }
| --------------------------------------------------- first implementation here
6 |
7 | impl Foo for f64 { fn foo(&self) {} }
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `f64`
|
= note: upstream crates may add new impl of trait `std::cmp::Ord` for type `f64` in future versions
```
I'm afraid I don't see how the error message is relevant, or how an upstream impl of `Ord` for `f64` could conflict with this impl of the local `Foo` trait. Is this intended behavior?
The above is a reduction, here's the original example which raises a few other questions:
```rust
#![feature(specialization)]
pub trait OrdSubset: PartialOrd<Self> + PartialEq<Self> {
fn is_outside_order(&self) -> bool;
}
impl<T: Ord> OrdSubset for T {
default fn is_outside_order(&self) -> bool {
false
}
}
// I'd expect this to work
impl OrdSubset for f64 {
fn is_outside_order(&self) -> bool {
(*self).is_nan()
}
}
// not sure about this
impl<'a, A: OrdSubset> OrdSubset for &'a A {
fn is_outside_order(&self) -> bool {
(**self).is_outside_order()
}
}
/* The next two are basically the same as above, &mut and f64
impl<'a, A: OrdSubset> OrdSubset for &'a mut A {
fn is_outside_order(&self) -> bool {
(**self).is_outside_order()
}
}
impl OrdSubset for f32 {
fn is_outside_order(&self) -> bool {
(*self).is_nan()
}
}
*/
fn main() {
}
``` | T-compiler,A-specialization,C-feature-request,F-specialization | low | Critical |
268,616,696 | rust | ABI code generates oversize loads when returning with a cast | ## Meta
```
$ rustc --version
rustc 1.22.0-nightly (185cc5f26 2017-10-02)
```
## STR
```Rust
#![crate_type="rlib"]
#[no_mangle]
pub extern "C" fn foo(x: &(i8, i8, i8)) -> (i8, i8, i8) {
*x
}
```
target is x86_64-unknown-linux-gnu
## Expected Result
Code generated should not have UB
## Actual Result
The generated no-opt LLVM IR is:
```llvm
; ModuleID = 'cast.cgu-0.rs'
source_filename = "cast.cgu-0.rs"
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
; Function Attrs: nounwind uwtable
define i32 @foo({ i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* noalias readonly dereferenceable(3)) unnamed_addr #0 {
start:
%_3 = alloca { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }
; COMMENT MINE: %_0 has size 3
%_0 = alloca { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }
%1 = bitcast { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* %0 to i8*
%2 = bitcast { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* %_3 to i8*
call void @llvm.memcpy.p0i8.p0i8.i64(i8* %2, i8* %1, i64 3, i32 1, i1 false)
%3 = bitcast { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* %_3 to i8*
%4 = bitcast { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* %_0 to i8*
call void @llvm.memcpy.p0i8.p0i8.i64(i8* %4, i8* %3, i64 3, i32 1, i1 false)
; COMMENT MINE it is cast to an i32 here
%5 = bitcast { i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }* %_0 to i32*
; COMMENT MINE and then loaded as through it was size 4
%6 = load i32, i32* %5, align 1
ret i32 %6
}
; Function Attrs: argmemonly nounwind
declare void @llvm.memcpy.p0i8.p0i8.i64(i8* nocapture writeonly, i8* nocapture readonly, i64, i32, i1) #1
attributes #0 = { nounwind uwtable "probe-stack"="__rust_probestack" }
attributes #1 = { argmemonly nounwind }
```
This loads 4 bytes of an alloca of size 3. I couldn't trivially turn this to an end-to-end mis-code-generation (this can't be used to load from anything *but* the return pointer, so you can't do the standard "load at end of page" trick), but I can't see how can oversize loads can be anything *but* UB.
cc @eddyb - I *think* one solution would be to pad the return pointer alloca to always have enough space for the cast, aka:
```llvm
%_0_store = alloca {{ i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }, [1 x i8]}
%_0 = getelementptr inbounds {{ i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }, [1 x i8]}, {{ i8, [0 x i8], i8, [0 x i8], i8, [0 x i8] }, [1 x i8]}* %_0_store, i32 0, i32 1
```
I *think* the problem load is the one in https://github.com/rust-lang/rust/blob/e847f30f571e617990f7193665ab10127100e9df/src/librustc_trans/mir/block.rs#L247, but I can't be sure. | I-crash,A-LLVM,A-codegen,P-medium,T-compiler,C-bug | low | Major |
268,663,623 | go | encoding/base64: make encoding/base64.init() smaller and faster | ### What version of Go are you using (`go version`)?
go version go1.9 darwin/amd64
### Does this issue reproduce with the latest release?
yes
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/a/go"
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/m9/qtbxkp6s3p96fk54rln7qhj80000gp/T/go-build906670350=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
### What did you do?
review code from https://github.com/golang/go/blob/master/src/encoding/base64/base64.go#L96
### What did you expect to see?
var StdEncoding = Encoding{....}
### What did you see instead?
var StdEncoding = NewEncoding(encodeStd)
I think we can write a simple program to generate that Encoding golang code to Encoding{....} to make encoding/base64.init() smaller and faster.
In current golang compile `NewEncoding(encodeStd)` in global variable will compile code into encoding/base64.init().
`Encoding{....}` in global variable will compile that data to some place. | Performance,NeedsDecision | low | Critical |
268,694,251 | ant-design | Calendar Day View (extend dateCellRender) | ### What problem does this feature solve?
I think it would be helpful to also have a day view for the calendar, not just month or year, so we can see and manipulate the data from dataCellRender.
I'm trying to build a calendar where users can add items/events per hour(s) on a specific day or on multiple days (repeating event, full week let's say).
At this moment, from what I understand, you can not select, edit or view a full item from dataCellRender.
### What does the proposed API look like?
I do not have code samples, but I believe that the first thing it would be a day switch (maybe even week), just as it's the case for month/year.
With the day selected from the week/month view, when entering on the day view, the user would see rows for each hour. When you click an hour row, a modal or something like that would appear to add your data/content and it would be added into a list that contains the details for each hour.
Maybe the developers can choose how to insert & display the data/events per hour, but the actual really valuable thing it would be the view for a day, with selectable/manageable rows.
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | 🗣 Discussion,💡 Feature Request,Inactive,IssueHuntFest | medium | Critical |
268,706,991 | vue | <input> rerenders while changes affects only sibling elements | ### Version
2.5.2
### Reproduction link
[https://codepen.io/anon/pen/OxKqbL?editors=1111](https://codepen.io/anon/pen/OxKqbL?editors=1111)
### Steps to reproduce
Please open codepen example and type something into input
### What is expected?
Input should not lose focus
### What is actually happening?
input rerenders and loses focus
---
happens only if there is such conditional elements exists before and after input. Workaround is to use v-show instead of v-if in such cases.
<!-- generated by vue-issues. DO NOT REMOVE --> | bug,has workaround | medium | Major |
268,762,895 | react | React should recognize the `valueAsDate` property on DOM elements | The `valueAsDate` property on the ES6 definition of `HTMLInputElement` is not yet recognized by React. It should be, though.
The `valueAsDate` property relieves the pain of having to deal with both browsers that support HTML5 date inputs and those who don't; the former require the `value` property to be of the form `"YYYY-MM-DD"` and the latter require a nicely formatted date (e.g. `"MM/DD/YYYY"`) since the user will see exactly that. (React won't even allow that in conjunction with `type="date"`, though, and proclaim that the machine readable format should be used.)
The browsers that do support HTML5 date input (should) alternatively support the date being passed in through the `valueAsDate` property. If we use that, we can always put a nicely formatted date in the `value` property. Pain relieved! (And also React should allow any format in the `value` property in that case.)
As indicated above, browser support is still lacky at best, even with the most avant garde browsers. Hence this is not an urgent issue for React. It will get relevant, though, and is herein duly noted. | Type: Feature Request,Component: DOM | medium | Critical |
268,799,949 | three.js | Feature Suggestion : Sphere and Cylinder impostors shaders | Hi everyone,
I needed to be able to generate a very large number of spheres or cylinders. To do so, I've implemented a sphere impostor and a cylinder impostor shaders. Those shaders are generating pixel perfect objects with a reduced cost in memory.
This work has been developped thanks to this [scientific publication](http://reality.cs.ucl.ac.uk/projects/quadrics/pbg06.pdf)
I planned to add my work to ThreeJS but encountered problems with [Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=740560).
My shaders can now do the following :
- use true impostors by using gl_PointSize in vertex shader
- use some quads to emulate the sprites (Chrome issue fix)
I don't really know where it will be better to add this to ThreeJS. I can either add this feature by adding it to /examples or /src.
By adding it to /examples, we may need to fix uniform updates from onBeforeRender callback #9927. By adding it to /src, I will be able to directly code uniform updates on WebGLRenderer.
Because those two possibilities are totally different, is it possible to know what do you prefer before going further ?
Thanks ! | Suggestion | low | Critical |
268,892,697 | TypeScript | Use before declaration errors when using let statements within a switch case | **TypeScript Version:** 2.5.3
**Code**
```ts
function test(value) {
switch (value) {
case 1:
let foo = 10;
break;
case 2:
foo = 20; // Runtime ReferenceError: foo is not defined
break;
default:
}
}
test(2);
tsc --target es2015 (or higher)
```
**Expected behavior:**
This should probably produce a compile time error: `Block-scoped variable 'pen' used before its declaration.` on reference to foo in `case 2`.
**Actual behavior:**
The code type-checks and compiles fine, however, when running the es2015 transpiled output, you will receive a ReferenceError error at runtime. Ideally this type of error could be caught at compile time. | Bug | low | Critical |
268,954,673 | flutter | Add warning comment to Debug/Release.xcconfig files | We should add some warning boilerplate to the `Debug.xcconfig` and `Release.xcconfig` templates above the `#include "Generated.xcconfig"`. Something along the lines of:
```
// Generated.xcconfig is critical for Flutter builds and must be #included in all Flutter projects
#include "Generated.xcconfig"
``` | platform-ios,tool,t: xcode,P3,team-ios,triaged-ios | low | Critical |
268,955,317 | flutter | Flutter iOS builds should verify that Generated.xcconfig is included in the configuration | The `FLUTTER_*` variables defined in `Generated.xcconfig` are critical to successfully building for iOS. These are used in at least two key places:
1. To locate the the `xcode_backend.sh` file in the build run-script phase.
2. Within of `xcode_backend.sh`, for the various Flutter build settings.
We should detect that this file is (transitively) included from the build configuration's `.xcconfig`. One way to do this might just be to use `xcodebuild -showBuildSettings` and verify that all required variables are set. That avoids parsing Xcode project files and tying ourselves to a proprietary file format that could change. | platform-ios,tool,t: xcode,P3,team-ios,triaged-ios | low | Minor |
268,956,081 | flutter | Verify that xcode_backend.sh snapshot build phase is in Xcode project | We should verify that the two xcode_backend.sh run-script build phases are present in the Xcode project when building for iOS.
There are two phases where we use this script:
1. Dart snapshotting phase: `xcode_backend.sh build`
2. Framework architecture-thinning phase: `xcode_backend.sh thin`
For the time being, even a quick grep with a regex might be a reasonable heuristic for spotting this. | platform-ios,tool,t: xcode,P3,team-ios,triaged-ios | low | Minor |
268,957,499 | flutter | Emit an actionable error message if FLUTTER_* not defined in Xcode run-script phases | If `Generated.xcconfig` has not been `#include`d in the Xcode project configuration, `FLUTTER_ROOT` is undefined and Xcode will be unable to locate `xcode_backend.sh`. In the `flutter create` project template, we should include something similar to the following boilerplate above the execution of the `xcode_backend.sh` script:
```
if [ ! -f "$FLUTTER_ROOT"/packages/flutter_tools/bin/xcode_backend.sh" ]; then
echo "xcode_backend.sh not found"
echo "FLUTTER_ROOT is '$FLUTTER_ROOT'"
echo "Verify that your Xcode project is configured to use the Debug or Release profile"
exit 1
fi
``` | platform-ios,tool,t: xcode,P3,team-ios,triaged-ios | low | Critical |
268,986,747 | go | cmd/link: cannot cross compile a linux plugin on macOS | ### What version of Go are you using (`go version`)?
`go version go1.9.2 darwin/amd64`
### Does this issue reproduce with the latest release?
Yes
### What operating system and processor architecture are you using (`go env`)?
macOS Sierra 10.12.6 with latest Xcode 9.0.1 and Command Line Tools installed.
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/mmazurskiy/gopath"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.9.2/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.9.2/libexec/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/fh/7zp6kdcj3rgdd_7_nmw439_st0zyrt/T/go-build968645272=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
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"
```
### What did you do?
```go
package main
func Process() {
}
```
```console
GOOS=linux go build -buildmode=plugin -i -v -o build/bin/p1 github.com/atlassian/smith/cmd/p1
github.com/atlassian/smith/cmd/p1
# github.com/atlassian/smith/cmd/p1
warning: unable to find runtime/cgo.a
/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: unknown option: -z
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
```console
GOOS=linux go build -buildmode=plugin -i -v -ldflags="-v" -o build/bin/p1 github.com/atlassian/smith/cmd/p1
github.com/atlassian/smith/cmd/p1
# github.com/atlassian/smith/cmd/p1
HEADER = -H4 -T0x401000 -D0x0 -R0x1000
searching for runtime.a in $WORK/runtime.a
searching for runtime.a in /usr/local/Cellar/go/1.9.2/libexec/pkg/linux_amd64_dynlink/runtime.a
searching for runtime/cgo.a in $WORK/runtime/cgo.a
searching for runtime/cgo.a in /usr/local/Cellar/go/1.9.2/libexec/pkg/linux_amd64_dynlink/runtime/cgo.a
warning: unable to find runtime/cgo.a
0.00 deadcode
0.01 pclntab=165547 bytes, funcdata total 31135 bytes
0.01 dodata
0.01 dwarf
0.01 symsize = 0
0.02 reloc
0.02 asmb
0.02 codeblk
0.02 rodatblk
0.02 datblk
0.02 sym
0.02 symsize = 22368
0.02 symsize = 102000
0.02 dwarf
0.03 headr
0.03 host link: "clang" "-m64" "-gdwarf-2" "-Wl,-z,relro" "-shared" "-Wl,-znow" "-Wl,-znocopyreloc" "-o" "/var/folders/fh/7zp6kdcj3rgdd_7_nmw439_st0zyrt/T/go-build232503875/github.com/atlassian/smith/cmd/p1/_obj/exe/a.out.so" "-rdynamic" "-Qunused-arguments" "/var/folders/fh/7zp6kdcj3rgdd_7_nmw439_st0zyrt/T/go-link-110686925/go.o"
/usr/local/Cellar/go/1.9.2/libexec/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
ld: unknown option: -z
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
With explicit `CGO_ENABLED=1` I get:
```console
CGO_ENABLED=1 GOOS=linux go build -buildmode=plugin -i -v -ldflags="-v" -o build/bin/p1 github.com/atlassian/smith/cmd/p1
runtime/cgo
# runtime/cgo
ld: unknown option: --build-id=none
clang: error: linker command failed with exit code 1 (use -v to see invocation)
```
### What did you expect to see?
Successfully compiled plugin.
### What did you see instead?
Failures.
| Documentation,help wanted,NeedsFix,compiler/runtime | medium | Critical |
269,020,252 | rust | std::process::Command hangs if piped stdout buffer fills | There's an issue on Windows when using `Stdio::piped()` for `stdout`. If the child process writes too many bytes to stdout, it appears to get permanently blocked. A minimal test case (echo 2049 blank lines to cmd) is:
```rust
fn main() {
::std::process::Command::new("cmd")
.args(&["/c", "for /l %i in (1, 1, 2049) do @echo["])
.stdout(::std::process::Stdio::piped())
.status();
}
```
This hangs for me, but succeeds if only 2048 `echo`s are specified (which is why I'm suspecting it's related to filling the 4096-byte buffer). | E-help-wanted,C-bug,T-libs,A-process | low | Major |
269,124,639 | go | go/types: some facts are missing after an error | The type checker `go/types` records various facts about well-typed trees. For example, `Uses` records the relationship between each "using" (non-defining) identifier and the object to which it refers. However, when the type checker detects certain kinds of errors, it does not attempt to record facts about the errant subtree. This issue is a request that it work harder to record facts about errant subtrees.
By way of motivation, consider a tool for generating completions in an IDE. The input to such a tool is an unsaved editor buffer that usually fails to type-check, but the tool must nonetheless extract type information from the partial tree. Consider the following fragment of a Go program in an unsaved editor buffer, with the current insertion point marked by a caret:
```
func _() {
fmt.⁁
test := 0
}
```
A completion tool should generate a list of qualified identifiers such as fmt.Print, fmt.Fprintf, and so on. The parser ignores the newline and generates a tree containing `fmt.test := 0`, for which the type checker emits an error because each operand on the left of `:=` must be an identifier, not a qualified identifier (*ast.SelectorExpr). Having emitted the error, the type checker does not then visit the LHS subtree, so no `Uses` fact is recorded for `fmt`. As a result, the completion tool simply doesn't work on programs of this form, which are fairly common.
The fix in this specific example is for the type checker, once it has reported the error, to visit the left subtree for side effects (facts) only, and ignore the resulting type. The more general problem is to find any other places in the type checker that skip visitation of a subtree after an error. | NeedsInvestigation | low | Critical |
269,148,824 | react | createPortal: support option to stop propagation of events in React tree | **Do you want to request a *feature* or report a *bug*?**
Feature, but also a bug cause new API breaks old `unstable_rendersubtreeintocontainer`
**What is the current behavior?**
We cannot stop all events propagation from portal to its React tree ancestors. Our layers mechanism with modals/popovers completely broken. For example, we have a dropdown button. When we click on it, click opens popover. We also want to close this popover when clicking on same button. With createPortal, click inside popover fires click on button, and it's closing. We can use stopPropagation in this simple case. But we have tons of such cases, and we need use stopPropagation for all of them. Also, we cannot stop all events.
**What is the expected behavior?**
createPortal should have an option to stop synthetic events propagation through React tree without manually stopping every event. What do you think?
| Type: Feature Request,Component: DOM | high | Critical |
269,149,356 | angular | [Bug] strange behaviour with error handlers and events | ## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
</code></pre>
I am trying to implement a general error handler capable of showing me a message after each error and let the application continue, but when I catch errors coming from http, something breaks.
## Current behavior
<!-- Describe how the issue manifests. -->
After I catch and rethrow an error from an http request, the application stops updating templates and everything stops working. If the error does not come from an http request (but comes from an observable), the message error updates fine.
## Expected behavior
<!-- Describe what the desired behavior would be. -->
No matter what the source of the error, the application should update and respond without problems
## Minimal reproduction of the problem with instructions
https://plnkr.co/edit/9vLZqf?p=preview
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Environment
<pre><code>
Angular version: 4.4.5
<!-- Check whether this is still an issue in the most recent Angular version -->
Browser:
- [x] Chrome (desktop) version 61 (64 bit)
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: v8.6.0
- Platform: Windows 10 Creator Update
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
| freq1: low,area: common/http,type: use-case,P4 | low | Critical |
269,152,063 | opencv | Building against OpenBLAS complains about missing lapacke.h | ##### System information (version)
- OpenCV => 3.3.1
- Operating System / Platform => Ubuntu 16.04. (xenial)
##### Detailed description
It is not possible to build openCV against libOpenBLAS unless one also installs an additional LAPACK implementation that includes the ```lapacke.h``` header, e.g. ```liblapacke-dev``` on Ubuntu.
To me that does not look like the intended behavior and it might be explained by the fact, that OpenBLAS on Ubuntu only include ```cblas.h``` and ```f77blas.h``` as an header.
On the other hand ```OpenCVFindOpenBLAS.cmake``` does not check for ```lapacke.h```, so it might just be the case that ```ocv_lapack_check()``` is too strict when it comes to OpenBLAS.
@alalek You seem to have some experience with this. Any thoughts on this?
##### Steps to reproduce
If I only install ```libopenblas-dev```, I get the following cmake output once ```ocv_lapack_check()``` inside ```OpenCVFindLAPACK.cmake``` is called:
```
-- LAPACK(OpenBLAS): LAPACK_LIBRARIES: /usr/lib/libopenblas.so
CMake Warning at cmake/OpenCVFindLAPACK.cmake:29 (message):
LAPACK(OpenBLAS): CBLAS/LAPACK headers are not found in '/usr/include'
Call Stack (most recent call first):
cmake/OpenCVFindLAPACK.cmake:155 (ocv_lapack_check)
CMakeLists.txt:596 (include)
```
If I now install any LAPACK implementation that includes a ```lapacke.h```, e.g.: ```liblapacke-dev```, everything passes and OpenBLAS will be used:
```
-- LAPACK(OpenBLAS): LAPACK_LIBRARIES: /usr/lib/libopenblas.so
-- LAPACK(OpenBLAS): Support is enabled.
```
| category: build/install,category: 3rdparty | medium | Critical |
269,173,839 | ant-design | Add support for css grid layout | ### What problem does this feature solve?
CSS Grid Layout is now supported in every modern browser.
Usage of Grid Layout will allow for more flexibility and ease of use than flexbox.
### What does the proposed API look like?
grid layput can be achieved without modifying the current api
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | 🗣 Discussion,💡 Feature Request,Inactive,IssueHuntFest | low | Major |
269,183,034 | puppeteer | Support response interception | As of today, we have "request interception" that allows puppeteer to intercept and amend requests before they are sent to the server.
Similarly to this, it would be really handy to have "Response interception" that would allow to intercept and amend responses from server before they are delivered to the browser. | feature,chromium | high | Critical |
269,197,298 | kubernetes | Admission webhook configuration API should report if the configuration is honored | The webhook [api](https://github.com/kubernetes/kubernetes/blob/v1.9.0-alpha.1/staging/src/k8s.io/api/admissionregistration/v1alpha1/types.go#L152) doesn't tell if a webhook configuration is honored by the kube-apiserver or the extension apiservers. We should support it.
The problem is less critical for initializers, because users can observe objects's `metadata.initializers` to check if the initializer configuration is honored
cc @lavalamp @cheftako @kubernetes/sig-api-machinery-misc | sig/api-machinery,kind/feature,area/admission-control,priority/important-longterm,lifecycle/frozen | medium | Major |
269,217,388 | thefuck | Doesn't handle quotes and arguments with spaces well | v3.24 using Python 3.5.3, on Ubuntu 17.04, GNU bash 4.4.7(1)-release.
Using an alias, but with no alias is indifferent:
$ theheck "catt 'My File'"
cat My File [enter/↑/↓/ctrl+c]
$ theheck "catt My\ File"
cat My File [enter/↑/↓/ctrl+c]
$ theheck "ehco -e '\n'"
echo -e \n [enter/↑/↓/ctrl+c]
$ theheck "ehco -n $'\n'"
echo -n $\n [enter/↑/↓/ctrl+c]
The debug output is here: https://pastebin.com/GjXPpQbs | help wanted,hacktoberfest,HackIllinois | low | Critical |
269,256,024 | TypeScript | Try enforcing contextual type of array literal elements | Part of #19236
**Code**
```ts
const s1: string[] = ["x", 3, null as any];
const s2: string[] = ["x", 3];
```
**Expected behavior:**
* `s1` should be an error
* `s2` should have an error span on `3`
**Actual behavior:**
* `s1` is not an error
* `s2` has an error span on `s2`, which makes it impossible to figure out which element is wrong
Hypothesis: When checking a contextually-typed array literal, if an element type isn't assignable to the contextual type, issue an error on *that element* and return `unknownType` | Suggestion,Breaking Change,Committed | low | Critical |
269,280,994 | godot | Warn on connected functions without correct argument count | **Operating system or device, Godot version, GPU Model and driver (if graphics related):**
MacOS, Godot 3.0 alpha
**Issue description:**
<!-- What happened, and what was expected. -->
Connecting a signal to a function that doesn't have the correct number of arguments means that the function is never called (and I haven't seen any warnings in the debugger being called). Ideally, either the editor puts a lint warning up, or when attempting to call the function it complains that the function is invalid.
**Steps to reproduce:**
I connected a no-argument function to an animation_finished callback, which never is called. Can upload examples if needed!
**Link to minimal example project:**
<!-- Optional but very welcome. You can drag and drop a zip archive to upload it. -->
Happy to make one if it helps; might poke around to see if I can cobble something together!
| enhancement,topic:core,usability | low | Critical |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.