Bug 58144 - [Connection] should not use multiple status objects to split long message
Summary: [Connection] should not use multiple status objects to split long message
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 minor (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-04-12 11:13 EDT by Rafael Chaves CLA
Modified: 2019-09-06 16:14 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Chaves CLA 2004-04-12 11:13:34 EDT
See the last 4 sub-entries in the log section below. The use of subentries to
separate the sentences of a message seems awkward. Is it to show easily readable
messages in the log view? Or is it because long messages are not properly
wrapped when written to the log file? If it is the latter, this would be a case
for a bug/enhacement request against Platform/Core. The former does not look
like a sound reason, since it makes reading the log file directly much harder
(and it looks like a misuse of status objects).

!ENTRY org.eclipse.team.core 4 -6 Apr 11, 2004 04:08:17.449
!MESSAGE CVS Workspace
!SUBENTRY 1 org.eclipse.team.core 4 0 Apr 11, 2004 04:08:17.481
!MESSAGE An error occurred refreshing /org.eclipse.core.tests.runtime: I/O has b
een interrupted.
!STACK 1
org.eclipse.team.internal.ccvs.core.connection.CVSCommunicationException[0]: jav
a.io.InterruptedIOException: Timeout while reading from input stream
        at org.eclipse.team.internal.core.streams.PollingInputStream.read(Pollin
gInputStream.java:123)
... (frames intentionally omitted)
!SUBENTRY 2 org.eclipse.team.cvs.core 4 0 Apr 11, 2004 04:08:17.840
!MESSAGE I/O has been interrupted.
!STACK 0
java.io.InterruptedIOException: Timeout while reading from input stream
        at org.eclipse.team.internal.core.streams.PollingInputStream.read(Pollin
gInputStream.java:123)
... (frames intentionally omitted)
!SUBENTRY 3 org.eclipse.team.cvs.core 4 4 Apr 11, 2004 04:08:17.840
!MESSAGE The most likely cause of the interrupt is either an intermittent networ
k failure or a communications timeout.
!SUBENTRY 3 org.eclipse.team.cvs.core 4 4 Apr 11, 2004 04:08:17.856
!MESSAGE The CVS communications timeout can be adjusted in the Team/CVS preferen
ces.
!SUBENTRY 3 org.eclipse.team.cvs.core 4 4 Apr 11, 2004 04:08:17.856
!MESSAGE Another possible cause is the improper configuration of the "ext" conne
ction method.
!SUBENTRY 3 org.eclipse.team.cvs.core 4 4 Apr 11, 2004 04:08:17.856
!MESSAGE The "ext" connection method can be configured on the Team/CVS/EXT Conne
ction Method preference page
Comment 1 Jean-Michel Lemieux CLA 2004-06-11 16:50:56 EDT
Post 3.0
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:14:20 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.