[01:11] <cjohnston> mhall119: james_w discussing the daily bug
[01:11] <mhall119> rebooting
[01:11] <cjohnston> mhall119: how can i rewrite that to include .date in the second one
[01:12] <mhall119> cjohnston: (utc_date+day).date
[01:12] <james_w> for slot in summit.slot_set.filter(start_utc__gte=utc_date.date, start_utc__lt=(utc_date+day).date).order_by('start_utc'):
[01:13] <james_w> cjohnston, ^
[01:13] <mhall119> hey, that's what I said
[01:13] <james_w> that's what it should be I think
[01:13] <cjohnston> it doesnt fix it
[01:13] <james_w> anything that starts today
[01:13] <james_w> cjohnston, I changed two other things
[01:13] <james_w> __lt rather than __lte
[01:13] <james_w> so that it's less than, rather than less than or equal
[01:13] <mhall119> ok, actually rebooting now
[01:13] <james_w> otherwise it will still do two days as you saw
[01:14] <mhall119> brb
[01:14] <james_w> the other change is end_utc to start_utc
[01:14] <cjohnston> james_w: should it be start, start?
[01:14] <cjohnston> ok
[01:14] <james_w> so that tests don't fail around midnight
[01:14] <cjohnston> still doesnt seem to work
[01:14] <cjohnston> for slot in summit.slot_set.filter(start_utc__gte=utc_date.date, start_utc__lt=(utc_date+day).date).order_by('start_utc')
[01:15] <james_w> hmm
[01:15] <james_w> still showing the same slots?
[01:15] <cjohnston> yup
[01:16] <cjohnston> for slot in summit.slot_set.filter(start_utc__gte=utc_date.date, start_utc__lt=(utc_date+day).date).order_by('start_utc')
[01:16] <cjohnston> something is invalid ^
[01:16] <cjohnston>  91.                 lookup_view = getattr(import_module(mod_name), func_name)
[01:16] <cjohnston> File "/home/chris/.virtualenvs/summit/lib/python2.6/site-packages/django/utils/importlib.py" in import_module
[01:16] <cjohnston>   35.     __import__(name)
[01:16] <cjohnston> Exception Type: SyntaxError at /lcq1-12/2012-02-07/
[01:16] <cjohnston> Exception Value: invalid syntax (views.py, line 77)
[01:20] <james_w> cjohnston, missing colon at the end of the line
[01:20] <cjohnston> der
[01:20] <cjohnston> still get
[01:20] <cjohnston> Tuesday >
[01:20] <cjohnston> 16:15 - 17:00 06 02
[01:21] <james_w> which day are you viewing?
[01:21] <cjohnston> its actually a problem with start date and not end date
[01:21] <cjohnston> daily
[01:21] <cjohnston> tues
[01:21] <cjohnston> cause the summit goes until 0200 on the next day utc
[01:21] <cjohnston> so end date isnt the problem
[01:22] <james_w> so it's really an issue with the fact that this summit crosses a utc day boundary?
[01:22] <cjohnston> james_w: somehow it needs to be done based on local time
[01:22] <cjohnston> yes
[01:22] <cjohnston> because its showing the last two sessions from monday on tuesday
[01:23] <james_w> I still think we should keep that change as well
[01:23] <cjohnston> which would be 00-01 and 01-02
[01:23] <cjohnston> ok
[01:23] <james_w> utc_date = summit.delocalize(viewdate)
[01:23] <james_w> it does call that
[01:23] <james_w> oh, I think I know
[01:24] <james_w> for slot in summit.slot_set.filter(start_utc__gte=utc_date, start_utc__lt=(utc_date+day)).order_by('start_utc'):
[01:24] <james_w> try that one?
[01:26] <james_w> we don't want to use .date which will take the start of the day in UTC, we already have the date as the start of the day in localtime, so just use the 24 hours after that
[01:26] <cjohnston> still not working
[01:28] <james_w> same results?
[01:28] <cjohnston> yes
[01:28] <james_w> hmm
[01:28] <james_w> sorry, but I have to go now
[01:28] <james_w> I hope you get this fixed
[01:28] <cjohnston> is there some way that we can change it from utc to local tz
[01:28] <cjohnston> ty james_w
[15:57] <danilos> nigelb, hi, I've heard from cjohnston about the problems with allowing people to be added to the private meeting directly
[15:57] <danilos> nigelb, I wonder what the status on that is and whether I can help anyhow? (if you are around, of course)
[15:57] <mhall119> nigelb: I wasn't sure if you've started on that or not, and if so how far you've gotten
[16:03] <nigelb> danilos: I played around, but now I figure I need a new form to do it.
[16:03] <nigelb> I never got around to actually doing it.
[16:04] <danilos> nigelb, right, I guess we can't add a reference to the model to be able to easily add it to the form as well :/
[16:05] <mhall119> danilos: no, since we're actually two relations apart
[16:06] <danilos> right
[16:06] <mhall119> we need to create what Django calls an inline formset
[16:08] <nigelb> yeah, that.
[16:18] <danilos> sounds interesting
[16:18]  * danilos reads up on that
[16:19] <danilos> btw, is the rest of the private meetings stuff up? can I have Stephen test it
[16:20] <cjohnston> danilos: we have one more bug that came up that we need to fix before pushing live.. otherwise it will break the plenary stuff again
[16:20] <cjohnston> removing the linaro hacks introduced a bug with the plenaries because last uds there were multiple plenaries
[16:22] <danilos> oh, right, so code burped on the last UDS data
[16:24] <cjohnston> kinda.. ya
[16:28] <danilos> cjohnston, anything I can look into to make it chug along?
[16:29] <cjohnston> danilos: in truck, plenaries are not currently displayed
[16:29] <danilos> cjohnston, have you tried a regular car? :)
[16:29] <cjohnston> https://code.launchpad.net/~chrisjohnston/summit/920751/+merge/89806
[16:29] <cjohnston> nice
[16:29] <cjohnston> trunk
[16:30] <cjohnston> add that mp, and plenaries are displayed, but i believe mhall119 has last uds in his db, which is what caused the error
[16:31] <cjohnston> danilos: from trunk, you can import-live-data uds-p and then you will have the data from the last uds to test against
[16:31] <cjohnston> im currently in the middle of debugging ubuntu one
[16:31] <cjohnston> so im stuck for a bit
[16:31] <danilos> cjohnston, cool, thanks
[16:35] <mhall119> danilos: we don't have a staging area for summit, but I can fire up a cloud instance for testing
[16:35] <danilos> mhall119, I'll try the import-live-data approach first, I used to have a DB dump myself, but since I am not really keeping up with things, I'll see how it goes
[16:36] <danilos> mhall119, cjohnston, nigelb: so, I've gotten a deadline to make this ready for use by EOD tomorrow, so if there's any help I can get, I'd appreciate it :)
[16:36] <cjohnston> this and the participants is it
[16:36] <cjohnston> afaik
[16:37] <mhall119> danilos: import-live-data only gets the schedule, nothing about attendees or participants
[16:37] <danilos> mhall119, right, so it's not going to be sufficient? I guess I need to run a few scripts for that (one the get the XML for the sprint and parse it, another to re-read all the BPs)
[16:38] <cjohnston> that should work for the pleanry thing tho
[16:38] <mhall119> you'll need to create an Attendee record for yourself in the admin for some of the features to be available
[16:38] <mhall119> but otherwise it'll work
[16:38] <cjohnston> well.. that too
[16:38] <mhall119> I was just letting you know that it won't import everything that is in production
[16:41] <danilos> mhall119, right, thanks
[16:43] <danilos> mhall119, cjohnston: I also don't see the import_live_data among the commands of manage.py, I wonder if I am missing something
[16:44] <cjohnston> import-live-data
[16:44] <cjohnston> danilos: ^
[16:44] <danilos> cjohnston, I don't see that either (and it reports "unknown command" for either _ or - version)
[16:45] <cjohnston> danilos: you updated from trunk I assume?
[16:46] <danilos> cjohnston, yes, I can see the import_live_data.py file and the rev I have is r259, let me try to clean up the tree and rebuild it
[16:48] <mhall119> cjohnston: it has underscores
[16:49] <cjohnston> oh.. i thought it was -
[16:57] <danilos> got it working, trying manage.py from the wrong path, it'd be nice if it set the sys.path to appropriate values itself
[17:06] <danilos> I am also going to use lpupdate command to get all the users in
[17:20] <danilos> cjohnston, I've pasted the modification which makes it work for me, it's very simplistic fix which ensures it doesn't crash, correctness can be debated (it gets the first agenda)
[17:21] <cjohnston> pasted?
[17:22] <mhall119> cjohnston: it's hyphens in LTP
[17:22] <mhall119> but hyphens in python files makes them useless as python modules
[17:24] <cjohnston> mhall119: gotcha
[17:29] <danilos> cjohnston, yes, want me to push a separate branch and create an MP?
[17:31] <cjohnston> please
[18:03] <danilos> cjohnston, mhall119: fwiw, for that particular problem with plenaries for uds-p — https://code.launchpad.net/~danilo/summit/fix-plenaries/+merge/89963
[18:08] <cjohnston> mhall119: can you throw that into mine from earlier that you were working on and test it please? I'm now trying to get my desktop back
[18:08] <mhall119> cjohnston: which one of yours?
[18:09] <mhall119> cjohnston: can  we just land his, I know what it's doing and i'm okay with it
[18:10] <cjohnston> thats fine
[18:11] <cjohnston> then land https://code.launchpad.net/~chrisjohnston/summit/daily-updates/+merge/89825
[18:16] <danilos> mhall119, I've set cjohnston's branch as a pre-req in LP, so if mine is landed, his will be included as well
[18:17] <danilos> https://code.launchpad.net/~chrisjohnston/summit/920751/+merge/89806 <- this one
[18:21] <mhall119> approved both
[18:21] <mhall119> tests pass, no more error on the wide display, thanks guys
[18:22] <cjohnston> mhall119: can you do the daily updates branch
[18:23] <cjohnston> mhall119: if you could also review the other two branches... the open graph and the twitter
[18:23] <cjohnston> ill push to production and push a release
[18:23] <cjohnston> then we can release the participants part when we get it
[18:24] <cjohnston> danilos: afaik the only thing left is the participants stuff
[18:24] <cjohnston> nigelb: can you hit tarmac please
[18:25] <danilos> cjohnston, right, I'll look into that as well, but I'll probably switch locations and stay off IRC while I do that to get more dedicated hacking time for it :)
[18:25] <cjohnston> ok.. should we leave it with you then danilos /
[18:25] <cjohnston> ?
[18:26] <cjohnston> (for that part)
[18:28] <danilos> cjohnston, well, I'll only look into the problem tonight, I'll connect with nigelb tomorrow morning to see where he's at
[18:29] <cjohnston> ok
[18:29] <cjohnston> sounds god
[18:29] <cjohnston> good
[18:29] <cjohnston> thanks danilos
[18:29] <danilos> no, thank you guys :)
[18:32] <cjohnston> mhall119: tarmac sucks sometimes
[18:36] <mhall119> cjohnston: open graph branch approved, landing it by hand becuase of a conflict with trunk
[18:36] <cjohnston> ok
[18:38] <mhall119> cjohnston: the twitter one had two more conflicts, can you update them please?
[18:39] <mhall119> also, what happens if a summit has no hashtag?
[18:39] <mhall119> I do like the social networking stuff on the meeting page though, that's nice
[18:41] <cjohnston> mhall119: i can do either an if, or require a hashtag
[18:41] <mhall119> do an if, since old summits won't have one
[18:41] <mhall119> and new summits might not have one when they are first created
[18:42] <cjohnston> ok
[18:54] <mhall119> cjohnston: danilos: all your fixes have landed
[19:10] <cjohnston> mhall119: pushed
[19:11] <cjohnston> mhall119: for the participant stuff.. is it the inline formset thats needed?
[19:11] <mhall119> cjohnston: I think so, yes
[19:12] <cjohnston> ya.. that doesnt look like fun
[19:12] <cjohnston> mhall119: if you can do a quick review of the hashtag thing, as soon as everything finishes merging, ill get it released
[19:29] <mhall119> cjohnston: the twitter feed pushes the schedule lists down quite a big
[19:29] <mhall119> bit
[19:31] <cjohnston> do you want it to the left?
[19:32] <cjohnston> mhall119: we need a new hash tag for uds
[19:32] <mhall119> yeah, i know
[19:33] <cjohnston> #devsummit >
[19:33] <cjohnston> ?
[19:33] <cjohnston> its no less ubuntu than uds
[19:33] <mhall119> yes it is
[19:34] <cjohnston> #ubuntu-devsummit
[19:34] <cjohnston> long as crap
[19:34] <mhall119> #uds-q ?
[19:34] <mhall119> or #udsq
[19:35] <cjohnston> i like not changing it each time
[19:39] <cjohnston> mhall119: what do you want me to do with the schedule list
[19:55] <mhall119> cjohnston: I'm not sure
[20:12] <cjohnston> merge it and we can decide later?
[20:17] <cjohnston> mhall119: where did you get your little sound icon from?
[20:18] <cjohnston> can you get one for chat?
[20:19] <mhall119> cjohnston: I stole if from the desktop icon set
[20:19] <mhall119> and yeah, I can get a chat one
[20:19] <cjohnston> could you email it to me please?
[20:19] <cjohnston> or tell me where in the folder structure i could find it
[20:21] <cjohnston> mhall119: what do you think about changing the QR code on the display screen and the daily screen to link to that same page on your cell phone
[20:21] <cjohnston> well.. to link to the daily page on your cell phone
[20:21] <mhall119> not yet, maybe when we have a decent mobile web interface
[20:21] <cjohnston> ok
[20:23] <cjohnston> mhall119: whats your thought about making the daily page and the display page automatically refresh every 5 minutes
[20:25] <mhall119> display page yes, daily page no
[20:25] <cjohnston> why no?
[20:26] <cjohnston> the ability doesnt exist on the daily page to make it refresh by ?refresh
[20:27] <cjohnston> what about removing     "django.core.context_processors.i18n", from settings.py too
[20:27] <cjohnston> and turning USE_I18N = True False
[20:33] <mhall119> the daily schedule shouldn't be auto-refreshing, IMO
[20:34] <mhall119> it's only for desktop use, it should conform to normal webpage usage
[20:35] <mhall119> i18n might be used by the admin
[20:40] <cjohnston> I think I removed it all from the admin
[20:40] <cjohnston> or are you saying outside of what we can control by code
[21:01] <mhall119> yeah, the django.contrib.admin stuff
[21:02] <cjohnston> ic