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
Maybe every time we open mill-chrome-profile.json, we should check if one exists, and if one does then open mill-chrome-profile-2.jsonmill-chrome-profile-3.json etc.. We can wipe out all mill-chrome-profile*.jsons at the start of each run. This would ensure that all profiles are saved, even if multiple evaluation runs are started re-entrantly
The same should probably be done for the other mill-* debug files, mostly mill-profile.json I think
I think this is because evaluator command use dedicated evaluator instances which don't use the outer profile logger. Instead, we could pass the profile logger around.
Evaluator commands make the
out/mill-chrome-profile.json
un-useful since they seem to overwrite it.Here is an example, where
idea
is a customized derivate ofmill.idea.GenIdea/idea
.While the command is still running, I can see a partially filled
out/mill-chrome-profile.json
with lots of details:But after the command finishes, the
out/mill-chrome-profile.json
looks less useful:The text was updated successfully, but these errors were encountered: