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 |
|---|---|---|---|---|---|---|
224,872,940 | go | proposal: cmd/vet: add check for common error mishandling pattern | People have proposed adding a test to vet to catch certain unused errors. This can be very noisy, and there are many cases where the error is genuinely known to be nil and can be ignored, such as in a call to `bufio.Writer.Write`. Therefore a general "unused error" check will be too noisy and fail the precision criterion described in `cmd/vet/README`.
However, my project has been badly bitten twice recently by a particular problem of unused errors that should be caught. The two looked schematically like these snippets:
```
func e() error { ... }
var err error
# Error value not caught in if init:
if e(); err != nil {...}
# Error value not caught before if:
e()
if err != nil { ... }
```
I did some experiments to catch calls to functions with the type of `e` that did not catch the error, and found too may false positives for things like `os.Setenv`.
However, since the real problem isn't that the error is discarded, but that it is discarded immediately before a check, I think it's worth trying a more targeted approach, one that would catch both of the problems in the snippets above.
The `-unusedresult` flag, on by default, already checks for things like calls to `fmt.Sprintf` where the value is not used, which is clearly a bug - there is no other reason to call `fmt.Sprintf`. That check works with a whitelist, but the problems in the examples above involved local functions that would never appear on a whitelist unless explicitly added when vet is called, which is error-prone (and not done in general).
I therefore propose to add to the `-unusedresult` check a test for the specific case with these three properties:
1. a call to a function that returns an error as one of its possibly several arguments;
2. return values from the function are dropped (no explicit `_`);
3. the next statement reads a variable of type error.
It's point 3 that makes this work, I think, eliminating almost all the noise from calls to things like `os.Setenv` while catching the real bugs. If you just called an error function and then ask about the error, if there's no flow from the call to the check, you almost certainly made a mistake.
Regarding the criteria:
Correctness: This is a real bug, and it's bitten our project twice with severe security problems as a result. This is a problem that needs fixing.
Frequency: It's hit our project twice, and our project isn't big. I believe the severity is high enough that even a modest frequency of hits justifies the fix. If I implement this, I predict it will find more.
Precision: I believe that rule 3 in this proposal should make it precise enough.
| Proposal,Proposal-Hold,Analysis | medium | Critical |
224,873,084 | kubernetes | Standardize Container-Related Kubelet Prometheus Metrics | Currently, the Prometheus metrics exposed by Kubelet are simply those directly exported by cAdvisor. In light of the move to make metrics more easily accessible to third-party monitoring pipelines (as per the monitoring vision), we should standardize and document the set of metrics that are guaranteed to be exported.
Currently, the set of metrics exported by cAdvisor don't follow the instrumentation guidelines in some cases. For instance, the container metrics use `pod_name` instead of `pod` (https://github.com/kubernetes/community/blob/master/contributors/devel/instrumentation.md#resource-referencing), and don't always follow proper naming conventions (e.g. `container_fs_inodes_total` is suffixed with `_total`, but is a gauge). This makes them difficult to use in conjunction in a consistent way.
However, on a more fundamental level, not having a well-defined set of metrics makes it difficult for monitoring solutions to know what they can rely on (e.g. I always want to display FS state on my dashboard -- what metric do I use), and it means that changes to cAdvisor can inadvertently break compatibility (e.g. changing the semantics of certain labels).
Standardizing the set of metrics we provide also means that we ever run without cAdvisor (e.g. because we've moved the responsibility of metrics onto the container runtime), whatever is providing the metrics instead knows exactly what it needs to provide. | sig/scalability,lifecycle/frozen | low | Major |
224,879,114 | TypeScript | checkJs: allow file extensions other than .js | First of all, this option is super exciting! Thank you so much for the TypeScript team to make such an incredible tool ❤️
Surprisingly enough, this week I wanted to have type check in a `*.jsfl` file (Scripting for Adobe Animate) and it worked pretty well using Facebook's Flow. They have [an option to configure a different file format](https://flow.org/en/docs/config/options/#toc-module-file-ext-string) other than `.js`.
It would be nice to allow this sort of configuration for TypeScript as well. I've naively tried to use `"include":["./src/*.jsfl"]` but it didn't worked. 😅
Or is there a hidden option for this? Thanks!
| Suggestion,Awaiting More Feedback | medium | Major |
224,973,928 | go | x/mobile: gomobile cause memory issue on android when use with react-native and fresco | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go version go1.7.4 darwin/amd64
### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/nary/Desktop/gopath
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.4_1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.4_1/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/f8/73mv3kjn2rxcv3rv_zvs6tn40000gn/T/go-build352177269=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
### What did you do?
use gomobile to create react-native cross platform app
### What did you expect to see?
### What did you see instead?
It is very easy to crash on android 4.3 when you use gomobile with react-native.
on android 4.4 and 5.0, 6.0 the situation is a little better but it will still lead to memory issue and the pic will never show when you browse a lot.
I create a complete reproducable demo on my github. https://github.com/narychen/ReactNativeListTest
It just print hello call from the gomobile in android/app/src/main/java/com/listtest/MainApplication.java
```
public void onCreate() {
super.onCreate();
Log.i("gotest", Gotest.greetings("gotest")); //delete it will make the app work without crash
SoLoader.init(this, /* native exopackage */ false);
}
```
On android 4.3 it will quickly crash and the android log shows
```
04-28 11:40:42.691 23953-24922/com.listtest D/skia: ---------- mmap failed for imageref_ashmem size=8294400
04-28 11:40:42.901 23953-24890/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 12460K, 30% free 18487K/26372K, paused 18ms, total 19ms
04-28 11:40:42.901 23953-24890/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 23.802MB for 4194320-byte allocation
04-28 11:40:42.931 23953-24922/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 45K, 27% free 22544K/30472K, paused 16ms, total 16ms
04-28 11:40:42.941 23953-24922/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 27.764MB for 4194320-byte allocation
04-28 11:40:42.971 23953-24899/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 135K, 23% free 26645K/34572K, paused 14ms, total 15ms
04-28 11:40:42.981 23953-24899/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 31.770MB for 4194320-byte allocation
04-28 11:40:42.981 23953-24922/com.listtest D/skia: ---------- mmap failed for imageref_ashmem size=8294400
04-28 11:40:42.991 23953-24899/com.listtest D/skia: ---------- mmap failed for imageref_ashmem size=8294400
04-28 11:40:43.021 23953-24917/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 8207K, 26% free 22547K/30468K, paused 16ms, total 16ms
04-28 11:40:43.021 23953-24917/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 27.767MB for 4194320-byte allocation
04-28 11:40:43.031 23953-24917/com.listtest D/skia: ---------- mmap failed for imageref_ashmem size=8294400
04-28 11:40:43.111 23953-24917/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 4380K, 26% free 22556K/30468K, paused 16ms, total 16ms
04-28 11:40:43.121 23953-24917/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 27.776MB for 4194320-byte allocation
04-28 11:40:45.731 23953-24899/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 8307K, 30% free 18594K/26372K, paused 17ms, total 17ms
04-28 11:40:45.741 23953-24899/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 21.907MB for 2097168-byte allocation
04-28 11:40:45.831 23953-24890/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 198K, 28% free 20524K/28424K, paused 15ms, total 15ms
04-28 11:40:45.841 23953-24890/com.listtest I/dalvikvm-heap: Grow heap (frag case) to 23.791MB for 2097168-byte allocation
04-28 11:40:45.941 23953-24922/com.listtest D/dalvikvm: GC_FOR_ALLOC freed 316K, 26% free 22563K/30476K, paused 27ms, total 27ms
04-28 11:40:46.101 23953-23953/com.listtest W/Adreno-GSL: <sharedmem_gpumem_alloc_id:1427>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
04-28 11:40:46.101 23953-23953/com.listtest E/Adreno-GSL: <ioctl_kgsl_sharedmem_alloc:1528>: ioctl_kgsl_sharedmem_alloc: FATAL ERROR : (null)
```
On android 4.3 and earlier version the facebook fresco module use Ashmem to manage the pic memory. So error shows that 'sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory'.
And if gomobile somewhere conflict with fresco on Ashmem. It may cause this problem.
Nowadays, react-native and fresco is used everywhere. Hope the gomobile team could see this problem and solve it.
When you use the demo, just change the GOPATH in android/gotest/build.gradle and you will compile it. If you are not familiar with react-native, just cd the demo's directory and run command
```
react-native run-android
```
or use android studio to compile and run it.
Should be test on real devices.
Thanks.
| mobile | medium | Critical |
224,975,272 | rust | Specialization results in spurious mismatch type errors | An upstream crate presents me with this API:
```rust
trait Foo { }
trait Bar {
fn bar<F: Foo>(&self, f: F);
}
```
This is a fine API as far as it goes, but my problem is that I only care about one `Foo`, and I need `Bar` to be object safe. For my use case, this is the API I want:
```rust
struct MyFoo;
impl Foo for MyFoo { }
trait MyBar {
fn my_bar(&self, f: MyFoo);
}
```
But I need to bridge `T: MyBar` to `T: Bar`. I have this solution, based on specialization, which I believe is correct:
```rust
trait BarBridge<F: Foo> {
fn bridge(&self, f: F) -> F::Assoc;
}
struct Bridge<T: MyBar>(T);
impl<T: MyBar> BarBridge<MyFoo> for Bridge<T> {
fn bridge(&self, f: MyFoo) -> bool {
self.0.my_bar(f)
}
}
impl<T: MyBar, F: Foo> BarBridge<F> for Bridge<T> {
default fn bridge(&self, _: F) {
unreachable!()
}
}
impl<T: MyBar> Bar for Bridge<T> {
fn bar<F: Foo>(&self, f: F) {
self.bridge(f)
}
}
```
However this appears to greedily attempt to unify `F` with `MyFoo` because of the implementation of `BarBridge<MyFoo>` instead of recognizing the implementation of `forall<F: Foo> BarBridge<F>`.
cc @nikomatsakis @aturon | T-compiler,A-specialization,C-bug,F-specialization | low | Critical |
224,979,661 | youtube-dl | Feature Request: Add support for dowloading VideoLectures.NET's slides | Since it's quite tedious to download each slide of a playlist, can youtube-dl also download the ppt/pdf files while downloading the corresponding videos? | question | low | Minor |
225,136,853 | go | net/http: BenchmarkClientServerParallel4 hangs and is useless | It seems the BenchmarkClientServerParallel4 benchmark sometimes hangs while running. Sometimes it needs to be killed (first example) and sometimes it recovers on its own, leading to useless numbers.
In any case, I can't get good numbers out of it.
I suspect it's consuming too many sockets and running out of addresses or something.
```
bradfitz@gdev:~/go/src/net/http$ go test -benchtime=1s -bench=BenchmarkClientServerParallel4 -count=3 -run=XXXX | tee before
goos: linux
goarch: amd64
pkg: net/http
BenchmarkClientServerParallel4-4 30000 39470 ns/op 7539 B/op 73 allocs/op
BenchmarkClientServerParallel4-4 50000 40934 ns/op 7563 B/op 73 allocs/op
BenchmarkClientServerParallel4-4 ^C
bradfitz@gdev:~/go/src/net/http$ go test -benchtime=1s -bench=BenchmarkClientServerParallel4 -count=3 -run=XXXX | tee before
goos: linux
goarch: amd64
pkg: net/http
BenchmarkClientServerParallel4-4 5000 283132 ns/op 7244 B/op 85 allocs/op
BenchmarkClientServerParallel4-4 1 7011289330 ns/op 54720 B/op 527 allocs/op
BenchmarkClientServerParallel4-4 1 7010777787 ns/op 37472 B/op 238 allocs/op
PASS
ok net/http 16.585s
```
| Testing,help wanted | low | Major |
225,165,478 | go | encoding/csv: add a way to limit bytes read per field/record | The [csv.Reader](https://golang.org/pkg/encoding/csv#Reader) has no way to limit the size of the fields read. In combination with [LazyQuotes](https://golang.org/pkg/encoding/csv/#Reader.LazyQuotes), this can lead to cases where a simple syntax error can make the Reader read everything until io.EOF into a single field.
Probably the simplest case (with LazyQuotes == true) is a quoted field, where there is some other rune between the closing quote and the comma (e.g. `a,"b" ,c`). In this case the second field will contain all bytes until either a single quote folowed by a comma or EOF is found. (See [my comment](https://github.com/golang/go/issues/8059#issuecomment-298054037) in #8059)
This behaviour can lead to excessive memory usage or even OOM when reading broken CSV files.
To avoid this I propose to add a new, optional field to Reader to allow limiting the size of each field. When set the Reader would return an error as soon as it hits the limit.
~~Alternatively the limit could be per record instead. This could help especially with situations where FieldsPerRecord == -1, because there can be a different, basically unlimitted number of fields per record so a limit of 100 bytes per field doesn't help with e.g. missing new lines leading to records with many fields.~~
The new field would be specified as (as proposed by @bradfitz)
```go
type Reader struct {
...
// BytesPerField optionally specifies the maximum allowed number of bytes
// per field. Zero means no limit.
BytesPerField int
``` | Proposal,FeatureRequest,Proposal-Hold | medium | Critical |
225,196,471 | go | proposal: spec: disallow T<->uintptr conversion for type T unsafe.Pointer | Currently, implementations permit conversions to/from `unsafe.Pointer` **and** to/from types with underlying type `unsafe.Pointer`.
Consequently, unsafe conversions can be hidden because package unsafe doesn't even have to be imported.
This was arguably an "implementation mistake" which we should fix. See also #19306. | LanguageChange,Proposal,LanguageChangeReview | low | Major |
225,205,683 | nvm | Install script should complain if $NVM_DIR isn't a valid base path | https://github.com/creationix/nvm/issues/1520#issuecomment-298117770 is an example of a user having an outdated `NVM_DIR` setting in their profile file.
The installation script should detect when the NVM_DIR does not exist (and ideally backtrack up til it can find the first nonexistent directory) and inform the user clearly that they need to fix their `NVM_DIR` setting (ideally with the default) and retry the installation. | feature requests,pull request wanted,installing nvm | low | Minor |
225,224,226 | angular | [animations] Missing Support for SVG-related Animations | **I'm submitting a ...** (check one with "x")
```
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```
**Current behavior**
The [Angular documentation](https://angular.io/docs/ts/latest/guide/animations.html) states:
> Since Angular's animation support builds on top of Web Animations, you can animate any property that the browser considers animatable. This includes positions, sizes, transforms, colors, borders, and many others. The W3C maintains a list of animatable properties on its CSS Transitions page.
These animatable properties include `svg` properties as per this [subsection 7.2](https://www.w3.org/TR/css3-transitions/#animatable-properties). A typical example would be the radius `r` of a `<svg:circle>` element.
Currently, the API for animations only supports a `style(...)` property, which does not fully allow the animation of to be supported `svg` properties.
Specifically, using the illustrative example component below, the animation will be performed in Chrome.
It will, however, fail in Firefox (and Edge). I.e. the end state will be immediately jumped to.
**Expected behavior**
Full support for all animatable `svg` properties in Angular on par with CSS style animation.
This could possibly involve adding a `attribute(...)` syntax as a complement to `style(...)` or expanding the supported use of the latter.
For added clarity, support for `svg` related animations should be a first class citizen in animation e.g. when addressing issues such as #9668 or any other means to creating dynamic animations.
Thanks in advance!!!
**Minimal reproduction of the problem with instructions**
The somewhat minimalistic component below allows reproduction.
```ts
import { Component } from '@angular/core';
import {
trigger,
state,
style,
animate,
transition
} from '@angular/animations';
@Component({
selector: 'app-root',
template: `
<svg width=100 height=100>
<circle
[@resize]
cx=50
cy=50
r=20
>
</circle>
</svg>
`,
styles: ['circle {stroke: slateblue; fill: slateblue;}'],
animations: [
trigger(
'resize', [
transition(
'void => *', [
style({ r: 0 }),
animate(2000)
])
]
)
]
})
export class AppComponent {
}
```
**What is the motivation / use case for changing the behavior?**
The primary use case are complex data visualizations using `svg` with animated changes in response to data changes.
Without adding in consistent support for `svg` related animations, it is necessary to utilize additional third party modules (e.g. `d3-selection` and `d3-transition`) to touch the DOM.
With full support for animations, D3 can be used to compute layout data, but as a segregated concern Angular can handle all DOM updates.
**Please tell us about your environment:**
Windows 10
VS Code 1.11.2
npm 3.10.10
* **Angular version:** Angular 4.1.0
* **Browser:** [| Chrome Version 57.0.2987.133 (64-bit) | Firefox 53.0 | MS Edge 40.15063.0.0 EdgeHTML 15.15063]
* **Language:** [all]
* **Node (for AoT issues):** n/a
| feature,area: animations,freq1: low,P4,feature: under consideration,feature: votes required | medium | Critical |
225,225,377 | rust | Tracking issue for RFC 1824: Proposal for default crate recommendation ranking | This is a tracking issue for the RFC 1824 (rust-lang/rfcs#1824).
**Steps:**
- [x] [Sort crates by number of downloads in the last 90 days](https://github.com/rust-lang/crates.io/issues/702)
- [x] [Render contents of README on crate pages](https://github.com/rust-lang/crates.io/issues/81)
- [ ] [Have `cargo new` add a template README and template documentation](https://github.com/rust-lang/cargo/issues/3506)
- [ ] ~[Create a "Well documented" badge for crates in the top 20%](https://github.com/rust-lang/crates.io/issues/703)~ (crates.io team decided against this)
- [x] [Add a badge for crate authors to self-report their maintenance intentions ](https://github.com/rust-lang/crates.io/issues/704)
- [x] [Add the ability for crate authors to add isitmaintained.com badges to their crate](https://github.com/rust-lang/crates.io/issues/705)
- [x] [Add the ability for crate authors to add code coverage badges to their crate](https://github.com/rust-lang/crates.io/issues/706)
- [ ] [Have "favorite owners" and highlight crates owned by your favorite owners in crate lists](https://github.com/rust-lang/crates.io/issues/494)
- [ ] Adjust documentation ([see instructions on forge][doc-guide])
[doc-guide]: https://forge.rust-lang.org/stabilization-guide.html#updating-documentation | B-RFC-approved,T-cargo,C-tracking-issue | low | Major |
225,228,428 | javascript | Define public API | Thank you all for this valuable resource. I was catching up on current practices with respect to "private" properties in JavaScript when I came upon the discussion in #490. It seems to me that the definition of public API used by this style guide is stricter than what SemVer describes. For example, the guide currently states that
> Although a leading underscore is a common convention to mean “private”, in fact, these properties are fully public, and as such, are part of your public API contract.
So, as far as this guide is concerned, anything which is accessible in a JavaScript library constitutes its public API. On the other hand, SemVer describes public API differently:
> 1. Software using Semantic Versioning MUST declare a public API. This API could be declared in the code itself or exist strictly in documentation. However it is done, it should be precise and comprehensive.
I take this to mean that, as a library author, I am free to explicitly include and exclude properties from my public API, regardless of whether or not they are accessible in my JavaScript library.
So I propose that this guide define public API for itself and explain why it adheres to the definition that it does. I think this would inform developers evaluating the pros and cons of whether or not to adopt or reject a private convention in their projects. | question,pull request wanted,editorial | low | Minor |
225,228,588 | rust | Inference disrupted by trait bound that is redundant with a HRTB | This compiles:
```rust
trait Trait<'a> {}
struct S<T>(T);
impl<'a, T> Trait<'a> for S<T> where T: for<'b> Trait<'b> {}
fn main() {}
```
This following does not. It seems like the impl already has `T: for<'b> Trait<'b>` so adding `T: Trait<'a>` should not affect the behavior.
```rust
trait Trait<'a> {}
struct S<T>(T);
// Added T: Trait<'a>
impl<'a, T> Trait<'a> for S<T> where T: for<'b> Trait<'b>, T: Trait<'a> {}
fn main() {}
```
```
error[E0283]: type annotations required: cannot resolve `T: Trait<'a>`
--> src/main.rs:6:1
|
6 | impl<'a, T> Trait<'a> for S<T> where T: for<'b> Trait<'b>, T: Trait<'a> {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: required by `Trait`
```
This currently affects the following and *many* people have run into it. The workaround is to remove the bound (https://github.com/rust-lang/rust-clippy/issues/1689).
```rust
#[derive(Deserialize)]
struct S<T: serde::de::DeserializeOwned>(T);
``` | A-lifetimes,A-trait-system,T-compiler,A-inference,C-bug,T-types,fixed-by-next-solver | low | Critical |
225,229,911 | rust | Tracking issue for RFC 1868: A portability lint | This is a tracking issue for the RFC "A portability lint" (rust-lang/rfcs#1868).
**Steps:**
- [ ] Implement the RFC (cc @rust-lang/compiler -- can anyone write up mentoring instructions?)
- [ ] 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:**
- [ ] It's not clear what the story should be for a library like `libc`, which currently involves intricate uses of `cfg`. We should have some idea for how to approach such cases before landing the RFC. | A-lints,B-RFC-approved,T-lang,E-help-wanted,C-tracking-issue,finished-final-comment-period,disposition-close,Libs-Tracked,S-tracking-unimplemented | medium | Major |
225,245,596 | opencv | OpenCVFindMKL fails to find MKL 2017 | <!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).
This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->
##### System information (version)
- OpenCV => 3.2.0
- Operating System / Platform => Windows (64-bit) / x86
- Compiler => Visual Studio 2017
- IPP => 2017.0.2
- MKL => 2017.0.2
- TBB => 2017.0.5
##### Detailed description
There are a number of issues with the script:
1. It doesn't set suffix when searching for `mkl_intel_<suffix>.lib` during 32-bit configuration, ending up searching for `mkl_intel_.lib`.
2. It fails to find `tbb.lib` when configuring with `-D MKL_WITH_TBB=ON`, since the directory structure of TBB 2017 differs from what the script expects.
3. It doesn't take into account what OpenCVDetectTBB has found, which could end up badly when OpenCV is being build with an open source version of TBB while the commercial version is installed side-by-side with MKL.
##### Steps to reproduce
```
set CPATH=<path-to-open-source-TBB-include>
set LIBRARY_PATH=<path-to-open-source-TBB-libraries>
cmake -G "Visual Studio 15 2017" -D BUILD_CUDA_STUBS=OFF -D BUILD_DOCS=OFF -D BUILD_EXAMPLES=OFF -D BUILD_PERF_TESTS=OFF -D BUILD_TBB=OFF -D BUILD_TESTS=OFF -D BUILD_opencv_python2=OFF -D BUILD_opencv_python3=OFF -D WITH_IPP=ON -D IPPROOT="C:\Program Files (x86)\IntelSWTools\compilers_and_libraries\windows\ipp" -D MKL_WITH_TBB=ON -D WITH_TBB=ON -D BUILD_SHARED_LIBS=ON -D BUILD_JASPER=ON -D BUILD_JPEG=ON -D BUILD_OPENEXR=ON -D BUILD_PNG=ON -D BUILD_TIFF=ON -D BUILD_ZLIB=ON ..
``` | bug,category: build/install | low | Critical |
225,251,363 | flutter | Input validator async | The input validator does not support future<String> so if i want to validate making a request i can't because flutter does not support sync http request. Any suggestion? | a: text input,c: new feature,framework,customer: crowd,c: proposal,P3,team-text-input,triaged-text-input | high | Critical |
225,252,643 | go | cmd/asm: change canonical spelling of CMOVLEQ to CMOVL.EQ etc | This proposal is originally from @rsc in issue #14069 and is about `CMOVLEQ` being ambiguous. I Extracted it as I believe it deserves its own issue.
> Recounting this to @aclements I figured out what is going on with CMOVLEQ. The GNU form is CMOV[cond][size] but the form added for Go is CMOV[size][cond]. So GNU's cmovleq is cmov-le-q while Go's CMOVLEQ is CMOV-L-EQ. The Intel syntax has no size suffix and is CMOVEQ/CMOVLE, but it seems clear that Go should not be inserting a size suffix in the middle of the defined opcode name. While in general I feel that we need to put up with past mistakes in our assembly definitions to avoid breaking existing assembly programs, this one seems so egregious and error-prone that I think we have no choice but to change these names for Go 1.7 to match the Intel and GNU syntax.
Unfortunately it seems too late for such a breaking change so the proposal evolved into introducing new aliases like `CMOVL.EQ` (`CMOV%size.%cond`) to lift the ambiguity and then, later on, remove the old versions. Maybe. | help wanted,Proposal,Proposal-Accepted,NeedsFix,compiler/runtime | low | Critical |
225,253,071 | youtube-dl | Support for OnBase Training Videos | Can you guys add - https://training.onbase.com/en/courses/eLearning and https://training.onbase.com/en/courses/premium. We have a premium login through work, but it has been taking me awhile to grab them individually. I am on version 2017-04-28. Thank you and let me know if you have any questions.
Here is the logs from the premium:
C:\Box Sync\IT\Austin's Folder\Apps\youtube-dl>youtube-dl --verbose --username XXXXX --password XXXXX"https://training.onbase.com/en/courses/premium/course?cid=P0963" -o "%USERPROFILE%\Downloads\OnBase\ %(playlist)s\%(chapter_number)s. %(chapter)s/%(playlist_index)s. %(title)s.%(ext)s" --sleep-interval 10
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '--username', 'PRIVATE', '--password', 'PRIVATE', 'https://training.onbase.com/en/courses/premium/course?cid=P0963', '-o', 'C:\\Users\\barbera\\Downloads\\OnBase\\ %(playlist)s\\%(chapter_number)s. %(chapter)s/%(playlist_index)s. %(title)s.%(ext)s', '--sleep-interval', '10']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.04.17
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: none
[debug] Proxy map: {}
[generic] course?cid=P0963: Requesting header
WARNING: Falling back on generic information extractor.
[generic] course?cid=P0963: Downloading webpage
[generic] course?cid=P0963: Extracting information
ERROR: Unsupported URL: https://training.onbase.com/en/courses/premium/course?cid=P0963
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7vri0rse\build\youtube_dl\YoutubeDL.py", line 760, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7vri0rse\build\youtube_dl\extractor\common.py", line 429, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp7vri0rse\build\youtube_dl\extractor\generic.py", line 2765, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: https://training.onbase.com/en/courses/premium/course?cid=P0963
Here is the logs for the e-learning:
C:\Box Sync\IT\Austin's Folder\Apps\youtube-dl>youtube-dl --verbose "https://training.onbase.com/en/courses/eLearning/course?cid=E1162" -o "%USERPROFILE%\Downloads\OnBase\ %(playlist)s\%(chapter_number)s. %(chapter)s/%(playlist_index)s. %(title)s.%(ext)s" --sleep-interval 10
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://training.onbase.com/en/courses/eLearning/course?cid=E1162', '-o', 'C:\\Users\\barbera\\Downloads\\OnBase\\ %(playlist)s\\%(chapter_number)s. %(chapter)s/%(playlist_index)s. %(title)s.%(ext)s', '--sleep-interval', '10']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.04.28
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: none
[debug] Proxy map: {}
[generic] course?cid=E1162: Requesting header
WARNING: Falling back on generic information extractor.
[generic] course?cid=E1162: Downloading webpage
[generic] course?cid=E1162: Extracting information
ERROR: Unsupported URL: https://training.onbase.com/en/courses/eLearning/course?cid=E1162
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\YoutubeDL.py", line 760, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\extractor\common.py", line 429, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpagq0np72\build\youtube_dl\extractor\generic.py", line 2781, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: https://training.onbase.com/en/courses/eLearning/course?cid=E1162 | site-support-request,account-needed | low | Critical |
225,283,521 | TypeScript | Make 'new.target' emit more precautions | I noticed that the polyfill for `new.target` ...
```
class Foo {
constructor() {
if (new.target)
alert("Good.");
else
alert("Bad!");
}
}
```
... outputs to this:
```
var Foo = (function () {
function Foo() {
var _newTarget = this.constructor;
if (_newTarget)
alert("Good.");
else
alert("Bad!");
}
return Foo;
}());
```
That seems dangerous to me, since this is always a true condition for older browsers that don't yet support `new.target`. Does it not make more sense to create an output such as this?:
```
var Foo = (function () {
function Foo() {
var _newTarget = this && this.constructor !== Window ? this.constructor : void 0;
/* (have to check 'this' also, in case of strict mode) */
if (_newTarget)
alert("Good.");
else
alert("Bad!");
}
return Foo;
}());
```
The [following code fails](https://www.typescriptlang.org/play/#src=class%20%24Foo%20%7B%0D%0A%20%20%20%20constructor()%20%7B%0D%0A%20%20%20%20%20%20%20%20if%20(new.target)%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20alert(%22Good.%22)%3B%0D%0A%20%20%20%20%20%20%20%20else%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20alert(%22Bad!%22)%3B%0D%0A%20%20%20%20%7D%0D%0A%7D%0D%0A%0D%0Atype%20FooConstructor%20%3D%20typeof%20%24Foo%3B%0D%0A%0D%0Ainterface%20CallableFoo%20extends%20FooConstructor%20%7B%20()%3A%20%24Foo%3B%20%7D%0D%0A%0D%0Anew%20%24Foo()%3B%20%2F%2F%20ok%0D%0Avar%20Foo%3A%20CallableFoo%20%3D%20%3Cany%3EFoo%3B%0D%0AFoo()%3B%20%2F%2F%20ok%3F%20%3A%2F%0D%0A%0D%0A) to work as expected in Chrome v56.0.2924.87 (output is "Good." in call cases):
```
class $Foo {
constructor() {
if (new.target)
alert("Good.");
else
alert("Bad!");
}
}
type FooConstructor = typeof $Foo;
interface CallableFoo extends FooConstructor { (): $Foo; }
new $Foo(); // ok
var Foo: CallableFoo = <any>Foo;
Foo(); // ok? :/
```
| Suggestion,Awaiting More Feedback | low | Major |
225,285,834 | realworld | Realistic data for RealWorld? | I wonder if it's possible/feasible/helpful to fill the production db with more realistic data from some open data sets that might be floating around. It would look better in FE demos than "aaaaa", "sample title" etc... BE repos could also use it for testing their dbs. Just a thought.
| Status: RFC,v2 changelog | low | Major |
225,301,862 | go | spec: clean up initialization language | The spec provides an value for uninitialized variables of some types, such as "The value of an uninitialized pointer is `nil`." This text is additionally redundant with the text at the end of the Variables section, which reads "A variable's value is retrieved by referring to the variable in an expression; it is the most recent value assigned to the variable. If a variable has not yet been assigned a value, its value is the zero value for its type."
However, there's an extra wrinkle here. This quoted text refers to assignment, but not to initialization. Initialization is not assignment (although expression initialization follows "the rules for assignments"). So we also need to make clear that expression initialization does count as assignment. | Documentation,NeedsInvestigation | low | Minor |
225,302,618 | go | spec: un-conflate variables and values | The notions of *variable* and *value*, although meaningfully distinct, are often conflated in the spec. Some examples:
1. Dynamic types are defined as a property of interface variables, but are properly a property of interface values. The definition of static type also treats elements of structs, arrays, and slices as variables (see next point).
2. There is a definition of structured type that provides that elements of slices, arrays, and structs and like variables. Putting aside the question of whether slices have elements or not, this is not true in any case of unaddressable arrays.
3. Pointers are defined as pointing to variables, not addressable values.
4. Variables of interface type are capable of storing values of any compatible type, but no mention is made of interface values.
5. "In other words, the switch expression is treated as if it were used to declare and initialize a temporary variable t without explicit type; it is that value of t against which each case expression x is tested for equality." does not seem like it actually clarifies anything to me; rather, it is just gymnastics to work around the possibility that values don't have a properly defined existence.
This is probably all of them, but I'm not sure. | Documentation,NeedsInvestigation | low | Minor |
225,317,432 | youtube-dl | [Go] Support live TV | ## 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.04.28*. 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.04.28**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [ ] Bug report (encountered problems with youtube-dl)
- [x] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--ignore-config', '--ap-mso', 'DTV', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', '-g', 'http://watchdisneychannel.go.com/live']
[debug] Encodings: locale cp1252, fs utf-8, out cp1252, pref cp1252
[debug] youtube-dl version 2017.04.28
[debug] Python version 3.6.1 - Windows-10-10.0.14393-SP0
[debug] exe versions: ffmpeg N-85653-gb4330a0, ffprobe N-85653-gb4330a0
[debug] Proxy map: {}
ERROR: Unable to extract show id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "c:\program files\python36\lib\site-packages\youtube_dl\YoutubeDL.py", line 760, in extract_info
ie_result = ie.extract(url)
File "c:\program files\python36\lib\site-packages\youtube_dl\extractor\common.py", line 429, in extract
ie_result = self._real_extract(url)
File "c:\program files\python36\lib\site-packages\youtube_dl\extractor\go.py", line 86, in _real_extract
show_id = self._search_regex(r'data-show-id=["\']*(SH\d+)', webpage, 'show id')
File "c:\program files\python36\lib\site-packages\youtube_dl\extractor\common.py", line 778, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract show id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: http://watchdisneychannel.go.com/live
- Single video: http://watchdisneyxd.go.com/live
- Single video: http://abc.go.com/watch-live
- Single video: http://freeform.go.com/watch-live
Note that **youtube-dl does not support sites dedicated to [copyright infringement](https://github.com/rg3/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free)**. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
---
### Description of your *issue*, suggested solution and other information
Downloading videos from go.com with a provider login is already possible, it would be nice if live TV was also supported.
| geo-restricted,tv-provider-account-needed | low | Critical |
225,326,231 | pytorch | BatchNorm should use Bessel's correction consistently | Currently, Bessel's correction is applied to the running variance estimator in BatchNorm on [this line](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/BatchNormalization.cu#L196) and the correction is not applied at train time. While the original paper for [BatchNorm](https://arxiv.org/abs/1502.03167) agrees with this, in the follow-up paper of the author, [Batch Renormalization](https://arxiv.org/abs/1702.03275), they state on page 2 when talking about BatchNorm during training:
> [...] the computation of the sample mean µ_B and sample standard deviation σ_B are part of the model architecture [...]
and on page 3 state:
> Batch Normalization, in fact, simply sets r = 1
where r is the ratio of minibatch standard deviation and estimated standard deviation, implying that during both training and testing, Bessel's correction is applied.
I think the approach for BatchNorm in Batch Renormalization makes more sense than unbiasing one variance but not the other, so I believe that PyTorch should allow an argument to BatchNorm that toggles this behaviour and perhaps consider switching the default. An argument would also bring visibility towards this implementation difference in Deep Learning frameworks.
Looking through some of the most popular DL libraries, I found no implementation that uses the unbiased variance during training and inference, but some that don't unbias either. Note that the former is essentially the same as the latter when the latter initializes gamma with the correction factor, so I imagine that they should behave mostly the same even without correcting gamma.
Some of the frameworks that don't unbias at all are: [Keras](https://github.com/fchollet/keras/blob/master/keras/layers/normalization.py#L182-L184), [Lasagne](https://github.com/Lasagne/Lasagne/blob/master/lasagne/layers/normalization.py#L297-L299), [TF-Slim](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/layers/python/layers/layers.py#L696-L697).
Some of course follow the original paper by unbiasing the running variance only: [Caffe](https://github.com/BVLC/caffe/blob/master/src/caffe/layers/batch_norm_layer.cpp#L143), [Theano](http://deeplearning.net/software/theano/library/tensor/nnet/bn.html).
Anecdotally, when biasing the running unbiased variances again by inverting Bessel's correction, I get statistically significant slightly better validation accuracies when using relatively small batch sizes (32) in densely connected networks.
cc @albanD @mruberry | module: nn,triaged,module: norms and normalization | low | Major |
225,335,100 | go | spec: an uninitialized slice (and other types) is nil, yet a slice variable is initialized to its zero (nil) value | I have two small issues with the definition of a slice type:
> A slice, once initialized, is always associated with an underlying array that holds its elements.
This is not true of a `nil` slice. Since this refers to initialization, it is talking about variables and not values. Changing this to "A non-`nil` slice value..." would probably fix this, since initialization of slices is already well-defined elsewhere.
> The capacity is a measure of that extent: it is the sum of the length of the slice and the length of the array beyond the slice; ...
This is not true of a slice whose capacity has been explicitly reduced. This is easily fixed by removing the explicit definition of capacity here and then, in the section on slice expressions, explicitly saying that the capacity of the slice `a[low:high]` is `cap(a) - low`. This also solves an ambiguity in that the capacity of `a[:]` is not actually defined and, based on the quoted statement, could be argued to extend the capacity back of up that of the underlying array if `a` is a limited-capacity slice. | Documentation,NeedsInvestigation | low | Major |
225,337,803 | rust | make install for multiple targets fails with install.sh not found | When configured for multiple targets (`--target=x86_64-unknown-linux-gnu,i686-unknown-linux-gnu,...`), `make install` exits with a file not found error while trying to install the std component for a target different from the host. Apparently, the `dist` step, which should create the `install.sh` file, is not being run for the other targets.
I'm compiling c0f86f5927377426fbaf72b17c87a6a7291406cb with the following configure args:
`./configure --prefix=/home/cesarb/opt/rust-git --android-cross-path=/home/cesarb/android-sdks/temp/arm-linux-androideabi --target=x86_64-unknown-linux-gnu,i686-unknown-linux-gnu,x86_64-pc-windows-gnu,arm-linux-androideabi,armv7-linux-androideabi`
The error message from `make install` is:
`sh: /home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-i686-unknown-linux-gnu/install.sh: Arquivo ou diretório não encontrado`
Full output from `make VERBOSE=1 install`:
```
"/usr/bin/python2.7" /home/cesarb/opt/rust-git/src/rust/src/bootstrap/bootstrap.py dist --install -v
Finished dev [unoptimized] target(s) in 0.0 secs
finding compilers
CC_x86_64-unknown-linux-gnu = "cc"
AR_x86_64-unknown-linux-gnu = "ar"
CC_x86_64-unknown-linux-gnu = "cc"
AR_x86_64-unknown-linux-gnu = "ar"
CC_i686-unknown-linux-gnu = "cc"
AR_i686-unknown-linux-gnu = "ar"
CC_x86_64-pc-windows-gnu = "x86_64-w64-mingw32-gcc"
AR_x86_64-pc-windows-gnu = "x86_64-w64-mingw32-ar"
CC_arm-linux-androideabi = "arm-linux-androideabi-gcc"
AR_arm-linux-androideabi = "arm-linux-androideabi-ar"
CC_armv7-linux-androideabi = "arm-linux-androideabi-gcc"
AR_armv7-linux-androideabi = "arm-linux-androideabi-ar"
CXX_x86_64-unknown-linux-gnu = "c++"
running sanity check
updating submodules
running: "git" "submodule" "sync"
Synchronizing submodule url for 'src/compiler-rt'
Synchronizing submodule url for 'src/doc/book'
Synchronizing submodule url for 'src/doc/nomicon'
Synchronizing submodule url for 'src/doc/reference'
Synchronizing submodule url for 'src/jemalloc'
Synchronizing submodule url for 'src/liblibc'
Synchronizing submodule url for 'src/llvm'
Synchronizing submodule url for 'src/rt/hoedown'
Synchronizing submodule url for 'src/rust-installer'
Synchronizing submodule url for 'src/tools/cargo'
Synchronizing submodule url for 'src/tools/rls'
running: "git" "reset" "--hard"
HEAD is now at c8a8767 Merge pull request #26 from TimNN/arm-cc
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at ad7de19 Merge pull request #631 from frewsxcv/new-unstable-book-links
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 616b984 Merge pull request #3 from rust-lang-nursery/add-readme
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 6b0de90 Merge pull request #43 from frewsxcv/fix-link
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 11bfb0d Merge pull request #16 from glandium/rust
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at c34a802 Auto merge of #572 - malbarbo:android-x86_64, r=alexcrichton
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 15745af Merge pull request #75 from pftbest/fix_msp430
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at da282f1 Merge pull request #8 from GuillaumeGomez/line_information
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 4f99485 Merge pull request #54 from brson/docdir
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at fa7584c Auto merge of #3921 - alexcrichton:less-asserts, r=matklad
running: "git" "clean" "-fdx"
running: "git" "reset" "--hard"
HEAD is now at 67babd2 Update README.md
running: "git" "clean" "-fdx"
learning about cargo
bootstrap top targets:
Step { name: "install", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
bootstrap build plan:
Step { name: "dist-src", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "llvm", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "create-sysroot", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "startup-objects", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "rustc", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-std", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libstd-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-test", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libtest-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "may-run-build-script", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-rustc-main", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libstd", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libtest", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc-tool", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "maybe-clean-tools", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "tool-rustbook", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-reference", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "create-sysroot", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "rustc", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "startup-objects", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-std", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libstd-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "may-run-build-script", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-test", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libtest-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "build-crate-rustc-main", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "create-sysroot", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "startup-objects", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libstd-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libtest-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-crate-std", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-crate-rustc-main", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "tool-error-index", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-error-index", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-standalone", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-nomicon", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-book", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "doc-unstable-book", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "dist-docs", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "dist-mingw", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "dist-std", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libstd", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "libtest", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "librustc", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "rustc", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "dist-rustc", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Step { name: "install", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "dist-src", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Dist src
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "vendor"
add this to your .cargo/config for this project:
[source.crates-io]
registry = 'https://github.com/rust-lang/crates.io-index'
replace-with = 'vendored-sources'
[source.vendored-sources]
directory = '/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rustc-1.19.0-dev-src/src/vendor'
running: "tar" "-czf" "/home/cesarb/opt/rust-git/src/rust/build/dist/rustc-1.19.0-dev-src.tar.gz" "rustc-1.19.0-dev-src"
running: "sh" "/home/cesarb/opt/rust-git/src/rust/src/rust-installer/gen-installer.sh" "--product-name=Rust" "--rel-manifest-dir=rustlib" "--success-message=Awesome-Source." "--image-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-src-1.19.0-dev-image" "--work-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist" "--output-dir=/home/cesarb/opt/rust-git/src/rust/build/dist" "--package-name=rust-src-1.19.0-dev" "--component-name=rust-src" "--legacy-manifest-dirs=rustlib,cargo"
gen-installer: looking for programs
gen-installer:
gen-installer: found tar
gen-installer: found cp
gen-installer: found rm
gen-installer: found mkdir
gen-installer: found echo
gen-installer: found tr
gen-installer: found awk
gen-installer:
gen-installer: processing arguments
gen-installer:
gen-installer: CFG_PRODUCT_NAME := Rust
gen-installer: CFG_COMPONENT_NAME := rust-src
gen-installer: CFG_PACKAGE_NAME := rust-src-1.19.0-dev
gen-installer: CFG_REL_MANIFEST_DIR := rustlib
gen-installer: CFG_SUCCESS_MESSAGE := Awesome-Source.
gen-installer: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-installer: CFG_NON_INSTALLED_OVERLAY :=
gen-installer: CFG_BULK_DIRS :=
gen-installer: CFG_IMAGE_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_WORK_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_OUTPUT_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer:
gen-installer: validating arguments
gen-installer:
gen-install-script: looking for install programs
gen-install-script:
gen-install-script: found sed
gen-install-script: found chmod
gen-install-script: found cat
gen-install-script:
gen-install-script: processing arguments
gen-install-script:
gen-install-script: CFG_PRODUCT_NAME := Rust
gen-install-script: CFG_REL_MANIFEST_DIR := rustlib
gen-install-script: CFG_SUCCESS_MESSAGE := Awesome-Source.
gen-install-script: CFG_OUTPUT_SCRIPT := /home/cesarb/opt/rust-git/src/rust/ ...
gen-install-script: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-install-script:
gen-install-script: validating arguments
gen-install-script:
executing step Step { name: "llvm", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "create-sysroot", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "startup-objects", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "rustc", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "build-crate-std", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--features" "panic-unwind jemalloc backtrace" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/libstd/Cargo.toml"
Fresh gcc v0.3.45
Fresh libc v0.2.21
Fresh core v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcore)
Fresh cmake v0.1.22
Fresh filetime v0.1.10
Fresh std_unicode v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd_unicode)
Fresh alloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc)
Fresh rand v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librand)
Fresh build_helper v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/build_helper)
Fresh libc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/rustc/libc_shim)
Fresh collections v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcollections)
Fresh alloc_system v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_system)
Fresh panic_abort v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_abort)
Fresh alloc_jemalloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_jemalloc)
Fresh rustc_lsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_lsan)
Fresh unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libunwind)
Fresh rustc_tsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_tsan)
Fresh rustc_asan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_asan)
Fresh panic_unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_unwind)
Fresh compiler_builtins v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcompiler_builtins)
Fresh rustc_msan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_msan)
Fresh std v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "libstd-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage0 std from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "build-crate-test", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage0 test artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/libtest/Cargo.toml"
Fresh term v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libterm)
Fresh getopts v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libgetopts)
Fresh test v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libtest)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "libtest-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage0 test from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "may-run-build-script", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "build-crate-rustc-main", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--features" " jemalloc" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/rustc/Cargo.toml"
Fresh rustc_platform_intrinsics v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_platform_intrinsics)
Fresh fmt_macros v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libfmt_macros)
Fresh bitflags v0.8.2
Fresh serialize v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libserialize)
Fresh rustc_bitflags v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_bitflags)
Fresh arena v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libarena)
Fresh gcc v0.3.45
Fresh syntax_pos v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax_pos)
Fresh log v0.3.7
Fresh rustc-serialize v0.3.23
Fresh rustc_errors v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_errors)
Fresh rustc_data_structures v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_data_structures)
Fresh rls-span v0.1.0
Fresh env_logger v0.4.2
Fresh syntax v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax)
Fresh rls-data v0.1.0
Fresh pulldown-cmark v0.0.14
Fresh graphviz v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libgraphviz)
Fresh proc_macro v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libproc_macro)
Fresh rustc_const_math v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_const_math)
Fresh rustc_back v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_back)
Fresh libc v0.2.21
Fresh syntax_ext v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax_ext)
Fresh filetime v0.1.10
Fresh build_helper v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/build_helper)
Fresh rustc_llvm v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_llvm)
Fresh flate v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libflate)
Fresh rustc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc)
Fresh rustc_resolve v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_resolve)
Fresh rustc_privacy v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_privacy)
Fresh rustc_save_analysis v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_save_analysis)
Fresh rustc_metadata v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_metadata)
Fresh rustc_const_eval v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_const_eval)
Fresh rustc_incremental v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_incremental)
Fresh rustc_typeck v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_typeck)
Fresh rustc_plugin v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_plugin)
Fresh rustc_mir v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_mir)
Fresh rustc_trans v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_trans)
Fresh rustc_passes v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_passes)
Fresh proc_macro_plugin v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libproc_macro_plugin)
Fresh rustc_borrowck v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_borrowck)
Fresh rustc_lint v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_lint)
Fresh rustc_driver v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_driver)
Fresh rustdoc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustdoc)
Fresh rustc-main v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/rustc)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "librustc-link", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage0 rustc from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "libstd", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "libtest", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "librustc", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "librustc-tool", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "maybe-clean-tools", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "tool-rustbook", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage0 tool rustbook (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/tools/rustbook/Cargo.toml"
Fresh utf8-ranges v1.0.0
Fresh unicode-segmentation v1.1.0
Fresh itoa v0.3.1
Fresh ansi_term v0.9.0
Fresh serde v0.9.11
Fresh strsim v0.6.0
Fresh num-traits v0.1.37
Fresh toml v0.3.1
Fresh pest v0.3.3
Fresh log v0.3.7
Fresh libc v0.2.21
Fresh getopts v0.2.14
Fresh bitflags v0.8.2
Fresh unicode-width v0.1.4
Fresh thread-id v3.0.0
Fresh atty v0.2.2
Fresh memchr v1.0.1
Fresh bitflags v0.5.0
Fresh dtoa v0.4.1
Fresh term_size v0.2.3
Fresh lazy_static v0.2.5
Fresh pulldown-cmark v0.0.8
Fresh serde_json v0.9.9
Fresh quick-error v1.1.0
Fresh regex-syntax v0.4.0
Fresh void v1.0.2
Fresh vec_map v0.7.0
Fresh rustc-serialize v0.3.23
Fresh aho-corasick v0.6.3
Fresh unreachable v0.1.1
Fresh clap v2.22.1
Fresh open v1.2.0
Fresh thread_local v0.3.3
Fresh regex v0.2.1
Fresh env_logger v0.4.2
Fresh handlebars v0.25.2
Fresh mdbook v0.0.21
Fresh rustbook v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/tools/rustbook)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "doc-reference", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "create-sysroot", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "rustc", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage1 compiler (x86_64-unknown-linux-gnu)
executing step Step { name: "startup-objects", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "build-crate-std", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage1 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--features" "panic-unwind jemalloc backtrace" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/libstd/Cargo.toml"
Fresh libc v0.2.21
Fresh core v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcore)
Fresh filetime v0.1.10
Fresh gcc v0.3.45
Fresh cmake v0.1.22
Fresh build_helper v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/build_helper)
Fresh alloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc)
Fresh std_unicode v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd_unicode)
Fresh libc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/rustc/libc_shim)
Fresh collections v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcollections)
Fresh panic_abort v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_abort)
Fresh rand v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librand)
Fresh alloc_system v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_system)
Fresh rustc_asan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_asan)
Fresh unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libunwind)
Fresh rustc_msan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_msan)
Fresh rustc_lsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_lsan)
Fresh panic_unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_unwind)
Fresh compiler_builtins v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcompiler_builtins)
Fresh alloc_jemalloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_jemalloc)
Fresh rustc_tsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_tsan)
Fresh std v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "libstd-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage1 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "may-run-build-script", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "build-crate-test", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage1 test artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/libtest/Cargo.toml"
Fresh term v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libterm)
Fresh getopts v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libgetopts)
Fresh test v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libtest)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "libtest-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage1 test from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "build-crate-rustc-main", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage1 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--features" " jemalloc" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/rustc/Cargo.toml"
Fresh log v0.3.7
Fresh rustc-serialize v0.3.23
Fresh fmt_macros v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libfmt_macros)
Fresh serialize v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libserialize)
Fresh arena v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libarena)
Fresh graphviz v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libgraphviz)
Fresh rustc_bitflags v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_bitflags)
Fresh bitflags v0.8.2
Fresh libc v0.2.21
Fresh syntax_pos v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax_pos)
Fresh rustc_errors v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_errors)
Fresh filetime v0.1.10
Fresh build_helper v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/build_helper)
Fresh rustc_platform_intrinsics v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_platform_intrinsics)
Fresh gcc v0.3.45
Fresh rustc_llvm v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_llvm)
Fresh env_logger v0.4.2
Fresh rustc_data_structures v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_data_structures)
Fresh syntax v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax)
Fresh rustc_back v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_back)
Fresh rls-span v0.1.0
Fresh rustc_const_math v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_const_math)
Fresh rls-data v0.1.0
Fresh rustc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc)
Fresh rustc_const_eval v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_const_eval)
Fresh rustc_resolve v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_resolve)
Fresh rustc_save_analysis v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_save_analysis)
Fresh rustc_lint v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_lint)
Fresh rustc_typeck v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_typeck)
Fresh rustc_privacy v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_privacy)
Fresh rustc_passes v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_passes)
Fresh rustc_mir v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_mir)
Fresh rustc_borrowck v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_borrowck)
Fresh rustc_incremental v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_incremental)
Fresh proc_macro v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libproc_macro)
Fresh syntax_ext v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax_ext)
Fresh flate v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libflate)
Fresh rustc_trans v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_trans)
Fresh rustc_metadata v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_metadata)
Fresh rustc_plugin v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_plugin)
Fresh proc_macro_plugin v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libproc_macro_plugin)
Fresh rustc_driver v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_driver)
Fresh pulldown-cmark v0.0.14
Fresh rustdoc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustdoc)
Fresh rustc-main v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/rustc)
Finished release [optimized] target(s) in 0.3 secs
executing step Step { name: "librustc-link", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage1 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "create-sysroot", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "startup-objects", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "libstd-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage2 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "libtest-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage2 test from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "librustc-link", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
executing step Step { name: "doc-crate-std", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Documenting stage2 std (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "doc" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/libstd/Cargo.toml" "--features" "panic-unwind jemalloc backtrace" "--no-deps" "-p" "alloc" "-p" "collections" "-p" "core" "-p" "std" "-p" "std_unicode"
Fresh gcc v0.3.45
Fresh core v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcore)
Fresh cmake v0.1.22
Fresh libc v0.2.21
Fresh rand v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librand)
Fresh filetime v0.1.10
Fresh std_unicode v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd_unicode)
Fresh alloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc)
Fresh libc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/rustc/libc_shim)
Fresh build_helper v0.1.0 (file:///home/cesarb/opt/rust-git/src/rust/src/build_helper)
Fresh collections v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcollections)
Fresh unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libunwind)
Fresh alloc_system v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_system)
Fresh panic_unwind v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_unwind)
Fresh panic_abort v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libpanic_abort)
Fresh rustc_lsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_lsan)
Fresh compiler_builtins v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libcompiler_builtins)
Fresh rustc_asan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_asan)
Fresh rustc_msan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_msan)
Fresh rustc_tsan v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_tsan)
Fresh alloc_jemalloc v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/liballoc_jemalloc)
Fresh std v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libstd)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "doc-crate-rustc-main", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Documenting stage2 compiler (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "doc" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/rustc/Cargo.toml" "--features" " jemalloc" "--no-deps" "-p" "proc_macro"
Fresh serialize v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libserialize)
Fresh rustc_bitflags v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_bitflags)
Fresh log v0.3.7
Fresh rustc_data_structures v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_data_structures)
Fresh syntax_pos v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax_pos)
Fresh rustc_errors v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/librustc_errors)
Fresh syntax v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libsyntax)
Fresh proc_macro v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/libproc_macro)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "tool-error-index", stage: 0, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Building stage0 tool error_index_generator (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "-j" "4" "--target" "x86_64-unknown-linux-gnu" "-v" "--release" "--manifest-path" "/home/cesarb/opt/rust-git/src/rust/src/tools/error_index_generator/Cargo.toml"
Fresh error_index_generator v0.0.0 (file:///home/cesarb/opt/rust-git/src/rust/src/tools/error_index_generator)
Finished release [optimized] target(s) in 0.0 secs
executing step Step { name: "doc-error-index", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Documenting error index (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0-tools/x86_64-unknown-linux-gnu/release/error_index_generator" "html" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/error-index.html"
executing step Step { name: "doc-standalone", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Documenting standalone (x86_64-unknown-linux-gnu)
executing step Step { name: "doc-nomicon", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "doc-book", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Documenting book index (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/index.md" "--markdown-css" "rust.css"
Documenting book redirect pages (x86_64-unknown-linux-gnu)
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/variable-bindings.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/casting-between-types.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/enums.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/drop.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/choosing-your-guarantees.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/mutability.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/ownership.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/effective-rust.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/if.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/crates-and-modules.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/patterns.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/raw-pointers.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/functions.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/using-rust-without-the-standard-library.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/documentation.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/structs.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/lifetimes.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/strings.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/compiler-plugins.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/loops.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/README.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/bibliography.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/type-aliases.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/syntax-and-semantics.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/match.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/testing.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/concurrency.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/guessing-game.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/unsized-types.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/unsafe.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/method-syntax.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/macros.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/syntax-index.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/error-handling.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/deref-coercions.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/ufcs.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/SUMMARY.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/iterators.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/generics.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/the-stack-and-the-heap.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/traits.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/if-let.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/comments.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/glossary.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/attributes.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/trait-objects.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/const-and-static.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/vectors.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/primitive-types.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/release-channels.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/procedural-macros.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/closures.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/operators-and-overloading.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/ffi.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/conditional-compilation.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/getting-started.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/borrow-and-asref.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/associated-types.md" "--markdown-css" "rust.css"
running: "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustdoc" "--html-after-content" "/home/cesarb/opt/rust-git/src/rust/src/doc/footer.inc" "--html-before-content" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/version_info.html" "--html-in-header" "/home/cesarb/opt/rust-git/src/rust/src/doc/favicon.inc" "--markdown-playground-url" "https://play.rust-lang.org/" "-o" "/home/cesarb/opt/rust-git/src/rust/build/x86_64-unknown-linux-gnu/doc/book" "/home/cesarb/opt/rust-git/src/rust/src/doc/book/redirects/references-and-borrowing.md" "--markdown-css" "rust.css"
executing step Step { name: "doc-unstable-book", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "dist-docs", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Dist docs stage2 (x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/src/rust-installer/gen-installer.sh" "--product-name=Rust-Documentation" "--rel-manifest-dir=rustlib" "--success-message=Rust-documentation-is-installed." "--image-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-docs-1.19.0-dev-x86_64-unknown-linux-gnu-image" "--work-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist" "--output-dir=/home/cesarb/opt/rust-git/src/rust/build/dist" "--package-name=rust-docs-1.19.0-dev-x86_64-unknown-linux-gnu" "--component-name=rust-docs" "--legacy-manifest-dirs=rustlib,cargo" "--bulk-dirs=share/doc/rust/html"
gen-installer: looking for programs
gen-installer:
gen-installer: found tar
gen-installer: found cp
gen-installer: found rm
gen-installer: found mkdir
gen-installer: found echo
gen-installer: found tr
gen-installer: found awk
gen-installer:
gen-installer: processing arguments
gen-installer:
gen-installer: CFG_PRODUCT_NAME := Rust-Documentation
gen-installer: CFG_COMPONENT_NAME := rust-docs
gen-installer: CFG_PACKAGE_NAME := rust-docs-1.19.0-dev-x86_64-unknown ...
gen-installer: CFG_REL_MANIFEST_DIR := rustlib
gen-installer: CFG_SUCCESS_MESSAGE := Rust-documentation-is-installed.
gen-installer: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-installer: CFG_NON_INSTALLED_OVERLAY :=
gen-installer: CFG_BULK_DIRS := share/doc/rust/html
gen-installer: CFG_IMAGE_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_WORK_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_OUTPUT_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer:
gen-installer: validating arguments
gen-installer:
gen-install-script: looking for install programs
gen-install-script:
gen-install-script: found sed
gen-install-script: found chmod
gen-install-script: found cat
gen-install-script:
gen-install-script: processing arguments
gen-install-script:
gen-install-script: CFG_PRODUCT_NAME := Rust-Documentation
gen-install-script: CFG_REL_MANIFEST_DIR := rustlib
gen-install-script: CFG_SUCCESS_MESSAGE := Rust-documentation-is-installed.
gen-install-script: CFG_OUTPUT_SCRIPT := /home/cesarb/opt/rust-git/src/rust/ ...
gen-install-script: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-install-script:
gen-install-script: validating arguments
gen-install-script:
executing step Step { name: "dist-mingw", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "dist-std", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Dist std stage2 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/src/rust-installer/gen-installer.sh" "--product-name=Rust" "--rel-manifest-dir=rustlib" "--success-message=std-is-standing-at-the-ready." "--image-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-x86_64-unknown-linux-gnu-image" "--work-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist" "--output-dir=/home/cesarb/opt/rust-git/src/rust/build/dist" "--package-name=rust-std-1.19.0-dev-x86_64-unknown-linux-gnu" "--component-name=rust-std-x86_64-unknown-linux-gnu" "--legacy-manifest-dirs=rustlib,cargo"
gen-installer: looking for programs
gen-installer:
gen-installer: found tar
gen-installer: found cp
gen-installer: found rm
gen-installer: found mkdir
gen-installer: found echo
gen-installer: found tr
gen-installer: found awk
gen-installer:
gen-installer: processing arguments
gen-installer:
gen-installer: CFG_PRODUCT_NAME := Rust
gen-installer: CFG_COMPONENT_NAME := rust-std-x86_64-unknown-linux-gnu
gen-installer: CFG_PACKAGE_NAME := rust-std-1.19.0-dev-x86_64-unknown- ...
gen-installer: CFG_REL_MANIFEST_DIR := rustlib
gen-installer: CFG_SUCCESS_MESSAGE := std-is-standing-at-the-ready.
gen-installer: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-installer: CFG_NON_INSTALLED_OVERLAY :=
gen-installer: CFG_BULK_DIRS :=
gen-installer: CFG_IMAGE_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_WORK_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_OUTPUT_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer:
gen-installer: validating arguments
gen-installer:
gen-install-script: looking for install programs
gen-install-script:
gen-install-script: found sed
gen-install-script: found chmod
gen-install-script: found cat
gen-install-script:
gen-install-script: processing arguments
gen-install-script:
gen-install-script: CFG_PRODUCT_NAME := Rust
gen-install-script: CFG_REL_MANIFEST_DIR := rustlib
gen-install-script: CFG_SUCCESS_MESSAGE := std-is-standing-at-the-ready.
gen-install-script: CFG_OUTPUT_SCRIPT := /home/cesarb/opt/rust-git/src/rust/ ...
gen-install-script: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-install-script:
gen-install-script: validating arguments
gen-install-script:
executing step Step { name: "libstd", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "libtest", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "librustc", stage: 1, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
executing step Step { name: "rustc", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Copying stage2 compiler (x86_64-unknown-linux-gnu)
executing step Step { name: "dist-rustc", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Dist rustc stage2 (x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/src/rust-installer/gen-installer.sh" "--product-name=Rust" "--rel-manifest-dir=rustlib" "--success-message=Rust-is-ready-to-roll." "--image-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rustc-1.19.0-dev-x86_64-unknown-linux-gnu-image" "--work-dir=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist" "--output-dir=/home/cesarb/opt/rust-git/src/rust/build/dist" "--non-installed-overlay=/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rustc-1.19.0-dev-x86_64-unknown-linux-gnu-overlay" "--package-name=rustc-1.19.0-dev-x86_64-unknown-linux-gnu" "--component-name=rustc" "--legacy-manifest-dirs=rustlib,cargo"
gen-installer: looking for programs
gen-installer:
gen-installer: found tar
gen-installer: found cp
gen-installer: found rm
gen-installer: found mkdir
gen-installer: found echo
gen-installer: found tr
gen-installer: found awk
gen-installer:
gen-installer: processing arguments
gen-installer:
gen-installer: CFG_PRODUCT_NAME := Rust
gen-installer: CFG_COMPONENT_NAME := rustc
gen-installer: CFG_PACKAGE_NAME := rustc-1.19.0-dev-x86_64-unknown-lin ...
gen-installer: CFG_REL_MANIFEST_DIR := rustlib
gen-installer: CFG_SUCCESS_MESSAGE := Rust-is-ready-to-roll.
gen-installer: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-installer: CFG_NON_INSTALLED_OVERLAY := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_BULK_DIRS :=
gen-installer: CFG_IMAGE_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_WORK_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer: CFG_OUTPUT_DIR := /home/cesarb/opt/rust-git/src/rust/ ...
gen-installer:
gen-installer: validating arguments
gen-installer:
gen-install-script: looking for install programs
gen-install-script:
gen-install-script: found sed
gen-install-script: found chmod
gen-install-script: found cat
gen-install-script:
gen-install-script: processing arguments
gen-install-script:
gen-install-script: CFG_PRODUCT_NAME := Rust
gen-install-script: CFG_REL_MANIFEST_DIR := rustlib
gen-install-script: CFG_SUCCESS_MESSAGE := Rust-is-ready-to-roll.
gen-install-script: CFG_OUTPUT_SCRIPT := /home/cesarb/opt/rust-git/src/rust/ ...
gen-install-script: CFG_LEGACY_MANIFEST_DIRS := rustlib,cargo
gen-install-script:
gen-install-script: validating arguments
gen-install-script:
executing step Step { name: "install", stage: 2, host: "x86_64-unknown-linux-gnu", target: "x86_64-unknown-linux-gnu" }
Install docs stage2 (x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-docs-1.19.0-dev-x86_64-unknown-linux-gnu/install.sh" "--prefix=/home/cesarb/opt/rust-git" "--docdir=/home/cesarb/opt/rust-git/share/doc/rust" "--libdir=/home/cesarb/opt/rust-git/lib" "--mandir=/home/cesarb/opt/rust-git/share/man" "--disable-ldconfig"
install: uninstalling component 'rust-docs'
install: creating uninstall script at /home/cesarb/opt/rust-git/lib/rustlib/uninstall.sh
install: installing component 'rust-docs'
Rust documentation is installed.
Install std stage2 (x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-x86_64-unknown-linux-gnu/install.sh" "--prefix=/home/cesarb/opt/rust-git" "--docdir=/home/cesarb/opt/rust-git/share/doc/rust" "--libdir=/home/cesarb/opt/rust-git/lib" "--mandir=/home/cesarb/opt/rust-git/share/man" "--disable-ldconfig"
install: uninstalling component 'rust-std-x86_64-unknown-linux-gnu'
install: creating uninstall script at /home/cesarb/opt/rust-git/lib/rustlib/uninstall.sh
install: installing component 'rust-std-x86_64-unknown-linux-gnu'
std is standing at the ready.
Install std stage2 (x86_64-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-x86_64-unknown-linux-gnu/install.sh" "--prefix=/home/cesarb/opt/rust-git" "--docdir=/home/cesarb/opt/rust-git/share/doc/rust" "--libdir=/home/cesarb/opt/rust-git/lib" "--mandir=/home/cesarb/opt/rust-git/share/man" "--disable-ldconfig"
install: uninstalling component 'rust-std-x86_64-unknown-linux-gnu'
install: creating uninstall script at /home/cesarb/opt/rust-git/lib/rustlib/uninstall.sh
install: installing component 'rust-std-x86_64-unknown-linux-gnu'
std is standing at the ready.
Install std stage2 (i686-unknown-linux-gnu)
running: "sh" "/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-i686-unknown-linux-gnu/install.sh" "--prefix=/home/cesarb/opt/rust-git" "--docdir=/home/cesarb/opt/rust-git/share/doc/rust" "--libdir=/home/cesarb/opt/rust-git/lib" "--mandir=/home/cesarb/opt/rust-git/share/man" "--disable-ldconfig"
sh: /home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-i686-unknown-linux-gnu/install.sh: Arquivo ou diretório não encontrado
command did not execute successfully: "sh" "/home/cesarb/opt/rust-git/src/rust/build/tmp/dist/rust-std-1.19.0-dev-i686-unknown-linux-gnu/install.sh" "--prefix=/home/cesarb/opt/rust-git" "--docdir=/home/cesarb/opt/rust-git/share/doc/rust" "--libdir=/home/cesarb/opt/rust-git/lib" "--mandir=/home/cesarb/opt/rust-git/share/man" "--disable-ldconfig"
expected success, got: exit code: 127
Build completed unsuccessfully in 0:01:02
Makefile:71: recipe for target 'install' failed
make: *** [install] Error 1
``` | T-bootstrap,C-bug | low | Critical |
225,343,054 | realworld | Support Bearer for authentication scheme | The RFC specification requires the use of '**Bearer**' as the authentication scheme. The '**Bearer**' scheme is also registered with the IANA. Most JWT packages and tools use '**Bearer**' as the default scheme.
http://www.iana.org/assignments/http-authschemes/http-authschemes.xhtml
https://tools.ietf.org/html/rfc6750
https://tools.ietf.org/html/rfc7523
https://en.wikipedia.org/wiki/JSON_Web_Token | Status: RFC,v2 changelog | low | Major |
225,358,791 | rust | Improve diagnostics for parse errors in proc macro output | Currently we make no real effort to inform users of parse errors in procedural macro output: https://github.com/rust-lang/rust/blob/9c15de4fd59bee290848b5443c7e194fd5afb02c/src/libsyntax_ext/deriving/custom.rs#L105
People are stumbling on this in the wild: https://www.reddit.com/r/rust/comments/689ogb/how_to_debug_procmacro_derive_produced/
CC @nrc @jseyfried
I have some ideas on how to move forward but should we wait until #40939 lands? I don't think it's necessary since the changes would be (mostly) orthogonal. | A-diagnostics,A-parser,T-compiler,A-proc-macros | medium | Critical |
225,420,725 | go | runtime/pprof: nil pointer panic in TestMathBigDivide and android/arm | The Android/arm builder failed once:
https://build.golang.org/log/49d8e3585a3501d3f82d92c762aa3d5724d45198
with the stack trace:
````
--- FAIL: TestMathBigDivide (0.31s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xf738b874]
goroutine 53 [running]:
testing.tRunner.func1(0xd7038120)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:712 +0x22c
panic(0xf740cef8, 0xf74e1418)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/panic.go:489 +0x218
runtime/pprof.fprintStack(0xf74e4e68, 0xd700c000, 0xd74700f0, 0x2, 0x2)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:340 +0x54
runtime/pprof.profileOk.func1(0x1, 0xd74700f0, 0x2, 0x2, 0x0)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:183 +0xd4
runtime/pprof.parseProfile(0xd7038120, 0xd7002d00, 0x719, 0x890, 0xd6fb5ea4)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:97 +0x130
runtime/pprof.profileOk(0xd7038120, 0x0, 0x0, 0x0, 0xd7002d00, 0x719, 0x890, 0x0, 0x0, 0x88b1f, ...)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:181 +0x110
runtime/pprof.testCPUProfile(0xd7038120, 0x0, 0x0, 0x0, 0xf742a140)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:140 +0x11c
runtime/pprof.TestMathBigDivide(0xd7038120)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/runtime/pprof/pprof_test.go:349 +0x3c
testing.tRunner(0xd7038120, 0xf742a144)
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:747 +0xbc
created by testing.(*T).Run
/private/var/folders/f6/d2bhfqss2716nxm8gkv1fmb80000gn/T/workdir-host-darwin-amd64-eliasnaur-android/go/src/testing/testing.go:789 +0x288
exitcode=2go_android_exec: adb shell rm -rf /data/local/tmp/pprof.test-31327
FAIL runtime/pprof 5.818s
````
I'm filing this issue so that we don't forget and in case someone else have an idea why it happens. | NeedsInvestigation,mobile,compiler/runtime | low | Critical |
225,429,243 | youtube-dl | Allow to keep all intermediate files. | ### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.05.01*. 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.05.01**
### 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)
- [ ] Site support request (request for adding support for a new site)
- [x] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### Description of your *issue*, suggested solution and other information
Reference: https://github.com/rg3/youtube-dl/pull/12949#discussion_r114120437
Not all temporary files are covered by ```--keep-video``` and ```--keep-fragments```. For example, metadata files from #12949 or PhantomJS scripts from #12754. Once those PRs are merged, I hope there will be an option to leave all temporary files so that debugging is easier. | request | low | Critical |
225,450,828 | TypeScript | Enum not block-scoped given closure and --target es5 | **TypeScript Version:** nightly 2.4.0-dev.20170501
**Code**
```ts
let getE;
{
enum E { A = 1 }
getE = () => E;
}
{
enum E { A = 3 }
}
console.log(getE().A);
```
**Expected behavior:**
Always prints `1`.
**Actual behavior:**
Prints `3` under `--target es5`.
This issue is similar to #15403 but requires a closure to reproduce. CC @rbuckton | Bug | low | Minor |
225,479,172 | opencv | Support for CODEC_ID_H264_OMX | ##### System information (version)
- OpenCV => 3.2
- Operating System / Platform => Raspberry Pi
##### Detailed description
On the Raspberry Pi, OpenMax (h264_omx) can be enabled while compiling FFMPEG. However there doesn't seem a way with OpenCV to specify the h264_omx codec in the VideoWriter class.
https://github.com/opencv/opencv/blob/master/modules/videoio/src/ffmpeg_codecs.hpp
| feature,priority: low,category: videoio | low | Major |
225,491,008 | TypeScript | Flag boolean in comparison operator operands as errors | From https://github.com/Microsoft/TypeScript/issues/15444#issuecomment-298055832
```ts
var x: boolean, y: boolean;
if (x > y) { // suspicious!
}
``` | Suggestion,Help Wanted,Good First Issue | low | Critical |
225,517,013 | youtube-dl | [bbc.co.uk] bug: Downloading Audio Described version now grabs Original version | ### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.05.01*. 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.05.01**
### Before submitting an *issue* make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your *issue*?
- [x] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other
---
### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*
---
### If the purpose of this *issue* is a *bug report*, *site support request* or you are not completely sure provide the full verbose output as follows:
Add `-v` flag to **your command line** you run youtube-dl with, copy the **whole** output and insert it here. It should look similar to one below (replace it with **your** log inserted between triple ```):
```
Partial log:
$ youtube-dl --verbose --abort-on-unavailable-fragment -f bestaudio http://www.bbc.co.uk/iplayer/episode/p048h1s0/ad/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '--abort-on-unavailable-fragment', '-f', 'bestaudio', 'http://www.bbc.co.uk/iplayer/episode/p048h1s0/ad/']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.05.01
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: ffmpeg 3.2.2, ffprobe 3.2.2, rtmpdump 2.4
[debug] Proxy map: {}
[bbc.co.uk] p048h1s0: Downloading video page
[bbc.co.uk] p048h1s0: Downloading playlist JSON
[bbc.co.uk] p04cb0dw: Downloading media selection XML
...
<end of log>
```
---
### If the purpose of this *issue* is a *site support request* please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Single video: http://www.bbc.co.uk/iplayer/episode/p048h1s0/ad/
- Single video: http://www.bbc.co.uk/iplayer/episode/p04c1bs4/ad/class-series-1-2-the-coach-with-the-dragon-tattoo
- Referenced series: http://www.bbc.co.uk/iplayer/episodes/p048h1bz
Note that **youtube-dl does not support sites dedicated to [copyright infringement](https://github.com/rg3/youtube-dl#can-you-add-support-for-this-anime-video-site-or-site-which-shows-current-movies-for-free)**. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
---
### Description of your *issue*, suggested solution and other information
The problem: When passing the Audio Described URL of a BBC iPlayer programme, youtube-dl _now_ grabs the normal/Original version instead. I assume this started happening when the BBC took down the XML feeds.
Opening the [playlist JSON](http://www.bbc.co.uk/programmes/p048h1s0.json) in a web browser (Firefox 53.0), the "Dubbed Audio Described" VPID is p04nzc8r, so the last line should have read:
`[bbc.co.uk] p04nzc8r: Downloading media selection XML`
and not
`[bbc.co.uk] p04cb0dw: Downloading media selection XML`
which is the PID for the "Original version."
How to fix: I'm not sure. I changed the user agent of my web browser to mirror what youtube-dl uses, but the JSON output is still different from when I ran youtube-dl with --write-pages.
In any case, when running youtube-dl with an iPlayer URL for an audio Described page, it should grab the "Dubbed Audio Described" version from the playlist JSON. | geo-restricted | low | Critical |
225,523,798 | svelte | Equivalent of Vue's out-in transition mode | For elements that are positioned statically or relatively, intros that happen at the same time as outros can be problematic:
```html
{{#if foo}}
<div transition:fade='{duration:1500}'>yep</div>
{{else}}
<div transition:fade='{duration:1500}'>nope</div>
{{/if}}
```
Vue has a nice solution to this — [transition modes](https://vuejs.org/v2/guide/transitions.html#Transition-Modes). Since Svelte doesn't have an equivalent of `<transition>`, the concept doesn't translate directly, but it would be nice to be able to express something similar without the hacky use of `delay`. | feature request,temp-stale | medium | Major |
225,529,318 | TypeScript | Cannot have array binding patterns without iterable extensions | **TypeScript Version:** 2.2.1 / nightly (2.2.0-dev.201xxxxx)
**Code**
```ts
declare function f([x, y]: [number, string]): void;
```
**Expected behavior:**
`src/a.ts(1,20): error TS1337: Destructuring is not allowed in a declaration.`
**Actual behavior:**
`src/a.ts(1,20): error TS2488: Type must have a '[Symbol.iterator]()' method that returns an iterator.`
For an object destructuring `{ x, y }: { x: number, y: string }` we currently give no error at all, but we probably should. | Bug | low | Critical |
225,532,086 | svelte | Staggered transitions | A common requirement is to *stagger* transitions:
In the GIF, it's been faked with an index and a delay:
```html
<g class='bars'>
{{#each points as point, i}}
{{#if show}}
<rect
in:grow='{delay: i*200}'
out:fade
x='{{xScale(i) + 2}}'
y='{{yScale(point.birthrate)}}'
width='{{ barWidth - 4 }}'
height='{{ height - padding.bottom - yScale(point.birthrate) }}'
></rect>
{{/if}}
{{/each}}
</g>
```
But that doesn't work well if new items are added, since their indices will start at *n* rather than 0.
If the intro is aborted (`show` becomes false, in the example above), if we have staggered outros then we probably want to a) reverse the stagger (last-in-first-out), and b) ignore any intro transitions that haven't yet started, so that the subject of the most recently started intro transition starts to outro immediately. That would be very hard to do with delays.
Not sure what that would look like. It probably needs to be a separate directive — something like this (means 'start each intro transition 200ms after the last one, and each outro transition 50ms after the last one but go backwards'):
```html
<rect
in:grow
stagger:in=200
stagger:out=-50
...
```
Something else you *might* want to do is supply a fraction rather than an absolute number. This variant means 'start each intro transition once the previous one is 80% done, but use a fixed 50ms interval for outros':
```html
<rect
in:grow
stagger:in=0.8
stagger:out=-50ms
...
```
Any thoughts? | feature request,stale-bot,temp-stale | low | Major |
225,535,669 | go | runtime/pprof: improve docs around short-lived processes | ### What version of Go are you using (`go version`)?
`go version go1.8.1 darwin/amd64`
### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/v832043/Code"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.8.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/zj/hgnczfs53zg8s4_d_t686715y61ynl/T/go-build686693782=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
```
### What did you do?
Added basic CPU profiling code to `main()`:
```
f, err := os.Create("test.prof")
if err != nil {
log.Fatal(err)
}
pprof.StartCPUProfile(f)
defer pprof.StopCPUProfile()
```
Then I ran my program and threw a load tester at it.
### What did you expect to see?
Data in `test.prof` after gracefully exiting my program.
### What did you see instead?
After heavily loading my program with a load testing tool I made I observed that no bytes were ever written to `test.prof`. It seems like there is no sampling being done at all...? | Documentation,help wanted,NeedsFix,compiler/runtime | low | Critical |
225,538,087 | flutter | "Lost connection to device" randomly when not doing anything in particular | We should keep closer track of what adb is doing. Is it dying on us? The logs don't say.
```
[+1366 ms] I/flutter (26953): <some stuff i was printing to the console>
[ +13 ms] I/flutter (26953): <ditto>
[ +1 ms] I/flutter (26953): <ditto>
[ ] I/flutter (26953): <ditto>
[ ] I/flutter (26953): <ditto>
[+128298 ms] Service protocol connection closed.
[ ] Lost connection to device.
[ +1 ms] DevFS: Deleting filesystem on the device (file:///data/user/0/io.flutter.examples.gallery/cache/flutter_galleryIgEdy5/flutter_gallery/)
[ +251 ms] TimeoutException after 0:00:00.250000: Future not completed
[ ] 'flutter run' took 561,659ms.
[ +32 ms] ensureAnalyticsSent: 31ms
[ ] exiting with code 0
``` | platform-android,tool,customer: crowd,P2,team-android,triaged-android | low | Critical |
225,550,777 | flutter | Add a doctor validator warning for multiple adb installations | Just helped track down an issue an internal customer was having whereby multiple `adb` instances were fighting each other:
* `/usr/bin/adb` existed as part of the `adb` Debian package that was installed on the user's system. It seemed to be restarting its server automatically when killed because of an entry in `init.d`
* `$ANDROID_HOME/platform-tools/adb` was the user's preferred `adb` instance and was also the instance detected by flutter tools since it lived in a proper SDK folder structure.
There was initially an issue whereby one `adb` client process would detect a mismatch between the client and server versions and restart the appropriate server, and in so doing, it'd echo a message to the terminal that flutter tools mistook for a device line (fixed in https://github.com/flutter/flutter/pull/9693).
Once that issue was fixed, the two `adb` servers still seemed to be fighting each other, causing the preferred `adb` to show no connected devices even though there were devices connected. The solution we eventually found for this was uninstalling `/usr/bin/adb` (via `sudo apt-get remove adb`)...
This experience, along with reports within the Flutter team of multiple `adb` instances not playing nicely with each other and with Flutter tools, means we probably want to add a doctor validator that will warn the user if multiple adb binaries are detected. | team,tool,t: flutter doctor,P3,team-tool,triaged-tool | low | Minor |
225,567,694 | godot | Rendering is broken on UWP | Just as a note to remind that the renderer is not working on UWP. I managed to get a GLES3 context but it still doesn't work with 3D games. | bug,topic:rendering,topic:porting,confirmed,platform:uwp | low | Critical |
225,569,842 | three.js | toJSON() and fromJSON() | ##### Description of the problem
We have toJSON api.
As a consistency, I think we should have fromJSON.
It will be powerful for data management.
##### Three.js version
- [x] Dev
##### Browser
- [x] All of them
- [ ] Chrome
- [ ] Firefox
- [ ] Internet Explorer
##### OS
- [x] All of them
- [ ] Windows
- [ ] macOS
- [ ] Linux
- [ ] Android
- [ ] iOS
##### Hardware Requirements (graphics card, VR Device, ...)
| Suggestion | medium | Major |
225,577,563 | rust | confusing error message saying variable must be valid for anonymous lifetime that it appears to live long enough for | I initially [raised this on twitter](https://twitter.com/davidbaron/status/856772994294788097) without a reduced testcase, and @SimonSapin [suggested I file an issue](https://twitter.com/SimonSapin/status/856795953851805696) because the error message could be improved.
A reasonably-reduced testcase for this error is the following code:
```rust
pub struct IrcServer {
options: String,
}
impl IrcServer {
fn new() -> IrcServer {
IrcServer { options: String::from("test") }
}
fn options(&self) -> &String {
&self.options
}
}
pub fn main_loop_iteration(server: IrcServer, irc_state: &mut IRCState) {
let options = server.options();
handle_bot_command(&server, options, irc_state)
}
fn handle_bot_command<'opts>(server: &IrcServer,
options: &'opts String,
irc_state: &mut IRCState<'opts>) {
}
pub struct IRCState<'opts> {
options: &'opts String,
}
impl<'opts> IRCState<'opts> {
fn new(options_: &'opts String) -> IRCState<'opts> {
IRCState { options: options_ }
}
}
```
which, when compiled with `rustc --crate-type lib lib.rs` gives the following error:
```
error: `server` does not live long enough
--> lib.rs:16:19
|
16 | let options = server.options();
| ^^^^^^ does not live long enough
17 | handle_bot_command(&server, options, irc_state)
18 | }
| - borrowed value only lives until here
|
note: borrowed value must be valid for the anonymous lifetime #2 defined on the body at 15:72...
--> lib.rs:15:73
|
15 | pub fn main_loop_iteration(server: IrcServer, irc_state: &mut IRCState) {
| _________________________________________________________________________^ starting here...
16 | | let options = server.options();
17 | | handle_bot_command(&server, options, irc_state)
18 | | }
| |_^ ...ending here
error: aborting due to previous error
```
This error is particularly confusing because it looks like the borrowed value *is* valid for the anonymous lifetime being pointed to; the "borrowed value only lives until here" points to the same point as the "...ending here".
The way to fix the code is with lifetime parameters and passing `options` in from the caller, i.e., to change the code to be:
```rust
pub struct IrcServer {
options: String,
}
impl IrcServer {
fn new() -> IrcServer {
IrcServer { options: String::from("test") }
}
fn options(&self) -> &String {
&self.options
}
}
pub fn main_loop_iteration<'opts>(server: IrcServer,
options: &'opts String,
irc_state: &mut IRCState<'opts>) {
handle_bot_command(&server, options, irc_state)
}
fn handle_bot_command<'opts>(server: &IrcServer,
options: &'opts String,
irc_state: &mut IRCState<'opts>) {
}
pub struct IRCState<'opts> {
options: &'opts String,
}
impl<'opts> IRCState<'opts> {
fn new(options_: &'opts String) -> IRCState<'opts> {
IRCState { options: options_ }
}
}
```
but it required stepping away from the problem for a bit and coming back to it later to recognize that. | C-enhancement,A-diagnostics,A-lifetimes,T-compiler | low | Critical |
225,578,318 | kubernetes | Unit test for pkg/kubelet/remote | There is no unit tests for pkg/kubelet/remote. We should add a fake runtime and add unit tests for the package.
- [x] Add a fake remote runtime #49762
- [ ] Add unit tests | area/kubelet,kind/cleanup,sig/node,help wanted,lifecycle/frozen,needs-triage | low | Major |
225,636,480 | go | encoding/base64: encoding is slow | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go 1.8.1
### What operating system and processor architecture are you using (`go env`)?
amd64, darwin
### What did you do?
go test encoding/base64 --bench=BenchmarkEncodeToString
### What did you expect to see?
It should be possible to increase the speed of the encoder by 3 or 4 times by using SIMD instructions. So ideally, I'd like to see something like
go test --bench=BenchmarkEncodeToString
BenchmarkEncodeToString-8 500000 3777 ns/op 2168.51 MB/s
PASS
### What did you see instead?
BenchmarkEncodeToString-8 200000 11393 ns/op 719.01 MB/s
PASS
ok encoding/base64 2.406s
| Performance,NeedsFix | low | Major |
225,672,815 | go | x/image/font: add a tool for running Unicode’s text rendering tests | Would you be interested in testing the Go font library through [Unicode text rendering tests](https://github.com/unicode-org/text-rendering-tests)?
I’m maintaining this test suite for Unicode, and would volunteer to do the integration with the test framework. But somebody familiar with Go would have to write a command-line tool that can be called like this:
```
path/to/some-command --font=fonts/TestCMAP14.otf --testcase=Foo-5/6 --render=≩≩
```
This should write an SVG file to standard output, looking like this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<svg version="1.1"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
viewBox="0 -120 1446 1200">
<symbol id="Foo-5/6.uni2269" overflow="visible"><path d="M100,334 L623,563 L623,619 L100,880 L100,793 L518,594 L100,420 Z M100,208 L622,208 L622,287 L100,287 Z M100,38 L622,38 L622,117 L100,117 Z M282,-93 L508,379 L436,413 L211,-59 Z"/></symbol>
<use xlink:href="#Foo-5/6.uni2269" x="0" y="0"/>
<use xlink:href="#Foo-5/6.uni2269" x="723" y="0"/>
</svg>
```
For test cases on variable fonts, your tool would be called with an additional argument for the variation settings, such as `--variation=wght:481.3;wdth:70`. Initially, you could ignore this.
The test fonts are [here](https://github.com/unicode-org/text-rendering-tests/tree/master/fonts). If you write a command-line tool that can be called as described, the generated test report will look like [this](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/FreeStack.html), [this](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/CoreText.html), [this](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/fontkit.html), or [this](https://rawgit.com/unicode-org/text-rendering-tests/master/reports/OpenType.js.html). | Testing,NeedsDecision | low | Minor |
225,707,194 | go | proposal: spec: disallow LTR/RTL characters in string literals? | TL;DR https://play.golang.org/p/LPkPTRF7fC
The above code looks quite plain and obvious, except it does something completely different than you'd expect (feel free to run it). The obvious thing that should happen is that it counts the number of bits set in the given string. The non-obvious thing that happens is that the mask is actually `0`, not `0x01`.
So, what happened there? The abuse in the above code is around the invisible Unicode characters that mark following text to be right-to-left or left-to-right. Since Go permits arbitrary Unicode characters to be present in string literals, it also allows me to have a string of the form "bla bla bla<right-to-left>abc<left-to-right>". Since we're dealing with valid Unicode sequences here, any modern editor/website will actually interpret those special characters, causing the content in between the two special marks to be reversed to the end of the line (alas still part of the string literal).
In my playground code this is abused by having the following source code:
```
str, mask := "Hello, World!<rtl>10x<ltr>", 0
```
Which will be displayed by all modern editors/websites as:
```
str, mask := "Hello, World!", 0x01
```
The security aspect of this issue is social engineering attacks. The "display" line of my sample code is obvious beyond doubt, so noone will ever inspect such a thing; however it managed to flip one bit in a mask (imagine doing this for file permission umasks). The issue is that such code could easily get past reviews and into a final product.
The tricky part is how to avoid these issues. My only meaningful suggestion would be to disallow these two special characters in string literals. This does break Go 1.0 compatibility guarantees, however I think it's worth it (I can't really figure out a meaningful use case for it). Using it in a single line string will screw up the display of the source code, so it doesn't make sense to do it, and using it in a multi line string is questionable at best. I think requiring users to explicitly use `\x` notation for adding these characters it a good compromise to protect source code sanity. | Proposal,Proposal-Hold | medium | Critical |
225,708,564 | go | proposal: spec: disallow unicode import paths to avoid punycode attacks | If you take a look at the following snippet https://play.golang.org/p/SpXVFRLUlX, it will look completely benevolent. It just pulls in the terminal package from the extended stdlib and read the user's password.
If you copy paste this snippet into a file and try to run it, you will get an error message along the lines of `cannot find package "gοlang.org/x/crypto/ssh/terminal" in any of: [...]`. The standard "reaction" from a user to this error message will be either to run `go get` or perhaps `go get gοlang.org/x/crypto/ssh/terminal`. And this is where things can go horribly wrong.
Thing is, the "gοlang.org" domain in the snippet's import path is not ASCII, rather Unicode. All modern URL libraries (including the one used by go and go get) will helpfully convert this URL to punycode, mapping the "gοlang.org/x/crypto/ssh/terminal" package silently to "xn--glang-rce.org/x/crypto/ssh/terminal". At this point, Go will go and fetch whatever package is at that import path, on a completely different domain that the user expected.
---
To fully demo this attack I've tried to actually register that domain, but the top registrars refused. There are plenty shadier ones that seem to be happy, however I'm not sure I want to give out my credit card to so many companies only to see if I can get the domain registered or not.
For the purpose of this demo, let's assume that I did manage to register it, and instead simulate my doing so by manually resolving xn--glang-rce.org to 130.211.147.254. You could do this by adding an entry to your hosts file. On Ubuntu this would be adding `130.211.147.254 xn--glang-rce.org` to /etc/hosts and possibly also enabling this in the network manager via adding `addn-hosts=/etc/hosts` to /etc/NetworkManager/dnsmasq.d/hosts.conf and doing a `sudo service network-manager restart`). Make sure `nslookup xn--glang-rce.org` works and results in 130.211.147.254 before continuing.
Ok, now that we have our domain "registered", we could actually try to to run that playground snippet I provided via `go get --insecure && go run snippet.go`. Note I'm doing insecure since we only have a "simulated" domain, but a real one can have cloudflare or let's-encrypt in front of it, so the HTTPS part at this point is irrelevant.
The program output will be:
```
Please enter a secret: <you enter "Hello" for example>
Thank you for sharing your password 'Hello' with us! ~MitM
```
---
It should be pretty obvious by now what happened here. Go get resolved silently my unicode domain into punycode, it reached out to wherever that was hosted and downloaded something that for every human looked like a trusted repository. In this particular case, I was running a vanity import path resolver at the above IP, which resolves this single import path to https://github.com/karalabe/mitm, a demo attack package that simulates a mitm attack for ssh passwords.
In my opinion this is a horribly dangerous social engineering attack. All it takes to break a project (open source are vulnerable the most), is to send a patch to a random project on GitHub, and beside fixing whatever to hide the attack, also helpfully reorg the imports, swapping one of the paths out with a custom homoglyph domain. The domain doesn't even have to attack immediately, it could just lay dormant there redirecting to the real import until someone decides to arm it.
This could allow arbitrary code to be injected at an arbitrary later point in time into a project without anyone being the wiser. For certain projects (e.g. Ethereum, which has its majority client written in Go) this is an end game scenario.
---
From Go's perspective, a possible solution against this attack vector could be to modify gofmt to swap out Unicode import paths to the final punycode variant `go get` would download anyway. This could provide a strong enough "hint" to developers that there's something very wrong with an import path without requiring on outside tooling. Beside this, I'd also venture to suggest that the compiler could be modified to reject any import paths that resolve into punycode but that are represented as Unicode in the source.
On the down side of course, my suggestion would be equivalent to dropping support for all internationalized domain names, alas the question is whether it's worth compromising the entire ecosystem for fancy import URLs.
---
Apparently "golang.org" is not so easily spoofable since there's a limitation in IDN domains that only characters from a single character set may be used (at least for the popular TLDs) and the "g" character saves the day, being fairly unique to Latin. However there are other interesting domains that can be fully represented in Cyrillic for example which require a single character set and thus pass all domain verification (e.g. "огео.com" actually being "xn--c1aezc.com", free to register at godaddy https://www.godaddy.com/domains/searchresults.aspx?checkAvail=1&tmskey=&domainToCheck=xn--c1aezc.com).
Given this constraint, the attack surface is much much smaller than I originally anticipated (most Go packages are hosted on github, which should arguably be harder to spoof), but there's still a potential to break future vanity addresses (e.g. if oreo decides to release a Go package in 5 years). Then again https://www.аррӏе.com | Proposal,Proposal-Hold | low | Critical |
225,724,105 | neovim | Resize windows "upwards" | AFAICT (documentation and brief source check), window resizing always goes "downwards"; if a window is expanded or shrunk, it shrinks or expands the buffer below it unless there is no downward space, and only then shrinks the buffer above.
However, sometimes I have buffers above the current window that I'd rather shrink when I expand the current window.
I suppose that can reasonably be scripted, though it's slightly painful due to #6643. If there's pushback, that's a fine solution, but I don't see any major reason why there couldn't be a flag to resize upwards rather than downwards.
As a concrete example consider the following sequence from a fresh `nvim -u NORC`:
```
:sp
:sp
:wincmd j
:resize +3
```
Maybe window 3 was exactly as big as I want it, but I really only need window 1 to be a couple lines. Currently, I have to replace `:resize +3` with either `:wincmd k | resize -3 | wincmd j` or `1 resize -3` (though as noted in #6643, that doesn't quite do what you expect), which are both uglier and are fragile if there are multiple windows above the current one. Why not just have something like `:resize up +3`? | enhancement,ui | low | Minor |
225,746,538 | neovim | :Install command (was: "add windows explorer integration") | Would be good to have something like `nvim --register` so it can register OS integrations (Vim has install.exe). Most likely this would be a neovim-qt feature.
Having `Edit in NeoVim` would be the minimal requirement but better if it can also figure out all open instances of neovim and have an ability to open in that particular instance like how vim does. In this example I have two separate instances of vim already opened - setenv.cmd and .vimrc.
| enhancement,platform:windows,ux,complexity:low | medium | Major |
225,756,790 | neovim | set job priority / niceness | It would be nice if you could configure the niceness of a job process via its options.
This was asked for Neomake in https://github.com/neomake/neomake/issues/1271.
I've looked quickly at libuv, but it does not appear to have native support for it?
The workaround is to either wrap the command in `nice` before starting the job (more difficult for Neomake, since `argv` can be a string or list etc), or adjusting the niceness once the job is started (https://github.com/neomake/neomake/pull/1273 - this adds an additional `system()` call though). | enhancement,job-control | low | Minor |
225,759,315 | rust | [RFC] figure out story around linear queries | PR #41625, in an effort to rationalize the MIR pipeline, introduced queries that yield a `Steal` type. Cribbing from a [rather long and overwrought comment that I wrote][c], the idea is to model linear queries as ordinary queries that return a `&'tcx Steal<D>`, which supports two operations ("borrow" and "steal"). Once a value is stolen, any further operation is a `bug!()`. This means that all parts of the compiler which invoke a query with a steal result must be aware of any other parts that might use that same query and coordinate with them. (This is a performance optimization: that is, we could make "stolen" queries simply regenerate the resulting value, and everything would work, but we don't want to be regenerating the results of these queries multiple times, so instead we make this error a `bug!`.)
In all the MIR cases, at least, there really isn't much to intercoordinate. For the most part, each MIR optimization is just used by one other query: the next optimization in the sequence. (In the current PR, each optimization pass has its own query, but if we convert to just having a query-per-suite, then this would apply at the level of suites.) Other parts of the compiler should use one of the queries (e.g., `optimized_mir()`) that do not return a `Steal` result.
However, there are a few exceptions. One example is const qualification. This is a lightweight scan of the contents of a `const` item, and it needs to take place relatively early in the pipeline (before optimizations are applied and so forth). The way I handled this is (a) to have it `borrow()` from the steal and then (b) to use `force` before we steal the relevant MIR, so that we know that it has executed. If we forgot to add the `force()` call, then the result would be dependent on the order in which queries were issued; that is, if one requested `const-qualif(D)` first, it would execute successfully, but if one requested `optimized_mir(D)` first, then `const-qualif(D)` afterwards, you would get a `bug!` because `const-qualif` would be trying to read stolen data. (However, if compilation succeeds, we are always assured of a consistent result.)
The complete set of examples that I am aware of where we have a linear query that also needs to be accessed is as follows:
- **Const qualification**, as just covered, needs to inspect the "const" MIR before validation, at least for const items.
- **Const evaluation** will, for `const fn`, need to save a copy of the IR before validation and optimization that can be used by miri (indeed, optimization may want to execute miri to evaluate constant expressions, perhaps even some appearing within the `const fn` itself).
- **Borrow checking** needs to access the MIR result after "validation" but before "optimization".
The current solution is simple and may indeed be "good enough" -- it depends a bit (in my mind) on how often we introduce linear queries and how many things depend on them. However, there have been some alternative proposals for how to handle it. The purpose of this issue is to describe those proposals and try to settle on which is best.
Rather than continuing with concrete examples, in the descriptions that follow, I will abstract out the pattern as follows. Consider a "stealable" query A that needs to be **read** by query B (e.g., borrow checking) but **consumed** by query C (e.g., optimization).
[c]: https://github.com/rust-lang/rust/pull/41625#issuecomment-298349595
For each system, I will describe how it works, and then discuss some of the tradeoffs.
### Current system: "stealable queries"
**How it works:** As described in the run-up, you have a query that yields a `&'tcx Steal<T>`. This can be either *borrowed* or *stolen*. An attempt to *borrow* after a steal (or a second attempt to steal) will result in a `bug!` call.
**How you can mess it up**: You can forget to call `force()` on a potential consumer when stealing. In the case of our example, this would mean that query C fails to force query B.
**What happens if you mess it up:** Compilation may succeed with some query execution orders (e.g., if `B` executes first) but fail with a `bug!` in others (e.g., if `C` execues first).
**Other downsides: entanglement** It's kind of a drag that the stealer (C) must be aware of the reader (B). It
### Proposed alternative: "linear queries" with "tuple providers"
**How it works:** @eddyb proposed an alternative in which linear queries can only be used once. In this scheme, once you execute a query once, any further attempt to request the same query is a `bug!`. So we can't have a query A that is read by B and consumed by C, as I had, since both B and C must consume, and that would violate linearity. To support this scenario, then, eddyb wanted to introduce "tuple" providers (name is mine). Basically, when setting up the `Providers` struct, I can use a bit of magic to knit together a function that processes the result from `A` and produces a `(B, C)` tuple. This magic would then divide the tuple and store the `B` into the `B` map and store the `C` into the `C` map in the right spots. This might look something like this:
```rust
fn produce_bc(tcx: TyCtxt, def_id: DefId) -> (B, C) {
let a = tcx.A(def_id); // consumes A
... // returns (B, C)
}
// this method will initialize `providers.b` and `providers.c`
// with generated glue functions:
providers.tuple().b().c().func(produce_bc);
```
**How you can mess it up**: You could fail to use the tuple system, and instead write queries B and C independently.
**What happens if you mess it up:** In any execution in which both queries B and C are used, no matter which order they are used in, compilation will ICE. This is thus mildly more robust than the stealable scheme.
**Other downsides: entanglement.** It's kind of a drag that we must produce B and C from one function.
**Other downsides: imprecise dependencies.** It's possible that producing B and C use different sets of inputs. But since there is one function that is doing both bits of work, we won't be able to tell them apart in the query system, and hence they will wind up with imprecise dependencies.
**Other advantages: splitting.** This technique allows you to take the result of query A and split it into pieces without cloning. This is not possible with the other alternatives.
### Proposed alternative: "linear queries" with "mapping providers"
In my [original comment][c], I described a variant of of tuple providers. I want to describe a variant here of that idea that I've been thinking since. The idea is to make linear queries part of the query framework, as in the "tuple providers" proposal. However, when you define a linear query, you don't use it in the same way as non-linear queries. That is, if you have a linear query `A`, you can't do `tcx.A(def_id)` as I showed earlier. Instead, when creating the provider struct, we use some magic functions to "connect" derived queries to a linear query. This connection can be in one of two modes ("read" or "consume"). For example:
```rust
fn produce_b(tcx: TyCtxt, def_id: DefId, a: &A) -> B {
// ^^^^^
// Note this extra argument: this will be the value of
// the `A` query, borrowed.
...
}
fn produce_c(tcx: TyCtxt, def_id: DefId, a: A) -> B {
// ^^^^
// Note this extra argument: since this query is on
// "consume" mode, it gets ownership of the `A` value.
...
}
// Register the B query as something that *reads* linear
// query A:
providers.read_a().to_produce_b_with(produce_b);
// Register the C query as something that *consumes* linear
// query A:
providers.consume_a().to_produce_c_from(produce_c);
```
(These `read_a()` and `to_produce_b_with()` methods would be auto-generated
by the macro.)
The basic idea here is that we are telling the providers struct two things:
- which linear queries we access (and whether we read or consume them)
- which query we are answering when we do that
This allows the framework to do more intelligent routing of results. In particular, if there is more than one consume query for a linear query, we can detect that **at provider creation time** -- i.e., before we even process any input. Moreover, we can ensure that before the "consume" query for a given linear value runs, we force all of the "read queries". (In this case, that means that if you request C, we will force the query B, so that it can read before C executes.) (This last part is why the provider functions have to know what query you are producing.)
**How you can mess it up**: You cannot mess this up, since you can't access linear queries using the normal methods. Even if you tried to register two "consume" queries for the same linear value, that would fail when creating the provider struct (so such a PR could never land, for example, and no test could ever pass).
**What happens if you mess it up:** You cannot, unless I missed something. =)
**Other advantages: no entanglement.** This is the only proposal that avoids the need for queries B and C to know about one another. Simply by registering the queries, you help the framework sort things out and ensure that the appropriate `force` calls happen.
### Other proposals?
I'll try to update this header if more ideas come up.
cc @rust-lang/compiler @matthewhammer | T-compiler,A-MIR | low | Critical |
225,795,077 | pytorch | Optimizers can't be moved to a different GPU | There is currently no good way to set the GPU id for an optimizer state. This is particuarly relevant in the use case that model training stops, and needs to be restarted on a different gpu.
I'm currently working around that problem with the following:
```
def set_gpu_recursive(var, gpu_id):
for key in var:
if isinstance(var[key], dict):
var[key] = set_gpu_recursive(var[key], gpu_id)
else:
try:
var[key] = var[key].cuda(gpu_id)
except:
pass
return var
opt.load_state_dict(torch.load(opt_save_path))
opt.state = set_gpu_recursive(opt.state, gpu_id)
```
| feature,triaged | low | Major |
225,841,197 | go | cmd/compile: missing line numbers with cgo pragmas | Reproduce: `go install -race cmd/compile`, `compilebench -run=SSA -cpuprofile=c`, `go tool pprof -lines $(go tool -n compile) c`.
Result: entries like `__tsan_read :-134217728`. That's no filename, line number underflow. Ideally it'd refer to the place where the symbol was defined. We have the position information as we enter `pragcgo` in the compiler, but it never gets recorded in `pragcgobuf`. Not sure how much work would be required to thread it through from there. | NeedsInvestigation,compiler/runtime | low | Minor |
225,865,261 | opencv | opencv builds unusable instruction sets | I was trying to install caffe and it gave me a wonderful error message stating that opencv had instructions sets built that couldn't be used. So, naturally I rebuilt opencv with those problematic instruction sets explicitly turned off. Below is that cmake command. Caffe no longer gave me that error message. I'm on a intel 2600k processor so that's why AVX2 is turned off.
`sudo cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D WITH_CUDA=ON -D ENABLE_FAST_MATH=1 -D CUDA_FAST_MATH=1 -D WITH_CUBLAS=1 -D OPENCV_EXTRA_MODULES_PATH=../../opencv_contrib/modules -D BUILD_EXAMPLES=ON -D WITH_TBB=ON -D WITH_OPENMP=ON -D WITH_IPP=ON -D ENABLE_AVX=ON -D ENABLE_POPCNT=ON -D ENABLE_SSE41=ON -D ENABLE_AVX2=OFF -D ENABLE_FP16=OFF -D ENABLE_FMA3=OFF -D ENABLE_SSE42=ON -D ENABLE_SSSE3=ON -D CUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda ..`
I'm submitting this as an issue because the cmake script should be catching this type of thing. I'm not sure if cmake has functionality for checking what can be built directly or if test projects are required.
| incomplete | low | Critical |
225,948,417 | neovim | win: tui: support :stop, :suspend (CTRL-Z) | https://github.com/neovim/neovim/pull/6315#issue-215261397 | platform:windows,tui | low | Major |
226,018,928 | go | encoding/gob: document or improve handling of untrusted data | It is pretty easy to construct small malicious encoding/gob packets with large impacts, e.g. by using a large map hint (CL 40113).
I don't see:
* anything in the encoding/gob docs that discusses safe handling of untrusted data
* anything in the encoding/gob API that would support checking whether untrusted data is safe to decode
* anything in the implementation that ensures e.g. that there is a relationship between the amount of data and the memory used; if there were limits on amplification, then a `io.LimitedReader` could be used
Although maybe I missed something.
It seems like we should add some or all of the above.
cc @bradfitz @gruszczy @randall77 @robpike
| NeedsDecision | low | Major |
226,060,592 | TypeScript | Filling in an implementation using VS Code will expand types | ```ts
type Foo = [string, number];
interface Bar {
test(a: Foo): void;
}
class Baz implements Bar{
}
```
Using fill in Baz implementation quick fix:
```ts
type Foo = [string, number];
interface Bar {
test(a: Foo): void;
}
class Baz implements Bar {
test(a: [string, number]): void {
throw new Error("Method not implemented.");
}
}
```
I expect:
```ts
class Baz implements Bar {
test(a: Foo): void {
throw new Error("Method not implemented.");
}
}
```
/cc @mjbvz | Bug,VS Code Tracked,Domain: Quick Fixes | low | Critical |
226,098,263 | pytorch | Change sparse_mask to take indexing mask, rather than entire sparse tensor | Currently, sparse_mask takes a sparse tensor, throws out the values, and uses just the indices to mask a dense tensor. This is not a very good API; for one, it causes trouble when the mask tensor is of different type of the dense tensor you're masking (this shouldn't cause any problems, but right now the dispatcher chokes, because it requires them to be the same.)
So let's introduce a new function: `sparse_select`, which takes JUST the indexing mask, and produces a sparse vector of just those indices selected.
There is one minor downside to doing things this way, which is that we lose information about whether or not the indices are coalesced or not.
----
**Old description.** Recently I got this error:
```
File "/Users/ezyang/Dev/pytorch/torch/optim/sgd.py", line 93, in step
d_s = (state['step'] - state['last_update']._sparse_mask(d_p.long())).type_as(p.data)
TypeError: _sparse_mask received an invalid combination of arguments - got (torch.sparse.LongTensor), but expected (torch.sparse.IntTensor mask)
```
That's a bit silly: in the end you're only ever going to use the indices of the sparse mask tensor, so you don't really care about what the values in the mask tensor.
Unfortunately, making sparse_mask polymorphic over the type of the mask tensor seems a bit fiddly to do (one existing function which is similarly polymorphic is `copy`, but the way it is polymorphic is by generating a copy of the function for each type.
Another strategy would be to introduce a variant of sparse_mask which takes only the index tensor, rather than the entire sparse tensor. This would be similar to index_select, but index_select indexes along a dimension, whereas with sparse_mask we have the coordinates for all dimensions.
Additionally, to a certain degree you can work around this problem:
1. If you don't care about efficiency, you can cast the sparse mask to the required type to make the dispatcher stop complaining. If you do care about efficiency, you could probably make a fake value tensor to get it the right type.
2. If your update is purely additive, you can use `spadd` to apply your sparse vector of additions to the new tensor. (For example, this is true for adagrad.) If you don't care about efficiency, you can manually difference out the original value so that you have an additive update.
3. If your sparse tensors are 1D, index_select and related functions can serve your needs.
cc @vincentqb | module: sparse,feature,triaged | low | Critical |
226,129,255 | svelte | Browser support | A few people have asked about browser support. We probably should be able to answer the question conclusively (maybe even running some tests in Browserstack or whatever?), and perhaps tell people which polyfills they'll need.
For example, `window.performance.now` isn't supported in IE9, but is used in transitions (https://github.com/sveltejs/svelte/pull/525#discussion_r114223085). | popular,documentation | high | Major |
226,150,510 | go | math/big, go/constant: fuzz with go-fuzz | go-fuzz found a few math/big and go/constant bugs indirectly, via go/types and cmd/compile:
https://github.com/golang/go/issues/20227
https://github.com/golang/go/issues/20228
That's a pretty inefficient way to find them, though. We should run it on them directly and flush out a few more.
@ALTree @dvyukov
| Testing,help wanted | low | Critical |
226,172,400 | go | encoding/base64: integer overflow in (*Encoding).EncodedLen | ### What version of Go are you using (`go version`)?
1.8.1
### What operating system and processor architecture are you using (`go env`)?
linux/386
### What did you do?
I called `base64.RawStdEncoding.EncodedLen()` with `1<<30` (2 to the 30th power) on a 32-bit platform, as in line 9 of https://play.golang.org/p/mV9110MxJ- , and `base64.StdEncoding.EncodedLen()` with `1<<31 / 4 * 3` (equal to 1,610,612,736) as in line 10 of the same example.
Line 10 also calls the method with the same argument on `base64.StdEncoding` for comparison.
### What did you expect to see?
I expected `EncodedLen()` on `RawStdEncoding` to return a value close to that returned by `StdEncoding` for `1<<30`I think 1,431,655,766 is the correct value, but I may have miscalculated) and `EncodedLen()` on `StdEncoding` to not return a negative encoded length for `1<<31 / 4 * 3` (perhaps to panic? I'm not certain what the appropriate behavior here is).
### What did you see instead?
Instead the first example returned `0` and the second `-2147483648`. Neither of these values are sufficient to hold a base64 encoding of a string of the supplied lengths. | help wanted,NeedsFix | low | Minor |
226,235,584 | pytorch | avg_pool functions hold input for backward | on backward avg pool only uses shape of the saved tensor, not the actual tensor, we should thus only hold shape, but this needs modifications in THNN and THCUNN.
https://github.com/pytorch/pytorch/blob/master/torch/nn/_functions/thnn/pooling.py#L316 | feature,triaged,module: pooling | low | Minor |
226,272,631 | go | x/mobile: gomobile build ios app can not be upload to itunes connect | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go 1.8
gomobile version +0f31740 Wed Apr 19 17:20:05 2017 +0000 (android,ios); androidSDK=
### What operating system and processor architecture are you using (`go env`)?
macos
xcode 8.1
### What did you do?
build example flappy and upload it to itunesconnect
edit below and go install gomobile
--- a/cmd/gomobile/build_iosapp.go
+++ b/cmd/gomobile/build_iosapp.go
@@ -31,7 +31,8 @@ func goIOSBuild(pkg *build.Package) (map[string]bool, error) {
infoplist := new(bytes.Buffer)
if err := infoplistTmpl.Execute(infoplist, infoplistTmplData{
// TODO: better bundle id.
- BundleID: "org.golang.todo." + productName,
+ BundleID: "org.xxxx.mug",
Name: strings.Title(path.Base(pkg.ImportPath)),
}); err != nil {
return nil, err
@@ -366,6 +367,7 @@ const projPbxproj = `// !$*UTF8*$!
CLANG_WARN_UNREACHABLE_CODE = YES;
CLANG_WARN__DUPLICATE_METHOD_MATCH = YES;
"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer";
+ DEVELOPMENT_TEAM = xxxxxxxxx;//
COPY_PHASE_STRIP = NO;
DEBUG_INFORMATION_FORMAT = "dwarf-with-dsym";
gomobile build -target=ios golang.org/x/mobile/example/flappy
flappy.app --itunes--> flappy.ipa
xcode Application Loader Upload.
### What did you expect to see?
go build app upload success
### What did you see instead?
Application Loader Reports
ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle org.xxxx.mug [Payload/flappy.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."
Bundle id is correct. Provision profile exist.
| mobile | low | Critical |
226,276,385 | vscode | Stop rendering pseudo-italic fonts when italic is not available | When using fonts which don't have italic variants, such as Fira Mono, VScode renders them anyway, using a simple skew. Goes the same for emojis.
This looks quite bad, and should be avoided.
| feature-request,upstream,font-rendering | medium | Major |
226,302,155 | vscode | [html] provide translations of tag documentation | - VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
- OS Version: Windows_NT ia32 10.0.14393
- Extensions: none
---
Steps to Reproduce:
Almost stuffs are displayed in Korean becuase dispaly language is already configured to "ko(Korean)". But intelliSense of HTML is not.
1. Mouse over HTML tag.
2. The information popped up under the cursor is not displayed in Korean.
3.
| feature-request,html,l10n-platform | medium | Critical |
226,384,868 | vscode | Improved search in "Go to file" panel | Would love to see a more accurate search for what I'm actually searching for. For example when I'm searching for "archive" and I'am in mid sentence i get these results:
I think, at least for me that the index.js inside the archive folder file is much more relevant than the .babelrc and yarn.lock. Sublime on the other hand does exactly what I want.
This change would make the workflow with VS Code even better than it already is 😄
| feature-request,search,quick-open | medium | Critical |
226,393,877 | rust | Reordering where clauses can change program behavior | Here's a contrived example:
```rust
use std::fmt::Debug;
trait Left<T> {}
trait Right<T> {}
trait Join<U> {
fn test();
}
// With the reordering,
// impl<T, U> Join<U> for T where T: Right<U>, T: Left<U>, U: Default + Debug {
// you'll get a different output
impl<T, U> Join<U> for T where T: Left<U>, T: Right<U>, U: Default + Debug {
fn test() {
println!("{:?}", U::default())
}
}
impl<T, U: Default + Debug> Left<U> for T {}
impl<T, U: Default + Debug> Right<U> for T {}
fn try_it<T: Default + Debug>() where T: Left<bool>, T: Right<()> {
<T as Join<_>>::test()
}
fn main() {
try_it::<u8>() // the type here is irrelevant
}
```
In the order given, the output is `false`. If you swap the order as suggested in the comment, the output is `()`.
What's happening here is a combination of a few things. The `Join` impl creates obligations in order of its where clauses, and the solution to each obligation informs inference, which affects future obligations. At the same time, when it comes time to show `T: Left<U>`, for example, it can be proved either by virtue of the blanket impl or the where clause on `try_it`. We currently give preference to the where clause, which then drives inference.
The same mechanisms also lead to cases where:
1. Adding a valid where clause can cause code to stop compiling.
2. Adding a where clause can change program behavior.
These issues seem fairly fundamental to the where clause preference approach, which is something we likely cannot change backwards compatibly (and there were good reasons for it in the first place). So it's possible that we will just have to live with these consequences. But I wanted to file a bug for posterity. | A-trait-system,T-compiler,C-bug,T-types | medium | Critical |
226,427,777 | javascript | Documentation: react/jsx-filename-extension can break checks without --ext arguments | Adding the `react/jsx-filename-extension` is just fine as a rule, but adding some direction that you will need to add the `--ext=js --ext=jsx` arguments to the eslint cli for it to work. It might cause issues for users who are not aware of this when they start using the `eslint-preset-airbnb` package. Adding a line to the README might be helpful, and I would be happy to do so. 😄
Ideally, you could configure this as an option in `.eslintrc` but that is not currently available:
https://github.com/eslint/eslint/issues/801
| pull request wanted,editorial | low | Minor |
226,441,676 | flutter | If a line is ellipsised, the text alignment is applied to the truncated line before the ellipsis is added | ```dart
import 'package:flutter/material.dart';
import 'dart:ui';
void main() {
runApp(new MyApp());
}
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return new CustomPaint(
painter: new Eazel(),
);
}
}
class Eazel extends CustomPainter {
@override
void paint(Canvas canvas, Size size) {
ParagraphBuilder builder = new ParagraphBuilder(
new ParagraphStyle(
textAlign: TextAlign.right,
maxLines: 2,
fontSize: 30.0,
fontFamily: 'monospace',
ellipsis: '---',
),
);
builder.addText('012345678901234567890123456789');
Paragraph p = builder.build();
p.layout(new ParagraphConstraints(width: 190.0)); // width of '0123456789'
canvas.drawParagraph(p, const Offset(100.0, 200.0));
}
@override
bool shouldRepaint(CustomPainter oldDelegate) => true;
}
```
...renders:
```
0123456789
012345---
``` | engine,a: typography,has reproducible steps,P2,team-engine,triaged-engine,found in release: 3.19,found in release: 3.20 | low | Major |
226,444,933 | flutter | Cannot draw right-aligned or centered text without width constraint | You cannot draw text that is right-aligned or centered, if you want it to be completely unconstrained (so it will overflow or get clipped, rather than wrapping).
If you left-align the text you can set its width constraint to infinity, but since we use that constraint to align the text, if it's infinite, the text will not be visible. | c: new feature,framework,a: internationalization,a: typography,P2,team-framework,triaged-framework | low | Minor |
226,455,665 | flutter | Generate the plugins .java/.h/.m files outside of user source directories | Let's move various codegen'ed outputs into the /build directory of the project instead of /android or /ios folders so that they're not user visible, or checked in-able, `flutter create`d, or in the example projects.
This is mostly consistent with codegen'ed frameworks such as dagger to not let intermediate code be user visible but not meaningfully editable.
cc @cbracken | platform-android,tool,t: gradle,customer: crowd,t: xcode,dependency: android,P2,team-android,triaged-android | low | Minor |
226,484,254 | vscode | [theming] Separate workbench theme and syntax theme | After upgrading to VS Code 1.12, I noticed that the workbench theme of the built-in **Monokai** color theme had been changed. However, I preferred the default workbench theme a lot.
But in VS Code, there are only two types of themes: **Color Theme** and **Icon Theme**, and the workbench theme is tightly coupled with the syntax theme in the Color Theme category.
In contrast, Sublime Text separates theme into `color_scheme` and `theme` in the preferences. For example, I can choose Material style for the workbench and Monokai for the syntax highlighting. Does the team have plan to separate them and let users have more flexibility to customize their editor?
By the way, I found that some of theme extensions use `.json` as their theme file (including the built-in [Monokai](https://github.com/Microsoft/vscode/blob/master/extensions/theme-monokai/themes/monokai-color-theme.json)), but the official documentation only mentions that we can use `yo code` to generate theme extension with an existing `.tmTheme` file. Is there any documentation for clarifying their difference and also the schema of the `.json` file? | feature-request,themes | high | Critical |
226,610,894 | pytorch | [feature request/proposal] Relax scale_factor for nearest neighbor upsampling | Much like #1257, I'd like to allow nearest neighbor upsampling to be non-uniform. From what I can tell, this means going down into cuda/c level code.
It seems like [this](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/generic/SpatialUpSamplingNearest.cu) is the relevant file, in particular lines [19-20](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/generic/SpatialUpSamplingNearest.cu#L19-L20), [54-55](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/generic/SpatialUpSamplingNearest.cu#L54-L55), and [](url) all use a single integer `scale_factor` parameter in simple ways, but also, [165-166](https://github.com/pytorch/pytorch/blob/master/torch/lib/THCUNN/generic/SpatialUpSamplingNearest.cu#L165-L166) is a cuda kernel call (I *think*). The idea would be to change this to a pair of ints, and do the tuple casting up in the python layers.
@apaszke @soumith any pointers about what I'd need to change or thoughts in general? also pinging @lantiga, who's been working on another upsampling PR, and has done work at the cuda/c level.
FWIW and for anyone that finds this via search I'll point out that I've build a manual solution for my needs in a `forward()` call within my network. Simply make a new `Variable` that's the size needed and manually fill the array with data from the smaller variable. | todo,feature,triaged | low | Minor |
226,624,964 | pytorch | Optimizer should track parameter names and not id | In the optimizer's `param_groups['params']` the order of the parameters (in which they were given to the optimizer's init) matters.
In load_state_dict the snippet shows this :
```
id_map = {old_id: p for old_id, p in
zip(chain(*(g['params'] for g in saved_groups)),
chain(*(g['params'] for g in groups)))}
state = {id_map.get(k, k): v for k, v in state_dict['state'].items()}
```
If we change the order in which the parameters are given to the optimizer when loading, the code breaks as the `state` dict now incorrectly maps parameters to their states.
Consider model (when using, say, Adam optimizer)
```
class Model(nn.Module):
def __init__(self):
super(Model, self).__init__()
self.p1 = nn.Linear(2,3, False)
self.p2 = nn.Linear(3,4, False)
```
After saving, if the order in which the parameters are defined in the model changes i.e. if I change the class to have
```
self.p2 = nn.Linear(3,4, False)
self.p1 = nn.Linear(2,3, False)
```
the loaded optimizer's state for p1 will be mapped to p2 and vice-versa. I tried this and this indeed happens which is wrong and now training cannot proceed (step() will, rightly so, give an error).
The `nn.Module` class is robust to such behavior as it uses parameter names instead of id ordering.
IMO the optimizer should also use parameter names instead of ids and relying on the ordering in which they are supplied to the optimizer when initializing.
Corresponding [PyTorch-Discuss post](https://discuss.pytorch.org/t/possible-issues-in-optimizer/2685)
@soumith
cc @vincentqb | module: optimizer,triaged | medium | Critical |
226,665,233 | realworld | Standardize README's for completed repos | For someone who is landing on an example repo and has no idea what RealWorld is, I'd imagine they'd be thinking "uh, wtf is this". For example, the backend codebases don't mention how to get an example frontend setup & running (much less where you can choose a frontend at all). This could easily be fixed with a standard "what is this"-esque section at the top of every README.
Further, would be great to have standard sections on common topics like "Installing Dependencies", "Running the Application", "Architecture Overview", etc that people will typically be looking for. Definitely a key improvement for the UX of perusing/exploring repo's.
Would love thoughts on this! | Status: RFC,v2 changelog | low | Major |
226,695,566 | youtube-dl | SITE REQUEST: tv.m24.ru | Hello dear coders!
Now I want to ask you about adding support of tv.m24.ru into YDL.
The video streaming tech. is chunks based, i.e., the same as on russia.tv, vesti.ru, 1tv.ru.
Also this tv.m24.ru contains two resolutions' sets those user can choose.
Here is the log:
C:\>youtube-dl -F -v http://tv.m24.ru/videos/128227
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-F', '-v', 'http://tv.m24.ru/videos/128227']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2017.05.01
[debug] Python version 3.4.4 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg 3.2.4, ffprobe 3.2.4, rtmpdump 2.4
[debug] Proxy map: {}
[generic] 128227: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 128227: Downloading webpage
[generic] 128227: Extracting information
ERROR: Unsupported URL: http://tv.m24.ru/videos/128227
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\YoutubeDL.py", line 760,in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\common.py", line 429, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp0io2aq9r\build\youtube_dl\extractor\generic.py", line 2834, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: http://tv.m24.ru/videos/128227
| site-support-request | low | Critical |
226,706,037 | opencv | Feature request: Support floating point image blending by FeatherBlender and MultiBandBlender | ##### System information (version)
- OpenCV => Latest from github
- Operating System / Platform => Ubuntu 16.04
- Compiler => GCC 5.4
##### Detailed description
Currently only 16 bit image (CV_16SC3) is supported by FeatherBlender and MultiBandBlender, is it possible add support for 32 bit floating point image (CV_32FC3) ?
``````
cv::Mat src = cv::Mat(h,w,CV_32FC3,cv::Scalar(0,0,0));
cv::Mat dst = cv::Mat(h,w,CV_32FC3,cv::Scalar(0,0,0));
cv::Mat src_valid = cv::Mat(h,w,CV_8UC1,cv::Scalar(255));
cv::Mat dst_valid = cv::Mat(h,w,CV_8UC1,cv::Scalar(255));
cv::detail::FeatherBlender featherblender(0.5f);
featherblender.prepare(cv::Rect(0, 0, w, h));
featherblender.feed(src, src_valid, cv::Point(0, 0));
featherblender.feed(dst, dst_valid, cv::Point(0, 0));
cv::Mat result;
cv::Mat result_mask;
featherblender.blend(result, result_mask);
``````
This returns error `OpenCV Error: Assertion failed (img.type() == CV_16SC3) in feed, file /home/hypevr/opencv/modules/stitching/src/blenders.cpp, line 151`, I had to convert it to 16 bit but there will be a lost of precision.
| feature,category: stitching | low | Critical |
226,718,368 | flutter | document flutter clause in build.gradle | In a newly-created Flutter directory, android/app/build.gradle contains this mysterious code snippet:
```
flutter {
source '../..'
}
```
This seems to be implemented in flutter_tools/gradle/flutter.gradle. However, that file has few comments and none of them are high level.
It seems like we should add some high-level documentation explaining to users what this command does, so it's not just a mystery. Some JavaDoc in flutter.gradle would be useful too. | tool,d: api docs,t: gradle,P2,team-tool,triaged-tool | low | Minor |
226,730,366 | TypeScript | [Discussion] Better Way to Declare Globals in JavaScript files | **Problem**
Using the new `checkJs` feature, it is currently difficult to tell TypeScript about a global variable:
```js
// @ts-check
myGlobal
window.myVar = 'foo';
```
<img width="458" alt="screen shot 2017-05-05 at 4 44 20 pm" src="https://cloud.githubusercontent.com/assets/12821956/25767871/268f4b00-31b2-11e7-988f-fe9f14165c60.png">
The only way around this that I know is to create a `.d.ts` file that defines these:
```ts
interface Window {
myVar: string;
}
declare var myGlobal: string;
```
JavaScript users should not have to write `*.d.ts` files.
**Possible Approaches**
@egamma proposes that may be able to use the `global` comment from ESlint http://eslint.org/docs/user-guide/configuring : `/* global var1, var2 */`
I'd also be interested to see if we could put type information in a jsdoc somehow, something like:
```js
/**
* @global {string} myGlobal
*/
```
| Suggestion,Needs Proposal,VS Code Tracked,Domain: JavaScript | high | Critical |
226,786,888 | godot | Content margin of stylebox does not work with Popup | **Operating system or device - Godot version:**
all version of Godot
**Issue description:**
<!-- What happened, and what was expected. -->
Content margin value does not work with `Popup` and it's inherited `Control`s.
Would `Popup` be better inherited by `Container` instead of `Control`? | enhancement,discussion,confirmed,topic:gui | low | Major |
226,788,587 | rust | Missed bound check removal | A little test program:
```
#[inline(never)]
fn almost_product(nums: &[i32]) -> Vec<i32> {
let mut result = vec![0; nums.len()];
let mut prod = 1;
for (i, &x) in nums.iter().enumerate() {
result[i] = prod;
prod *= x;
}
result
}
fn main() {
let data = [1, 2, 3, 4, 11];
println!("{:?}", almost_product(&data));
let data = [1, 2, 3, 4, 11, 26, 54, 6];
println!("{:?}", almost_product(&data));
}
```
If I compile it with:
`nightly-x86_64-pc-windows-gnu - rustc 1.19.0-nightly (f4209651e 2017-05-05)`
Using:
`rustc -C opt-level=3 --emit asm test1.rs`
I get this asm for the loop:
```
_ZN5test114almost_product17he2636a2faa7b0543E:
...
.LBB4_9:
cmpq %r12, %rdi
jae .LBB4_10
movl (%r15,%rdi,4), %eax
movl %esi, (%rcx,%rdi,4)
incq %rdi
imull %esi, %eax
addq $-4, %rbx
movl %eax, %esi
jne .LBB4_9
...
.LBB4_10:
leaq panic_bounds_check_loc.5(%rip), %rcx
movq %rdi, %rdx
movq %r12, %r8
callq _ZN4core9panicking18panic_bounds_check17h1fe2f83f670bcee9E
ud2
```
The bound check isn't removed. To remove it I need to use get_unchecked_mut(), or code like this (with the same main function):
```
#![feature(core_intrinsics)]
use std::intrinsics::assume;
#[inline(never)]
fn almost_product(nums: &[i32]) -> Vec<i32> {
let mut result = vec![0; nums.len()];
let mut prod = 1;
for (i, &x) in nums.iter().enumerate() {
unsafe { assume(i < result.len()); }
result[i] = prod;
prod *= x;
}
result
}
```
Now the loop gives a clean asm:
```
.LBB3_11:
movl %edx, %esi
movl (%r12,%rcx,4), %edx
imull %esi, %edx
movl %esi, (%rax,%rcx,4)
incq %rcx
addq $-4, %rdi
cmpq %rcx, %rbx
jne .LBB3_11
```
If I use:
`unsafe { *result.get_unchecked_mut(i) = prod; }`
The loop also gets unrolled four times:
```
.LBB3_15:
movl (%rcx), %esi
imull %edx, %esi
movl %edx, -12(%rbx)
movl 4(%rcx), %edx
imull %esi, %edx
movl %esi, -8(%rbx)
movl 8(%rcx), %esi
imull %edx, %esi
movl %edx, -4(%rbx)
movl 12(%rcx), %edx
imull %esi, %edx
movl %esi, (%rbx)
addq $16, %rbx
addq $16, %rcx
cmpq %rdi, %rcx
jne .LBB3_15
```
| A-LLVM,I-slow,C-enhancement,A-codegen,T-compiler | low | Minor |
226,791,197 | vscode | [theming] Allow theming workbench fonts | Including
- Family
- Weight
- Style/Variant/Features
- Include typeface files in theme pack
- Per-language settings (to support fallbacks, cf. #5260) | feature-request,themes | high | Critical |
226,791,200 | vscode | [theming] Theming for workbench icons | Give one way to specify UI icons. | feature-request,themes | low | Major |
226,872,752 | go | cmd/cgo: never generate Go fields for zero-sized C fields | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
tested with 1.7.5 and 1.8.1
### What operating system and processor architecture are you using (`go env`)?
linux/amd64
### What did you do?
```go
package main
/*
struct foo {
int x;
char padding;
char y[];
};
*/
import "C"
import "fmt"
var Y C.struct_foo
func main() {
fmt.Println(Y.y)
}
```
### What did you expect to see?
Y.y undefined (type C.struct_foo has no field or method y)
(because Y.y is a zero-length field and Go code cannot refer to these fields)
### What did you see instead?
Compiles and prints:
```
[]
```
I've checked that it's dependent on memory alignment. If the `padding` field is removed from struct foo, generated cgo type doesn't have the `y` field. With the padding, the field is included. | NeedsFix,compiler/runtime | low | Major |
226,874,734 | youtube-dl | Site Support Request: samanthabee.com / Core Video Player | ### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.05.07*. 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.05.07**
### 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:
```
$ youtube-dl -v http://samanthabee.com/episode/45/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'http://samanthabee.com/episode/45/']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.05.07
[debug] Python version 2.7.10 - Darwin-16.5.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.2.2-tessus, ffprobe 3.0.2, rtmpdump 2.4
[debug] Proxy map: {}
[generic] 45: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 45: Downloading webpage
[generic] 45: Extracting information
ERROR: Unsupported URL: http://samanthabee.com/episode/45/
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 1955, in _real_extract
doc = compat_etree_fromstring(webpage.encode('utf-8'))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2526, in compat_etree_fromstring
doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 2515, in _XML
parser.feed(text)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
ParseError: syntax error: line 2, column 0
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 760, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 433, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 2834, in _real_extract
raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://samanthabee.com/episode/45/
```
---
### 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**):
- Playlist: http://samanthabee.com/episode/45/
- Single video: https://amanthabee.com/episode/46/clip/not-the-white-house-correspondents-dinner-pt-1-peaches-and-monologue/
- Single video: http://samanthabee.com/episode/bonus-act/clip/steve-king-say-anything-else/
---
### Description of your *issue*, suggested solution and other information
Right clicking on a video on Samanthabee.com reveals that it's using something called the "Core Video Player." I wasn't able to find any information about this player on Google (because it's an extremely generic name), but it may well be in use on other sites as well. | site-support-request | low | Critical |
226,882,931 | pytorch | Cannot find Intel MKL | Attempting to compile pytorch from git, Intel MKL 2017 is not found unless I change in `torch/lib/TH/cmake/FindMKL.cmake`:
```
- SET(mklvers "em64t")
+ SET(mklvers "intel64")
```
and define in the `build_all.sh` script in the cmake call `INTEL_MKL_DIR=$MKLROOT` and `CMAKE_LIBRARY_PATH=/opt/intel/compilers_and_libraries_2017/linux/lib/intel64`. | module: dependency bug,module: build,triaged,module: mkl | low | Major |
226,884,307 | godot | Light2D Mix/Mask mode issues with other lights | Windows 10 x64 - Gtx 680 - GD v.3.0 x64
**Hello, Godot devs...**
I have come across a very make or break issue for me in Godot, and that is when I use a light2D with the blending mode Mix or Mask and if that light2D gets close to some or sometimes all of them, light2D's then it will randomly turn off / or get cut in half... Now if I re-open the scene all the lights who is in or close to the light2D with mix/mask mode will be randomly on or of. I've been experiencing this since 2.1.x and up to now on my main win 10 computer and on my win 10 x86 laptop in the editor or exported version of the project.
**How I reproduce this:**
- Create at least one light2D with mask/mix mode
- Create some normal light2Ds with add mode
- Move around the light with mix mode over the other lights, if all is working as it shud try to re-open the level several times and that shud make some lights behave badly.
**Example project:**
https://www.dropbox.com/s/f0und6dkzzugxx2/Light2DModes_Project.zip?dl=0
[Light2DModes_Project.zip](https://github.com/godotengine/godot/files/989466/Light2DModes_Project.zip) | bug,topic:rendering,confirmed,topic:2d | medium | Major |
226,886,085 | rust | “type must outlive the static lifetime” makes no sense | For the following code
```
pub trait Arbitrary: Sized + 'static {}
impl<'a, A: Clone> Arbitrary for ::std::borrow::Cow<'a, A> {}
```
The diagnostic looks like this:
```
error[E0477]: the type `std::borrow::Cow<'a, A>` does not fulfill the required lifetime
--> <anon>:3:20
|
3 | impl<'a, A: Clone> Arbitrary for ::std::borrow::Cow<'a, A> {}
| ^^^^^^^^^
|
= note: type must outlive the static lifetime
```
The note here makes no sense, because the static lifetime is the longest lifetime of all and cannot really be outlived. We should reword the note so it doesn’t say “outlive”.
Bonus points for explaining where the lifetime requirement comes from, because it is not entirely clear what here introduces the requirement, when the trait and implementation definitions aren’t so close together. | C-enhancement,A-diagnostics,T-compiler | low | Critical |
227,011,705 | TypeScript | Noncrashing property access through non-null assertion operator should narrow that property to NonNullable |
**TypeScript Version:** 2.3 (Playground)
**Code**
Using `strictNullChecks`.
```ts
interface Foo {
optional?: number;
}
interface Bar {
foo?: Foo;
}
function test(bar: Bar) {
if (bar.foo!.optional) {
let num: number = bar.foo.optional;
}
if (bar.foo && bar.foo.optional) {
let num: number = bar.foo.optional;
}
}
```
**Expected behavior:**
No errors or warnings.
**Actual behavior:**
* `num` in first `if` block is `number | undefined`
* `bar.foo` in first `if` block can be `undefined`
| Bug,Help Wanted | low | Critical |
227,044,797 | TypeScript | Object key signature is not taken into account with destructive assignment on method definition level | <!-- BUGS: Please use this template. -->
**TypeScript Version:** 2.3.2
**Code**
```ts
interface IMyInterface {
onChange(changes : {[key : string] : {newValue : any, oldValue : any}})
}
class MyClass implements IMyInterface {
onChange({config}) {
console.log(config);
}
}
class MyAnotherClass implements IMyInterface {
onChange(changes) {
const {config} = changes;
console.log(config);
}
}
```
**Expected behavior:**
compiled without errors
**Actual behavior:**
```
test.ts(5,7): error TS2420: Class 'MyClass' incorrectly implements interface 'IMyInterface'.
Types of property 'onChange' are incompatible.
Type '({config}: { config: any; }) => void' is not assignable to type '(changes: { [key: string]: { newValue: any; oldValue: any; }; }) => any'.
Types of parameters '__0' and 'changes' are incompatible.
Type '{ [key: string]: { newValue: any; oldValue: any; }; }' is not assignable to type '{ config: any; }'.
Property 'config' is missing in type '{ [key: string]: { newValue: any; oldValue: any; }; }'.
```
**Note:** this affects Angular >1.5 users when writing component controllers and implementing `$onChanges` method | Bug | low | Critical |
227,074,518 | go | proposal: io/v2: add Context parameter to Reader, etc. | Related to #18507, it would be nice if the `io` interface methods all took in `Context` as their first parameter. This allows a cancellation signal to be attached directly to the I/O calls that are using them, instead of requiring an out-of-band method, as in `net.Conn`.
This is obviously a backward-incompatible change and would have broad impact on the ecosystem. I wanted to open this as a proposal for consideration in Go 2.
**EDIT:** See [below](https://github.com/golang/go/issues/20280#issuecomment-320712428) for the more backward-compatible proposal
**EDIT 2:** I've written an experience report/blog post detailing the background for this proposal: [Canceling I/O in Go Cap’n Proto](https://medium.com/@zombiezen/canceling-i-o-in-go-capn-proto-5ae8c09c5b29). Feedback and alternatives welcome. | v2,Proposal | high | Critical |
227,097,304 | pytorch | [feature request] Support tensors of different sizes as batch elements in DataLoader | Motivating example is returning bounding box annotation for images along with an image. An annotation list can contain variable number of boxes depending on an image, and padding them to a single length (and storing that length) may be nasty and unnecessarily complex.
```python
import torch.utils.data
loader = torch.utils.data.DataLoader(dataset = [(torch.zeros(3, 128, 128), torch.zeros(i, 4)) for i in range(1, 3)], batch_size = 2)
for batch in loader:
print(batch)
```
Currently this blows with a message below because collate wants to `torch.stack` batch elements, regardless if they have same size:
```
File "...torch/utils/data/dataloader.py", line 188, in __next__
batch = self.collate_fn([self.dataset[i] for i in indices])
File ".../torch/utils/data/dataloader.py", line 110, in default_collate
return [default_collate(samples) for samples in transposed]
File ".../torch/utils/data/dataloader.py", line 92, in default_collate
return torch.stack(batch, 0, out=out)
File ".../torch/functional.py", line 56, in stack
inputs = [t.unsqueeze(dim) for t in sequence]
RuntimeError: cannot unsqueeze empty tensor at .../torch/lib/TH/generic/THTensor.c:530
```
Returning a list instead of variable-sized tensor doesn't work either. Providing a custom collate isn't very nice either, since most of the default behavior needs to be copied, and the default collate doesn't allow hooks.
A solution would be either adding an easy way to extend the default collate, or changing the first collate's branch to something like:
```python
if all(map(torch.is_tensor, batch)) and any([tensor.size() != batch[0].size() for tensor in batch]):
return batch
```
As a workaround, I'm currently monkey-patching the default collate like this:
```python
collate_old = torch.utils.data.dataloader.default_collate
torch.utils.data.dataloader.default_collate = lambda batch: batch if all(map(torch.is_tensor, batch)) and any([tensor.size() != batch[0].size() for tensor in batch]) else collate_old(batch)
```
cc @SsnL @VitalyFedyunin @ejguan @NivekT @cpuhrsch | feature,module: dataloader,triaged,module: nestedtensor | medium | Critical |
227,104,300 | flutter | Document why files are in the template | Before we add more files to the template, I think we should make sure the template contains a README that documents, for each file in the template:
* What the file is for
* Why you would edit that file
* How to verify that the edits are valid
* How to test the file
The template is growing really big and it's not at all clear why some of these files are part of the user code and not just part of the framework.
We should also have a test that verifies that all files created by "flutter create" have an entry in this README file. | team,tool,d: examples,d: wiki,P2,team-tool,triaged-tool | low | Major |
227,167,656 | TypeScript | Extra entries for JavaScript auto complete(intellisense) make no sense | <!-- 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.2.1 / nightly (2.2.0-dev.201xxxxx)
**Code**
The following code in javascript:
```js
/**
* @param {MessageActivity} activity
* @param {IConversationContext} context
*/
export function Prompt_beforeResponse(activity, context)
{
// MessageActivity is defined in typescript definition provided to the editor as having 4 properties (attachements, text, speak, type).
// Typing activity. will show those for properties but also:
// activity - why should activity be under itself?
// context - why should the second parameter be under activity?
// IConversationContext - why would a type, that is not a property in any object be under activity?
// MessageActivity - same question as above
// onRun - why should a global function be under activity
// Prompt_when - same as above
// Prompt_beforeResponse - same question as above and this is the function itself
// Here is another example. obj. should display only a and b, but it also shows activity, context, MessageActivity, IConversationContext, etc.
/**
* @type {{a: number, b: string }}
*/
var obj = {};
obj.
}
```
```ts
// A *self-contained* demonstration of the problem follows...
```
**Expected behavior:**
When a javascript type is not "any", i.e. when it is definded in jsdoc or in the typescript definition helper (See https://github.com/Microsoft/TypeScript/wiki/JavaScript-Language-Service-in-Visual-Studio#unsupported-patterns) only those defined members should be part of intellisense.
Even if the type is any, throwing everything on intellisense like that defeats the purpose of finding out what reasonably could be under the object.
**Actual behavior:**
A bunch of extra entries show up in intellisnese that make no sense for either typed or untyped scenarios, but it is specially bad for typed scenarios where some thought was put in place in what should appear in intellisense. Adding all those entries makes the intellisense feature less useful.
| Suggestion,Committed,Domain: Completion Lists,Domain: JavaScript | low | Critical |
227,184,064 | go | os/exec: Cmd produces misleading error when using Setpgid | ### What version of Go are you using (`go version`)?
```
$ go version
go version go1.8.1 darwin/amd64
```
### What operating system and processor architecture are you using (`go env`)?
```
$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/aron/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/ts/s940qvdj5vj1czr9qh07fvtw0000gn/T/go-build901749947=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
```
### What did you do?
```go
package main
import (
"fmt"
"os/exec"
"syscall"
)
func main() {
var cmd *exec.Cmd
var err error
cmd = exec.Command("/bin/ls")
cmd.Dir = "/this/does/not/exist"
cmd.SysProcAttr = &syscall.SysProcAttr{
Setpgid: true,
}
err = cmd.Run()
fmt.Printf("error was: %v\n", err)
cmd = exec.Command("/bin/ls")
cmd.Dir = "/this/does/not/exist"
err = cmd.Run()
fmt.Printf("error was: %v\n", err)
}
```
### What did you expect to see?
```
$ go run baddir.go
error was: chdir /this/does/not/exist: no such file or directory
error was: chdir /this/does/not/exist: no such file or directory
```
### What did you see instead?
```
$ go run baddir.go
error was: fork/exec /bin/ls: no such file or directory
error was: chdir /this/does/not/exist: no such file or directory
```
Note that the error string makes the reader believe that "/bin/ls" is the thing that may not exist. Compare when not using `Setpgid`; the working directory is properly reported as not existing. | NeedsInvestigation | low | Critical |
227,185,184 | rust | Non-optimal derived PartialEq for POD struct | Given a struct like
```rust
pub struct Foo {
a: bool,
b: bool,
c: bool,
d: bool
}
```
I would expect generated asm to be doing a dword comparison to check for equality. However, that's not what is seen unless explicitly transmuting before the comparison (interactive: https://godbolt.org/g/kYPaOh).
The `PartialEq` implementation looks something like:
```rust
pub fn eq(a: &Foo, b: &Foo) -> bool {
a.a == b.a &&
a.b == b.b &&
a.c == b.c &&
a.d == b.d
}
```
which produces the assembly:
```asm
example::eq:
push rbp
mov rbp, rsp
mov al, byte ptr [rdi]
cmp al, byte ptr [rsi]
jne .LBB0_1
mov al, byte ptr [rdi + 1]
cmp al, byte ptr [rsi + 1]
jne .LBB0_1
mov al, byte ptr [rdi + 2]
cmp al, byte ptr [rsi + 2]
jne .LBB0_1
mov cl, byte ptr [rdi + 3]
mov al, 1
cmp cl, byte ptr [rsi + 3]
je .LBB0_3
.LBB0_1:
xor eax, eax
.LBB0_3:
pop rbp
ret
```
An optimized version using transmute (Rust):
```rust
pub fn eq_transmute(a: &Foo, b: &Foo) -> bool {
unsafe {
transmute_copy::<_, u32>(a) == transmute_copy::<_, u32>(b)
}
}
```
produces the assembly:
```asm
example::eq_transmute:
push rbp
mov rbp, rsp
mov eax, dword ptr [rdi]
cmp eax, dword ptr [rsi]
sete al
pop rbp
ret
```
Is this an optimization we should expect to be handled automatically? | A-LLVM,I-slow,C-enhancement,T-compiler,C-optimization | low | Minor |
227,195,760 | rust | Compiling to Webassembly quickly fills up available RAM and crashes computer | When compiling to wasm on a Dell XPS 13 running Ubuntu 16.10, rustc begins using more and more RAM until the computer begins thrashing and eventually becomes unusable.
rustc version: `rustc 1.19.0-nightly (f4209651e 2017-05-05)`
Judging by the `--verbose` output, cargo doesn't even get as far as calling `emcc` before compilation gets bogged down.
Happy to help debug further. | I-slow,C-enhancement,O-wasm | low | Critical |
227,300,123 | go | x/mobile: how to change screen to landscape | Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?
go version 1.8
gomobile version +0f31740 Wed Apr 19 17:20:05 2017 +0000 (android,ios); androidSDK=
### What operating system and processor architecture are you using (`go env`)?
CGO_ENABLE=1 arm64 darwin
### What did you do?
the default example are all in portrait screen mode
### What did you expect to see?
screen change to landscape
### What did you see instead?
no api to change that
| NeedsInvestigation,FeatureRequest,mobile | low | Minor |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.