[00:58] Anyone, I have trouble synchronizing Tomboy notes; one second computer connected to ubuntu one, I am not able to see the notes synchronized from first computer. [01:13] Anyone listening that may help with Tomboy synch with ubuntu one? [01:16] Staff, is there anyone listening that may help with Tomboy synch with ubuntu one? Or is this the appropriate place? [01:29] Anyone? [01:41] Anyone? [02:12] Staff, is there anyone listening that may help with Tomboy synch with ubuntu one? Or is this the appropriate place? [08:48] morning all [11:35] aquarius: we forgot to have a beer together at UDS and talk about 'interesting uses for ubuntu one' :) [11:40] Hi ! [11:41] hello mahen [11:41] duane [11:43] duanedesign, we did. Bah! [11:45] duanedesign: do you know if I should open a bugreport for the timeout problem ? (indeed : my client keeps uploading data infinitely but never finishes a 350MB file apparently because of some timeout -- I upload at about 100KB/sec) [11:46] mahen: i am glad you mentioned that [11:47] mahen: i meant to look and see if a report exists for that [11:47] ah :) [11:47] let me poke around and see what i can find [11:47] ok, thanks ! [14:02] what about: [14:02] me [14:03] me [14:04] dobey mandel_ nessita thisfred ? [14:04] me! [14:04] vds: thanks [14:04] me [14:04] np === mandel_ is now known as mandel [14:06] thisfred? [14:07] shall we? [14:07] vds: go! [14:07] DONE: branch to port to a newer python-couchdb version proposed #675551 still waiting for one review, started a branch of python-couchdb to port the oauth session from DC to python-couchdb, code review [14:07] TODO: [14:07] BLOCKED: not at all [14:07] CardinalFang: go [14:07] me [14:07] DONE: reviews. Reconcile my proxy branch and get-port branch; might be tricky. [14:07] TODO: review and merge remaining branches. [14:07] BLOCKED: None [14:07] DONE: branch for bug #627496 and bug #677518, more folders tab for control panel bug #674455, talked with Asif about UI usability issues, weekly call [14:07] TODO: wrap up branches for aforementioned bugs and fix ussoc nightlies [14:07] BLOCKED: nopes [14:07] NEXT: mandel [14:07] NOTES: today is holiday in Argentina, tomorrow I'm taking the day off (swapp from today) [14:08] Launchpad bug 627496 in ubuntu-sso-client (Ubuntu) (and 1 other project) "Registration screen looks cramped when big fonts selected (affects: 2) (dups: 1) (heat: 14)" [Undecided,New] https://launchpad.net/bugs/627496 [14:08] Launchpad bug 677518 in ubuntu-sso-client (Ubuntu) (and 1 other project) "Split gui code to allow other implentations (affects: 1) (heat: 6)" [High,Triaged] https://launchpad.net/bugs/677518 [14:08] Launchpad bug 674455 in ubuntuone-control-panel "Add "Folders" tab to UI (affects: 1) (heat: 6)" [High,In progress] https://launchpad.net/bugs/674455 [14:08] DONE: branch reviews for desktopcouch. Finished changes for #680039, #675522 and #675530 [14:08] TODO: new msi to share for testing. Finish command manager to fix #675842. Propose merge fo my desktopcouch work. Provide images of Ubuntu One iwndows for cparrino. [14:08] BLOCKED: no [14:08] * mandel looks at thisfred [14:09] DONE: bug 510159 bug 678313 TODO finish 510159 and start packaging BLOCKED no [14:09] Launchpad bug 510159 in desktopcouch (Ubuntu) (and 1 other project) "Split desktopcouch in two: a records library that can be used on the server and a desktop application/library (affects: 1) (heat: 6)" [Medium,In progress] https://launchpad.net/bugs/510159 [14:09] Launchpad bug 678313 in desktopcouch "Use Abstract Base Classes in RecordDict and MergeableList (affects: 1) (heat: 6)" [Medium,In progress] https://launchpad.net/bugs/678313 [14:09] any comments? [14:09] dobey: stand up? [14:10] wait, we have to use bug rather than # for the bug numbes? [14:10] lame [14:10] mandel: we said that last week! :-) [14:11] mandel: is the difference between hal and ubot4 [14:11] nessita, really? was not reading :P [14:11] mandel: I can tell :-P [14:11] ok, eom it is? [14:11] oh! ubot4 I hate u! [14:12] eom! [14:14] λ DONE: discovery and some work on 677162, 677211, 677480; initial branch for 677632; [14:14] λ TODO: releases, nightlies, banshee tests [14:14] λ BLCK: None. [14:14] nessita, do you know if lucio and guillermo are on holidays, marianna needs them [14:15] mandel: yes they are [14:15] mandel: if urgent, I can contact them [14:15] nessita, I think, so, let me see [14:16] nessita, can you tell them to contact marianna asap, they need to book the hotel asap for the sprint [14:17] nessita, which is next week! [14:18] mandel: I'll talk to marianna [14:18] nessita, ok [14:18] nessita, I started to fill like a 'corre ve y dile' :P [14:28] mandel: already handled [14:29] nessita, thx! [15:29] duanedesign: did you find a bugreport concerning the issue btw ? [16:07] joshuahoover: do you know if their is a bug report about the timeouts when uploading large files over dial up connections? [16:09] duanedesign: not that i'm aware of, though it's likely there's something there for timeouts when uploading large files [16:36] duanedesign: okay then, I'll file a report about those :) [16:38] mahen: ok :) [16:39] mahen: can you post the bug numbers here when you do. Thank you! [16:55] duanedesign: here it is : https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/680128 [16:55] mahen: Error: Bug #680128 is private. [18:06] hi all [18:06] you have a typo [18:06] "This share is no longer available [18:06] This share has already been accepted by someone else. [18:06] If this is now what you where expecting, try contacting the person who gave you the link. [18:06] " [18:06] last sentence, 4th word [18:13] rajul: thanks! can you please file a bug? [18:13] https://bugs.launchpad.net/ubuntuone-client/+filebug [18:14] rajul: please detail where you're seeing this typo [18:17] nessita: https://bugs.launchpad.net/ubuntuone-client/+bug/680159 [18:18] Launchpad bug 680159 in ubuntuone-client "Typo in a string after clicking an expired shared-folder-link (affects: 1) (heat: 6)" [Undecided,New] [18:19] rajul: where are you seeing this? nautilus? web site? [18:20] thisfred: would you be up for a review? not trivial but fun (?) [18:20] rajul: ah, web site. Thanks! [18:20] yes :-) [18:20] bye! [18:21] nessita: in a minute [18:21] thisfred: awesome! [18:21] nessita: paste me the link! [18:22] thisfred: the high count of diff'ed lines comes from moving files from a directory to another https://code.launchpad.net/~nataliabidart/ubuntu-sso-client/split-gui/+merge/41369 [18:24] nessita: I'm on it. I may ask you for one in return. Also not small, but for the greater good: the branch that will start enforcing u1lint in desktopcouch. (and thus fixes a bazillion lint issues.) [18:24] thisfred: sure, shoot! [18:24] thisfred: for my merge proposal, detailed instructions on testing were added as description [18:24] awesome === didrocks1 is now known as didrocks [18:27] hi all [18:27] hi rickspencer3, how are you? [18:27] I've been keeping all of my notes in a desktopcouch app [18:28] I want to reinstall, how can I make sure all my notes are safely on the server? [18:28] vds, CardinalFang, thisfred: can you take this one? ^ [18:30] rickspencer3: that's a tricky one. Are those tomboy notes, or a different db altogether? [18:30] thisfred, different [18:30] it's my own app [18:30] "daily-journal" [18:30] rickspencer3: ah ok. (should still be using the same db, but that's a different discussion for a different day ;) [18:31] anyhoo [18:31] thisfred, no [18:31] I thought tomboy went through this screwy snowy API [18:31] a successful replication will signify they're there, but those are hard to come by [18:32] rickspencer3, you can verify by looking at the replication log. ~/.cache/desktop-couch/log/desktop-couch-replication.log [18:32] rickspencer3, A line starting asking 'http://localhost:42715/' to replicate todo to {'url': 'https://couchdb.one. ... [18:32] rickspencer3: it does, but it does end up in the notes database, and as long as your app respects the notes record type, and puts everything else in application_annotations['daily-journal'] your notes would work in both apps [18:32] but again, that's for later [18:32] thisfred, does the ubuntuone preferences dialog cover desktopcouch, or such file sync? [18:32] rickspencer3, with the appropriate db for "todo". [18:33] rickspencer3, and following that is the result line. replicate result: {'status': '200', ... [18:33] preferences does not list arbitrary databases to toggle sync of [18:33] but when it says "sync in progress" does that count for desktopcouch? [18:33] only some known ones, like bookmarks, contacts, and gwibber [18:33] no [18:33] dudes [18:33] the status is just for files [18:34] desktopcouch is not synced on-demand [18:34] rickspencer3: we will be working on getting succesful replication notices into zeitgeist this cycle, which will then tell you when the last one for a particular db was. But that's not started yet [18:34] rickspencer3: no it does not AFAIK [18:34] thisfred: but still, they will not be on demand, right? [18:34] dobey: nope, although we could add that [18:35] Pushed on demand, but we don't know when the demand is for pulling. [18:35] rickspencer3: so the replication logs are your best bet for now [18:35] rickspencer3: to be super sure, I'd back up the .couch file before reinstalling [18:35] thisfred: is zg tracking any desktopcouch db? I don't think so... === larsemil_ is now known as larsemil [18:35] CardinalFang: i guess we'd have to add something to the storage protocol for that, and have syncdaemon tell desktopcouch to sync [18:35] thisfred: I mean "will" [18:35] dobey, Yes. [18:36] so if there's no status:200 since 3 days ago, I am not up to date? [18:36] if I backup .couch and then just copy it over when I reinstall, will that work? [18:36] rickspencer3, Yes. And yes. [18:37] CardinalFang, where is .couch? [18:37] rickspencer3, to make sure we're talking about the same thing: ~/.local/share/desktop-couch/ [18:37] ok [18:37] nessita: I think that's on the roadmap, right? [18:38] I see .local/share/desktop-couch is not small [18:38] * rickspencer3 drums fingers [18:38] thisfred: we will track zg events for ubuntu one related, you aresaying that independent dbs will be tracked too? [18:39] thisfred: I'm not sure, that's why I'm asking you [18:40] nessita: eh, every db in couchdb is ubuntu one related, unless you disable replication, right? [18:40] in desktopcouch couchdb that is [18:40] This is part of what we'll be figuring out I guess [18:41] we don't want to flood the user, but it' [18:41] d definitely be interesting to know about successful replications, esp. as long as they are not the norm :( [18:41] thisfred: hum [18:42] thisfred: I think I need to talk to alecu about this to have a clearer picture [18:43] nessita: my branch (now starting on reviewing yours) https://code.launchpad.net/~thisfred/desktopcouch/my-use-devtools/+merge/41497 [18:43] nessita: I have only the vagues understanding of the ZG work, so I could be completely wrong [18:43] It would not be the first time [18:43] today. [18:44] thisfred: reviewing... [18:46] geeze, mu couch directory is 5.3 gigs! [18:46] rickspencer3: and without gwibber_messages.couch? [18:47] I don't know [18:47] don't discount the views for gwibber_messages [18:47] I remember this particular database using a lot of space in the past [18:47] who live in separate files [18:48] yeah, it's huge, because gwibber stored every single message as it comes in, which is the worst way to write to couchdb. [18:48] compaction helps [18:48] but we don't do that automatically [18:49] thisfred: running ./run-tests fail with [18:49] fp = open(bookmark_template) [18:49] UnboundLocalError: local variable 'bookmark_template' referenced before assignment [18:50] huh, weird, does not do that here [18:50] File "/home/nessita/canonical/desktopcouch/review_my-use-devtools/desktopcouch/application/start_local_couchdb.py", line 207, in update_bookmark_file [18:50] looking [18:50] thisfred: want the full trace? [18:50] thisfred: ah! I know what can be. I don't have desktopcouch installed (I needed to confirm that gwibber doesn't use dc anymore) [18:51] you shouldn't need it to be installed to run tests in the tree [18:51] dobey: makes sense, but I want to confirm that's the issue [18:52] confirmed [18:52] thisfred: desktopcouch needs to be installed at system level to test run [18:52] nessita: yeah, I see. That sucks [18:52] thisfred: any idea why? [18:52] also that implies it talks to the real bookmark file [18:52] is it easu fixable? [18:52] nessita: it should not [18:53] let me see. [18:53] thisfred: also, I've got this failure https://pastebin.canonical.com/40030/ [18:53] Error, I mean, Error [18:54] nessita: when you do ./run-tests do the first two lines look like this: https://pastebin.canonical.com/40031/ ? [18:54] people [18:54] pastebin.ubuntu.com for publicly visible things. [18:54] dobey: thru [18:54] dobey: sry force of habit [18:54] true* [18:55] http://pastebin.ubuntu.com/535306/ [18:55] thisfred: there are at least 3 instances of desktopcouch that get started up in the tests [18:55] thisfred: yes, they do. full run at http://pastebin.ubuntu.com/535307/ [18:56] nessita: thx [18:56] thisfred: there are also some logging formatting errors (TypeError: not all arguments converted during string formatting) [18:56] thisfred: those should be fixed as well [18:56] CardinalFang: so desktopcouch tests seem to require desktopcouch is installed. That's pretty bad... :( [18:57] nessita: Yeah, I have no idea where they come from... :S [18:57] thisfred: I'll help you find that [18:58] thisfred, eh? [18:59] CardinalFang: nessita is reviewing my branch, and it breaks horribly [18:59] CardinalFang: while the tests pass hee [18:59] here [18:59] CardinalFang: uninstall desktopcouch and related and try to run the tests [18:59] they won't run [19:00] CardinalFang: full trace http://pastebin.ubuntu.com/535312/ [19:01] So for one thing start_local_couchdb.py is under tested, since there is a path through it that leads to the use of an undeclared variable [19:02] nessita, PYTHONPATH=`pwd` ./run-tests # what does this do? [19:02] CardinalFang: let's see [19:03] CardinalFang: exact same trace [19:03] CardinalFang: u1trial adds . to the sys.path [19:03] CardinalFang: try it yourself, uninstall everything dc-related [19:03] nessita, doing now. [19:04] thisfred: bin/desktopcouch-pair line 653 should be logging.exception("Service %s had an error", srv_name) [19:04] instead of logging.error("Service %s had an error", srv_name, e) [19:04] nessita: thx, good find [19:04] nessita: more correctly it should probably have a ": %s" added at the end of the string [19:04] thisfred: checking if that was the only issue.... [19:05] dobey: nopes [19:05] dobey: on try:except you have to use logging.exception [19:05] and not log the exception yourself [19:06] dobey: logging.exception handles the logging of the exception within a context where an exception occurred in a graceful manner [19:06] thisfred: that wasn't the (only) problem, I ll keep checking [19:07] * dobey suspects there may still be many problems, but less than there were before [19:07] yep [19:07] I meant regarding log formatting... not the whole thing :-) [19:08] thisfred: also, but this is mostly me thinking out loud, there mixed are %s and %r [19:08] there are mixed* [19:08] thisfred: no need to change that noe, of course [19:11] thisfred: same fix (logging.exception instead of anything else) on desktopcouch/application/pair/couchdb_pairing/dbus_io.py:103 (though this case should not be failing) [19:11] thisfred: same file, same fix, line 133 [19:13] nessita: huh? You mean use the comma syntax and %r in both? [19:13] thisfred: nopes, replace logging. for logging.exception [19:13] thisfred: and remove any formatting [19:13] thisfred: do you know what logging.exception do? [19:14] thisfred: if not, what I'm saying is probably chinese :-) [19:14] nessita: I can guess probably [19:14] thisfred: let me show you [19:15] hi [19:15] anybody there [19:15] thisfred: http://pastebin.ubuntu.com/535316/ [19:15] nessita: in testing your branch, to what do I connect d-feet? [19:15] hey [19:16] thisfred: the exception traceback is automatically logged when using logging.exception [19:16] blip: hi there [19:16] nessita: awesome, fixing that [19:16] thisfred: you just need to add a proper message, without caring about the exception [19:17] thisfred: regarding d-feet, you need to connect to the session bus [19:17] thisfred: File -> Connect to Session Bus [19:17] filter per com.ubuntu.sso service [19:17] nessita: thx, gotcha [19:18] i have got several tropuble when i want to connect [19:18] to the server [19:18] in my computer [19:18] thisfred: and in the /com/ubuntu/sso/credentials path, browse the CredentialsManagement iface [19:18] blip: how are you connecting? what ubuntu are you running? [19:18] is not running [19:18] well [19:19] i put the ubuntu into [19:19] virtual machine [19:19] but is not working [19:19] blip: how can you tell is not working? [19:19] thisfred: fwiw, i just proposed a branch to add coverage reporting to u1trial, as well [19:19] blip: I mean, what are you expecting to see that you're not seeing? what ubuntu are you running? [19:21] thisfred: same logging.exception fix for start_local_couchdb.py:234 [19:21] thisfred: no! sorry, my lie. That line is juts perfect [19:21] dobey: let me know if you want me to review that [19:22] sure, go ahead [19:22] https://code.edge.launchpad.net/~dobey/ubuntuone-dev-tools/add-coverage/+merge/41503 [19:23] dobey: I like show_missing=True, but fear I may be alone in that [19:24] thisfred: i wouldn't mind if it didn't make the output harder to read [19:25] dobey: yeah, a little, but there's an easy and fun way to make it prettier: increase coverage ;) [19:25] yes, well. i'm not going to increase coverage of everyone else's code just to make the output easier to read [19:25] I like to see when there's a single statement or maybe two untested in a file. That's low hanging fruit, usually [19:26] a percentage doesn't tell me that without doing math in my head, which it's not cut out for ;) [19:26] thisfred: found another issue: (desktopcouch/application/migration/__init__.py) 53 logging.info("Migrating DB: ", db.db.name) [19:26] yeah, but for large files with little coverage, you get multiple lines of output from show_missing [19:26] yep [19:26] nessita: thx fixing [19:27] thisfred: and that was the last culprit (as far as test coverage goes) [19:28] nessita: revno 224 pushed [19:28] thisfred: ack [19:28] dobey: +1d [19:28] thisfred: if it was '\n\t'.join(x.name for x in missing_methods) or something, then i'd like it more :) [19:29] nessita: I can't get the import errors you promised when testing your branch [19:29] thisfred: what dbus methid you invoked? login or register? [19:29] dobey: since you parse and redisplay the lint output..... ;) [19:29] nessita: both [19:29] nessita: commented on the proposal [19:29] thisfred: are you sure you're running the dbus service from my branch? [19:30] thisfred: show_missing doesn't give parseable output in the respect. it just gives a string of number pairs [19:30] nessita: I ran the killall and start from your branch yes [19:30] dobey: yeah, let's forget about it for now, any coverage stats at all are awesome [19:31] thisfred: so, let's go from the top since the ImportError should appear :-). I'll be asking silly questions but I want to know we're in synch. How do you setup a branch to review it? [19:34] nessita: bzr branch lp:~nessita etc. [19:35] nessita: wait! [19:35] nessita: I lied [19:35] thisfred: so, recommended way of setuping a review is: branch project trunk, then bzr merge target branch to ensure that target branch doesn't generate conflicts [19:35] thisfred: you did? [19:35] The import errors are totally there [19:36] thisfred: I told you! :-P [19:36] I just expected errors in the UI or something :) [19:36] thisfred: ah no, we signal back every outcome [19:36] but they're in the console of course [19:36] thisfred: my bad for not being explicit about that [19:36] I'm too used having alecu doing the reviews (bad nessita, bad!) [19:37] nah, it's pretty obvious if you're not stupid. [19:37] I was just doing twelvity things at once again [19:39] nessita: +1 [19:39] thisfred: awesome, thanks! [19:40] thisfred: I'm still having the test Error on your branch desktopcouch.application.pair.tests.test_couchdb_io.TestCouchdbIo.test_get_database_names_replicatable [19:40] thisfred: I do have desktopcouch installed [19:40] maybe I need some other package? [19:41] nessita: I don't think so. CardinalFang any ideas? (test error at the end of http://pastebin.ubuntu.com/535307/ ) [19:42] I have never seen that one before [19:45] hrmm [19:45] oh i know how to fix that [19:45] one second [19:46] thisfred: in test_couchdb_io.py change the import of unittest from twisted.trial to just be import unittest [19:47] dobey: will do [19:48] thisfred: I tried trunk but I've got ImportError: No module named coverage [19:48] ah fun [19:48] nessita: ah, yeah, that runtest.py assumes you have coverage installed. [19:49] that is gone on my branch, but .... [19:49] ok, I'll wait your fix then [19:49] well, gone partially [19:49] dobey: we can't skip that one test then. I think I'll kill it anyway. It talks to the internet. [19:49] thisfred: skip the one io test? [19:50] dobey: there's a conditionally skipped test [19:50] thisfred: the reactor error when away when i switched it to use plain unittest [19:50] huh [19:50] s/when/went/ [19:50] dobey: ah yes, but your provider likely does not hijack non existing domains then [19:50] thisfred, No, I don't have any specific idea. [19:51] which goes to show that the test is not all that unit ;) [19:51] dobey: fun, now I get the sorted error [19:51] heh [19:52] thisfred: well i didn't see anything in the runtests.py that suggested it did anything beyond just collecting the tests and running them, in that respect [19:52] thisfred: so i presume the issue is coming up now because u1trial installs a glib twisted reactor [19:52] thisfred: where runtests.py did not [19:53] thisfred: i guess it was always sullying the reactor, but there wasn't always a running reactor [19:54] right [19:55] anyways [19:57] CardinalFang: any news on the tests depending on an installed dc? [19:58] nessita: i wonder what specifically is requiring something to be installed, there [20:00] * nessita wonders too [20:00] nessita: pushed 225, which should solve the reactor issue [20:00] dobey: ah, I just remember. Any news on the nautilus plugin crash issue? I'm having u1client-gnome uninstalled because it kills my syste, [20:01] system* [20:01] thisfred: ack [20:02] nessita: i have not seen any new information on it, no [20:02] dobey: what new info do you need? besides the one from Thomas [20:03] thisfred: I have tons of FIXMEs and TODOs [20:03] XXX I mean [20:03] and some lint errors:desktopcouch/application/pair/__init__.py: [20:03] 19: [W0511] FIXME constants should be upper case [20:03] desktopcouch/application/pair/tests/test_couchdb_io.py: [20:03] 31: [W0611] Unused import httplib2 [20:03] 32: [W0611] Unused import socket [20:04] nessita: i need a backtrace from him. even with the extra glib symbols, your backtrace simply looks like something is corrupting memory somehow, and isn't making much sense [20:04] dobey: is there any chance you give review the nautilus plugin to look for "obvious" memory issues? [20:04] nessita: yes, if I understand correctly, those will not block landing branches, but hopefully nag people into fixing the issuyes [20:05] thisfred: I agree on XXX and FIXMEs (though I think they do block tarmac) [20:05] thisfred: but the unused import should be fixed [20:05] nessita: ah yes, that's weird [20:06] nessita: i looked at libsyncdaemon where your trace points, and i don't see anything there. [20:07] nessita: unused imports removed in 226 [20:07] thisfred: ack [20:07] dobey: Did I misread u1lint? It seems to do *something* special with W0511 messages [20:08] dobey: to be clear, my question is, will these block in tarmac? [20:08] My hope is no :) [20:09] My name is legion [20:10] thisfred: "maybe" [20:10] I can live with maybe [20:10] thisfred: i think pylint exits with a non-zero value now for FIXME, where it didn't used to [20:10] ah [20:10] thisfred: if your branch gets blocked by that, i can hack u1lint to do something about that [20:10] that would suck, but I can make them into TODO I guess :) [20:10] dobey: will let you know [20:11] although, actually, i also have to change the config to use ./run-tests instead of ./runtests.py before it will potentially succeed anyway [20:11] thisfred, dobey: from my POV, I prefer tarmac not landing branches with XXX and FIXMEs and TODOs [20:11] dobey: I thought I saw some hackery to that effect in u1lint already [20:11] thisfred, dobey: and making those bugs in LP [20:11] nessita: they should be bugs if they are going to be there, but i don't think we should block on them being there [20:12] blocking on bugs existing in the code is dumb, because there are always going to be bugs [20:12] thisfred: so, in the code we may find a comment like # needs better implementation (LP: #XXXXX) [20:12]