-
Notifications
You must be signed in to change notification settings - Fork 106
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
Flush log output immediately #78
Comments
Ah, I forget to look around for separate release/dev branches... |
It did work, thanks again to both of you. I did get a preliminary version of BladeBit support in plotman last night in ericaltendorf/plotman#916. Other than the automated tests, I am only aware of it having been run briefly on my insufficient laptop where it was able to launch and detect a BladeBit process. |
Thank you, Kyle! I appreciate you making this available for your vast community. |
I am just now getting around to trying to add BladeBit support to plotman. Generally speaking the multiple-process scheduling features of plotman should be much less useful for BladeBit, but it makes it easier for people to experiment with configurations and still handle plotting and archiving from the single tool. Anyways...
When the output of BladeBit is redirected to a file it ends up buffering until the flush at the end (well, I didn't wait that long what with only 64GB of RAM at the moment but...). plotman would like to have regular updates so that it can track the progress of the plot. With the logging functions already being centralized it looks like this could be a straightforward change.
Does this seem like a good change for BladeBit?
The text was updated successfully, but these errors were encountered: