#development
- r
rough-minister-58256
06/12/2018, 5:10 AMđź‘Ť - a
aloof-angle-91616
06/12/2018, 5:28 AMthanks, squashed and merged - a
aloof-angle-91616
06/12/2018, 7:45 AM@witty-crayon-22786 do you know why i might be seeing this error in the export integration test? i'm seeing this zinc output and it's complaining about
not being a real command, which it didn't do before my PR, and i've been trying to track down why for a while. the output is in this comment here: https://github.com/pantsbuild/pants/pull/5815#issuecomment-396424884-X123w- 2
- 2
- r
rough-minister-58256
06/13/2018, 2:26 AMCopy codeerror[E0477]: the type `futures::AndThen<futures::Join<futures::MapErr<std::boxed::Box<futures::Future<Error=std::io::Error, Item=std::vec::Vec<std::option::Option<fs::PathStat>>> + std::marker::Send>, [closure@process_execution/src/local.rs:57:42: 57:90]>, futures::MapErr<std::boxed::Box<futures::Future<Error=std::io::Error, Item=std::vec::Vec<fs::PathStat>> + std::marker::Send>, [closure@process_execution/src/local.rs:53:41: 53:88]>>, std::boxed::Box<futures::Future<Error=std::string::String, Item=fs::Snapshot> + std::marker::Send>, [closure@process_execution/src/local.rs:60:17: 75:8 self:&&local::CommandRunner, posix_fs:std::sync::Arc<fs::PosixFS>]>` does not fulfill the required lifetime --> process_execution/src/local.rs:75:10 | 75 | }).to_boxed() | ^^^^^^^^ | = note: type must satisfy the static lifetime` - r
rough-minister-58256
06/13/2018, 2:28 AMwhen trying to break out a new method on
in this diff: https://gist.github.com/kwlzn/fe28eeb4779c1e865f519fcde0d0f44aCommandRunner - r
rough-minister-58256
06/13/2018, 2:29 AMwhat am I missing there? - r
rough-minister-58256
06/13/2018, 2:57 AMhmm, going from
to&self
fixed one instance of thatself - r
rough-minister-58256
06/13/2018, 2:59 AMnow just:Copy codeCompiling process_execution v0.0.1 (file:///Users/kwilson/dev/pants/src/rust/engine/process_execution) error[E0477]: the type `futures::Map<futures::Map<futures::AndThen<futures::Map<futures::MapErr<futures::FutureResult<fs::PosixFS, std::string::String>, [closure@process_execution/src/local.rs:124:20: 129:12]>, [closure@process_execution/src/local.rs:130:16: 130:45]>, std::boxed::Box<futures::Future<Error=std::string::String, Item=fs::Snapshot> + std::marker::Send>, [closure@process_execution/src/local.rs:131:21: 133:12 self:&&local::CommandRunner, output_file_paths:std::collections::BTreeSet<std::path::PathBuf>, output_dir_paths:std::collections::BTreeSet<std::path::PathBuf>]>, [closure@process_execution/src/local.rs:135:16: 135:42 workdir:local::tempfile::TempDir]>, [closure@process_execution/src/local.rs:136:16: 136:43]>` does not fulfill the required lifetime --> process_execution/src/local.rs:137:12 | 137 | .to_boxed() | ^^^^^^^^ | = note: type must satisfy the static lifetime - r
rough-minister-58256
06/13/2018, 2:59 AM - r
rough-minister-58256
06/13/2018, 3:00 AMbrb, need to walk the dog - r
rough-minister-58256
06/13/2018, 3:54 AMseems like that would compile if I madefn run(s/&self/self/
but I feel like there’s probably a better way that involves.. explicit lifetimes?) - a
aloof-angle-91616
06/13/2018, 3:59 AM@rough-minister-58256 the limit of my understanding is basically that futures are always
for every borrowed thing you have in them'static - a
aloof-angle-91616
06/13/2018, 4:00 AMand the nice part about async await is that it is supposed to ease that let me find the blog post - r
rough-minister-58256
06/13/2018, 4:00 AMah sounds familiar-ish - a
aloof-angle-91616
06/13/2018, 4:00 AM - a
aloof-angle-91616
06/13/2018, 4:01 AM(couldn't find a less intense blog post) - a
aloof-angle-91616
06/13/2018, 4:02 AMso like i think you can also start throwing out clones in like the return values of things, but i'm not sure why that error message is so nonspecific - a
aloof-angle-91616
06/13/2018, 4:03 AMoh right, it's&self - a
aloof-angle-91616
06/13/2018, 4:03 AM(it's not clear why the
bound needs to exist to me but i'm sure there's a good one)'static - r
rough-minister-58256
06/13/2018, 4:26 AMcaving in and installing rust-intellij - r
rough-minister-58256
06/13/2018, 4:27 AMis there an ideal way to feed all of the disparate Cargo.toml’s into intellij? - a
aloof-angle-91616
06/13/2018, 4:30 AMdoes it not handle that? that's frustrating, that should be a normal cargo thing - a
aloof-angle-91616
06/13/2018, 4:31 AMi've been using emacs but i'll honestly jump in and try to set it up - r
rough-minister-58256
06/13/2018, 4:32 AMhm - r
rough-minister-58256
06/13/2018, 4:32 AMsays “No cargo projects found” and prompts me to “Attach” one, when i load the root Cargo.toml it persists - r
rough-minister-58256
06/13/2018, 4:33 AMand can’t e.g. “build” - e
enough-analyst-54434
06/13/2018, 4:43 AMJust a sec, but short of it is you just feed the root Cargo.toml - a
aloof-angle-91616
06/13/2018, 4:43 AMyeah, that worked for me just now! - e
enough-analyst-54434
06/13/2018, 4:49 AMYeah, so after doing https://github.com/pantsbuild/pants/tree/master/src/rust/engine#configuring-intellij-to-work-with-rust, I just add a Rust module to my project: - e
enough-analyst-54434
06/13/2018, 4:49 AMThen add
as a source root.src/rust/engine