Anonymous | Login | 03-01-2021 19:49 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0003265 | [Squeak] Network | major | random | 03-07-06 21:18 | 03-07-06 21:18 | |||||||
Reporter | renggli | View Status | public | |||||||||
Assigned To | cdegroot | |||||||||||
Priority | normal | Resolution | open | |||||||||
Status | assigned | Product Version | 3.9 | |||||||||
Summary | 0003265: (Fast)SocketStream SocketStream>>upTo: is broken | |||||||||||
Description | There is a bug in the implementation of #upTo:, however it is quite hard to reproduce: What I observe is that sometimes the "inBuffer at: lastRead" is actually pointing at the character I am looking for, but the socket stream is trying to load new data and then times-out. | |||||||||||
Additional Information | ||||||||||||
Attached Files | ||||||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
32 total queries executed. 27 unique queries executed. |