Bitgroup/Bugs

Current bugs

Bug #3 (2013-09-07)

An ugly hack is required to ensure that all change events are sent since the last sync request. I'm having to double the time period when collecting the changes to send, but this means that often changes are being sent twice (which is no problem, but is inefficient).

content = json.dumps( g.changesForClient( client, ts - (now-ts) ) )

Bug #4 (2013-09-16)

Returning binary files is intermittently failing - it always seems to be image files from the jQueryUI theme, some times some fail and other times not. I've tried sending the content as directly as I can from the file into the socket, but it complains about unicode interpretation problems. For example:

error: uncaptured python exception, closing channel <http.handler connected 127.0.0.1:40165 at 0x1537f38> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0x89 in position 0: invalid start byte [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|449] [/var/www/tools/Bitgroup/http.py|handle_read|123] [/usr/lib/python2.7/encodings/utf_8.py|decode|16])

Resolved bugs

Bug #1 (2013-09-05)

Checkboxes and select lists events failing on Firefox 17. When a select list of checklist input changes due to a remote change, the incoming data arrives and the change event fires leading to a change in the "selected" or "checked" attribute (this can be seen with Firebug), but the actual state of the input element sometimes has no visible change.

Solution (2013-09-12): Checkboxes and select list's states should be updated with the selected(bool) and checked(bool) methods on the DOM object, not via updating the element's attributes.

Bug #2 (2013-09-05)

Multiple events are firing on input components, for example a single change comes in and three or four event handlers are responding to it.

Solution (2013-09-10): When the view is re-rendered (by a node change or view change for example), the original input element is removed from the DOM and replaced with a newly rendered one. But because the original element is still referred to by it's event-handler function it does not die and so still receives the change events. The solution is to check if the element is in the DOM by checking that it has valid parent nodes and if not, remove the handler allowing the element to die since nothing then refers to it any longer.