Modify ↓
Opened 18 years ago
Closed 17 years ago
#155 closed defect (wontfix)
ParseError from slave
Reported by: | doug@… | Owned by: | cmlenz |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | BEEP implementation | Version: | 0.5.3 |
Keywords: | Cc: | ||
Operating System: | Linux |
Description
I'm getting a parse error in the bitten slave. It looks similar to #119, but my master and slave are both running on Linux, and are in fact the same box.
When I trigger a build, I get the traceback:
Traceback (most recent call last): File "asyncore.py", line 69, in read obj.handle_read_event() File "asyncore.py", line 391, in handle_read_event self.handle_read() File "asynchat.py", line 137, in handle_read self.found_terminator() File "build/bdist.linux-i686/egg/bitten/util/beep.py", line 278, in found_terminator File "build/bdist.linux-i686/egg/bitten/util/beep.py", line 311, in _handle_frame File "build/bdist.linux-i686/egg/bitten/util/beep.py", line 465, in handle_data_frame File "build/bdist.linux-i686/egg/bitten/slave.py", line 98, in handle_msg File "build/bdist.linux-i686/egg/bitten/util/xmlio.py", line 182, in parse ParseError: not well-formed (invalid token): line 1, column 1
I'm happy to provide some help debugging, if you can tell me what you need to know.
Attachments (0)
Change History (1)
comment:1 Changed 17 years ago by cmlenz
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The BEEP stuff is being phased out for the next release.