| * erikhatcher joins | 05:44 | |
| * erikhatcher leaves | 05:49 | |
| * erikhatcher joins | 07:03 | |
| * rsinger joins | 09:22 | |
| * jamieorc joins | 10:15 | |
| * erikhatcher leaves | 10:58 | |
| * rduplain joins | 11:12 | |
| * jkeck joins | 12:21 | |
| * bess joins | 12:24 | |
| * rduplain_ joins | 12:43 | |
| * rduplain_ leaves | 12:44 | |
| * rduplain leaves | ||
| * rduplain joins | ||
| * jkeck leaves | 12:45 | |
| * jrochkind1 joins | 13:02 | |
| * jrochkind leaves | 13:04 | |
| * bess leaves | 13:25 | |
| <jrochkind1> | hmm, trunk blacklight still seems to have code in controllers directly, not in modules? Am I misunderstanding the change that matt committed, or looking at the wrong place, or not really looking at trunk, or...? | 13:27 |
| * bess joins | 13:40 | |
| * bess leaves | 13:47 | |
| * ndushay joins | 14:13 | |
| * bess joins | 14:17 | |
| <cbeer_> | has anyone done date range facets + blacklight? | 14:44 |
| <bess> | hey, cbeer | 14:45 |
| cbeer: the closest thing I've done are the date ranges at http://nwda.projectblacklight.org | ||
| which are of the form "10 years ago", "Within the past year" and prose facets like that | 14:46 | |
| cbeer: so which bagit library are you using? | ||
| this one? http://github.com/flazz/bagit | ||
| <cbeer_> | bess: thanks, i'll take a look.. not sure it'll do it, but its a start | 14:51 |
| the library i used wasn't on github, but it wouldn't surprise me if they are one and the same | ||
| yeah, they are | 14:52 | |
| <MrDys> | I remember something coming up in yonik's solr webinar about a better way to do date ranges | 14:54 |
| ah yeah | 14:56 | |
| using Trie fields | ||
| "Best case: 40x speedup of range queries" | 14:57 | |
| http://www.lucidimagination.com/files/file/LI-mastering-solr-webinar.pdf | ||
| <cbeer_> | MrDys: i've heard about Trie fields -- those are the slides from the thing last week? | 14:59 |
| <MrDys> | yep | |
| * erikhatcher joins | 15:03 | |
| * bess leaves | 15:04 | |
| <jrochkind1> | MrDys: I _think_ if you use the new date range facetting stuff, you're using trie fields under the hood even if you don't know you are. But I could be wrong, and you have to explicitly use them to get the full benefit. | 15:06 |
| <MrDys> | jrochkind1: the slide says you need to state it explicitly | 15:08 |
| tint, tdate, tfloat, etc | ||
| <cbeer_> | ok, surely there is a better way to express: response['moreLikeThis'].first.last['docs'] (data structure looks something like {'moreLikeThis' => {'wgbh' => {'docs' => [1,2,3] } } } ) | 15:17 |
| <erikhatcher> | yeah, you definitely have to use the trie field types if you want to take advantage of the performance improvements | 15:38 |
| <jrochkind1> | hmmm, for some reason my blacklight features have stopped running properly in my branch, and I have no idea why. | 15:43 |
| shows weird output like "F-----F-"... instead of the usual cucumber output, which even for failed tests doesnt' usually look like that. | 15:44 | |
| <MrDys> | jrochkind1: related to the template upgrade? | |
| <jrochkind> | no idea. | |
| ah, I think I see my problem. | 15:46 | |
| and it was just my problem. | ||
| for some reason, I need to write my bugs to IRC or email before I can find em, heh. | ||
| i'm still confused about why spec:features sometimes outputs all of the features/scenarios tested, and sometimes just outputs dots. | 15:49 | |
| * bess joins | 16:11 | |
| <ndushay> | jrochkind: "for some reason, I need to write my bugs to IRC or email before I can find em, heh." we noticed. | 16:24 |
| jrochkind: you solve a lot of your own with no help. | 16:25 | |
| jrochkind: try the "45 min" rule - don't write the note (or write it and don't press send) for 45 min. if it's still unsolved at that point, bring it on. | ||
| jrochkind: specs are dots, features/scenarios are written out. | 16:26 | |
| <BillDueber> | rsinger: My perl job finally finsihed -- 75mn including on-the-fly gunzippping. | 16:37 |
| <rsinger> | BillDueber: mine was 48min | 16:38 |
| BillDueber: still not sure about the U-G-L-Y, though | 16:39 | |
| <BillDueber> | rsinger: I ddin't see your python code, but it's not as bad as teh ruby I took it from... | |
| <rsinger> | BillDueber: all of my code is crappy, bill | 16:44 |
| <BillDueber> | rsinger: Not the stuff I've dealt with. Unless royt secretly codes all your public stuff :-) | |
| * BillDueber is outtahere. | ||
| * rduplain leaves | 16:50 | |
| <cbeer_> | i love when ruby makes it easy to just do the right thing | 17:00 |
| * bess leaves | 17:18 | |
| <jrochkind> | ndushay: but when I run "rake solr:features"... I get dots, not written out examples. Is it really running my features? I think so. | 17:40 |
| <ndushay> | ah. sorry. please pardon my ignorance. | |
| * cbeer__ joins | 17:46 | |
| * cbeer leaves | ||
| <jrochkind> | ndushay: yeah, I'm confused about what's going on too. Oh well. | 17:47 |
| <ndushay> | jrochkind: i have come to accept a perpetual level of confusion as a baseline. | |
| <jrochkind> | heheh, yeah, I hear that. | |
| * bess joins | 17:48 | |
| * bess leaves | ||
| * bess joins | 17:49 | |
| * jamieorc leaves | ||
| * bess leaves | 18:23 | |
| * bess joins | 18:30 | |
| <jrochkind> | i think maybe it only spells out the scenarios if one of them fails, or something. I dunno. | 18:45 |
| <bess> | jrochkind: are you referring to the fact that cucumber has stopped spelling out the scenarios? | 18:46 |
| <jrochkind> | bess: yes! you have some insight? | |
| <bess> | no, except that I just noticed the same thing. | |
| <jrochkind> | heheh, okay, well, glad it's not just me. :) | |
| <bess> | I used to always spell them out and now it's stopped | |
| I have been baffled | ||
| <jrochkind> | me and naomi too. :) | 18:47 |
| at first i thought i was doing something wrong, or maybe not really running the features when I thought i was. But I think I'm not, and I am. | ||
| it IS somewhat more convenient this way. I don't need to see 20 pages of scenarios that passed anyway every time I run the features. | ||
| <bess> | yeah, but I want to find a way to get it to print | 18:48 |
| and verbose doesn't do it | ||
| <jrochkind> | yeah, i'm not really sure why it stopped. | |
| if you figure it out, let us know. | ||
| <bess> | ok | |
| <jrochkind> | i could swear that I saw it print out the scenarios, and then stop, without me changing anything. But maybe I updated to trunk in between, I dunno. | |
| <bess> | jrochkind: I saw the same thing!! | 18:52 |
| * bess vows to get to the bottom of this | ||
| <jrochkind> | bess: Weird! | |
| especially weird that it effected both of us at exactly teh same time, when neither of us THOUGHT we had done a code update. | 18:53 | |
| <cbeer> | sorry, what sort of output are you getting? | 19:09 |
| <jrochkind> | when running features, getting "......" spec-style output, instead of getting the actual narrative scenarios we used to get. | |
| I am running features with rake solr:features, not sure if bess is doing the same. | 19:10 | |
| <cbeer> | so, ..................................F................... ? | |
| <jrochkind> | righto. | |
| <cbeer> | i always thought that was normal :P | |
| of course, i didn't run any tests until c4l10 | ||
| <jrochkind> | i dunno man. | 19:11 |
| <cbeer> | i'm on trunk with cucumber 0.6.2, if that matters | |
| * erikhatcher leaves | 19:13 | |
| <bess> | jrochkind: I'm asking on #cucumber too | 19:16 |
| * bess leaves | 19:34 | |
| * bess joins | 20:15 | |
| * erikhatcher joins | 20:18 | |
| * ndushay leaves | 20:19 | |
| * erikhatcher leaves | 20:34 | |
| * ndushay joins | 21:25 | |
| * ndushay leaves | 22:05 | |
| * bess leaves | 23:41 | |
| * ndushay joins | 23:43 | |
| anybody here? | 00:40 | |
Generated by Sualtam