my scp'ed files are getting truncated at 204800 bytes after upgrading openssh

Discussed in https://github.com/PowerShell/Win32-OpenSSH/discussions/2096

^{Originally posted by tomwlane July 12, 2023}
my scp'ed files are getting truncated at 204800 bytes after upgrading openssh to v9.2.2.0p1-Beta

I'm using an openbsd client on windows (git/bash for windows), it works on other systems, all other combinations actually, but this one system to my one upgraded system just truncates the thing last minute like.

heres the log from the client

scp: debug3: Received data 256977920 -> 257009159
scp: debug3: Short data block, re-requesting 257009160 -> 257080319 ( 1)
scp: debug3: Finish at 257080320 ( 1)
scp: debug3: Received reply T:101 I:2522 R:1
nfhl_s_fld_haz_ar.shp 100% 245MB 19.0MB/s 00:12
scp: debug1: truncating at 204800
scp: debug3: Sent message SSH2_FXP_CLOSE I:2523
scp: debug3: SSH2_FXP_STATUS 0
debug2: channel 0: read failed rfd 5 maxlen 32768: Broken pipe
debug2: channel 0: read failed

$ ls -l nfhl_s_fld_haz_ar.shp
-rw-r--r-- 1 AzureAD+TomLane 4096 204800 Jul 12 08:41 nfhl_s_fld_haz_ar.shp

and on the server
$ sshd -v
OpenSSH_9.3p1, OpenSSL 1.1.1u 30 May 2023

Start with discussion 2096 and the attached scp debug log, comparing the reported OpenSSH 9.2.2.0p1-Beta client behavior with the OpenSSH 9.3p1 server. Trace why the transfer completes but the destination is truncated at 204800 bytes; done means the same reproduction transfers the full file without the truncation message.