-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to figure out which tests are flaky and fix, adding debug info… #140
Changes from all commits
b411bea
8c32d47
869085d
d8540c9
26c92d5
6bdceae
269855a
bfea3c1
ff6a7d3
4c858f0
f876f67
21dd3b0
4410665
131ab1d
e4623d6
cb10c20
1f73209
eb0e4c7
8b43d2e
55a7df7
40a7015
48fdc3a
99d9e78
75354b2
de44534
b27a872
70d7a67
e060f30
f1090e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,7 +4,7 @@ | |
|
||
#[cfg(feature = "ros1")] | ||
#[tokio::main] | ||
async fn main() -> Result<(), Box<dyn std::error::Error>> { | ||
async fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync>> { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why make the return of There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should punt to #118 I ended up having to add this bound in a number of places to make it valid to return the errors from tasks. |
||
use roslibrust::NodeHandle; | ||
|
||
simple_logger::SimpleLogger::new() | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it was necessary to remove this macro entirely. It just didn't need to be changing the working directory. Like it just need to prepend the provided paths in the macro with the manifest directory path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to remove because I do think it is just a bad API (like the method name is a joke) we could have fixed it, but I really think this macro came about from me not understanding aspects of when macros were expanded and what working directory / cargo manifest dir were under different circumstances.
I think ultimately we figure out a new API in the future for the same reason.