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
Apparently the call to p4.exe print -q fails. The file in question is 272kb.
Edit: To clarify this only happens when editing an open file via the changelist. If I manually diff a file it seems to call p4.exe print -q -o to a tmp file, which works fine.
The text was updated successfully, but these errors were encountered:
The default value for perforce.maxBuffer is 204800 (200KB)
You can increase it to your needs in your user profile. I personally set it to 1MB on large projects:
{
"perforce.maxBuffer": 1048576
}
I might increase the default value on the next release
Perhaps a good thing to do would be to at least catch this error and report it to the user, as it seems to just hang there and do nothing and without examining the output log you'd have no clue that an error had happened.
The error should display in the status bar, next to the p4 icon, for a few seconds, although it might not be that much noticeable.
It was previously displaying as a message box next to the command palette, but people found it annoying. I should probably priorities some error messages, and implement a mechanism to individually ignore them.
Apparently the call to
p4.exe print -q
fails. The file in question is 272kb.Edit: To clarify this only happens when editing an open file via the changelist. If I manually diff a file it seems to call
p4.exe print -q -o
to a tmp file, which works fine.The text was updated successfully, but these errors were encountered: