Closed xobs closed 7 years ago
I have the same problem on 1.16 nightly, however cargo run --example router
works well though (even though it's basically the same code)
Found it : staticfile
has still the old dependencies on crates.io ( iron 0.4 , mount 0.2 ), @untitaker can we get dependencies bump and a version bump on crates.io as well ?
@xobs : in the meanwhile, replace staticfile = "*"
by
staticfile = {git = "https://github.com/iron/staticfile.git"}
Blocked by latest iron-test version on Crates.io not supporting Iron 0.5. @reem please move project to iron org
On Sat, Feb 04, 2017 at 05:31:48AM -0800, Cobrand wrote:
Found it :
staticfile
has still the old dependencies on crates.io ( iron 0.4 , mount 0.2 ), @untitaker can we get dependencies bump and a version bump on crates.io as well ?@xobs : in the meanwhile, replace
staticfile = "*"
bystaticfile = {git = "https://github.com/iron/staticfile.git"}
-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/iron/staticfile/issues/94#issuecomment-277446084
@untitaker he actually moved iron-test to iron organization, but someone needs to release a new version.
Yeah i can't do that
On 5 February 2017 10:29:47 CET, Onur Aslan notifications@github.com wrote:
@untitaker he actually moved iron-test to iron organization, but someone needs to release a new version.
-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/iron/staticfile/issues/94#issuecomment-277507212
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Just did cargo owner --add github:iron
which I believe should let people in the iron organization release new versions. Please let me know if that did not work!
Yeah that didn't work, unfortunately.
I've recreated the iron organization dev-team
team and am attempting cargo owner --add github:iron:dev-team
, but cargo is telling me I have to be part of the team (which I am) to add it. I think this is likely to be an ephemeral error (since I just created the team) so I'll try again in an hour or so.
Alright, for whatever reason I am still not able to add dev-team
to the package, but I have released iron-test
0.5.0
.
released 0.4.0
On Sun, Feb 05, 2017 at 08:21:48AM -0800, Jonathan Reem wrote:
Alright, for whatever reason I am still not able to add
dev-team
to the package, but I have releasediron-test
0.5.0
.-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/iron/staticfile/issues/94#issuecomment-277530149
I guess you can close that @xobs
This appears to be back when using iron 0.6.0
Cargo.toml looks like
[dependencies]
handlebars-iron = "0.25.2"
router = "0.5.1"
maplit = "*"
staticfile = "*"
mount = "*"
iron = "0.5.1"
Offending line looks like
let mut mount = Mount::new();
mount.mount("/assets/", Static::new(Path::new("src/assets")));
error is
the trait `for<'r, 'r, 'r> std::ops::Fn<(&'r mut iron::request::Request<'r, 'r>,)>` is not implemented for `staticfile::Static`
UPDATE It was because mount updated to iron 0.6.0. So if i pin everything to the iron 0.5.1 supported crates it works fine.
@martincalvert can you post the Cargo.toml that worked for you?
@jessbowers I believe this is what i ended up with https://github.com/SensorArray/sensor_rust/blob/master/Cargo.toml
I believe the issue is those lines https://github.com/iron/staticfile/blob/master/Cargo.toml#L15-L16 but Iron 0.6 is not compatible with Iron 0.5 apparently so try a combination of cargo clean
and cargo update
to fix it
If I copy the example from README.md into a main.rs file and run it, the resulting files does not build. I get the following output:
This is using the example from README.md:
My Cargo.toml contains:
This was built using the latest Rust 1.15.