-
Notifications
You must be signed in to change notification settings - Fork 96
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
thread 'main' has overflowed its stack #68
Comments
@steveklabnik I tested it myself and got
...since #58 looping through workspace members is not supported yet. Which version of |
> cargo outdated --version
cargo-outdated v0.4.0 I had just run 'cargo-install'. |
@steveklabnik Well, I don't have the permission to publish the new But even though since I haven't got time to do #58 , it cannot be used on a virtual manifest out of the box yet. Maybe a simple Bash script could do the job for now. |
Ah interesting, thanks! (Also, This seems bad though; what happened? I really love cargo-outdated. How hard do you think #58 is? |
@steveklabnik @kbknapp has been a bit busy recently, let's just wait him to be back patiently :) I don't think #58 would be too hard. Basically it would be a matter of replacing |
My apologies! Yeah my time has been monopolized lately, @Frederick888 I'll add you so you can publish new version as well. |
@Frederick888 you should be able to publish new versions to crates.io now as well. Aside, feel free to add yourself to the authors array as well, I think you've earned it 😉 |
Ah, it's all good! Everyone needs some time off. Looks like @kbknapp came back briefly between now and then; thank you for one of the most useful cargo commands! |
@kbknapp Many thanks! I have just published I think I'm going to close this issue in support of #58. And by the way, I have assigned #58 with a P1 label and I'd work on it first if I can make some time. My uni assessments are killing me right now lol... |
This happens whenever I run
cargo-outdated
in the Rust repository's src directory.Rust 1.20.
The text was updated successfully, but these errors were encountered: