![[personal profile]](http://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I'd just like to personally thank the entire Internet for explaining how and where to point my satellite dish when I moved it higher on the roof. Then I'd like to lodge a few complaints regarding the weather, the height of roofs, the failure modes of caulking guns, and asphalt. That is all.
Testing crossposter with wrong password stored in DW prefs.
I'm using the feed from this account to test the fix for bug 640 over on Afuna's machine. I need a new entry so syn-suck will update. And it should probably contain a Unicode character that I think would previously have caused the entry not to show up in the feed account. So here's a Lira Sign (Unicode 0x20A4, UTF8: E2 82 A4): ₤
This post contains a literal right single quotation mark: ’
Unicode: 2019
UTF8: E2 80 99
Unicode: 2019
UTF8: E2 80 99
This post contains a literal euro sign: €
Unicode: 20AC
UTF8: E2 82 AC
Unicode: 20AC
UTF8: E2 82 AC
The sudafed woke me up at 3am today so I started looking at the directory search bug. Read some code, poked the directory search and results pages a bit, but no definite progress. I probably need to look under the hood while a search is running to get anywhere. Debug logging, figuring out whether it's using Gearman or not, etc. So I doubt I'll be of much use without a working dreamwidth installation to mess with. Hrm.
Edit: Oh, the directory geographic stats do work, so you can find out how many accounts are where. But of course that uses a different set of queries.
Edit 2: I have a theory now, at least. From UserSearch.xs comes this gem:
Gee, I wonder what OS dreamwidth is running on...
Edit 3: That comment was a total red herring. Left a real diagnosis in the comments of the bug linked above. I really would have gotten nowhere fast without the hack space Janine mentioned and Sophie provided, plus this comment over on lj_dev.
Edit: Oh, the directory geographic stats do work, so you can find out how many accounts are where. But of course that uses a different set of queries.
Edit 2: I have a theory now, at least. From UserSearch.xs comes this gem:
// FIXME: this will kinda blow w/ 64-bit pointers... we should/could just store 32-bit id instead.
resultset[resultset_size++] = &usermeta[uid];
Gee, I wonder what OS dreamwidth is running on...
Edit 3: That comment was a total red herring. Left a real diagnosis in the comments of the bug linked above. I really would have gotten nowhere fast without the hack space Janine mentioned and Sophie provided, plus this comment over on lj_dev.
Tags:
Sure, why not? I read LJ thru RSS anyway, so what's one more feed to add? I definitely won't feel as sketchy about putting my content up on here.
Tags:
.
