BUG #18842: Wrong state in pg_stat_replication?

The following bug has been logged on the website:

Bug reference: 18842
Logged by: Bowen Shi
Email address: zxwsbg12138@gmail.com
PostgreSQL version: 15.6
Operating system: centos
Description:

Hi dears,

I recently discovered that when the primary->standby connection fails (I'm
afraid I'm not sure about the cause of the primary-standby interruption, it
is likely due to WAL forking.). The state of pg_stat_replication cycles
continuously from
walsender process start -> catchup -> streaming -> walsender process exit.

And the walsender process only existed in less than 1 second. I would like
to know if anyone has encountered a similar scenario before? And do we have
any discussion about this?