Skip to content
Snippets Groups Projects
Select Git revision
  • main default protected
  • next protected
  • UI-EvenMoreTweaks
  • merge/materials_featurette protected
  • merge/webrtc protected
  • darl/linux-sh-installer
  • xenhat/maint/bolt
  • xenhat/features/cinematic-mode-new
  • screensquare
  • ssestuff
  • spdlog
  • 7.1.7.2486-beta
  • 7.1.4.2442-beta
  • 7.1.4.2413-beta
  • 7.1.3.2338-beta
  • 7.1.3.2332-beta
  • 7.1.2.2304-beta
  • 7.1.1.2251-beta
  • 7.0.1.2244-beta
  • 7.0.1.2240-beta
  • 7.0.1.2230-beta
  • 7.0.1.2206-beta
22 results

tests

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Nat Goodspeed authored
    While we're accumulating the 'length:' prefix, the present socket-based logic
    reads 20 characters, then reads 'length' more, then discards any excess (in
    case the whole 'length:data' packet ends up being less than 20 characters).
    That's probably a bug: whatever characters follow that packet, however short
    it may be, are probably the 'length:' prefix of the next packet. We probably
    only get away with it because we probably never send packets that short.
    Earlier llleap_test.cpp plugin logic still read 20 characters, then, if there
    were any left after the present packet, cached them as the start of the next
    packet. This is probably more correct, but complicated. Easier just to read
    individual characters until we've seen 'length:', then try for exactly the
    specified length over however many reads that requires.
    30e8e23d
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.