Here, ‘current’ is #f, hence the type error. We could be defensive andcheck whether ‘current’ is #f before proceeding; however, it’s “notsupposed to happen” as that indicates an inconsistency: that ‘status’doesn’t match reality. The root cause is probably that (guix status) missed a trace, one ofthese “@ download-progress …” lines, which would probably be a bug in‘build-event-output-port’. Or it could be that the output fromguix-daemon is already intermingled, though that’s again not supposed tohappen. Perhaps the best course of action here would be to hammer‘build-event-output-port’ with semi-randomly generated data until we canreproduce the bug, assuming this is where it takes place. Thanks,Ludo’.