Describe the bug
So I wanted to run the new du command, and then this happened 馃槄

I assume it caused by the new security features introduced with Catalina, i.e. https://www.howtogeek.com/443611/how-macos-catalinas-new-security-features-work/
System
I'm running
Works for me.
Did you run this in a directory where there was a subdirectory/file that your account didn't have the privileges to stat? I'm guessing that's the problem, which is still a bug, just interested if that's the problem. You can try running ^du -d1 to see if it has the same issue (although it may complete, but may output errors to stderr).
Ah, you're right! Running ^du I get errors like:
du: ./Library/Application Support/CallHistoryTransactions: Operation not permitted
du works fine in 'regular' directories.
I'd consider it an enhancement then to limit the impact of these errors and still list all other directories.
Yeah, I think there's a more general enhancement here, or at least something to think about: when an output stream emits an error, should we fail immediately, or ignore? I think the latter shouldn't be done automatically, but perhaps a user could request it.
[EDIT]
To back up why I think the above w.r.t. an example. If we ignored errors in du's output stream, we'd be providing incomplete information, and users may not realize that.
Most helpful comment
Ah, you're right! Running
^duI get errors like:duworks fine in 'regular' directories.I'd consider it an enhancement then to limit the impact of these errors and still list all other directories.