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 |
|---|---|---|---|---|---|---|
243,322,924 | pytorch | [Feature request] truncated normal initializer(sampler) | There has been a recent discussion on the discuss about truncated normal initializer [link](https://discuss.pytorch.org/t/implementing-truncated-normal-initializer/4778/15).
I have implemented one on my own, but the code is basically paraphrasing the tensorflow code, which I feel like may cause problem. If you feel good to add this, I can submit a PR once you tell me if it's ok to paraphrase or what's the alternative. | triaged,enhancement,module: initialization | low | Major |
243,420,183 | kubernetes | Orphaned objects can remain after their namespace is removed | If namespaced resources exist, but their associated namespace does not, the namespace lifecycle controller does not recognize/remedy this. | sig/api-machinery,area/admission-control,lifecycle/frozen | low | Major |
243,440,818 | opencv | DNN now predicts incorrectly in Universal Windows Platform build | - OpenCV => 3.3.0-rc
- Operating System / Platform =>Windows 10 - 64 bit
- Compiler =>Visual Studio 15 2017
- cmake => 3.8.2
##### Detailed description
Using the following [dnn code example](http://www.docs.opencv.org/trunk/d5/de7/tutorial_dnn_googlenet.html) with a win32 build of opencv `3.3.0-rc` produces correct predictions/classifications with both the Debug and Release binaries, and in x86_64 and x86 builds. However, running the same code in a Universal Windows Platform build (where the APPCONTAINER bit is set) using the same model (GoogLeNet), and input image (`space_shuttle.jpg` from the example in the wiki), produces different results. The version of the DNN module shipped with `3.2.0` opencv_contrib outputs correct probabilities in both win32 and UWP however. Below are the probability matrixes produced in 3.3.0-rc:
- Using the x86 and the x86_64 UWP Debug binaries, the probability matrix `prob` is filled with zeros and a class prediction of `342`:
>[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
- Using the x86 and the x86_64 UWP Release binaries, the probability matrix `prob` is filled with incorrect values, and a class prediction of `693`:
> [131, 227, 76, 58, 87, 222, 194, 58, 43, 119, 215, 58, 33, 191, 231, 58, 92, 3, 234, 58, 113, 151, 6, 59, 239, 148, 243, 58, 190, 124, 103, 59, 47, 20, 145, 59, 126, 70, 84, 59, 205, 235, 51, 59, 108, 31, 38, 59, 79, 62, 217, 58, 82, 61, 143, 58, 1, 244, 193, 58, 30, 183, 205, 58, 3, 252, 187, 58, 38, 42, 236, 58, 31, 154, 30, 59, 56, 228, 20, 59, 0, 132, 11, 59, 177, 168, 87, 59, 62, 181, 131, 59, 109, 50, 96, 59, 69, 43, 61, 59, 54, 132, 54, 59, 230, 94, 20, 59, 97, 200, 181, 58, 53, 105, 53, 59, 155, 11, 58, 59, 32, 242, 15, 59, 143, 25, 242, 58, 134, 232, 242, 58, 146, 199, 253, 58, 39, 25, 14, 59, 67, 250, 97, 59, 36, 74, 92, 59, 219, 39, 80, 59, 68, 211, 114, 59, 130, 73, 87, 59, 32, 73, 42, 59, 203, 202, 246, 58, 44, 249, 115, 59, 92, 191, 64, 59, 138, 206, 93, 59, 1, 2, 30, 59, 21, 176, 4, 59, 91, 28, 199, 58, 248, 125, 241, 58, 231, 197, 96, 58, 88, 252, 136, 58, 138, 41, 175, 58, 246, 229, 197, 58, 210, 194, 184, 58, 88, 112, 170, 58, 93, 164, 145, 58, 159, 224, 210, 58, 163, 16, 206, 58, 46, 62, 165, 58, 248, 11, 230, 58, 109, 236, 188, 58, 98, 56, 145, 58, 83, 37, 117, 58, 42, 226, 163, 58, 182, 127, 159, 58, 233, 22, 239, 58, 52, 172, 68, 59, 44, 219, 81, 59, 120, 77, 58, 59, 174, 222, 250, 58, 188, 191, 21, 59, 90, 91, 51, 59, 92, 164, 74, 59, 176, 88, 83, 59, 228, 216, 23, 59, 121, 61, 239, 58, 3, 240, 221, 58, 235, 233, 212, 58, 4, 221, 20, 59, 29, 1, 21, 59, 10, 122, 14, 59, 83, 107, 242, 58, 176, 242, 58, 59, 64, 157, 15, 59, 163, 174, 52, 59, 46, 211, 72, 59, 48, 165, 30, 59, 209, 98, 241, 58, 68, 241, 179, 58, 238, 109, 195, 58, 89, 31, 192, 58, 66, 90, 197, 58, 216, 85, 6, 59, 44, 1, 51, 59, 38, 201, 65, 59, 142, 245, 71, 59, 242, 19, 73, 59, 204, 81, 37, 59, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 167, 240, 43, 58, 137, 234, 135, 58, 216, 163, 107, 58, 99, 164, 74, 58, 220, 255, 48, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 194, 58, 49, 58, 27, 108, 57, 58, 61, 197, 45, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 79, 151, 17, 58, 157, 72, 42, 58, 131, 213, 35, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 209, 235, 21, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 141, 130, 42, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 126, 126, 33, 58, 215, 102, 9, 58, 161, 221, 39, 58, 174, 114, 37, 58, 215, 102, 9, 58, 215, 102, 9, 58, 122, 254, 18, 58, 53, 206, 127, 58, 101, 25, 109, 58, 219, 210, 61, 58, 238, 48, 25, 58, 125, 87, 11, 58, 73, 220, 14, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 16, 209, 39, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 112, 84, 32, 58, 193, 103, 63, 58, 211, 167, 127, 58, 218, 197, 52, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 84, 5, 36, 58, 244, 212, 46, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 215, 102, 9, 58, 247, 127, 68, 58, 56, 156, 150, 58, 33, 163, 181, 58, 245, 216, 138, 58, 19, 58, 91, 58, 115, 39, 32, 58]
- The win32 binaries, which predict correctly class `812` for space shuttle, has the following probability matrix:
> [221, 219, 55, 43, 225, 109, 178, 44, 24, 114, 131, 45, 174, 158, 99, 45, 21, 162, 159, 45, 58, 236, 167, 44, 13, 110, 207, 41, 151, 24, 130, 45, 63, 46, 61, 45, 128, 213, 191, 41, 208, 103, 75, 44, 244, 37, 183, 44, 48, 188, 222, 45, 44, 38, 139, 44, 15, 232, 246, 44, 143, 95, 32, 46, 87, 132, 57, 43, 229, 254, 139, 46, 189, 208, 76, 47, 94, 162, 150, 45, 10, 119, 248, 44, 152, 196, 3, 45, 216, 15, 246, 45, 212, 220, 225, 46, 7, 94, 200, 45, 13, 64, 60, 45, 32, 75, 212, 45, 193, 46, 11, 45, 112, 241, 210, 44, 135, 192, 109, 46, 89, 20, 225, 42, 176, 2, 252, 45, 68, 158, 29, 44, 248, 218, 136, 43, 183, 235, 6, 45, 141, 14, 101, 44, 137, 23, 85, 46, 129, 215, 234, 43, 13, 1, 110, 43, 78, 135, 42, 45, 143, 50, 200, 44, 90, 68, 200, 44, 56, 207, 161, 44, 150, 27, 243, 44, 202, 160, 59, 46, 131, 43, 88, 42, 30, 201, 93, 44, 190, 189, 241, 47, 223, 178, 254, 43, 35, 237, 82, 45, 190, 147, 72, 45, 206, 134, 226, 48, 13, 20, 67, 43, 228, 249, 136, 42, 224, 74, 143, 43, 253, 188, 45, 42, 44, 254, 127, 42, 116, 77, 148, 41, 70, 197, 128, 43, 34, 82, 196, 42, 64, 56, 223, 42, 238, 206, 50, 44, 61, 52, 125, 44, 215, 139, 119, 40, 10, 75, 176, 43, 7, 105, 117, 43, 11, 142, 113, 45, 213, 1, 90, 42, 156, 207, 52, 43, 214, 184, 52, 43, 1, 138, 34, 42, 74, 224, 183, 43, 94, 225, 143, 44, 1, 168, 211, 45, 12, 45, 150, 44, 14, 127, 220, 42, 135, 72, 188, 43, 219, 118, 149, 45, 14, 130, 12, 45, 230, 169, 174, 42, 28, 38, 96, 46, 203, 114, 100, 45, 73, 5, 130, 43, 104, 203, 209, 45, 149, 205, 28, 45, 29, 28, 175, 45, 2, 91, 129, 43, 55, 25, 75, 46, 42, 168, 218, 44, 59, 148, 148, 48, 36, 177, 178, 43, 18, 9, 236, 45, 150, 40, 2, 43, 32, 84, 133, 43, 12, 84, 211, 47, 36, 114, 12, 45, 101, 133, 203, 45, 234, 244, 139, 44, 58, 53, 12, 43, 235, 255, 161, 46, 85, 71, 47, 44, 26, 128, 172, 42, 92, 157, 18, 41, 115, 231, 47, 45, 44, 145, 92, 45, 42, 191, 159, 41, 107, 98, 34, 44, 208, 128, 133, 43, 196, 248, 145, 40, 90, 171, 25, 41, 60, 123, 189, 42, 86, 173, 179, 44, 156, 229, 189, 47, 174, 199, 181, 45, 100, 134, 34, 47, 182, 26, 81, 46, 246, 27, 65, 41, 152, 254, 16, 43, 157, 232, 203, 42, 147, 156, 11, 42, 229, 56, 34, 46, 57, 223, 123, 43, 217, 219, 4, 44, 194, 214, 14, 43, 176, 184, 81, 46, 123, 86, 173, 42, 81, 84, 156, 44, 52, 147, 157, 46, 223, 29, 83, 45, 141, 119, 168, 47, 222, 42, 132, 43, 100, 207, 199, 43, 250, 225, 140, 47, 107, 239, 129, 42, 10, 29, 114, 45, 10, 117, 160, 44, 246, 163, 99, 44, 132, 188, 185, 42, 125, 153, 245, 43, 212, 47, 39, 43, 214, 65, 206, 44, 23, 92, 19, 44, 23, 16, 48, 43, 154, 217, 97, 46, 238, 103, 218, 50, 10, 96, 187, 43, 199, 92, 19, 47, 252, 9, 86, 46, 133, 101, 154, 49, 231, 15, 50, 45, 102, 49, 15, 47, 57, 94, 28, 46, 4, 86, 88, 45, 145, 31, 136, 43, 106, 15, 143, 44, 94, 180, 225, 42, 200, 140, 139, 44, 206, 248, 13, 45, 54, 78, 144, 46, 236, 211, 100, 43, 86, 57, 15, 44, 193, 27, 34, 44, 135, 54, 17, 42, 235, 59, 33, 43, 155, 250, 6, 45, 71, 130, 218, 44, 120, 188, 22, 43, 155, 247, 148, 42, 76, 255, 138, 43, 141, 93, 167, 44, 131, 85, 33, 43, 153, 164, 148, 43, 192, 221, 169, 42, 64, 88, 146, 46, 182, 15, 21, 45, 103, 138, 208, 43, 185, 163, 12, 42, 185, 247, 64, 44, 17, 195, 141, 43, 17, 18, 134, 42, 126, 218, 31, 42, 239, 6, 133, 45, 5, 76, 181, 41, 63, 106, 158, 45, 114, 208, 129, 45, 177, 149, 162, 46, 156, 230, 17, 47, 167, 145, 148, 43, 201, 244, 55, 46, 98, 240, 55, 44, 69, 195, 83, 47, 52, 10, 200, 42, 188, 148, 60, 46, 248, 81, 119, 44, 90, 201, 101, 45, 116, 81, 20, 46, 17, 102, 34, 44, 96, 103, 10, 45, 242, 172, 205, 43, 237, 103, 129, 46, 205, 140, 2, 42, 91, 166, 136, 45, 26, 115, 171, 43, 241, 66, 191, 47, 28, 57, 65, 43, 52, 175, 228, 45, 36, 200, 75, 44, 175, 3, 138, 44, 4, 41, 178, 44, 25, 105, 157, 41, 253, 176, 207, 42, 108, 127, 160, 45, 211, 70, 66, 47, 97, 48, 141, 44, 239, 62, 203, 44, 152, 96, 80, 44, 229, 205, 102, 47, 29, 110, 205, 45, 158, 255, 35, 43, 5, 59, 204, 44, 221, 60, 128, 45, 214, 242, 136, 43, 31, 186, 23, 47, 39, 57, 38, 48, 54, 8, 98, 45, 124, 189, 164, 42, 218, 44, 49, 43, 100, 229, 72, 47, 190, 0, 103, 45, 64, 133, 102, 43, 23, 76, 67, 43, 114, 251, 188, 46, 67, 132, 198, 43, 231, 176, 240, 42, 151, 82, 210, 43, 222, 161, 105, 45, 114, 231, 20, 44, 32, 76, 236, 44, 43, 98, 236, 42, 144, 217, 197, 43, 244, 137, 196, 42, 230, 85, 118, 43, 178, 183, 56, 43, 167, 124, 13, 43, 60, 35, 199, 42, 56, 106, 62, 46, 190, 39, 1, 43, 82, 114, 201, 42, 158, 158, 104, 46, 47, 93, 139, 44]
I have verified that the model appears to be loading correctly by checking to make sure all the layers are the same in both the win32 and UWP builds. The input image / matrix is also identical in both win32 and UWP.
| bug,priority: low,platform: winrt/uwp,category: dnn,Hackathon | low | Critical |
243,447,195 | rust | rustbuild: rpath=false does not work, maybe because `build-script-build` bypasses `rustc.rs` wrapper | When experimenting with `rpath = false` in `config.toml` for rustbuild:
~~~~
Running `/rust.git/build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build`
error: failed to run custom build command for `pulldown-cmark v0.0.14`
process didn't exit successfully: `/rust.git/build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build` (exit code: 127)
--- stderr
/rust.git/build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build: error while loading shared libraries: libstd-61d72c8bf510b9ba.so: cannot open shared object file: No such file or directory
Build failed, waiting for other jobs to finish...
error: build failed
~~~~
Setting `LD_LIBRARY_PATH` seems to fix things:
~~~~
$ ./build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build
./build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build: error while loading shared libraries: libstd-61d72c8bf510b9ba.so: cannot open shared object file: No such file or directory
exit code 127
$ LD_LIBRARY_PATH=$PWD/build/x86_64-unknown-linux-gnu/stage2/lib/rustlib/x86_64-unknown-linux-gnu/lib/ ./build/x86_64-unknown-linux-gnu/stage1-rustc/release/build/pulldown-cmark-efa2881d679d19c8/build-script-build
exit code 0
~~~~
I had a poke around the code and it seems that rustbuild does make some attempt to set `LD_LIBRARY_PATH` [here](https://github.com/rust-lang/rust/blob/master/src/bootstrap/bin/rustc.rs#L93) however this is not affecting the `build-script-build` stuff apparently.
This is also causing `--no-fail env` to be ineffective for this case, presumably because `build-script-build` also bypasses rustbuild's `rustc.rs` wrapper (which is the only place that actually does anything in reaction to `--no-fail`.
| T-bootstrap,T-infra,C-bug | low | Critical |
243,471,127 | vscode | Regex Find can cause VS Code to Freeze | <!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->
<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: 1.14.1
- OS Version: Mac OSX Sierra 10.12.5 (16F73)
Steps to Reproduce:
1. `code --disable-extensions`
1. *File->New File*
1. Paste file from here: [snippets.py](https://raw.githubusercontent.com/GoogleCloudPlatform/python-docs-samples/master/auth/http-client/snippets.py) (it happens with other files, but this is a simple example)
1. Edit->Find `"""(.*?\n?)+?"""` regex
1. Try to remove the last `?` from the regex.
1. The editor freezes at this point
1. Code Helper goes to 100% CPU.
Result:
<!-- Launch with `code --disable-extensions` to check. -->
Reproduces without extensions: Yes | bug,upstream,freeze-slow-crash-leak,editor-find,upstream-issue-linked,terminal-find | high | Critical |
243,508,522 | flutter | complex_layout__start_up timeToFirstFrameMicros noise | The complex_layout__start_up timeToFirstFrameMicros benchmark is very noisy. We should run it multiple times and average the result.
cc @yjbanov | a: tests,team,framework,P3,team-framework,triaged-framework | low | Minor |
243,533,450 | go | runtime: sub optimal gc scalability | ### What version of Go are you using (`go version`)?
go version devel +4e9c86a Wed Jun 28 17:33:40 2017 +0000 linux/amd64
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/localdisk/itocar/gopath"
GORACE=""
GOROOT="/localdisk/itocar/golang"
GOTOOLDIR="/localdisk/itocar/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build633808214=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
### What did you do?
Run test/bench/garbage/tree2 on machine with 88 threads (2 sockets, 22 cores per socket, 2 threads per core) 2x Xeon E5-2699 v4
With following options:
./tree2 -cpus=88 -heapsize=1000000000 -cpuprofile=tree2.pprof
### What did you expect to see?
runtime.gcDrain taking insignificant amount of time
### What did you see instead?
runtime.gcDrain taking about half of all time:
```
Showing top 10 nodes out of 33
flat flat% sum% cum cum%
36.95s 45.03% 45.03% 75.98s 92.59% runtime.gcDrain /localdisk/itocar/golang/src/runtime/mgcmark.go
12.38s 15.09% 60.11% 12.38s 15.09% runtime.(*lfstack).pop /localdisk/itocar/golang/src/runtime/lfstack.go
7.51s 9.15% 69.27% 7.51s 9.15% runtime.greyobject /localdisk/itocar/golang/src/runtime/mgcmark.go
6.28s 7.65% 76.92% 19.49s 23.75% runtime.scanobject /localdisk/itocar/golang/src/runtime/mgcmark.go
4.54s 5.53% 82.45% 4.54s 5.53% runtime.(*lfstack).push /localdisk/itocar/golang/src/runtime/lfstack.go
```
Looking into runtime.gcDrain, I see that almost all time is spent on
35.66s 35.66s 924: if work.full == 0 {
I couldn't reproduce this behavior on machine with small number of cores.
Looking into cache miss profile shows that this is due to all cores updating head of work.full,
which causes all reads needed for check to miss cache.
| Performance,NeedsInvestigation,compiler/runtime,Scalability | low | Critical |
243,537,076 | angular | Height on auto only animates some of the time when the child height changes | ## I'm submitting a...
<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
</code></pre>
## Current behavior
There is a animation on a parent div with height auto.
There is a child element with a height in pixels.
When the child height changes, the parent should animate, but only does so once in a while.
## Expected behavior
The parent should animate its height every time
## Minimal reproduction of the problem with instructions
Plunker; http://plnkr.co/edit/pyfrnV?p=preview
Click the buttons a couple of times.
## What is the motivation / use case for changing the behavior?
Image gallery. In my use case the inner element is an image. Below the image are a couple of thumbs the user can click on to change the larger image above it. The images can be all kinds of different sizes, I want a very quick animation on the height when another image is chosen.
## Environment
<pre><code>
Angular version: 4.3.0
Browser:
- [X] Chrome (desktop) version 59
- [ ] 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
Others:
</code></pre>
| type: bug/fix,area: animations,freq2: medium,P4 | low | Critical |
243,553,193 | TypeScript | Properties of instances of anonymous classes have type <any> after an instanceof guard. | **TypeScript Version:** 2.4.1
**Code**
```ts
function create_my_class<T>() {
return class {
value: T;
constructor(
value: T
) {
this.value = value;
}
}
}
const MyClassWithNumber = create_my_class<number>();
const with_number = new MyClassWithNumber(234);
with_number.value = 10;
// with_number.value = "sdf"; // error, and rightly so
const something: any = with_number;
if(something instanceof MyClassWithNumber) {
something.value = 20;
something.value = "sdf"; // not an error, but should be one
}
```
**Expected behavior:**
The last assignment should be marked as a type error by TS.
**Actual behavior:**
The last assignment is not marked as error. This is somewhat surprising, as the line
```
with_number.value = "sdf";
```
is righteously reported as a type error by TS.
Not a huge issue, but prevented me from using a class factory.
| Bug | low | Critical |
243,604,668 | go | runtime: cannot run GO in Windows Server 2016 | [Issue]
When running go, a problem is encountered
```
C:\Users\Administrator>go
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0
runtime.asmstdcall(0x8fdd8, 0x40ee8d, 0x10f4000, 0x0, 0x100000044f980, 0x20, 0x11, 0x10f4000, 0x44f8c0, 0x10f0000, ...)
c:/go/src/runtime/sys_windows_amd64.s:60 +0x5e fp=0x8fd80 sp=0x8fd70
rax 0x0
rbx 0xa992c0
rcx 0xab4e20
rdi 0x204000
rsi 0x8fea0
rbp 0x8fe68
rsp 0x8fd68
r8 0x42e36e
r9 0x8fee0
r10 0xc042000000
r11 0xffffffff
r12 0x0
r13 0xffffffee
r14 0x0
r15 0x0
rip 0x0
rflags 0x10293
cs 0x33
fs 0x53
gs 0x2b
```
[Environment]
Version:
Go 1.8.3 From go1.8.3.windows-amd64.msi (newest).
And the issue resists in go1.9beta2 (newest unstable)
OS:
Microsoft Windows Server 2016 Datacenter
Hardware:
ASUSTek COMPUTER INC. Z10PA-D8 Series
Intel(R) Xeon(R) CPU E5-2620 v4 @2.10GHz, Intel(R) Xeon(R) CPU E5-2620 v4 @2.10GHz
128GB RAM
512GB SSD + 2TB HHD + 6TB HHD | OS-Windows,NeedsInvestigation | low | Major |
243,658,851 | opencv | Nightly test failure: Features2d_FLANN_Auto.regression | [Win32 without IPP](http://pullrequest.opencv.org/buildbot/builders/master_noICV-win32-vc14/builds/10160):
```
[ RUN ] Features2d_FLANN_Auto.regression
C:\build\master_noICV-win32-vc14\opencv\modules\ts\src\ts.cpp(541): error: Failed
failure reason: Bad accuracy
test case #-1
seed: ffffffffffffffff
-----------------------------------
LOG:
correct_perc = -1580547965
bad accuracy of Find
-----------------------------------
[ FAILED ] Features2d_FLANN_Auto.regression (52716 ms)
```
[20170728](http://pullrequest.opencv.org/buildbot/builders/master_noOCL-win32-vc14/builds/10169)
[20170820](http://pullrequest.opencv.org/buildbot/builders/master_noOCL-win32-vc14/builds/10195)
[20190523](http://pullrequest.opencv.org/buildbot/builders/master_noOCL_noICV-win32-vc14/builds/10812)
[20211120](http://pullrequest.opencv.org/buildbot/builders/master_noOCL_noICV_noSSE-win64-vc14/builds/11712)
[ARMv7 20190406](http://pullrequest.opencv.org/buildbot/builders/3_4_ARMv7-lin/builds/345) | bug,priority: normal,category: features2d | low | Critical |
243,683,150 | vscode | Add support for different fonts in the same file | Add support for choosing different font ligatures, than those within the `"editor.fontFamily"` selected font. For example, I would really like to use Operator Mono letters together with [Fira Code ligatures](https://github.com/tonsky/FiraCode). Atom-editor lets you do this.
A hacky workaround is with the `Custom CSS and JS Loader` extension. https://medium.com/@zamamohammed/multiple-fonts-alternative-to-operator-mono-in-vscode-7745b52120a0 @mohammedzamakhan
The `Custom CSS and JS Loader` extension makes vscode think it is corrupted, so I'd really prefer avoiding this hack.
Another custom workaround, which stopped working: https://gist.github.com/Mikeysax/e707e6971d991a7552017b4c00ef6a97
Semi-related: https://github.com/Microsoft/vscode/issues/192
Possibly helpful: https://github.com/tonsky/FiraCode/wiki/VS-Code-Instructions
| feature-request,font-rendering | medium | Critical |
243,793,805 | go | proposal: spec: panic on send/receive on nil channel | In Go 1 a send or receive operation on a nil channel blocks forever. This is by analogy with the select statement, in which a case with a nil channel is ignored. In particular, these four code snippets all block forever:
var c1 chan int
<-c1
var c2 chan int
select {
case <-c2:
}
var c3 chan int
c3 <- 1
var c4 chan int
select {
case c4 <- 1:
}
However, the fact is that send statements and receive expressions are not the same as select cases. They look different in the program and they are implemented differently. While it is nice to have a send or receive operation behave identically to a select statement with a single case that corresponds to that operation, it is not necessary, and I claim that changing that correspondence will not cause confusion.
I claim further that the fact that nil channels block forever is a point of confusion for new Go programmers. They must learn to call `make` to create a channel. When learning Go, it is easy to forget that. This then leads to confusion when programs simply block rather than reporting an error. Sample comments:
https://groups.google.com/d/msg/golang-nuts/QltQ0nd9HvE/mAb2K4UHWxUJ
https://groups.google.com/d/msg/golang-nuts/JFTymqVDBcs/E8GDJiQFBQAJ
http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/index.html#using_nil_ch
My final claim is that essentially no real programs rely on the current behavior for nil channels. I have no way to prove this claim, but in general blocking forever is a goroutine leak, and when people do want to block forever anyhow they use `select {}`.
Give the above, I recommend that for Go 2 we change this corner case and make send or receive operations on nil channels panic. To be clear I am not proposing that we change the behavior of select statements with nil channels, and I am not proposing that we change any aspect of the behavior for closed channels. In the above four code snippets, the first and third will panic, while the second and fourth will continue to behave as in Go 1. | LanguageChange,Proposal,LanguageChangeReview | medium | Critical |
243,814,485 | go | x/build/cmd/gopherbot, x/build/maintner: handle non-Go Github issue repos like gddo | https://github.com/golang/gddo has a separate issue tracker, but gopherbot ("CL X mentions this issue") can only comment on golang/go repos.
We might also need to update parseGithubRefs in maintner/github.go but at first look at that function makes it seem like it is capable of doing the right thing. | help wanted,Builders | low | Minor |
243,827,892 | flutter | NestedScrollView should assert when child scrollables are passed controllers | Since `NestedScrollView` wants to provide controllers to the children, it should throw a helpful assertion message if it detects that the children already have controllers.
## Steps to Reproduce
```dart
import 'package:flutter/material.dart';
class Demo extends StatefulWidget {
@override
DemoState createState() => new DemoState();
}
class DemoState extends State<Demo> with TickerProviderStateMixin {
ScrollController _scrollController = new ScrollController();
@override
Widget build(BuildContext context) {
ThemeData themeData = Theme.of(context);
return new ListView.builder(
controller: _scrollController,
itemBuilder: (BuildContext context, int index) {
return new Container(
child: new Text("Foo $index", style: themeData.textTheme.display2),
);
},
);
}
}
void main() {
runApp(new MaterialApp(
home: new NestedScrollView(
headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
return <Widget>[
new SliverAppBar(
title: new Text('NestedScrollView demo'),
expandedHeight: 300.0,
pinned: true,
),
];
},
body: new Material(
child: new Demo(),
),
)
));
}
```
The child ListView is scrollable instead of reducing the size of the SliverAppBar.
/cc @HansMuller | framework,f: scrolling,has reproducible steps,P3,found in release: 3.0,found in release: 3.1,team-framework,triaged-framework | low | Major |
243,844,438 | opencv | segmentation fault on Mac OSX when opening an .avi file | <!--
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)
Process: Python [7126]
Path: /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: 2.7.10 (2.7.10)
Code Type: X86-64 (Native)
Parent Process: zsh [5380]
Responsible: Python [7126]
User ID: 501
PlugIn Path: /usr/local/opt/ffmpeg/lib/libavutil.55.dylib
PlugIn Identifier: libavutil.55.dylib
PlugIn Version: ??? (0)
##### Detailed description
<!-- your description -->
#### Steps to reproduce
when I ran the code below:
```.python
import cv2 as cv
cap = cv.VideoCapture('my/path/to/the/video/file.avi')
```
I got ```[1] 7533 segmentation fault python```
<!-- to add code example fence it with triple backticks and optional file extension
```.cpp
// C++ code example
```
or attach as .txt or .zip file
--> | priority: low,platform: ios/osx,incomplete | low | Critical |
243,856,244 | go | runtime: before execve, set signal mask according to os/signal functions | If a program calls the os/signal functions `Notify` and `Ignore`, we should reflect those calls in the signal mask that we pass to child processes that we start using the os or os/exec packages. The code for this is in https://github.com/golang/go/issues/19196#issuecomment-315907446 . | NeedsFix,early-in-cycle,compiler/runtime | low | Minor |
243,907,763 | rust | Exact same bound check happens twice in loops when processing slices known to be of the same size | When compiling in release mode, it is possible to move most bound checks out of a loop when processing slices of the same size by asserting beforehand that they really are of the same size. A simple example of that would be:
```rust
fn process_slices(x: &[u32], y: &[u32], z: &mut [u32]) {
assert!(x.len() == y.len() && x.len() == z.len());
for i in 0..x.len() {
z[i] = x[i] + y[i];
}
}
```
Unfortunately there's a bound check that remains and is obviously redundant since exactly the same registers are compared at the top and at the bottom of the loop. The snippet of assembly for the inside loop of the above function looks like this:
```assembly
.LBB3_4:
cmpq %rax, %rsi
jae .LBB3_8
movl (%rdx,%rsi,4), %ecx
addl (%rdi,%rsi,4), %ecx
movl %ecx, (%r8,%rsi,4)
incq %rsi
cmpq %rax, %rsi
jb .LBB3_4
```
The LBB3_4 label isn't used anywhere else. It seems that it would make sense to move it two lines down since if we have %rsi < %rax then surely we cannot have %rsi >= %rax right afterwards.
The same also happens for more complicated loops.
[Here's a Rust Playground link for the example.](https://play.rust-lang.org/?gist=7efa9123866972f1c4195bc5973c8080&version=stable&mode=release)
| I-slow,C-enhancement | low | Minor |
244,031,424 | TypeScript | Unexpected TS4094 with the build parameter `declaration: true` | **TypeScript Version:** 2.4.1
**Code**
```ts
var Foo = class Foo {
private _message = "Hi";
hi() { return this._message; }
}
```
`tsc test.ts -t es2017 -d`
**Expected behavior:** `-d` should not cause this message: `test.ts(1,5): error TS4094: Property '_message' of exported class expression may not be private or protected.`
**Actual behavior:** It does.
There should at least be a suppression parameter to ignore this error. | Bug,Domain: Declaration Emit | medium | Critical |
244,033,784 | TypeScript | Unexpected type listing for `keyof T` on declaration file | **TypeScript Version:** 2.4.1
**Code**
```ts
var Foo = class Foo {
method<T extends keyof ElementTagNameMap>() {};
}
class Bar {
method<T extends keyof ElementTagNameMap>() {};
}
```
`tsc test.ts -t es2017 -d`
**Expected behavior:** Both should use `keyof ElementTagNameMap`
**Actual behavior:**
```ts
declare var Foo: {
new (): {
method<T extends "symbol" | "object" | "track" | "progress" | "a" | "applet" | "area" | "audio" | "base" | "basefont" | "blockquote" | "body" | "br" | "button" | "canvas" | "caption" | "col" | "colgroup" | "data" | "datalist" | "del" | "dir" | "div" | "dl" | "embed" | "fieldset" | "font" | "form" | "frame" | "frameset" | "h1" | "h2" | "h3" | "h4" | "h5" | "h6" | "head" | "hr" | "html" | "iframe" | "img" | "input" | "ins" | "isindex" | "label" | "legend" | "li" | "link" | "listing" | "map" | "marquee" | "menu" | "meta" | "meter" | "nextid" | "ol" | "optgroup" | "option" | "output" | "p" | "param" | "picture" | "pre" | "q" | "script" | "select" | "source" | "span" | "style" | "table" | "tbody" | "td" | "template" | "textarea" | "tfoot" | "th" | "thead" | "time" | "title" | "tr" | "ul" | "video" | "x-ms-webview" | "xmp" | "circle" | "defs" | "desc" | "ellipse" | "filter" | "g" | "image" | "line" | "marker" | "mask" | "path" | "metadata" | "pattern" | "polygon" | "polyline" | "rect" | "svg" | "stop" | "switch" | "tspan" | "text" | "use" | "view" | "abbr" | "acronym" | "address" | "article" | "aside" | "b" | "bdo" | "big" | "center" | "cite" | "clippath" | "code" | "dd" | "dfn" | "dt" | "em" | "feblend" | "fecolormatrix" | "fecomponenttransfer" | "fecomposite" | "feconvolvematrix" | "fediffuselighting" | "fedisplacementmap" | "fedistantlight" | "feflood" | "fefunca" | "fefuncb" | "fefuncg" | "fefuncr" | "fegaussianblur" | "feimage" | "femerge" | "femergenode" | "femorphology" | "feoffset" | "fepointlight" | "fespecularlighting" | "fespotlight" | "fetile" | "feturbulence" | "figcaption" | "figure" | "footer" | "foreignobject" | "header" | "hgroup" | "i" | "kbd" | "keygen" | "lineargradient" | "mark" | "nav" | "nobr" | "noframes" | "noscript" | "plaintext" | "radialgradient" | "rt" | "ruby" | "s" | "samp" | "section" | "small" | "strike" | "strong" | "sub" | "sup" | "textpath" | "tt" | "u" | "var" | "wbr">(): void;
};
};
declare class Bar {
method<T extends keyof ElementTagNameMap>(): void;
}
```
| Bug,Domain: Declaration Emit | low | Minor |
244,077,661 | rust | GDB pretty printers incorrectly print Path slices | Given this source file:
```rust
use std::path::Path;
fn main() {
let a = Path::new("a/b");
let b = a.parent().unwrap();
let c = "a/b";
let d = &c[..1];
let e = 3;
}
```
When compiled and run through `rust-gdb` it yields:
```
$ rustc -g foo.rs
$ cat cmds
break foo.rs:9
run
print *a
print *b
print c
print d
quit
$ rust-gdb ./foo -x cmds
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./foo...done.
Breakpoint 1 at 0x7c8c: file /home/alex/code/cargo/foo.rs, line 9.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Breakpoint 1, foo::main () at /home/alex/code/cargo/foo.rs:9
9 let e = 3;
$1 = Path = {inner = OsStr = {inner = Slice = {inner = 0x555555590c80 <str> "a/b"}}}
$2 = Path = {inner = OsStr = {inner = Slice = {inner = 0x555555590c80 <str> "a/b"}}}
$3 = "a/b"
$4 = "a"
A debugging session is active.
Inferior 1 [process 31595] will be killed.
Quit anyway? (y or n) [answered Y; input not from terminal]
```
The variable `b` was printed as `a/b` instead of `a`, although string slices appear to work! | A-debuginfo,T-compiler,C-bug | low | Critical |
244,123,656 | go | net: resolver should call res_init when resolv.conf changes | If you force the cgo resolver on **non-Debian-based** Linux with glibc <=2.25 (that is, any stable glibc as of this writing) and Go 1.8.3 (probably any released version), it's very easy to get into a state where all network connections fail even though the machine's network is up:
```go
package main
import (
"fmt"
"net"
"time"
)
func main() {
i := 1
for {
ip, err := net.LookupIP("google.com")
if err != nil {
fmt.Printf("%3d error: %s\n", i, err)
} else {
fmt.Printf("%3d success: %s\n", i, ip)
}
time.Sleep(1 * time.Second)
i++
}
}
```
1) Turn off / unplug the network connection on your machine.
2) Observe that NetworkManager or whatever daemon on your machine updates `/etc/resolv.conf` and removes the nameservers. (This does depend on what Linux distro / local network configuration you have, so if `/etc/resolv.conf` never changes you might need to repro this on a different machine.)
3) `GODEBUG=netdns=cgo go run test.go` (or whatever you named it) on the file above. The `GODEBUG` setting forces the net library to use the cgo resolver. Note that the pure-Go resolver does not exhibit this bug.
4) Watch it for a few seconds and observe a couple lookup errors (`no such host`). This is expected, because the network is down.
5) Without stopping the test program above, turn the network back on.
6) Confirm again that `/etc/resolv.conf` changes, and that your nameservers are back.
7) Keep watching the output of the test program.
BUG: The test program's DNS requests keep failing. Sometimes they fix themselves eventually, I'm not sure under exactly what conditions, but sometimes I never see them recover. It seems like if the test program ran with the network off for a minute, recovery is less likely than if you turned the network back on after a couple seconds.
This seems to be related to [a bug in glibc](https://sourceware.org/bugzilla/show_bug.cgi?id=984), where `/etc/resolv.conf` isn't checked for changes as often as it should be. It looks like glibc is going to ship a fix for this in their next release, though affected versions will still be around for years. Debian has patched this fix themselves for a long time ([this patch?](https://anonscm.debian.org/git/pkg-glibc/glibc.git/tree/debian/patches/any/local-dynamic-resolvconf.diff)), which is why I don't think the bug will repro on Debian-based distros. I've recently had to work around this issue [in application code](https://github.com/keybase/client/pull/7790), by calling `libc::res_init` manually. The Rust standard library [has started calling `res_init` after DNS failures](https://github.com/rust-lang/rust/issues/41570) by default, and that issue links to similar workarounds in other languages and applications.
> Seems like a lot of big programs have gone through the pain of re-discovering this issue. Here's Mozilla Firefox from [14 years ago](https://bugzilla.mozilla.org/show_bug.cgi?id=214538). And more recently, [Chef (and Ruby)](https://github.com/chef/chef/issues/2894).
I think the Go standard library should consider adding a workaround similar to what Rust has done. It looks like this was considered in https://github.com/golang/go/issues/10850, but it might not have been clear how common this bug is? The most painful case is a long-running Go process on a laptop where the WiFi comes and goes.
[Apologies if the "proposal" label was incorrect. This could be called a bugfix, depending on how you feel about it :) ] | help wanted,Proposal,Proposal-Accepted,NeedsFix,early-in-cycle | low | Critical |
244,129,858 | go | x/build/maintner: store Github pull request data | If we want this to be a tool for wider use (and I think it would be good to do that), we need to store Github pull request data for projects.
Furthermore, we currently get Git commits from Gerrit CL's, we'll need to allow people to specify Github as their primary Git upstream and fetch commits from Github instead of Gerrit, and also to read some of the metadata from Github's API that we currently parse out of the Git commits in Gerrit. | Builders | low | Major |
244,131,342 | go | x/build/maintner: load tokens from XDG config dir | Right now we hardcode the file to get Github tokens from as `$HOME/.github-issue-token`. If a user has XDG_CONFIG_HOME specified we should try to load tokens from there too. | Builders | low | Minor |
244,136,731 | go | x/build: rewrite Hg hashes in issue tracker | Some old issues refer to mercurial hashes in their issue tracker. There is a mapping at https://golang.org/change/XXXXX and the git commits have this data too (as a golang-hg header in the commit), but if you don't know that it can be hard to track down.
Instead of people having to know this, one could rewrite all codesite URLs in the issue tracker to become googlesource.com URLs.
example: https://github.com/golang/go/issues/2516 mentions http://code.google.com/p/go/source/detail?r=4e38cad33649. | help wanted,Builders,NeedsFix | low | Minor |
244,188,147 | vscode | Support large documents in extension host | - VSCode Version: 1.14.1
- OS Version: Windows 7 and Windows 10, likely all OSes
When editing documents with very long lines, such as lines containing data-URIs, the property `vscode.window.activeTextEditor` will be `undefined` when it should be defined.
Steps to reproduce:
1. Create a new (blank) VSCode extension, and add this command to `extension.ts`:
```
'use strict';
import * as vscode from 'vscode';
export function activate(context: vscode.ExtensionContext) {
let disposable = vscode.commands.registerCommand('bigDocTest.runDocTest', () => {
let hasActiveTextEditor = (vscode.window.activeTextEditor !== undefined);
if (hasActiveTextEditor) {
vscode.window.showInformationMessage('Success, activeTextEditor is defined.');
} else {
vscode.window.showErrorMessage('Oops, activeTextEditor is not defined.');
}
});
context.subscriptions.push(disposable);
}
export function deactivate() {
}
```
2. Launch this extension, load any normal text file, and run this command, you see the "Success, activeTextEditor is defined" information message appear.
3. But, try loading a file with a very long line contained inside it, such as this one: [MetalRoughSpheres.gltf](https://raw.githubusercontent.com/KhronosGroup/glTF-Sample-Models/9ba6ae1352c8b59f684a11858b152615026660a4/2.0/MetalRoughSpheres/glTF-Embedded/MetalRoughSpheres.gltf). This file has long lines due to the use of embedded data URIs in the file. If you run the above sample extension while editing this file, you see "Oops, activeTextEditor is not defined."
This makes it difficult for VSCode extensions to work with such files. I'm the lead dev of the GLTF extension for VSCode, and this prevents my extension from running on GLTF files that embed large images as data URIs. | feature-request,api,editor-textbuffer | high | Critical |
244,190,665 | TypeScript | Uncaught compiler error: Block-scoped variable from import used before its declaration. | <!-- 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 -->
**TypeScript Version:** 2.4.0 / nightly (2.5.0-dev.201xxxxx)
**Code**
Input Typescript
```ts
namespace A {
export namespace B {
export class C {
constructor()
{
console.log("Hello World");
}
}
}
}
import myA_B = myA.B;
import myA = A;
new myA_B.C();
```
Output JavaScript from tsc
```js
var A;
(function (A) {
var B;
(function (B) {
var C = (function () {
function C() {
console.log("Hello World");
}
return C;
}());
B.C = C;
})(B = A.B || (A.B = {}));
})(A || (A = {}));
var myA_B = myA.B;
var myA = A;
new myA_B.C();
```
**Expected behavior:**
Expected the typescript compiler error `Block-scoped variable 'myA' used before its declaration.`
**Actual behavior:**
Runtime error of `Uncaught TypeError: Cannot read property 'B' of undefined`
**Comments**
The typescript compiler will catch this if I use `const` or `let` keywords instead, so I expected the same error handling for `import` in this case.
My team prefers using `import` over `const` or `let` when we can for performance of not pulling in javascript code from external files when we are only referencing types.
| Bug | low | Critical |
244,199,321 | rust | pthread_get_stacksize_np returns incorrect values for the main thread on OS X 10.9 | See:
https://github.com/robovm/robovm/issues/274
https://groups.google.com/forum/#!topic/address-sanitizer/7_abqFZ5wXw
http://mail.openjdk.java.net/pipermail/hotspot-dev/2013-October/011388.html
pthread_get_stacksize_np returns 512KB for the main thread instead of the 8MB that it's supposed to. This causes us to allocate our guard page in the middle of the stack. | P-medium,T-libs-api,C-bug,A-stack-probe | low | Major |
244,200,947 | go | encoding/json: unmarshal into slice reuses element data between len and cap | ### What version of Go are you using (`go version`)?
go1.8
### What operating system and processor architecture are you using (`go env`)?
GOOS=nacl
GOARCH=amd64p32
### What did you do?
https://play.golang.org/p/lbYUhgOe--
### What did you expect to see?
According to the [json Unmarshal docs](https://golang.org/pkg/encoding/json/#Unmarshal), Unmarshal resets the slice length to zero and then appends each element to the slice.
### What did you see instead?
Instead Unmarshal resets the slice length to zero and then modifies the elements of the underlying slice.
| NeedsFix | medium | Major |
244,222,321 | react-native | Oppo A77 - Some texts gets cut-off | ### Environment
1. `react-native -v`: 0.34 through 0.59
2. `node -v`:4.4.7
3. `npm -v`: 4.5.0
4. `yarn --version`<!-- (if you use Yarn) -->:
- Target Platform: Android
- Development Operating System: Windows
- Build tools: The issue is specific to Oppo A77 model. Note that upgrading to latest react-native version is not an option now due to breaking changes and time constraints
### Steps to Reproduce
There's no necessary steps to produce these bug. You just have to run the app either in dev or production
### Expected Behavior
<!--
How did you expect your project to behave?
It’s fine if you’re not sure your understanding is correct.
Just write down what you thought would happen.
-->
Texts should not be cut-off
### Actual Behavior
<!--
Did something go wrong?
Is something broken, or not behaving as you expected?
Describe this section in detail, and attach screenshots if possible.
Don't just say "it doesn't work"!
-->
Some texts are cut-off as shown below. These cut-off issue doesnt occur in iphone and other phone models except Oppo A77
Screenshots:
Those screenshots are just few of the texts that are cut-off
<!--
Please share a project that reproduces the issue.
There are two ways to do it:
* Create a new app using https://snack.expo.io/ and try to reproduce the issue in it.
This is useful if you roughly know where the problem is, or can’t share the real code.
* Or, copy your app and remove things until you’re left with the minimal reproducible demo.
This is useful for finding the root cause. You may then optionally create a Snack.
This is a good guide to creating bug demos: https://stackoverflow.com/help/mcve
Once you’re done, copy and paste the link to the Snack or a public GitHub repository below:
-->
Sorry i can't provide a link to the project
<!--
What happens if you skip this step?
Someone will read your bug report, and maybe will be able to help you,
but it’s unlikely that it will get much attention from the team. Eventually,
the issue will likely get closed in favor of issues that have reproducible demos.
Please remember that:
* Issues without reproducible demos have a very low priority.
* The person fixing the bug would have to do that anyway. Please be respectful of their time.
* You might figure out the issues yourself as you work on extracting it.
Thanks for helping us help you!
-->
| Help Wanted :octocat:,Platform: Android,Bug | high | Critical |
244,262,369 | opencv | A problem about normalizeBlockHistogram() used to compute HOG descriptor | ##### System information (version)
- OpenCV => 2.2
##### Detailed description
when doing the first normalization of block histogram, the scale coefficient is computed as `float scale = 1.f/(std::sqrt(sum)+sz*0.1f)`, after the hysteresis thresholding and when doing the renormalization, the scale coefficient is computed as `scale = 1.f/(std::sqrt(sum)+1e-3f)` .
`1e-3f` is used to avoid division by zero, but why `sz*0.1f` is added when doing the first normalization? is it a sloppy or something I misunderstand? | category: objdetect,RFC | low | Minor |
244,370,929 | opencv | problem with linux Raspberry Pi,cv::directory | <!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).
This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->
##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->
- OpenCV => :grey_question:2.4.13
- Operating System / Platform => :grey_question: linux Raspberry Pi
- Compiler => :grey_question:g++ cmake
##### Detailed description
<!-- your description -->i use the cv::directory,GetListFolders,compile success,but i find the GetListFolders doesnt work,the size of vector i get is zero,when i do it in vs2015 in windows10,it works,which makes me really confuse
##### Steps to reproduce
<!-- to add code example fence it with triple backticks and optional file extension
```.cpp
// C++ code example
```
or attach as .txt or .zip file
-->cv::Directory images_Dir;
std::vector<std::string> images_Sub_Dirs = images_Dir.GetListFolders("/home/pi/images");
std::cout << "size:" << images_Sub_Dirs.size() << std::endl; | bug,priority: low,affected: 2.4 | low | Critical |
244,411,837 | vscode | [html] provide rename for embedded JavaScript | <!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->
<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: v1.14.1
- OS Version: macOS Sierra v10.12.6
- Reproduces without extensions: Yes
Steps to Reproduce:
1. Create these two files:
`my-custom-element.js`
```javascript
class MyCustomElement extends HTMLElement {
static get is() {
return 'my-custom-element';
}
}
customElements.define(MyCustomElement.is, MyCustomElement);
```
`my-custom-element.html`
```html
<script>
class MyCustomElement extends HTMLElement {
static get is() {
return 'my-custom-element';
}
}
customElements.define(MyCustomElement.is, MyCustomElement);
</script>
```
2. Try the Rename Refactoring with `F2` in both files:
<img width="514" alt="screen shot 2017-07-20 at 17 48 44" src="https://user-images.githubusercontent.com/1007051/28426567-cabae566-6d73-11e7-99e9-d69cce38a617.png">
<img width="535" alt="screen shot 2017-07-20 at 17 48 57" src="https://user-images.githubusercontent.com/1007051/28426573-cfe49c76-6d73-11e7-9e64-573b3a8a0a83.png">
With the same code, the "Rename Refactoring" doesn't work in HTML language. | help wanted,feature-request,javascript,html,keep | low | Major |
244,432,895 | rust | Stabilize -Zunpretty=expanded | `--pretty=expanded` is an incredibly useful debugging tool for macros. The change in rustc 1.19 to stop supporting unstable command-line options on the stable/beta compilers makes it all the more important to stabilize unstable options that people use, and this seems like it easily qualifies.
Much like `--emit mir`, this should not make any commitments about the *output*, only that the option should continue to exist. In particular, I'd even suggest making it explicitly clear that there's no commitment for the output to *compile*. | A-pretty,T-compiler,C-feature-request | medium | Critical |
244,448,875 | kubernetes | RFE: Policy on versioning e2e tests | **FEATURE REQUEST**:
Objective: Ensure a newer build of e2e tests can run a the tests on older clusters without having failures, and ensure upgrade tests don't test deprecated features.
Currently if a new feature adds coverage to the e2es there is no version information that denotes that this feature is new and may not work on an older version. We should ensure that the e2es in question check the server version and make certain >= to the version it was introduced in.
Also on a similar note we should cherry-pick a check of <= on issues where we know features are going to be deprecated.
This has caused a bunch of consternation on upgrade tests and has wasted copious amounts of time. It should be the sig-leads responsibility to ensure that the tests are in order prior to code freeze for a given cycle.
/kind feature
/cc @kubernetes/sig-testing-feature-requests @kubernetes/sig-release-feature-requests
| priority/awaiting-more-evidence,kind/feature,sig/testing,sig/release,lifecycle/frozen | low | Critical |
244,459,059 | vscode | Git - Support interactive rebase | Since it is typical for projects like Code and others to have PRs with a single command
for brevity and cleanliness, this feature would be really helpful to not have to go into the
terminal.
Willing to do a PR... | help wanted,feature-request,git | medium | Critical |
244,467,389 | rust | core::fmt fails to optimize on arm-none-eabi | While generating code for an Cortex-M0 I noticed that using core::fmt to generate printable output generates extremely bloated code, even when just using a plain string as format.
According to @rkruppe on IRC this is most likely due to a missed elimination of dead code by LTO.
A stripped down example can be found here:
https://gist.github.com/anonymous/7cfc8b881fcb8fdc792428dd772502cb
The generated assembly is here:
https://gist.github.com/anonymous/9cfa48e53e3b1c8ba1ddb69f8ae3ea3b
I also have an example (serial_slow_helloworld) in this repo https://github.com/therealprof/stm32f042.git . `xargo build --release --examples` will create a binary demonstrating the problem.
This happens for me with:
```
rustc 1.20.0-nightly (8f1339af2 2017-07-16)
binary: rustc
commit-hash: 8f1339af2e5d1b33ec9ee3c8a3c531bcd61770fc
commit-date: 2017-07-16
host: x86_64-apple-darwin
release: 1.20.0-nightly
LLVM version: 4.0
``` | I-slow,C-enhancement,T-libs-api,T-compiler,WG-embedded,I-heavy | low | Major |
244,533,026 | vscode | Can I put the extensionsGallery on my vscode fork? | By default the https://github.com/Microsoft/vscode does not come with key:
"extensionsGallery": {
"serviceUrl": "",
"cacheUrl": "",
"itemUrl": ""
}
on its https://github.com/Microsoft/vscode/blob/master/product.json file. That entry is required to install extensions from the marketplace as showed on:
1. https://stackoverflow.com/questions/37143536/no-extensions-found-when-running-visual-studio-code-from-source
Also there are commits, where their developer putted the key.
But sequentially removed it justifying:
> Revert inadvertant change to product.json
Why they are removing it? Seems they are using it while developing, as we may see he let slip the line to the upper stream. Can I put it on my fork? Or I can only use it locally as they seem to be doing?
___
Related issues:
1. https://github.com/Microsoft/vscode/issues/60 Command "Extensions: Install Extension" missing when running vscode from source
1. https://github.com/Microsoft/vscode/issues/2647 Command "Extensions: Install Extension" missing when running vscode from source
1. https://github.com/Microsoft/vscode/issues/28253 Can't see extensions or load via command line
1. https://github.com/Microsoft/vscode/issues/23831 How do I enable extensions in the extensions dir in OSS Dev mode
1. https://github.com/Microsoft/vscode-wiki/pull/30 Add marketplace extension installation details
| extensions,under-discussion,license | high | Critical |
244,541,652 | kubernetes | kubectl in-cluster mode conflicts with --request-timeout | /kind bug
**What happened**:
From a container running inside of a cluster:
```
# kubectl get po --request-timeout=11s
The connection to the server localhost:8080 was refused - did you specify the right host or port?
```
**What you expected to happen**:
```
# kubectl get po --request-timeout=11s
...long list of pods here...
```
**How to reproduce it (as minimally and precisely as possible)**:
- Run a container with kubectl installed (I used an Ubuntu container)
- `kubectl get po` <- this works
- `kubectl get po --request-timeout=11s` <- this fails
**Anything else we need to know?**:
Looking through the logs -v=8, it looks like --request-timeout bypasses the part where it realizes that in-cluster mode is enabled.
**Environment**:
- Kubernetes version (use `kubectl version`): I tested v.1.6.3 through v1.7.1
- Cloud provider or hardware configuration**: Parallels hypervisor
- OS (e.g. from /etc/os-release):
```
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
```
- Kernel (e.g. `uname -a`): Linux ubuntu 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
- Install tools: kubeadm
- Others:
| kind/bug,area/kubectl,sig/cli,lifecycle/frozen | medium | Critical |
244,566,421 | go | x/text: requires explicit (old) version of icu library accidentally | ### What version of Go are you using (`go version`)?
1.8.3
### What operating system and processor architecture are you using (`go env`)?
darwin amd64
### What did you do?
Attempt to build a project with a dependency on collate/tools/colcmp/icu.go with the icu tag.
### What did you expect to see?
Clean build.
### What did you see instead?
Failure to find icu version 57 because of the hard dependency from https://github.com/golang/text/blob/master/cases/icu.go (which as noted is only for tests but is not a test file due to the cgo). This could be changed to match the same versionless dependency like in the collate file. | NeedsInvestigation | low | Critical |
244,612,335 | go | proposal: testing: allow examples to return an error | Currently, all example functions must return nothing. However, it is common
for examples to call things which might possibly return errors. Printing the
error, panicking, ignoring it or calling log.Fatal is not ideal for an example where
real code would almost always just return the error. It makes the example code
less representative of the actual code and more cluttered.
I propose that example functions should be allowed to return an error,
For runnable examples, tests would fail if the example
returns a non-nil error.
| Proposal,Proposal-Hold | medium | Critical |
244,683,361 | pytorch | Discrepancy in BCEWithLogitsLoss and ClassNLLLoss | In BCEWithLogitsLoss, weights are unnormalized and used, while in ClassNLLLoss weights are normalized and used.
Some discussion around this can be found [here](https://github.com/pytorch/pytorch/commit/67968cb60b1d3021834594967d4140a36a8213e3#commitcomment-23155134). Is this discrepancy expected? Else if this is an issue I can send a PR to resolve this. | module: loss,module: cuda,module: cpu,triaged | low | Minor |
244,695,261 | kubernetes | `kubectl get` should have a way to filter for advanced pods status | **What happened**:
I'd like to have a simple command to check for pods that are currently not ready
**What you expected to happen**:
I can see a couple of options:
* There is some magic flag I am not aware of
* Having a flag for `kubectl get` to filter the output using go/jsonpath
* Distinguish between Pod Phase `Running&Ready` and `Running`
* Flag to filter on ready status
**How to get that currently**:
```
kubectl get pods --all-namespaces -o json | jq -r '.items[] | select(.status.phase != "Running" or ([ .status.conditions[] | select(.type == "Ready" and .state == false) ] | length ) == 1 ) | .metadata.namespace + "/" + .metadata.name'
```
| kind/feature,sig/cli | high | Critical |
244,709,795 | kubernetes | Remove the hardcoded list of group/versions from config | There is a hardcoded list of priorities that needs to be plumbed up from storage maps.
https://github.com/kubernetes/kubernetes/blob/6fb3d3a79c95f75e3f5a66b37f530fd337d6c57e/cmd/kube-apiserver/app/aggregator.go#L230 | priority/important-soon,kind/cleanup,sig/api-machinery,lifecycle/frozen | low | Major |
244,831,807 | go | net/http: update DetectContentType sniff signature for MP3 without ID3 | This is a placeholder bug to remind me to look into updating the http.DetectContentType sniff mechanisms to accomodate an addition to whatwg/mimesniff in which MP3s can be sniffed without an ID3 tag https://mimesniff.spec.whatwg.org/#signature-for-mp3-without-id3.
This shall require updating the max buffer size from 512 to 1445 and reviewing that algorithm described in https://mimesniff.spec.whatwg.org/#signature-for-mp3-without-id3. I noticed this after seeing this tweet https://twitter.com/mimesniff/status/888665270025420800 which pointed me to PR https://github.com/whatwg/mimesniff/pull/4.
This can be discussed when the tree opens up for Go1.10. | NeedsFix,FeatureRequest | low | Critical |
244,836,406 | opencv | Why CvGBTrees and GBTrees were being commented out in opencv3? | Boost and RTrees in opencv3 are very useful. After testing the previous two methods, then I want to try the GBDT method, but founded it was disappeared. I am very puzzled, anyone knows the details? | RFC | low | Minor |
244,850,739 | youtube-dl | Add AppStream metadata(was: Add donate to AppStream information) | Not sure how to do this but please incorporate: https://rg3.github.io/youtube-dl/donations.html
Once done, a donation button appears in Solus Software Center. :-)
https://dev.solus-project.com/T4148 | request | low | Major |
244,856,097 | rust | Array lengths don't support generic parameters. | **EDIT**: This can now be made to work on nightly compilers, although it's a bit awkward to use. See [this comment](https://github.com/rust-lang/rust/issues/43408#issuecomment-917600907).
It would seem that when using size_of in const fn context, it fails to properly compute the size of generic types.
The following function fails
```rust
unsafe fn zeroed<T: Sized>() -> T {
// First create an array that has the same size as T, initialized at 0
let x = [0u8; std::mem::size_of::<T>()];
// Then, transmute it to type T, and return it
std::mem::transmute(x)
}
```
The error is the following :
```
error[E0277]: the trait bound `T: std::marker::Sized` is not satisfied
--> src/main.rs:3:19
|
3 | let x = [0u8; std::mem::size_of::<T>()];
| ^^^^^^^^^^^^^^^^^^^^^^ `T` does not have a constant size known at compile-time
|
= help: the trait `std::marker::Sized` is not implemented for `T`
= help: consider adding a `where T: std::marker::Sized` bound
= note: required by `std::mem::size_of`
```
This is very confusing because it complains that `T` doesn't have `std::marker::Sized`, even though it does have that bound.
## Meta
rustc_version : rustc 1.20.0-nightly (ae98ebfcb 2017-07-20) | T-compiler,A-const-eval,A-const-generics,A-lazy-normalization,glacier,A-array | high | Critical |
244,885,216 | go | proposal: spec: add const literals for reference types like structs, maps, and arrays | **Summary:**
I propose adding const literals for reference types. E.g.
```go
const c = []string{"1", "2", "3"}
```
**Background:**
Having const structs and arrays and maps is very useful to make sure the value is not changed. This is specially for tests where you want to make sure the value you are passing to functions, the only way right now is to make a copy of the object explicitly. When passing a const to a function or over a chan or assigning it to a variable Go would make a copy.
**Proposal:**
Allow definition of constants of reference types like structs, maps, and arrays.
Impact:
No impact on existing code.
**Discussion:**
This can simplifies code.
**Alternatives:**
**Alternative 1:** use var definitions, do explicitly copy
Without a built-in DeepCopy standard function the developer has to write their own copy functions for each type. It is also likely to break if the language adds new basic types in future.
But even if we had a DeepCopy standard function one cannot be sure that some other part of code is not changing the value of the variable. This gets worse when the const has to be exported or when the packages consists of multiple files.
```go
var c = []string{"1", "2", "3"}
.
.
.
v := cCopy(c)
```
**Alternative 2:** generator function
We can write functions that create the struct and return it. E.g.
```go
func genC() []string { return []string{"1", "2", "3"} }
.
.
.
v := genC(c)
```
This leads to code with lots of functions just for creating values.
| LanguageChange,Proposal,LanguageChangeReview | medium | Critical |
244,921,816 | rust | Improve error message for one named, one anonymous lifetime parameters | For the following example
```
fn foo<'a>(x: &'a i32, y: Vec<&i32>) {
- consider changing the type of `y` to `std::vec::Vec<&'a i32>`
y.push(x);
^ this reference must have lifetime 'a
}
```
can be refined to
```
fn foo<'a>(x: &'a i32, y: Vec<&i32>) {
---- consider changing this type to `&'a i32`
y.push(x);
^ this reference must have lifetime 'a
}
```
Underline `&i32` instead of the whole type.
cc @nikomatsakis | C-enhancement,A-diagnostics,A-lifetimes,T-compiler | low | Critical |
244,959,344 | angular | Animations - stagger not working in route outlet | <!--
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. -->
My parent component has router-outlet where Home or About component is rendered. Router animation is working fine, all components have the same list and animations - `@expand` and `@listXXX`.
Issue: When refreshed the page, both `@expand` and `@listParent` work fine, but when navigated between Home and About, `@listChild` never seems to work at `ngFor` initialization. If I try to push / pop a single item, animation works though.
When router animation done, I am querying `@expand`, `@listChild` and calling animateChild().
## Expected behavior
<!-- Describe what the desired behavior would be. -->
When refreshed or navigated, `@listChild` stagger animation should work just like `@expand` animation.
## 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).
-->
https://embed.plnkr.co/Ft0I5iPpvbMra5ZrV7wc/
## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
## Environment
<pre><code>
Angular version: 4.3.1
<!-- Check whether this is still an issue in the most recent Angular version -->
Browser:
- [x] Chrome (desktop) version 59
- [ ] Chrome (Android) version XX
- [x] Chrome (iOS) version 59
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: 6.10.0 <!-- run `node --version` -->
- Platform: Windows<!-- Mac, Linux, Windows -->
Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
| type: bug/fix,area: animations,freq2: medium,P3 | low | Critical |
244,983,251 | go | x/build/cmd/coordinator, x/build/cmd/gomoteserver: ssh proxy should support scp | As of https://golang.org/cl/50750 the build coordinator has an ssh server to proxy to buildlets. (That was bug #19956)
But there's no scp support yet.
This is a tracking bug to figure that out.
| help wanted,Builders,FeatureRequest | low | Critical |
245,009,664 | vscode | Support workspace projects / folders under different colors in sidebar and tabs |
- VSCode Version: Nightly
- OS Version: Any
Workspace feature is really useful as it is today, but could themes API be extended so to display different projects with different colors/nuances?
See:
It would be even better if tabs could have different colors, to resemble the project they belong to:
Thanks for all the beautiful code and the effort you put in this superb project.
Roberto.
| feature-request,ux,themes,workbench-tabs,workbench-multiroot | high | Critical |
245,067,426 | kubernetes | testing.StartTestServer doesn't tear down cleanly | **What happened**:
The new `k8s.io/kubernetes/cmd/kube-apiserver/app/testing.StartTestServerOrDie` function (introduced in https://github.com/kubernetes/kubernetes/pull/46865) returns a teardown function which doesn't cleanly shut down the test server. This results in the accumulation of goroutines and log spam which prevents effective use of the test server across multiple test functions within the same process.
**What you expected to happen**:
Calling the teardown function should gracefully terminate everything that started up when `StartTestServerOrDie` was called.
**How to reproduce it (as minimally and precisely as possible)**:
Using the following sample integration test code:
```go
import (
"fmt"
"runtime"
"testing"
apitesting "k8s.io/kubernetes/cmd/kube-apiserver/app/testing"
)
func TestTeardown(t *testing.T) {
_, tearDown := apitesting.StartTestServerOrDie(t)
tearDown()
stack := make([]byte, 8196)
size := 0
for {
size = runtime.Stack(stack, true)
if size < len(stack) {
break
}
stack = make([]byte, len(stack)*2)
}
fmt.Printf("%s\n", string(stack[0:size]))
}
```
After `tearDown()` returns, there are several lingering goroutines which forever attempt to maintain etcd connections to the terminated etcd instance. Here's an example stack dump:
https://gist.github.com/ironcladlou/52b3e3306948db3943b426c70ce7f85b
Among all the etcd connection threads, some things you'll notice are lingering `Cacher` instances (which are created due to the default `EnableWatchCache` storage setting) which seem to try and hold watches, and configuration_manager (which may or may not hold connections; I'm not sure yet). This seems to indicate various components started during apiserver setup aren't actually shutting down.
**Anything else we need to know?**:
This is important for enabling integration testing of custom resource garbage collection (https://github.com/kubernetes/kubernetes/pull/47665).
**Environment**:
- Kubernetes version (use `kubectl version`): master (as of 088141ca3a193feab943375bcc564db1a66ef58a)
- Cloud provider or hardware configuration**:
- OS (e.g. from /etc/os-release): darwin/amd64
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
/cc @sttts @caesarxuchao @deads2k @liggitt @kubernetes/sig-api-machinery-bugs
/kind bug
| kind/bug,priority/backlog,area/apiserver,sig/api-machinery,lifecycle/frozen | low | Critical |
245,108,541 | angular | Content Projection using ngIf causes animations to not work | ## I'm submitting a...
<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
Nested components in a content projection container with ngIf causes animations not to animate correctly.
## Minimal reproduction of the problem with instructions
Take the following use case: I have a tabs component that uses ng-content to slot the content. The content is only rendered when the active tab is focused, done through an ngIf.
**TabComponent**
```javascript
@Component({
selector: 'tab',
template: `
<ng-content *ngIf="active"></ng-content>
`
})
export class TabComponent {
@Input() active: boolean = false;
}
```
**TabsComponent**
```javascript
@Component({
selector: 'tabs',
template: `
<section>
<ul>
<li *ngFor="let tab of tabs" class="tab">
{{tab.title}}
</li>
</ul>
<div class="tab-content">
<ng-content></ng-content>
</div>
</section>
`
})
export class TabsComponent {
@ContentChildren(TabComponent) tabs: QueryList<TabComponent>;
}
```
then I compose my markup like:
```html
<tabs>
<tab>Something<tab>
<tab><component-with-animation></component-with-animation></tab>
</tabs>
```
when I click the second tab the animation is not run. I've tried running `changeDetectionRef.markForCheck()` in the component doing the animation but it does not seem to work. If I change the `ngIf` to `hidden` it does correctly work.
Upon investigation, I found that the component with the animation is still getting initialized despite it not being rendered ( ref: https://github.com/angular/angular/issues/13921 ). I tried to work around this by creating the body of the content using `createEmbeddedView` and reading out the content from the tab like:
```javascript
@Component({
selector: 'tab',
template: `
<ng-template><ng-content></ng-content></ng-template>
`
})
export class TabComponent {
@ViewChild(TemplateRef) templateRef;
}
```
and in the my parent component when the tab was activated I would create that view like:
```javascript
@Component({
selector: 'tabs',
template: `
<section>
<ul>
<li *ngFor="let tab of tabs" class="tab">
{{tab.title}}
</li>
</ul>
<div class="tab-content" #tabContent></div>
</section>
`
})
export class TabsComponent {
@ContentChildren(TabComponent) tabs: QueryList<TabComponent>;
@ViewChild('tabContent', { read: ViewContainerRef }) tabContent:
activate(tab) {
this.tabContent.clear();
this.tabContent.createEmbeddedView(tab.templateRef);
}
}
```
but that resulted in the same result.
You can see the result of a more complex demonstration in this plunker http://plnkr.co/edit/2o4hyPhfMiFHLINIpT57?p=preview.
## Environment
Angular version: 4.3.0
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: 8.x
- Platform: Mac | type: bug/fix,area: animations,freq3: high,core: content projection,P3 | low | Critical |
245,115,019 | opencv | derivAperture, histogramNormType not used in HOGDescriptor | OpenCV => 3.2 & master
If I am right <code>derivAperture</code> and <code>histogramNormType</code> parameters are not used in the <code>HOGDescriptor</code> class.
There are references of them in [hog.cpp](https://github.com/opencv/opencv/blob/master/modules/objdetect/src/hog.cpp) and [objdetect.hpp](https://github.com/opencv/opencv/blob/master/modules/objdetect/include/opencv2/objdetect.hpp).
Are they here for future development or should they be removed ?
In the first case I think something should be added to the documentation to explain their future role and that they are not currently used. | RFC | low | Minor |
245,132,789 | TypeScript | `const enum` inside a namespace makes it treated as a value | **TypeScript Version:** nightly (2.5.0-dev.20170719)
**Code**
```ts
declare const N: number;
declare namespace N {
const enum E {}
}
```
**Expected behavior:**
No error. `N` does not contain any values, so it should be OK to merge it with a value.
**Actual behavior:**
```
src/foo.d.ts(1,15): error TS2451: Cannot redeclare block-scoped variable 'N'.
src/foo.d.ts(2,19): error TS2451: Cannot redeclare block-scoped variable 'N'.
``` | Bug | low | Critical |
245,221,967 | rust | Tracking issue for RFC 2044: dual-MIT/Apache2 licensing | This is a tracking issue for RFC 2044 ([thread](https://github.com/rust-lang/rfcs/pull/2044), [rendered](https://github.com/rust-lang/rfcs/blob/master/text/2044-license-rfcs.md)), to put the `rust-lang/rfcs` repo under dual MIT/Apache-2 licensing terms.
Necessary steps for execution:
Asking past contributors to agree with the licensing terms (with <=40 contributors each to bypass the github mention limit of 50):
- [ ] https://github.com/rust-lang/rfcs/issues/2076
- [x] https://github.com/rust-lang/rfcs/issues/2077
- [x] https://github.com/rust-lang/rfcs/issues/2078
- [ ] https://github.com/rust-lang/rfcs/issues/2079
And further:
- [x] PR to `rust-lang/rfcs` to add LICENSE-MIT and LICENSE-APACHE files, talk about the licensing situation in the README, and edit the template to include the header: https://github.com/rust-lang/rfcs/pull/2075
- [x] Asking first time contributors who opened PRs before the PR above got merged to agree with the terms: https://github.com/rust-lang/rfcs/issues/2096
- [ ] PR to `rust-lang/rfcs` to signify the licensing change is complete. Doable once every (or almost every) contributor has signified consent with the licensing terms. Also, figure out what to do about the contributions by people who didn't give their consent: ~https://github.com/rust-lang/rfcs/pull/2193~ | B-RFC-approved,T-core,C-tracking-issue | low | Major |
245,252,040 | flutter | GestureRecognizers should bid when they win | Suppose you have two gesture detectors, A and B.
A accepts when you move X pixels.
B accepts when you move 2X pixels.
They are in the arena in the order B then A.
If you move 2X pixels, B accepts.
If you move 0.9X pixels then 1.1X pixels, B accepts.
If you move 1.9X pixels, A accepts.
If you move 0.9X pixels then 0.9X pixels, A accepts.
This means which one accepts depends on the device's touch event rate.
Unfortunately, another name for A would be HorizontalDragGestureRecognizer and another name for B would be ScaleGestureRecognizer.
We could address this by having the recognizers report how the number of pixels beyond the point where they would have won, when they accept. Then, after all the recognizers have had a chance, the lowest one actually wins. | c: new feature,framework,f: gestures,P2,team-framework,triaged-framework | low | Minor |
245,252,217 | flutter | Tap recognizer shouldn't give up when it goes beyond its slop if there's a defined rect for it | You should be able to slop around a big button without rejecting the tap recognizer. | c: new feature,framework,f: gestures,P2,team-framework,triaged-framework | low | Minor |
245,280,784 | rust | Tracking issue for RFC 1861: Extern types | This is a tracking issue for [RFC 1861 "Extern types"](https://github.com/rust-lang/rfcs/blob/master/text/1861-extern-types.md).
**Steps:**
- [x] Implement the RFC (#44295)
- [ ] Adjust documentation ([see instructions on forge][doc-guide])
- [ ] Stabilization PR ([see instructions on forge][stabilization-guide])
[stabilization-guide]: https://forge.rust-lang.org/stabilization-guide.html
[doc-guide]: https://forge.rust-lang.org/stabilization-guide.html#updating-documentation
**Unresolved questions:**
- [ ] Rust does not support types that don't have dynamically computed alignment -- we need the alignment to compute the field offset in structs. `extern type` violates this basic assumption, causing pain, suffering, and ICEs all over the compiler. What is the principled fix for this?
- [ ] Should we allow generic lifetime and type parameters on extern types?
If so, how do they effect the type in terms of variance?
- [x] [In std's source](https://github.com/rust-lang/rust/blob/164619a8cfe6d376d25bd3a6a9a5f2856c8de64d/src/libstd/os/raw.rs#L59-L64), it is mentioned that LLVM expects `i8*` for C's `void*`.
We'd need to continue to hack this for the two `c_void`s in std and libc.
But perhaps this should be done across-the-board for all extern types?
Somebody should check what Clang does. Also see https://github.com/rust-lang/rust/issues/59095.
RESOLVED because all pointer types are `ptr` now.
- [ ] How should this interact with unsized arguments? Currently it ICEs: https://github.com/rust-lang/rust/issues/115709 | A-FFI,T-lang,B-unstable,B-RFC-implemented,C-tracking-issue,F-extern_types,S-tracking-needs-summary | high | Critical |
245,318,735 | kubernetes | The attachdetach controller failed to set statusUpdateNeeded when controller restart | <!-- This form is for bug reports and feature requests ONLY!
If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
-->
**Is this a BUG REPORT or FEATURE REQUEST?**:
/kind bug
**What happened**:
restart controller manager , the attachdetach controller will generate following errors when processing all nodes in nodeAdd:
````
E0725 07:56:32.458142 1 actual_state_of_world.go:500] Failed to set statusUpdateNeeded to needed true because nodeName="k8s-community-16-master.novalocal" does not exist
E0725 07:56:32.458149 1 actual_state_of_world.go:514] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true because nodeName="k8s-community-16-master.novalocal" does not exist
````
**What you expected to happen**:
attachdetach controller should work fun when normally restart
**How to reproduce it (as minimally and precisely as possible)**:
- get controller manager docker id
- docker restart $(dockerid)
**Anything else we need to know?**:
**Environment**:
- Kubernetes version (use `kubectl version`):
````
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.0", GitCommit:"fff5156092b56e6bd60fff75aad4dc9de6b6ef37", GitTreeState:"clean", BuildDate:"2017-03-28T16:36:33Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.1", GitCommit:"1dc5c66f5dd61da08412a74221ecc79208c2165b", GitTreeState:"clean", BuildDate:"2017-07-14T01:48:01Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
````
- Cloud provider or hardware configuration**:
generated by kubeadm
````
- --cluster-signing-cert-file=/etc/kubernetes/pki/ca.crt - --address=127.0.0.1
- --insecure-experimental-approve-all-kubelet-csrs-for-group=system:bootstrappers - --kubeconfig=/etc/kubernetes/controller-manager.conf
- --root-ca-file=/etc/kubernetes/pki/ca.crt - --service-account-private-key-file=/etc/kubernetes/pki/sa.key
- --cluster-signing-key-file=/etc/kubernetes/pki/ca.key - --leader-elect=true
- --use-service-account-credentials=true - --controllers=*,bootstrapsigner,tokencleaner
- -v=5
````
- OS (e.g. from /etc/os-release):
````
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
````
- Kernel (e.g. `uname -a`):
````
Linux k8s-community-16-master.novalocal 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
````
- Install tools:
- Others: we find it was occured from v1.6.0 to 1.7.1, but other version not tested | kind/bug,sig/storage,lifecycle/frozen | low | Critical |
245,346,795 | opencv | C++11: use _MSVC_LANG define for C++ features detection on MSVC | https://msdn.microsoft.com/en-us/library/b0084kay.aspx | feature,priority: low,category: build/install | low | Minor |
245,500,012 | three.js | Fade out shadows as one approaches the left/right/top/bottom/near/far clip planes | ##### Description of the problem
Right now when one has a shadow casting light there is a far plane and a near plane and shadows start and end abruptly at these planes. I think it would be much nicer if we faded in the shadow and faded out the shadow when one approaches the clip plane.s This way limited frustum shadows can be used in larger regions without nasty clip artifacts. Fading out shadows often looks very natural.
I noticed this when playing the game Kingdoms and Castles ( http://store.steampowered.com/app/569480/Kingdoms_and_Castles/ ). See how the shadow fades out at the top. It allows this game to have high quality shadows in the regions right in front of the camera, but they fade out as you scroll the clouds away from the center. This is very effective and also not jarring. Should be relatively easy to implement:
##### Three.js version
- [x] Dev
- [x] r85
##### Browser
- [x] All of them
##### OS
- [x] All of them
| Enhancement | low | Minor |
245,507,073 | go | x/review/git-codereview: use rebase branch during rebase | Currently git-codereview doesn't add the appropriate "[branch]" prefix to commit messages created or amended during a rebase because all it sees is the detached HEAD state. As a fall back, it could look for .git/rebase-merge/head-name, which contains the full ref name of the branch being rebased and find that branch's upstream.
For example, this happened in https://golang.org/cl/50875.
/cc @josharian | Suggested | low | Minor |
245,508,723 | youtube-dl | Please add Watchbox.de | ### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.07.23*. 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.07.23**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [x] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.watchbox.de/serien/he-man-and-the-masters-of-the-universe-12247/staffel-1/der-kosmische-komet-328614']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2017.07.23
[debug] Python version 3.4.4 - Windows 10
[debug] exe versions: ffmpeg N-71883-geb9fb50, ffprobe N-71883-geb9fb50
[debug] Proxy map: {}
[generic] der-kosmische-komet-328614: Requesting header
WARNING: Falling back on generic information extractor.
[generic] der-kosmische-komet-328614: Downloading webpage
[generic] der-kosmische-komet-328614: Extracting information
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://www.example.com/video123.flv'
ERROR: unable to download video data: HTTP Error 404: Not Found
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu6zpd7mk\build\youtube_dl\YoutubeDL.py", line 1863, in process_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu6zpd7mk\build\youtube_dl\YoutubeDL.py", line 1805, in dl
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu6zpd7mk\build\youtube_dl\downloader\common.py", line 361, in download
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu6zpd7mk\build\youtube_dl\downloader\http.py", line 61, in real_download
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpu6zpd7mk\build\youtube_dl\YoutubeDL.py", line 2166, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
urllib.error.HTTPError: HTTP Error 404: Not Found
...
<end of log>
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: https://www.watchbox.de/serien/he-man-and-the-masters-of-the-universe-12247/staffel-1/der-kosmische-komet-328614.html
- Single video: https://www.watchbox.de/filme/free-jimmy-12325.html
- Playlist: https://www.watchbox.de/serien/he-man-and-the-masters-of-the-universe-12247/
Note: Content seems to be region-locked to German speaking areas.
Watchbox.de replaces Clipfish.de
Site seems to use MPEG-DASH | geo-restricted | low | Critical |
245,561,568 | neovim | persistent undo: handle very long paths, avoid E828 | So recently when going through my plugins and cleaning stuff up I found that I still have https://github.com/pixelastic/vim-undodir-tree installed. I thought neovim might have solved that problem and tested it out. But neovim still has this problem with deep directory structures (or just a really long filename).
I feel like this is something Neovim could add by default because I do not see a drawback to it right now. If there is a drawback which I am not aware of, please let me know. | enhancement,filesystem | low | Major |
245,568,306 | flutter | Add isGoodDiagnosticsNode matcher to flutter_test | Similar to existing hasAGoodToStringDeep but smarter now that there is structured DiagnosticsNode information.
For example, error if string or int properties are added without using IntProperty or StringProperty
Error on DiagnosticTreeStyle transitions that are not currently supported. E.g. no switching from sparse to dense without an intermediate DiagnosticsTreeStyle.transition node. | a: tests,c: new feature,framework,c: proposal,P2,team-framework,triaged-framework | low | Critical |
245,594,232 | flutter | Flutter needs a way to collect device info (e.g. chrome's about:gpu) | Particularly about the graphics functionality of the device in question. This would help us not only diagnose when graphics issues are going wrong, but also collect info from users in the field.
Chrome has something along this vein called "about:gpu".
Examples of things we should dump:
- Information about how the GrContext initialized (8888? sRGB, etc)
- Make and model of the GPU
- probably lots more i'm forgetting.
We would only do this if it were useful to folks like @chinmaygarde @jason-simmons and @brianosman | c: new feature,tool,a: triage improvements,P2,team-tool,triaged-tool | low | Major |
245,678,298 | angular | routerLinkActive applies active class to null routerLink | ## 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 using routerLinkActive and the routerLink is null the active class is applied. Even if using routerLinkActiveOptions to set exact to true.
## Expected behavior
Null roots should not have the active class applied as there is no route to actually be active for
## Minimal reproduction of the problem with instructions
Set routerLink to null and add routerLinkActive with options exact to set to true.
See Plunker: http://plnkr.co/edit/ZXycO0ld2uQRqwALYdDT?p=preview
## What is the motivation / use case for changing the behavior?
There was an issue reported that null routeLink should do nothing when clicked and this was fixed. This is related to this issue - the two go hand in hand. As currently the only way round this is to have two *ngIf to cater for null routes
## Environment
<pre><code>
Angular version: v4.3.1
@angular/cli: 1.2.1
Browser:
- [ X] Chrome (desktop) version XX
For Tooling issues:
- Node version: v8.1.4
- Platform: Windows
| type: bug/fix,effort1: hours,freq2: medium,area: router,state: confirmed,router: directives,P3 | low | Critical |
245,706,273 | neovim | Error with Python Provider: Invalid argument: Channel id must be a positive integer | I've found similar issues but not quite the same I have (and also no solution) so I decided to post it.
- `nvim --version`
```
NVIM v0.2.0
Build type: Release
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNDEBUG -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/config -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/src -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/src/nvim/auto -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/include
Compiled by [email protected]
Optional features included (+) or not (-): +acl +iconv +jemalloc +tui
For differences from Vim, see :help vim-differences
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/local/Cellar/neovim/0.2.0_1/share/nvim"
```
- Operating system/version: **macOS Sierra 10.12.5**
- Terminal name/version: **iTerm Build 3.1.20170619-nightly**
- `$TERM`: **xterm-256color**
- `pip2 show neovim`:
```
Name: neovim
Version: 0.1.13
Summary: Python client to neovim
Home-page: http://github.com/neovim/python-client
Author: Thiago de Arruda
Author-email: [email protected]
License: Apache
Location: /usr/local/lib/python2.7/site-packages
Requires: msgpack-python, trollius, greenlet
```
- `pip3 show neovim`:
```
Name: neovim
Version: 0.1.13
Summary: Python client to neovim
Home-page: http://github.com/neovim/python-client
Author: Thiago de Arruda
Author-email: [email protected]
License: Apache
Location: /usr/local/lib/python3.6/site-packages
Requires: msgpack-python, greenlet
```
`:CheckHealth` reports nothing out of the ordinary
### Actual behaviour
Every time I open Neovim it outputs the following message. After that, everything works just fine.
```
function <SNR>54_InitializePythonBuiltin[23]..provider#python#Call[9]..remote#host#Require[10]..provider#pythonx#Require, line 15
Vim(if):E475: Invalid argument: Channel id must be a positive integer
Failed to load python host. You can try to see what happened by starting nvim with $NVIM_PYTHON_LOG_FILE set and opening the generated log file. Also, the host stderr is available in messages.
Press ENTER or type command to continue
```
### Expected behaviour
I expect Neovim to open without showing me something is wrong.
### Things I've tried
Removed and reinstalled `python`, `python3`, `neovim`. Installed either `neovim` stable and `neovim --HEAD` on homebrew. The error persists.
The error does not occur when I run `nvim -u NONE`
| provider,job-control,has:plan | medium | Critical |
245,728,484 | TypeScript | Eliminate non-generic functions | Every non-generic function can be expressed as generic function with a single type parameter corresponding to each argument. Explicit parameter type annotations simply correspond to `extends` constraints on the type parameters of the generic equivalent.
While the title of the issue is "eliminate non-generic functions", in practice this simply gets rid of all the syntax ceremony involved in declaring generic functions. A function declaration as follows:
```
function repeat(item, n: number) => Array(n).fill(item)
```
will be inferred as: `type F = <T1 extends any, T2 extends number>(item: T1, number: T2) => T1[]`, and the result of invoking it with `repeat("foo", 10)` is inferred as `string[]`, not `any[]`. | Suggestion,Needs Proposal | medium | Critical |
245,777,887 | javascript | Clarification for Inline Comments | Thanks for the excellent style guide!
One thing that is not explicitly defined by the guide is inline comments. Can a section on this topic be added to the "Comments" section block, please?
For example,
```
let foo = 145; // This is modified below in the "baz()" function
```
Is this a legal line in the airbnb style?
And the follow-up question: if it is not legal, then I assume that the correct fix to have it be moved above, like this?
```
// This is modified below in the "baz()" function
let foo = 145;
```
Yet another follow-up question: if inline comments are legal, then what is the correct fix for in-line comments that make the line extend past 100 character? Like the following:
```
// This is a comment describing the following block of variable initializations
let foo = 123; // used in various contexts, but mostly for soccer games, basketball, and football games
let bar = 456; // used only for horse races; it is explicitly reset at the beginning of the "endRace()" function
let baz = 789; // used only for car races; it will be overwritten once we reach the "oilChange()" function
```
If it were moved above, it would overlap with the block comment header. So then does it make the most sense to move them down to the next line, like this?
```
// This is a comment describing the following block of variable initializations
let foo = 123;
// used in various contexts, but mostly for soccer games, basketball, and football games
let bar = 456;
// used only for horse races; it is explicitly reset at the beginning of the "endRace()" function
let baz = 789;
// used only for car races; it will be overwritten once we reach the "oilChange()" function
``` | pull request wanted,editorial | low | Minor |
245,862,314 | go | proposal: spec: reduce noise in return statements that contain mostly zero values | Update: the current proposal is to permit `return ..., v` to return the zero value for all but the last result, and to return `v` as the last result. The most common use will be `return ..., err`.
A variant under discussion include `return ..., v1, v2` to return zeroes for all but the last N.
Another variant is to permit `return ...` to return zeroes for all.
In general `...` is only permitted if it omits one or more values--`func F() err { return ..., errors.New("") }` is not permitted.
---
# Proposal
In return statements, allow `...` to signify, roughly, "and everything else is the zero value". It can replace one or more zero values.
This is best described by example:
Given the function signature `func() (int, string, *T, Struct, error)`:
`return 0, "", nil, Struct{}, nil` may be written `return ...`
`return 0, "", nil, Struct{}, err` may be written `return ..., err`
`return 0, "", nil, Struct{X: Y}, nil` may be written `return ..., Struct{X: Y}, nil`
`return 1, "", nil, Struct{}, nil` may be written `return 1, ...`
`return 1, "a", nil, Struct{}, nil` may be written `return 1, "a", ...`
`return 1, "", nil, Struct{}, err` may be written `return 1, ..., err`
`return 1, "a", nil, Struct{X: Y}, err` may be written `return 1, "a", ..., Struct{X: Y}, err`
The following is invalid:
`return ..., Struct{X: Y}, ...` — there can be at most one `...` in a return statement
# Rationale
It is common for a function with multiple return values to return only one non-zero result when returning early due to errors.
This creates several annoyances of varying degrees.
When writing the code one or more zero values must be manually specified. This is at best a minor annoyance and not worth a language change.
Editing the code after changing the type of, removing one of, or adding another return value is quite annoying but the compiler is fast enough and helpful enough to largely mitigate this.
For both of the above external tooling can help: https://github.com/sqs/goreturns
However, the unsolved problem and motivation for the proposal is that it is quite annoying to read code like this. When reading `return 0, "", nil, Struct{}, err` unnecessary time is spent pattern matching the majority of the return values with the various zero value forms. The only signal, `err`, is pushed off to the side. The same intent is coded more explicitly and more directly with `return ..., err`. Additionally, the previous two minor annoyances go away with this more explicit form.
# History
This is a generalized version of a suggestion made by @nigeltao in https://github.com/golang/go/issues/19642#issuecomment-288559297 where #19642 was a proposal to allow a single token, `_`, to be sugar for the zero value of any type.
I revived the notion in https://github.com/golang/go/issues/21161#issuecomment-317891763 where #21161 is the currently latest proposal to simplify the `if err != nil { return err }` boilerplate.
# Discussion
This can be handled entirely with the naked return, but that has greater readability issues, can lead too easily to returning the wrong or partially constructed values, and is generally (and correctly) frowned upon in all but the simplest of cases.
Having a universal zero value, like `_` reduces the need to recognize individual entries as a zero value greatly improving the readability, but is still somewhat noisy as it must encode n zero values in the common case of `return _, _, _, _, err`. It is a more general proposal but, outside of returns, the use cases for a universal zero value largely only help with the case of a non-pointer struct literal. I believe the correct way to deal that is to increase the contexts in which the type of a struct literal may be elided as described in #12854
In https://github.com/golang/go/issues/19642#issuecomment-288644162 @rogpeppe suggested the following workaround:
```
func f() (int, string, *T, Struct, error) {
fail := func(err error) (int, string, *T, Struct, error) {
return 0, "", nil, Struct{}, err
}
// ...
if err != nil {
return fail(err)
}
// ...
}
```
This has the benefit of introducing nothing new to the language. It reduces the annoyances caused by writing and editing the return values by creating a single place to write/edit the return values. It helps a lot with the reading but still has some boilerplate to read and take in. However, this pattern could be sufficient.
This proposal would complicate the grammar for the return statement and hence the go/ast package so it is not backwards compatible in the strict Go 1 sense, but as the construction is currently illegal and undefined it is compatible in the the Go 2 sense.
# Possible restrictions
Only allow a single value other than `...`.
Only allow it on the left (`return ..., err`).
Do not allow it in the middle (`return 1, ..., err`).
While these restrictions are likely how it would be used in practice anyway, I don't see a need for the limitations. If it proves troublesome in practice it could be flagged by a linter.
# Possible generalizations
Allow it to replace zero or more values making the below legal:
```
func f() error {
// ...
if err != nil {
return ..., err
}
// ...
}
```
This would allow easier writing and editing but hurt the readability by implying that there were other possible returns. It would also make this non-sequitur legal: `func noop() { return ... }`. It does not seem worth it.
Allow `...` in assignments. This would allow resetting of many variables to zero at once like `a, b, c = ...` (but not `var a, b, c = ...` or `a, b, c := ...` as their is no type to deduce) . In this case I believe the explicitness of the zero values is more a boon than an impediment. This is also far less common in actual code than a return returning multiple zero values. | LanguageChange,Proposal,error-handling,dotdotdot,LanguageChangeReview | high | Critical |
245,936,594 | You-Dont-Know-JS | ES6 & Beyond - Chapter 7: Meta Programming - Reflect API | Hi,
**URL:** https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch7.md#reflect-api
About **Reflect.enumerate** (url: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect/enumerate)
> The static **Reflect.enumerate**() method used to return an iterator with the enumerable own and inherited properties of the target object, **but has been removed in ECMAScript 2016 and is deprecated in browsers**. | for second edition | medium | Minor |
245,938,490 | flutter | Messages dropped if sent to a detached platform view | See https://github.com/flutter/engine/pull/3927 | engine,P2,a: plugins,team-engine,triaged-engine | low | Minor |
245,987,308 | vscode | Change all occurrences in a single 100MB line leads to a crash when autosave on | Testing #30243.
32-bit Windows
0. Enable autosave.
1. Open 100MB file generated by Dummy File Creator (non-random content). I got single line generated.
2. Type 'sd' in several places on the same line.
3. Do an edit via 'Change all occurrences' from the context menu.
Observe crash.
Should we disable triggering autosave for large files?
| feature-request,editor-core | low | Critical |
246,075,381 | go | runtime: label runtime functions based on their roles | As runtime provides more features, we often observe a program's profile is dominated by runtime functions. For example, this is a cpu profile of a program from blog.google.com/profiling-go-programs article (but compiled with go1.9). I highlighted the runtime function frames with purple color. Even for more complex program, we expect at least a quarter of the profiled CPU time to be associated with runtime.
This is useful to analyze performance issues related to runtime. However, often times, it distracts users from focusing on the application logic. On the other hand, Go runtime provides various functionalities (scheduling, GC, map, synchronization, etc), it's still difficult to answer questions like e.g.,
- what's the CPU time spent by GC?
- what's the CPU time spent by map operation?
without knowledge on runtime implementation.
Go 1.9 introduced profiler labels that allows users to label profile samples.
(http://tip.golang.org/doc/go1.9#pprof-labels)
Users can do aggregation or filtering of samples based on the labels (e.g. rpc methods, users, operation mode, etc).
Similarly, I propose to add labels for runtime functions based on the roles of functions to help aggregating and analyzing the cost involving runtime more conveniently. Labels are grouping of runtime functions curated by runtime developers. Implementation-wise, it doesn't necessarily have to use the similar mechanism like the profiler label. Instead, when pprof proto is constructed, it can check the existence of the runtime functions and label based on them.
note 1: Alternative approach discussed was to name the runtime functions based on feature it offers, (e.g. all GC related functions should be prefixed with GC or gc, etc) and users use them to filter or hide using pprof options. That is not as nice as labels, and requires more efforts from users to use it right. Another approach mentioned was to filter out uninteresting frames when publishing or visualizing profiles. That is not ideal because sometimes we want the details and also the list of 'uninteresting' functions may change over time.
note 2: We can envision that pprof recognizes runtime labels and presents the aggregated boxes for each group instead of the detailed runtime call graphs unless asked to display the detailed runtime call graph.
@rakyll @randall77 @aclements
| help wanted,NeedsFix,FeatureRequest,compiler/runtime | medium | Major |
246,103,643 | go | x/build/maintner: poll Gerrit more often than 5 minutes | If Gerrit emails are delayed (there's no SLA?), maintner (our Gerrit+GitHub mirror) doesn't get updated until the next Gerrit poll every 15 minutes.
We should probably do a cheap poll more often than 15 minutes.
I just saw an email delay of 3-5 minutes.
@andybons, what's a cheap (for Gerrit, and for our quota) way to ask Gerrit what's changed recently, including comments & votes?
A full git ls-remote on each project is pretty expensive, both in network & since we need to do it for each project.
A query over all changes/projects with a Limit of 1 seems cheap network-wise, but not sure what the quota is for that. Can we do it every minute?
| Builders | low | Major |
246,162,223 | flutter | TextSelectionControls.handlePaste is racy | handlePaste doesn't lock the text field while it's waiting for a response from the clipboard. The user could tap "paste" multiple times in a row, or paste then edit text, or paste then leave the page entirely. Results could vary from the appearance of inoperative UI (only one paste when you tap twice), to data corruption or data loss (paste overwriting what the user has since written), to crashes (if we try to interact with the delegate after it's been disposed). | a: text input,c: crash,framework,engine,P2,team-engine,triaged-engine,fyi-text-input | low | Critical |
246,189,933 | youtube-dl | Support decoding Coub videos (was: Downloaded Coub video file broken) | ## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like
---
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.07.23*. 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.07.23**
### Before submitting an *issue* make sure you have:
- [X] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [X] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [X] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
casval@casval-X6815 /tmp % youtube-dl http://coub.com/view/eq9pa -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'http://coub.com/view/eq9pa', u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.07.23
[debug] Python version 2.7.13 - Linux-4.10.0-28-generic-x86_64-with-Ubuntu-17.04-zesty
[debug] exe versions: avconv 3.2.4-1build2, avprobe 3.2.4-1build2, ffmpeg 3.2.4-1build2, ffprobe 3.2.4-1build2, rtmpdump 2.4
[debug] Proxy map: {}
[Coub] eq9pa: Downloading JSON metadata
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on u'http://s3.storage.akamai.coub.com/get/b130/p/coub/simple/cw_file/30cf7df5d5e/aa6e6b21fbdf78b11538d/muted_mp4_big_size_1473445250_muted_big.mp4'
[download] Destination: Spergberb-eq9pa.mp4
[download] 100% of 1.77MiB in 00:00
casval@casval-X6815 /tmp % mpv Spergberb-eq9pa.mp4
Playing: Spergberb-eq9pa.mp4
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: moov atom not found
[lavf] avformat_open_input() failed
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: moov atom not found
[lavf] avformat_open_input() failed
Failed to recognize file format.
Exiting... (Errors when loading file)
---
When I try to download a Coub video, the resulting video file is unplayable (I tried VLC, as well) and judging by the URL is also tried to download the muted version of the video. | request,bug | medium | Critical |
246,199,943 | godot | Gizmos aren't Z-sorted properly with transparent surfaces | Godot 3.0 alpha1 official
Windows 10 64 bits
nVidia geforce 940M
It depends on the viewing angle, gizmos get randomly drawn behind or in front of transparent surfaces. In the screenshot, the blue plane is slightly transparent:
| bug,topic:rendering,topic:editor,topic:3d | medium | Major |
246,208,704 | TypeScript | Allow calls to overloaded functions when all possible combinations of union type parameters resolve to valid overloads | **TypeScript Version:** 2.4.1
**Code**
Case 1
```ts
// overloaded functions
declare function f(a: number): number;
declare function f(a: string): string;
function g<T extends number | string>(a: T) {
return f(a); // either of arguments is acceptable
// ~
// Argument of type 'T' is not assignable to parameter of type 'string'.
// Type 'string | number' is not assignable to type 'string'.
// Type 'number' is not assignable to type 'string'.
}
```
Case 2
```ts
declare function f2<T>(a: Promise<T>): number;
declare function f2<T>(a: T): string;
function g2<T>(a: T) {
const result: string = f2(a); // first overload is ignored, but the argument can be a Promise
return result;
}
```
**Expected behavior:**
Case 1: compiles with no errors
Case 2: error that type `string | number` is not assignable to type `string`
**Actual behavior:**
Case 1: error
```
Argument of type 'T' is not assignable to parameter of type 'string'.
Type 'string | number' is not assignable to type 'string'.
Type 'number' is not assignable to type 'string'
```
Case 2: compiles without errors
**Note**
I remember here were some discussions about that, so that verifying all possible paths may result in N*M complexity (N overloads, M constituent types in unions). I could not find it.
The second case seems unsafe at all, because skips a possibly valid overload which may effect on return type. I expect that `f2(a)` would be of type `number | string` because either of these two overloads can play. It actually has the same result with `a: any`. | Suggestion,In Discussion | medium | Critical |
246,210,257 | TypeScript | Infer constrained generic parameters after instanceof check | <!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->
**TypeScript Version:** 2.4.0
When a variable passes an `instanceof` check generic type with constraints on the type parameter, apply to constraints to the variable. There is currently no clean way to handle the following without an explicit cast:
**Code**
```ts
interface Foo {
foo: string;
}
class Bar<T extends Foo> {
constructor(readonly bar: T) {}
}
let a: any;
if (a instanceof Bar) {
a.bar; // <-- a.bar should be 'Foo' instead of 'any'
}
```
**Expected behavior:**
`a.bar` is inferred as an instance of `Foo`.
**Actual behavior:**
`a.bar` is `any`
This change would only impact type checking, and will not affect compilation output. | Suggestion,In Discussion,Fix Available | medium | Major |
246,229,105 | thefuck | Hitting enter does not execute the previous command in Windows Git Bash | ```
$ echo "foo'
> ^C
$ fuck
echo "foo" [enter/↑/↓/ctrl+c]
(hangs here...)
```
---
This is on Windows Git Bash (bash 4.4). `thefuck --version` and `type fuck` are below.
```
$ thefuck --version
The Fuck 3.18 using Python 2.7.13
$ type fuck
fuck is a function
fuck ()
{
TF_PREVIOUS=$(fc -ln -1);
TF_PYTHONIOENCODING=$PYTHONIOENCODING;
export TF_ALIAS=fuck;
export TF_SHELL_ALIASES=$(alias);
export PYTHONIOENCODING=utf-8;
TF_CMD=$( thefuck $TF_PREVIOUS THEFUCK_ARGUMENT_PLACEHOLDER $@ ) && eval $TF_CMD;
export PYTHONIOENCODING=$TF_PYTHONIOENCODING;
history -s $TF_CMD
}
``` | help wanted,hacktoberfest | low | Major |
246,295,257 | vscode | [Feature] Color Picker: Keyboard accessibility | Refs: #31457
It is good that the color picker can be triggered via our "Show Hover" command, however after that you can not do any changes to it using the keyboard.
It should be possible to use the keyboard to navigate inside the color picker and choose colors appropriatly. | help wanted,feature-request,accessibility,editor-color-picker | low | Major |
246,319,057 | rust | reached the recursion limit while instantiating `function_name::<[closure]>` | Here is a shortened version of the code I hit this with:
https://play.rust-lang.org/?gist=01e76f65024cbf57bb018547932aaef2&version=stable
The error message is everything but enlightening as to what is going wrong, and from a programmer perspective, there is nothing in there that should hit a recursion limit.
@bluss had this to say on irc:
> So the first call is `Arguments::from` with `F` = `U1` (some unique closure type for the initial closure) which recursively calls from with `F` = `U2` (new type for `|| None`) which calls from with `F` = `U3` (new type for `|| None`) And `U2` and `U3` are different because they are compiled in functions with different type parameters? `U2` is compiled with `F`=`U1` and `U3` is compiled with `F` = `U2`
> I think we can test if that's true
> with this we have a closure with an anonymous type still, but that doesn't depend on any type parameter. It's `Self::nop()` in this code. https://play.rust-lang.org/?gist=c82188fa9cf9c592b1956f6a5b5babe4&version=nightly
> so yeah, rustc could be a lot smarter in this case
Note that I worked around it by just manually inlining the recursion, which is also shorter. | A-closures,T-compiler,C-bug | low | Critical |
246,353,891 | godot | Module Question: How to write a module that replaces a core piece of the engine? | I am currently working on a project, and due to the nature of the project, and the target I need to write a few modules to replace some core components of the engine.
Specifically the Renderer, and the Physics system.
The documentation states that you can use a module to replace the current renderer, and the physics system. But it is only a hint. There's no information about how to do this correctly.
Can someone point me in the right direction? | topic:core,topic:buildsystem,documentation | low | Minor |
246,370,502 | youtube-dl | Support Youtube/Google one-touch authentication with Android | When using 2FA to login to Youtube, there is either `HTTP Error 500: Internal Server Error` or `HTTP Error 402`.
I suspect it is because Google accounts with an active Android device allow the Android device to authorize sign in request, and 2FA is not required. This is what appears on my Android device:
Could youtube-dl support this one-click sign on for Android when available, and fall back to TOTP/2FA only when it is not available?
### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2017.07.23**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [x] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [x] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
$ youtube-dl -v 'https://www.youtube.com/watch?v=TAgVVc5hAiE'
[debug] System config: []
[debug] User config: ['--proxy', 'localhost:8888', '[email protected]', '--mark-watched']
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.youtube.com/watch?v=TAgVVc5hAiE']
Type account password and press [Return]:
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.07.23
[debug] Python version 3.6.1 - Darwin-14.5.0-x86_64-i386-64bit
[debug] exe versions: avconv 12, avprobe 12, ffmpeg 3.3.2, ffprobe 3.3.2, rtmpdump 2.4
[debug] Proxy map: {'http': 'localhost:8888', 'https': 'localhost:8888'}
[youtube] Downloading login page
[youtube] Looking up account info
[youtube] Logging in
Type 2-step verification code and press [Return]:
[youtube] Submitting TFA code
WARNING: Unable to submit TFA code: HTTP Error 500: Internal Server Error
WARNING: Unable to extract CheckCookie URL
[youtube] TAgVVc5hAiE: Downloading webpage | request | low | Critical |
246,410,009 | kubernetes | Cache mounts on the host | <!-- This form is for bug reports and feature requests ONLY!
If you're looking for help check [Stack Overflow](https://stackoverflow.com/questions/tagged/kubernetes) and the [troubleshooting guide](https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/).
-->
**Is this a BUG REPORT or FEATURE REQUEST?**:
/kind feature
/sig storage
**What happened**:
In #48402 a new mount check was added to handle the case of bind mounts on directories (and not actual mount points). The new check has to iterate through all the mounts on the system, which could be time-consuming if there are many mounts. It may be worth looking into caching the mounts to optimize this check. | sig/storage,kind/feature,lifecycle/frozen | low | Critical |
246,416,164 | kubernetes | Add garbage collector tests to cover aggregated API servers | With the introduction of [CRD support in the garbage collector](https://github.com/kubernetes/kubernetes/pull/47665), we decided to open this followup issue to introduce expanded test coverage to verify GC works with custom resources backed by aggregated API servers.
/kind feature
@kubernetes/sig-api-machinery-feature-requests
| area/test,sig/api-machinery,kind/feature,lifecycle/frozen | low | Major |
246,466,215 | rust | No explanation for source of static lifetime requirement in E0597 | The compiler can do better at indicating the source of the `'static` requirement from various sources, including closures passed to functions (e.g., `thread::spawn`) and `Box<Error>` having an implicit `Error + 'static` bound.
-----------------
## Thread::spawn case
This minimized code:
```rust
use std::thread;
struct Thing<'a> {
blut: &'a str
}
fn main() {
let dest = String::from("/etc");
let dest = &dest[..];
let thing = Thing { blut: dest };
let t = thread::spawn(|| { thing; });
}
```
gives the error
```
error[E0597]: `dest` does not live long enough
--> <source>:9:17
|
9 | let dest = &dest[..];
| ^^^^ does not live long enough
...
12 | }
| - borrowed value only lives until here
|
= note: borrowed value must be valid for the static lifetime...
```
which is as intended, I think (ending with a ellipsis is a little weird, but it historically was followed by a second note about a "block suffix" which was removed because nobody knows what that means). But it would be great if the error could tell me the two critical pieces of information leading to the error:
1. The `'static` requirement comes from `F` in `thread::spawn::<F>`
2. `dest` is used in the closure because it's in the struct `thing`
Especially number 2 is not obvious at all.
## Box<Error> case
(code partially stolen from https://github.com/rust-lang/rust/issues/35580)
```rust
use std::error::Error;
struct SomeStruct;
#[derive(Debug)]
enum SomeError<'a> {
Something(&'a str),
Other,
}
fn do_stuff(doc: &usize) -> Result<SomeStruct, SomeError> {
Ok(SomeStruct)
}
fn get_things() -> Result<SomeStruct, Box<Error>> {
let res = try!(Err(SomeError::Other));
Ok(try!(do_stuff(&res)))
}
impl<'a> std::fmt::Display for SomeError<'a> {
fn fmt(&self, f: &mut std::fmt::Formatter) -> Result<(), std::fmt::Error> {
write!(f, "blah")
}
}
impl<'a> Error for SomeError<'a> {
fn description(&self) -> &str { "blah" }
}
```
```
error: `res` does not live long enough
--> ./test.rs:17:23
|
17 | Ok(try!(do_stuff(&res)))
| ^^^ does not live long enough
18 | }
| - borrowed value only lives until here
|
= note: borrowed value must be valid for the static lifetime...
``` | C-enhancement,A-diagnostics,T-compiler | low | Critical |
246,490,260 | go | math/rand: tests are too weak due to misuse of statsResults.maxError | The math/rand tests use the function `nearEqual` to compare floats:
```go
func nearEqual(a, b, closeEnough, maxError float64) bool {
absDiff := math.Abs(a - b)
if absDiff < closeEnough { // Necessary when one value is zero and one value is close to zero.
return true
}
return absDiff/max(math.Abs(a), math.Abs(b)) < maxError
}
```
A bit of thought suggests that `maxError` should always be pretty small, if this function is ever to return false. However, maxError is usually scaled everywhere it is used (e.g. stddev * 0.08), and in practice it frequently ends up >> 2.
As a result, many of the math/rand tests have no teeth. An extreme example of this is TestReadUniformity, which requires (among other things) that the mean of just 2 randomly selected bytes must be very near 255.0/2, a test which should almost always fail, but which currently succeeds, due to a large value of maxError. (Related: [CL 51310](https://go-review.googlesource.com/c/51310/).)
Replacing maxError with a constant `0.08` causes most math/rand tests to pass, except TestReadUniformity when called with small n (in which case it should fail).
However, I don't have enough domain expertise to know whether this is reasonable or whether an alternative bound would be better. Advice requested.
golang.org/s/owners lists no one for math/rand, so I'll guess and cc: @rsc @aclements @robpike
| Testing,help wanted,NeedsFix | low | Critical |
246,491,440 | rust | Bors: 422 Update is not a fast forward | Periodically we'll see bors not manage to push the built PR into master for some reason.
This is possibly because of submodules not being synchronized? Wild stab in the dark.
| A-spurious,T-infra,C-tracking-issue,A-CI | low | Major |
246,567,363 | TypeScript | Expose serializers from TypeScript transformer (ts.ts) | With the introduction of the Transform API some of the logic in [transformers/ts.ts](https://github.com/Microsoft/TypeScript/blob/30d973bdcbbe2b39723345448cb457ebbc41ae03/src/compiler/transformers/ts.ts) needs to be exposed. (and maybe from other places...)
I'll explain by example:
```ts
@SomeDecorator()
export class MyClass {
constructor(public myInterface: MyInterface, public myClass: MyOtherClass) {}
}
```
If I want to transform the code so all **parameter** type metadata will be on a static property of the class. (this is angular DI)
```ts
@SomeDecorator()
export class MyClass {
constructor(public myInterface: MyInterface, public myClass: MyOtherClass) { }
static ctorParams: [Object, MyOtherClass];
}
```
This operation is currently impossible.
To get the right identifier for each type I need to serialize the type with some logic so **MyInterface** will become **Object** since it's not really a value.
The native **TypeScript** transformer has a lot of code for handling the logic of type serialization and it's not something one will want to copy, its huge.
Even if someone decided to replicate the logic, there's not access to the `EmitResolver` which is the "type checker" used by the native transformer to serialize the types.
`TransformationContext.getEmitResolver()` is `@internal`
The workaround is to actually run another `Program` process to get access to a `TypeChecker`.
It's not even possible to get a hold of the current running `Program` instance since `TransformerFactory` does not get access to it.
Is it possible to expose the serializatoin logic in the TypeScript transformer? I know it's complex, recursing and state dependant (scope) but it seems like not being able to serialize a type to create a literal is something basic | Suggestion,Needs Proposal,API | low | Major |
246,594,659 | go | plugin: -buildmode=plugin not supported on linux/mips | According to https://golang.org/pkg/plugin/ plugins under Linux should be supported.
### What version of Go are you using (`go version`)?
go version go1.8.3 linux/amd64
go version devel +ac29f30dbb Fri Jul 28 00:29:08 2017 +0000 linux/amd64
### What did you do?
GOOS=linux GOARCH=mips ./go build -a -buildmode=plugin main.go
### What did you expect to see?
Successfully building mips(32) plugin
### What did you see instead?
"-buildmode=plugin not supported on linux/mips"
| Documentation,NeedsFix,compiler/runtime | medium | Critical |
246,606,816 | rust | Tracking issue for tweaks to dyn compatibility (RFC 2027) | This is the tracking issue for RFC 2027, tweaks to dyn-compatibility[^1] (rust-lang/rfcs#2027)
* [x] Implement (https://github.com/rust-lang/rust/pull/57545)
* [ ] Document
* [ ] Stabilize
[^1]: Formerly known as "object safety". | A-trait-system,T-lang,B-unstable,B-RFC-implemented,C-tracking-issue,F-dyn_compatible_for_dispatch,S-tracking-needs-summary | medium | Major |
246,609,205 | go | x/crypto/acme/autocert: Hooks for "CertAcquired", "CertRenewed" | My use-case for ACME / LetsEncrypt is to setup a TLS Listener that isn't a HTTP/HTTPS endpoint. e.g: IRC, or something else.
The code in x/crypto/acme/autocert doesn't make it very obvious how one can identify whether a cert was successfully acquired or renewed. The only solution I've come up with in poking at this is to "watch" for changes to the file system with a file-system implementation of the `Cache` interface.
Is this something we can add or is there a more recommended way to handle this? | NeedsInvestigation | low | Minor |
246,630,198 | rust | Xcode Instruments can not read Rust source code automatically. | Since I almost completely misunderstood the issue, I update it.
I am not quite sure if it is related with rustc or not...
In the past, adding `debug = true` into Cargo.toml seemed to enable Rust source code profiling on Xcode Instruments (on macOS).
But at present, it does not work.
Instruments seems to read dSYM file correctly (you can check it via File->Symbols...), but Instruments seems not to know source code path.
Who has a responsibility about the source code path?
[ORIGINAL]
Hi.
In the past, adding `debug = true` into Cargo.toml seemed to enable Rust source code profiling on Xcode Instruments (on macOS).
But at present, it does not work.
Trying to add dSYM path causes the following error.
No new libraries to symbolicate
The specified path didn't locate a dSYM for any of the selected libraries.
I will appreciate very much if anyone let me know workarounds or Rust team resolves it kindly.
Thanks. | O-macos,A-debuginfo,T-compiler,E-help-wanted,C-bug | low | Critical |
246,813,873 | angular | BrowserAnimationsModule changes the behaviour of select-dropdowns | <!--
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. -->
It is rather complicated to sum up the situation, here is my SO-Posting on the matter:
[https://stackoverflow.com/questions/45420803/browseranimationsmodule-altering-behaviour-of-select-dropdowns](https://stackoverflow.com/questions/45420803/browseranimationsmodule-altering-behaviour-of-select-dropdowns)
Basically, when I programmatically remove an option form a dropdown, I dont want the selection to change. In case the select-dropdown is pristine, removing an option will cause the select to display the first option as the selected one:
Here is the defective plunkr:
[https://plnkr.co/edit/ayzM2HNtO6Hkkr8jkgVA?p=preview](https://plnkr.co/edit/ayzM2HNtO6Hkkr8jkgVA?p=preview)
## Expected behavior
<!-- Describe what the desired behavior would be. -->
I dont think the selection of a pristine select should change, when an option is removed programmatically. Here is a working plunkr:
https://plnkr.co/edit/dPDpEQm14pWlFNfLe4nP?p=preview
Now the thin is, the only difference between defective and working plunkr is that in the working plunkr I have remove the BrowserAnimationsModule from the Module-Imports (at the bottom of the file, I did keep the ts-import )
This makes it seem that the BrowserAnimaitonsModule is somehow responsible for changing the behaviour of the select-dropdown.
## 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.3.2
<!-- 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
- [ x] 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,freq1: low,P4 | low | Critical |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.