You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
When running migrations, there is some extra, unnecessary logging that gets left around in the terminal.
The things to note in the screenshot are the extra "Blocks: 0...." and "Saving migration to chain." at the end. You can also see that there is a "Blocks: 0..." in the second line of data under the "Replacing 'MetaCoin'" section which I don't believe should be there.
I'm also pretty sure that ora plays a role in this code getting left around as it doesn't really play well with other logs that get printed. You can often get some pretty weird, ugly results using this spinner package while logging other things. It might be just that the spinner is not stopped at the appropriate time during the logging of all this information or some other async nonsense that is not supposed to be occurring.
The text was updated successfully, but these errors were encountered:
When running migrations, there is some extra, unnecessary logging that gets left around in the terminal.
![Screen Shot 2021-12-16 at 5 15 04 PM](https://user-images.githubusercontent.com/14827965/146457130-bc5feb62-c320-4660-86f9-8e9d597c2433.png)
The things to note in the screenshot are the extra "Blocks: 0...." and "Saving migration to chain." at the end. You can also see that there is a "Blocks: 0..." in the second line of data under the "Replacing 'MetaCoin'" section which I don't believe should be there.
This comes from the migrations logging, and more specifically from this bit of code and involves this method and maybe this method.
I'm also pretty sure that ora plays a role in this code getting left around as it doesn't really play well with other logs that get printed. You can often get some pretty weird, ugly results using this spinner package while logging other things. It might be just that the spinner is not stopped at the appropriate time during the logging of all this information or some other async nonsense that is not supposed to be occurring.
The text was updated successfully, but these errors were encountered: