Timestamp issues for upstream crates on http repo

[pnkfelix]

I do not have very much to report here because I have not been able to narrow it down exactly.

I just wanted to make a note of the problem.

Here's the issue: I'm building a crate A and it has as build dependency on a different crate B.

• crate B is located at an https location on github (though that may be a red herring), and
• crate B's source is checked in using .md files, not .rs files (thought that may be a red herring).

All I know is that during the build of crate A, I am seeing:

thread 'main' panicked at 'called Result::unwrap() on an Err value: CheckInputError { error: Error(TangoStampOlderThanTarget { tgt: "src/svg/mod.rs" }, Transform { source_time: Timestamp { secs: 1475233056, nsecs: 0 }, target_time: Modified(Timestamp { secs: 1474498671, nsecs: 0 }), original: "src/svg/mod.md", generate: "src/svg/mod.rs" }) }', ../src/libcore/result.rs:799

(where the src/svg/mod.md is the code from crate B.)

cargo clean does nothing to fix this.

---

(Or maybe this is somehow an artifact of my own messing with the multirust internal checkout of the crate in question? So many questions...)

[paholg]

I am having the same issue, and it crops up when I do either of the following:

1. Edit .rs file, build, edit .md file, build -> Error
2. Edit .md file, build, edit .rs file, build -> Error

The only way I have found to fix it is to delete either the .rs or the .md file.

I have one dependency, but while I'm working on this crate, I'm also editing that dependency and one of its dependencies. As a result, I am pointing at a local version of it, and I have a line that replaces another crate down the line with a git version.

You can see the repo here: https://github.com/paholg/monte-carlo-test/tree/01c2e4165e75e25963bc3cd7b21a5c6098db11c4

[alobaid]

I have the same issue
Edit .rs file, build, edit .md file, build -> Error
Edit .md file, build, edit .rs file, build -> Error

[pnkfelix]

Okay sorry that I have not been on top of this; thanks to you two for noting that you are also encountering this (and for sharing your code in the casing where it is arising).

[pnkfelix]

Note to @paholg and @alobaid: I'm sorry it took me ages to look further into this.

I would not be surprised if the problem each of you was encountering might have in fact been issue #13.

I hope to upload a new version of tango to crates.io as soon as I can.