| Summary: | Add "null event" handling | ||
|---|---|---|---|
| Product: | Zeitgeist | Reporter: | Siegfried-Angel Gevatter Pujals <siggi.gevatter> |
| Component: | libzeitgeist | Assignee: | zeitgeist-bugs <zeitgeist-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | zeitgeist-bugs <zeitgeist-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 0.9.x | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | fix | ||
|
Description
Siegfried-Angel Gevatter Pujals
2012-07-31 17:02:31 UTC
Created attachment 66848 [details] [review] fix Let's rather have zeitgeist_log_get_events return GenericArray, ResultSet didn't really make sense here. (GenericArray is consistent with Python, where we returna list vs. a dictionary). I'm keeping the iterator changes in. If we don't want those after all, it's important to note that the previous implementation had a bug (cursor being compared to events.length before increasing it). I really would like to remove ResultSet in general and also stick to a GenericArray... This would make introspection cleaner too This was fixed with 1543988402a80c1b70652dd73bdb60b756c6bf08 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.