Team Chat Logs

March 2, 2010

2010 2
Mo Tu We Th Fr Sa Su
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31        
<< <   > >>

[02:05:14.666242]<osimons>Hodgestar: thanks for picking up the lint stuff... though your patch is not quite obvious to me - unless elements are magically added to saved items for any report?
[02:05:51.574810]<osimons>if so, msg="the warning" should also work, right?
[02:07:00.325332]<Hodgestar>The patch changes the pylint upload recipe command to add a <msg>the warning</msg> child element.
[02:07:30.331493]<Hodgestar>The recipe receiver already takes these children and records them in the report item.
[02:07:36.971160]<Hodgestar>Does that make things clearer?
[02:08:09.066838]<Hodgestar>Obviously there isn't an easy way to add such messages to old reports that didn't upload them.
[02:08:21.981316]<Hodgestar>For old reports I just use '-' as the message.
[02:50:19.229939]<osimons>right. but, msg="the warning" as attribute would also work?
[02:52:49.630430]<osimons>Hodgestar: what we should do is move the ReportFormats into the rst docs as a reports.txt or something - that way we can migrate to new features more easily, and keeps things together
[02:53:47.478069]<osimons>how about: in commands.html under <report> we say "see reports.html for known types of reports", and then reports.html contains the report format docs much like they look today in the wiki?
[02:55:33.233718]<Hodgestar>osimons: Yes, msg="the warning" would also work. Do you prefer that?
[02:58:28.458153]<Hodgestar>What / where is ReportFormats currently?
[02:59:09.479734]<osimons>Hodgestar: just looks cleaner in the docs, i think. but, no big deal. http://bitten.edgewall.org/wiki/ReportFormats
[02:59:35.171671]<osimons>a very typical reference page...
[02:59:45.345134]<Hodgestar>Oh, I see.
[02:59:54.764667]<Hodgestar>Yes, I think that should be included in the rst docs in svn.
[03:02:25.050470]<osimons>page was started before my time, but i've added all things i've discovered with report formats there. including the supported lint format that don't work as advertised...
[03:03:38.104668]<Hodgestar>The report collector on the master is actually extremely generic -- you can upload practically anything and it will try and make sense of it.
[03:04:20.883554]<Hodgestar>None of the documented reports appear to use the <child>some value</child> functionality I discovered by reading the code.
[03:04:23.282432]<osimons>yeah, see that. so formats is really just the formats that bitten has rendering/graphing support for - "known report formats"
[03:04:34.745150]<Hodgestar>Yep.
[03:05:26.730157]<osimons>Hodgestar: still, the alternative format is useful for those using xls tranform or something - may sometimes be easier to use elements rather than attributes. optional, either-or anyay.
[03:05:53.827752]<Hodgestar>I guess we should just update the documentation to say that either can be used?
[03:06:32.676057]<osimons>the test reports example shows it, but the docs does not mention it explicitly
[03:06:42.307806]<osimons>docs can still be improved
[03:06:44.110786]<osimons>:-)
[03:06:45.619655]<Hodgestar>Ah, yes.
[03:06:59.946508]<Hodgestar>Docs are such a pain. :-)
[03:07:51.085934]<osimons>exactly
[03:27:15.433723]<osimons>Hodgestar: it would be really cool to get a lint annotator working in the source browser...
[03:30:00.233238]<Hodgestar>I'll save that for round 2. :)
[03:35:25.929554]<Hodgestar>Feel free to make a ticket and assign it to me though.
[03:35:47.053656]<Hodgestar>I'm done Bittening for the day though -- have to get some other coding done this afternoon.