[12:37] <carlos> BradB: is it normal?: Posted by  165  at  2004-11-07 08:48 PM
[12:37] <carlos> BradB: it's from a comment added to the ubuntu website
[12:37] <carlos> seems like it's using the id instead of the real name or nick name
[12:37] <BradB> there's a bug for that
[12:38] <BradB> i had that working; i'm not yet sure what broke it, because i haven't looked
[12:38] <carlos> ok, I was browsing the we and saw it, not sure if it was a know bug
[03:39] <BradB> hm, i guess a malone bug doesn't have an "absolute url".
[03:42] <BradB> it seems to me we need to give locations to our objects in order to, for example, provide URL's to bugs in notification emails.
[03:42] <BradB> as it stands, a bug container doesn't contain bugs
[03:43] <BradB> it just looks like it does, but there's no true container/contained relationship there.
[03:46] <stub> We need an absolute URL - just hasn't been done yet. It will be particularly important if we get to doing bugtracker virtual hosting for projects (gnome.launchpad.org)
[03:46] <BradB> well, sure, that's exactly the problem i'm pondering
[03:47] <BradB> it seems to me that without locations though, bugs can't have absolute URL's
[03:47] <BradB> i.e. without implemented IContained
[03:47] <BradB> and bug containers implementing IContainer
[03:47] <BradB> s/implemented/implementing/
[03:48] <BradB> i need this right now, for notification emails.
[03:48] <stub> The Z3 mechanism is to use an adapter to IAbsoluteURL, which is how I would expect it to be implemented. It doesn't require containment (although I had all that stuff in an earlier implementation of Malone, and it worked quite well that way).
[03:48] <stub> As a quick fix, it would involve writing an adapter from IBug -> IAbsoluteURL that just hardcodes the URL
[03:48] <BradB> yep, that doesn't work though
[03:49] <BradB> because of VH'ing
[03:49] <stub> And this could be replaced with a non hardcoded url later
[03:49] <BradB> how can something that doesn't have a home have an absolute URL?
[03:50] <stub> Because you give it one - you could give an object an absolute url of www.google.com?q=Malone%20Bug%206543 if you want, although that would be rather... ummm.... odd.
[03:53] <stub> We would need to determine 'one true url' for objects though if they can be accessed in different contexts (launchpad.ubuntu.com/bugs/12, gnome.ubuntu.com/bugs/12, launchpad.ubuntu.com/projects/gnome/bugs/12)
[03:53] <stub> Which is a UI decision
[03:54] <BradB> i wonder why we don't just use locations
[03:55] <stub> locations?
[03:55] <BradB> since by not using them, our containers, well, aren't.
[03:55] <BradB> IContainer/IContained
[03:55] <stub> oh.
[03:55] <stub> It is because SteveA has been arguing about the the differences between containment and traversal
[03:56] <stub> I don't see a problem with organising our stuff in a containment heirarchy though.
[03:56] <BradB> me neither, particularly since our naming scheme gives the impression that we have containers and objects contained in them, when we in fact don't.
[03:57] <stub> (Like I said - I had it like that at one stage.  I pulled it to make the code more similar to the Rosetta and Soyuz implementations.
[03:57] <stub> Which is why Malone has containers and other tools have sets ;)
[03:57] <BradB> ah
[03:57] <BradB> that term would make a hell of a lot more sense
[03:58] <stub> Although that implementation had problems, because it was setting __parent__ during traversal, which meant only objects traversed to had it set up properly.
[03:58] <BradB> setting __parent__ during /traversal/? eek.
[03:59] <BradB> i'd expect __parent__ gets set when an object is added to a container
[03:59] <stub> I've since learnt about descriptors which are probably the correct way of doing it.
[03:59] <stub> Bug.__parent__ would need to be a descriptor that calls getUtility(IBugContainer)
[04:00] <stub> Or we can pull out that Utility bullshit since we don't need to switch between PostgreSQL/stub implementations any more
[04:01] <stub> (Hmmm.... probably best leave that in or we have to reengineer the entire traversal mechanism for Malone)
[04:04] <BradB> stub: as long as we've got true containment relationships, absolute URL's seem like a SMOP
[04:04] <stub> SMOP?
[04:04] <BradB> simple matter of programming
[04:05] <BradB> without that, i have no idea how we do an IAbsoluteURL adapter that works with VH'ing.
[04:05] <stub> If we have true containment relationships, the programming already exists (There are already adapters from IContained -> IAbsoluteURL)
[04:05] <BradB> yeah, that makes sense.
[04:07] <stub> I think we can go with a hardcoded IAbsoluteURL adapter for Bug right now (we aren't doing vhosting yet, although we might need to interrogate request or set an environment variable to determine the server url.
[04:08] <BradB> well "hardcoded", but not, because it has to be able to work when developing locally.
[04:08] <BradB> hardcoded at least to the point that it's $SERVER_URL + "/malone/bugs/" + bug.id
[04:08] <stub> Do we have access to request as a global now?
[04:09] <stub> I think we do, but can't remember how to access it...
[04:09] <BradB> not that i'm aware of (which isn't to say there isn't though)...i don't know if there's a utility that can give you the request.
[04:09] <BradB> in stock Z3, there doesn't seem to be such a thing.
[04:10] <BradB> then it's just r.getApplicationURL() + "/malone/bugs/" + str(bug.id) sorta thing
[04:10] <stub> Jim was writing thread specific globals, which has been fed into the threading module in python 2.4 IIRC
[04:10] <BradB> wow
[04:13] <BradB> speaking of which ++apidoc++ really needs to not raise a NotFoundError on favicon.ico
[04:13] <stub> ++apidoc++ needs its cool tree icons too...
[04:13] <stub> oh... I hacked my local Z3 to fix that.
[04:14] <BradB> yeah, i remember you mentioning it somewhere, couldn't remember what it was though.
[04:14] <stub> I thought it was a bug in the favicon implementation, so was hoping Steve would look into it.
[04:14] <stub> There are two page templates mentioning favicon in the apidoc area - remove those bits.
[04:18] <BradB> ah yeah
[04:19] <BradB> bradb@oxygen:~/launchpad/lp/sourcecode/zope/src/zope/app/apidoc/browser$ grep -rn favico *
[04:19] <BradB> details_macros.pt:25:          tal:attributes="href context/++resource++favicon.png" />
[04:19] <BradB> menu_macros.pt:27:          tal:attributes="href context/++resource++favicon.png" />
[04:24] <stub> Ahh sod. SteveA doesn't have an account on lunchfood
[04:24] <stub> Can't assign him bugs ;)
[04:25] <BradB> heheh...he doesn't? eeek.
[04:27] <BradB> he does
[04:28] <stub> ok - I need to go pay for my Barcelona tickets and get some groceries. Any bugs you think I should be looking at when I get back, or do you want me to look at the IAbsoluteURL stuff?
[04:28] <BradB> you could look at formatting bug report text and comment text if you want.
 and s/\n/<br \/>/ are, of course, not viable options, so have fun
[04:29] <stub> Has there been a decision on how that is actually supposed to be done?
[04:29] <stub> oic - make it up, make it sane.
[04:29] <BradB> no idea...
[04:31] <BradB> stub: no, it's simpler than that, but much harder.
[04:32] <BradB> stub: the only thing i mean by "formatting" is to have everything look precisely as it looks now, except that user-entered line breaks should show as line breaks when rendered
[04:39] <stub> Which sounds like newline-to-br, but you said that isn't a viable option?
[04:39] <BradB> insecure
[04:40] <stub> it is if you htmlquote as part of the procedure (?)
[04:41] <BradB> hm?
[04:41] <stub> def newline_to_br(txt): return htmlquote(txt).replace('\n','<br/>'
[04:41] <stub> )
[04:42] <BradB> ah
[04:43] <BradB> yeah, that looks good
[04:43] <stub> ok. I'll knock that up and some sort of TAL syntax to make it not suck
[04:43] <BradB> yeah, that's what i was hoping for (tal syntax)
[04:44] <BradB> is this something that'll be fixed in z3 then?
[04:53] <stub> It might already be there for all I know - "structure context/foo/zope:newline_to_br" or something similar. I'll ask about rolling it back to Z3 if it isn't in there already.
[04:56] <BradB> ok
[11:16] (Kinnison/#launchpad) I guess it's good that I never quite get to the coding stage before the glaring bug stares back at me and makes itself known
[11:26] <SteveA> Kinnison: it's usually possible to write some of the tests before even thinking about the algorithm
[11:27] <Kinnison> SteveA: the issue I have is that the algorithm I end up choosing will, to an extent, dictate the data structures the function needs to be given
[11:27] <Kinnison> SteveA: I can't write "testbinarydomination" until I know what _dominateBinaries() will need to be passed to do its job
[11:28] <Kinnison> I think I've gone full-circle back to the simpler algorithm so I'm almost ready :-)
[11:28] <Kinnison> well, Domination is in the glossary :-)
[11:28] <Kinnison> SteveA: how was your holiday?
[11:35] <SteveA> Kinnison: it was very good.  went to sicily and lounged around and ate well and walked up hills
[11:36] <Kinnison> sounds good
[12:03] <Kinnison> Morning cprov, salgado 
[12:04] <salgado> morning Kinnison
[12:06] <Kinnison> soyuz people: Given a binarypackage.id how do you decide what architecture it is for?
[12:06] <Kinnison> Esp. how do you decide if it is arch-specific or arch-independant?
[12:11] <Kinnison> Anyone?
[12:12] <salgado> Kinnison: BynaryPackage.build.processor ?
[12:12] <Kinnison> well, binarypackage.build.processor.processorfamily gets me most of the way there
[12:12] <Kinnison> but it doesn't tell me which of the binarypackage rows are arch-independant
[12:13] <Kinnison> Unless we create an arch-independant processor or something; but that won't sit right with the rest of the publishing stuff
[12:17] <debonzi> Kinnison, another way is packagepublishing.distroarchrelease.processorfamily
[12:17] <Kinnison> again; doesn't help on the whole arch-specific vs. arch-independant thing
[12:17] <Kinnison> elmo: ping?
[12:20] <debonzi> Kinnison, uhmmmm .. I think I dont know the arch-independant concept .. what you mean with it?
[12:20] <Kinnison> binary packages are either specific to a given architecture or are shared among all of them
[12:20] <Kinnison> E.g. vim is arch-specific, but vim-common is arch-independant
[12:21] <Kinnison> I.E. vim-common is arch: all
[12:21] <debonzi> Kinnison, right.. I see 
[12:24] <debonzi> Kinnison, is it too stupid to have and processorfamily.name='all'? does it hurt any concept?
[12:25] <Kinnison> erm; where did that extra ping come from I wonder
[12:25] <Kinnison> flarp
[12:26] <Kinnison> please wait while I try to restore normality
[12:26] <debonzi> Kinnison, :)
[12:26] <Kinnison> there; better
[12:26] <lifeless> Kinnison: did you see anything in the CVS protocol that would let me probe for the remote servers time ?
[12:26] <Kinnison> debonzi: right; where do we link that in?
[12:28] <Kinnison> It's going to cause all sorts of amusing issues with referential integrity IMO
[12:30] <debonzi> Kinnison, you mean witch page?
[12:30] <Kinnison> page? I'm thinking of the database itself
[12:31] <debonzi> Kinnison, oohhh.. sorry.. I missunderstood
[12:31] <Kinnison> Because currently there's no way to actually determine the architecture of a package referenced in a publishing record
[12:31] <Kinnison> The most I can say is "it is most likely to be <foo arch>"
[12:33] <Kinnison> s/our$/out/
[12:34] <carlos> morning
[12:34] <debonzi> carlos, morning
[12:34] <Kinnison> Morning carlos
[12:59] <lifeless> Kinnison: ping
[12:59] <Kinnison> lifeless: pong
[12:59] <lifeless> lifeless> Kinnison: did you see anything in the CVS protocol that would let me probe for the remote servers time ?
[01:01] <Kinnison> Nope
[01:02] <lifeless> :[
[01:10] <Kinnison> lifeless: Any particular reason to want it?
[01:10] <lifeless> yeah, to filter commits that are in progress
[01:11] <Kinnison> oh blergh; yeah
[02:08] <carlos> hmm, any explanation about this: /home/carlos/Work/dists/launchpad/lib/canonical/lp/sql.py:51: FutureWarning: Need to set add_missing_from=false in /etc/postgresql/postgresql.conf
[02:09] <salgado-afk> carlos: I think this is to help finding out bad queries
[02:09] <carlos> ok
[02:10] <salgado-afk> this way, postgres will not add missing from clauses in queries, and then the query will break. 
[02:24] <carlos> lunch time
[04:25] <Kinnison> FAILED (failures=12, errors=4)
[04:25] <Kinnison> anyone else getting lots of 'make check' errors?
[04:25] <Kinnison> 80-add-comment.txt
[04:26] <BradB> the code checked in on chinstrap passes all the tests when run on chinstrap
[04:26] <Kinnison> bumflakes.
[04:27] <Kinnison> I've done a blank database schema make too
[04:27] <BradB> what does the exception look like?
[04:27] <BradB> (for one of the failing func tests)
[04:27] <Kinnison> Failed example:
[04:27] <Kinnison>     print http(r"""
[04:27] <Kinnison>     GET /malone/bugs/2/ HTTP/1.1
[04:27] <Kinnison>     Referer: http://localhost:9000/malone/bugs/2
[04:27] <Kinnison>     """)
[04:27] <BradB> paste.husk.org for the full tb
[04:29] <Kinnison> http://paste.husk.org/1956
[04:34] <BradB> Kinnison: you're running the tests with "make check" presumably?
[04:34] <Kinnison> yep
[04:34] <Kinnison> on a fresh db
[04:35] <BradB> what had you just changed?
[04:36] <Kinnison> I just star-merged :-)
[04:37] <BradB> Kinnison: have you cd database/schema; make'd lately?
[04:37] <Kinnison> Like I said.. a fresh db
[04:38] <Kinnison> launchpad is not missing anything from me
[04:42] <BradB> Kinnison: are there any other func tests failing?
[04:43] <Kinnison> BradB: yes
[04:44] <BradB> wee hee, tee!
[04:45] <BradB> my hunch is that there's something b0rked about your configuration, not yet sure what though.
[04:46] <Kinnison> quite possible
[04:46] <BradB> dude, try this
[04:46] <BradB> hm, well, it's a bit of a longshot, but...
[04:47] <BradB> drop your DB's first
[04:47] <Kinnison> the schema make does
[04:47] <BradB> yeah, actually PgTest does it in between stories too, urph
[04:49] <Kinnison> right
[04:49] <Kinnison> https://chinstrap.warthogs.hbd.com/~dsilvers/launchpad-make-check.txt
[04:49] <Kinnison> If you can spot the obvious problem which has eluded me; you win a prize
[04:51] <BradB> i don't know what the u/p is to access that page
[04:51] <BradB> just mail it to me: bradb@bbnet.ca
[04:54] <Kinnison> which I think is @canonical.com
[04:56] <BradB> Kinnison: have you got a connection open to launchpad_ftest atm? it's worth verifying.
[04:56] <Kinnison> nup
[04:56] <BradB> your db isn't getting reset properly.
[04:57] <Kinnison> fresh bootup
[04:58] <BradB> there's a connection open to launchpad_ftest when there shouldn't be. due to that, it fails to reset the db.
[04:58] <BradB> put an import pdb; pdb.set_trace() in lib/canonical/ftests/pgsql.py, line 72.
[04:58] <BradB> and then "n" over:
[04:58] <BradB>             name = zapi.getUtility(IConnectionName).name
[04:58] <BradB>             db_adapter = zapi.getUtility(IZopeDatabaseAdapter, name)
[04:58] <BradB>             if db_adapter.isConnected():
[04:58] <BradB>                 # we have to disconnect long enough to drop
[04:58] <BradB>                 # and recreate the DB
[04:59] <BradB>                 db_adapter.disconnect()
[04:59] <BradB> (which is code i added to disconnect from the db, so that statements further down can drop it)
[04:59] <BradB> and make sure it doesn't raise a ComponentLookup error the second time through onwards (the first time through it does, because the config hasn't been loaded for that func test)
[05:08] <Kinnison> Okay; let me finish this food and I'll do that
[05:14] <Kinnison> running...
[05:16] <BradB> and, if it doesn't raise a CLE, then you could step down to the place where it drops the DB and then look at what other connections are open to launchpad_ftests
[05:16] <BradB> s/ftests/ftest/
[05:16] <Kinnison> still waiting...
[05:21] <Kinnison> it didn't stop
[05:26] <BradB> eh, something sounds very b0rked about your config
[05:26] <BradB> it might be that you have another version of the code installed somewhere else, i dunno.
[05:40] <carlos> SteveA: hey, welcomed back
[05:57] <SteveA> hi carlos
[06:14] <cprov> Hi everybody, I apologize for not be present today ...
[06:15] <cprov> Kinnison: any new about publishing system ? do you need help ? I need :), how to get librarian interface for sourcefiles portlet in sourcepackage page ?
[06:17] <Kinnison> The launchpad instance should probably have a global instance of canonical.librarian.client.FileDownloadClient which has been initialised according to some global config somewhere (I don't understand zope so you'll have to get someone who does to do that bit)
[06:17] <Kinnison> Then you can simply call fooobject.getFileByAlias(the_file_alias)
[06:17] <Kinnison> where fooobject is that FileDownloadClient instance
[06:18] <Kinnison> the alias is the value of the column libraryfile in sourcepackagereleasefile
[06:18] <cprov> Kinnison: great !! there is something already published to play ? Any idead about how will be the behavior to download an .orig or .deb using Zope ? 
[06:19] <Kinnison> anything gina has imported has those files in the librarian ready
[06:19] <Kinnison> no idea how you would stream it through zope
[06:19] <Kinnison> I have a patch (uncomitted) which would allow you to get the URL out; but I haven't finished and tested it yet
[06:19] <Kinnison> I could bubble that to the top of my todo if you'd like
[06:20] <cprov> Kinnison: yes, or if you'd like help for test it, just send it to me 
[06:21] <Kinnison> It has some utf-8 changes in it too; so I'll have to test it well first
[06:24] <cprov> Kinnison: ok, as you want, just let me know if you need help
[06:29] <cprov> BradB: what do you mean ? bar = 2; foo = `bar`, then foo is '2' ...is it tricky ?
[06:32] <BradB> it's surprising
[06:33] <BradB> `` is normally for stringifying the output of a shell command, where i come from. odd that python ok's things like ``, but not (foo ? bar : baz)
[06:34] <BradB> SteveA: ping
[06:34] <SteveA> hi brad
[06:34] <cprov> BradB: aha, it surprises me too 
[06:35] <BradB> SteveA: hey! how was your vacation?
[06:35] <SteveA> thanks, it was great
[06:35] <SteveA> I'm very refreshed
[06:35] <BradB> good to hear
[06:35] <BradB> SteveA: we've got a problem with placelessness now.
[06:36] <BradB> SteveA: i want to be able to provide a URL to a bug, e.g. in a notification email
[06:36] <BradB> as well, i'm sure there are lots of places we either do, or will want to provide an absolute URL for a given object (a bug, a source package release, a whatever)
[06:37] <BradB> in a placeful world, this is simple (and, AFAIK, well-supported in Z3, with an adapter from IContained to IAbsoluteURL)
[06:37] <SteveA> well, kind of
[06:37] <BradB> how do I provide an absolute URL for things that don't live anywhere though?
[06:37] <SteveA> it is actually a little more trickly than that
[06:38] <BradB> SteveA: point being though, if i implemented IContained, getting my absolute url in Z3 Just Works, right?
[06:39] <Kinnison> BradB: would it amuse you to know that having had a snack; the ftests run okay now?
[06:39] <BradB> Kinnison: computers suck
[06:39] <Kinnison> BradB: I blame a gremlin
[06:39] <SteveA> it's trickier than that
[06:40] <SteveA> consider the situation where you want an XMLRPC request on an internal ip address and port to signal the sending of email
[06:40] <SteveA> but, the email will need to have the official URL used
[06:41] <SteveA> one element is the domain and protocol and port to use.  another element is the path of the url to use
[06:41] <BradB> SteveA: that's trivial to work around though
[06:41] <BradB> e.g. with /etc/hosts
[06:41] <SteveA> the path can be handled with a correct absolute url implementation  
[06:41] <SteveA> not with /etc/hosts, I think
[06:41] <SteveA> I don't think we need IContained
[06:41] <BradB> or just using the real url?
[06:42] <BradB> it seems to me we do. i have zero understanding of how to provide an absolute url that works with VH'ing for objects that have no location.
[06:43] <BradB> SteveA: what's your proposal for providing an absolute url to a placeless object?
[06:44] <BradB> the only way i can see is to make some assumptions about the $SERVER_URL, which will not obey the principal of least surprise, i think.
[06:44] <SteveA> right now, I have some ideas, and some principles.  I need to consider this properly, though.  Right now, I'm up to mid-thursday's email ;-)
[06:44] <SteveA> Shall we chat about this tomorrow morning (your time) ?
[06:45] <BradB> sure. i'll be around by 14:00 GMT
[06:45] <SteveA> ok, great
[06:45] <BradB> SteveA: another issue of pressing concern is answering the question "when do we consider a bug 'resolved'?"
[06:46] <BradB> maybe you, mark, stub and I need to chat about that one
[06:46] <SteveA> in malone, or in our own processes?
[06:46] <SteveA> I guess you mean in malone
[06:47] <BradB> in malone. we've got a couple dozen bugs reported, several of which are fixed, but we have no way of signalling that currently
[06:47] <BradB> (or, at the least, if it's doable, it's entirely unclear how to mark a bug "resolved")
[06:47] <SteveA> there's a resolved in the DBSchema status isn't there?
[06:48] <BradB> i don't see it in the UI, so i guess not
[06:48] <BradB> there is a "Fixed" on infestations, and a "Closed" on assignments, but that's a few levels of indirection, i.e. confusing.
[06:48] <BradB> i don't want to have to mark something infested to be able to say i fixed that bug.
[06:49] <SteveA> so, something with no infestation should be considered "Fixed" by default ?
[06:50] <BradB> no. the only assumption about a bug with no reported infestation is that noone reported an infestation.
[06:50] <BradB> you've got:
[06:50] <BradB> 1. a bug report, which describes something that isn't working as expected.
[06:50] <BradB> 2. an assignment to zero one or more packages or products, which is simply a way of getting that bug in the face of the person who should see it (e.g. the maintainer of the source package.)
[06:51] <BradB> 3. infestations, which say precisely which versions are affected by this bug, and exactly how they're affected.
[06:51] <BradB> in many real world scenarios, the bug will be so quick to fix that going to the effort of #3 won't be worth it.
[06:53] <BradB> but then, let's say you're doing a listing of bugs that are outstanding. how do you know which bugs haven't been fixed? what if all the "assignments" are "closed", but there's somehow still an infestation or two that are marked as "affected" (instead of "fixed")?
[06:56] <SteveA> and, what about bogus bugs?
[06:56] <SteveA> it should be easy to say "not a bug"
[06:59] <BradB> you can mark infestations as "won't fix"
[06:59] <BradB> but again, that requires two levels of indirection, if you will (e.g. assigning to a package, and then specifying an infested version of that package too)
[07:01] <BradB> the workflow really needs some thinking through (i've reported a bug for it in malone)
[07:01] <SteveA> ok
[07:02] <SteveA> it's a recurring problem in launchpad -- we're modeling complex things, but we have pretty simple overall actions sometimes
[07:02] <BradB> is there a meeting on wednesday? maybe we can discuss it then.
[07:04] <SteveA> Did stu arrange a time for the next meeting at the end of wednesday's one?
[07:04] <sabdfl> hi all
[07:05] <SteveA> hiya
[07:05] <sabdfl> hey SteveA, have a good break?
[07:05] <kiko> hello mark
[07:05] <BradB> SteveA: no
[07:05] <BradB> hi sabdfl 
[07:05] <sabdfl> kiki!
[07:05] <kiko> !
[07:05] <sabdfl> am just catching up now
[07:05] <sabdfl> refueling
[07:05] <sabdfl> any immediate news?
[07:05] <SteveA> BradB: I think this is something best disussed among you malone folks, perhaps with some input from james or kinnison
[07:05] <SteveA> sabdfl: great break.  very refreshed.  still catching up on email / code.
[07:06] <BradB> sabdfl: two pressing issues in malone: 1. how to get a URL to a bug (seems like a bit of a doozy with placeless objects), and perhaps slightly more urgent 2. answering the question "is this bug resolved?"
[07:12] <sabdfl> bradb: regarding number 2: "it depends on your perspective", it depends on the assignment to your context
[07:12] <sabdfl> for example, if you are upstream, then check the product assignment
[07:13] <BradB> what if an assignment is "closed", but the infestation says "affected"? what if there's an infested release of a product for which there's been no assignment of the bug to that product?
[07:16] <BradB> more specifically, several of the bugs at https://launchpad.ubuntu.com/malone/bugs shouldn't be showing, because they're already fixed. i don't know how to decide which ones to show and not show though.
[07:19] <SteveA> brad and I are going to talk in detail about 1 tomorrow
[07:20] <sabdfl> BradB: yes, that page is just listing every bug in the system
[07:20] <sabdfl> i guess a "show me the bugs view" is useless without a context
[07:20] <sabdfl> need to show the bugs for a product or source package
[07:20] <sabdfl> or possible a project or distro, which are aggregates of products and packages respectively
[07:23] <BradB> yes, i think the mdz's of the world will want a god view
[07:24] <BradB> there's a third pressing issue to note too, which is the need for a combo box (it's exceedingly difficult to choose values for certain fields currently)
[07:32] <BradB> sabdfl: (sticking with #2 for the moment) by "context" do you mean we turn the bug listing into a search form (e.g. to specify packages assigned to, products assigned to, etc.) with default search params set based on the current user where possible?
[07:32] <sabdfl> yes
[07:32] <sabdfl> see the bugs assigned page i've done
[07:32] <sabdfl> it's basically a search form
[07:35] <BradB> yeah, ok. the implementation of this gets slightly hairy (because e.g. we need all the package and product assignment and infestation search fields to i. allow us to easily choose from a huge # of options and 2. be multi-select), but i don't see any other way
[07:36] <BradB> IOW, the search criteria widgets will take up a lot of real estate
[07:46] <carlos> Do we have already an example about how to create a temporal database to do some funtional tests?
[07:46] <carlos> I mean, how to integrate it into the make fullcheck command
[07:46] <carlos> the rosetta functional tests are broken at this moment because all database changes we did
[07:47] <BradB> inherit from LaunchpadTestCase
[07:47] <carlos> BradB: is it documented in any place?
[07:49] <BradB> carlos: only in the docstring of the class (which is pretty pithy)
[07:50] <BradB> sorry, there's LaunchpadFunctionalTestCase too (which inherits from LaunchpadTestCase)
[07:50] <BradB> other than that, i'd just read the other functional test cases
[07:50] <carlos> ok, thanks
[07:56] <carlos> hmm
[07:56] <carlos> I'm trying to file my first bug report with malone
[07:56] <carlos> for Rosetta
[07:57] <BradB> file it against the source package rosetta
[07:57] <carlos> Which ones should be the "Source Package" and Product?
[07:57] <carlos> yeah, that was my question :-)
[07:57] <BradB> psychic i am :P
[07:57] <carlos> BradB: should I select a product?
[07:57] <BradB> nope
[07:57] <carlos> I suppose you already know that... but it's not too user friendly...
[07:58] <carlos> also, the lists should be sorted by name
[08:00] <carlos> how could I assign the bug or set its severity, priority or just change its status?
[08:00] <BradB> carlos: yep, malone isn't launchpad friendly, because it's not built for systems like launchpad, but rather for linux distributions with source packages and products.
[08:00] <BradB> carlos: and there's a bug already filed for sort order (but we need a combo box too, of course)
[08:01] <BradB> carlos: by editing the package assignment
[08:02] <carlos> ooh, we need a way to show the user that it's clicking over that field
[08:02] <carlos> I did not saw that's the way to edit it...
[08:02] <BradB> ?
[08:02] <BradB> what do you mean "that it's clicking over that field"?
[08:02] <BradB> oh, click to edit
[08:02] <carlos> yes
[08:03] <carlos> it did not thought about it
[08:03] <carlos> i did not thought about it
[08:03] <carlos> hmm, last comment about malone :-P
[08:03] <carlos> the bug report comes from your mail domain instead of canonical or ubuntu, is that normal?
[08:04] <carlos> From: 	noreply@bbnet.ca
[08:04] <carlos> Reply-To: 	noreply@bbnet.ca
[08:04] <carlos> To: 	carlos.perello@canonical.com
[08:04] <carlos> Subject: 	'Fix Rosetta functional tests' added
[08:04] <carlos> Date: 	Mon, 08 Nov 2004 18:58:40 -0000  (19:58 CET)
[08:04] <BradB> that's fixed, but not deployed
[08:04] <carlos> ok
[08:05] <BradB> if you think there are things that are weird about malone, by all means take a look and see if someone's already reported it and if not, feel free to report it.
[08:05] <carlos> ok
[08:06] <carlos> Will do, don't worry
[08:06] <BradB> cool, thanks :)
[08:06] <carlos> We use hardly the BTS from Rosetta
[10:43] <daf> BradB: any chance of getting Malone notification emails to include bug numbers any time soon?
[10:45] <BradB> daf: the idea is to put the URL in there, which isn't trivial. i'll be discussing that with SteveA tomorrow morning
[10:45] <BradB> elmo: ping
[10:45] <daf> I think having the bug number would be good enough for now
[10:46] <daf> to get Dilys working with Malone, at least
[10:47] <BradB> ah yeah, i could indeed throw it in the subject line
[10:47] <BradB> to also be consistent with bugzilla
[10:47] <daf> that would be groovy
[10:55] <carlos> daf: dilys is not doing her work today, I closed two bugs and did some commits and I don't remember see them in the channel
[10:57] <daf> hmm
[10:58] <dilys> test
[11:04] <dilys> test
[11:06] <dilys> Bug 2147 resolved: We are not setting the iscomplete flag when a translation has all needed strings
[11:06] <dilys> https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=2147
[11:06] <daf> ah, found it
[11:07] <daf> I recently made dilys use a config file, and the Bugzilla address in the config file was wrong
[11:20] <carlos> daf: :-P
[11:31] <SteveA> daf: what is the earliest reasonable time you can attend a launchpad meeting?
[11:32] <daf> well, I thought 8am was possible, but it seems I was wrong
[11:32] <dilys> foo
[11:32] <dilys> say foo
[11:32] <dilys> me foo
[11:32] <daf> hmm
[11:35] <daf> SteveA: I'm willing to try for 8am one more time
[11:36] <Kinnison> SteveA: are you thinking tomorrow or wednesday?
[11:45] <carlos> daf: what time is 8am in UTC ?
[11:46] <daf> carlos: 12:00
[11:46] <carlos> ok
[11:50] <SteveA> Kinnison: wednesday
[11:50] <Kinnison> SteveA: *nod* just thought I'd check and remind myself :-)
[11:51] <SteveA> let's say 12:30 UTC then.  sound okay?
[11:51] <daf> fine for me
[11:51] <carlos> yeah
[11:52] <Kinnison> yip; sounds good
[11:53] <SteveA> ok
[11:53] <SteveA> BradB: 
[11:53] <BradB> sure
[11:54] <SteveA> great