| ../irclogs/#mantishelp.2009-06-05.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10563 - informatyk - open - new | 10:30 |
|---|---|---|
| mantisbot | New bug: After customize view_issues_page_columns, the priority column crashes - http://www.mantisbt.org/bugs/view.php?id=10563 | 10:30 |
| mantisbot | New bug: Bug 10564 - Jimi_Joma - open - new | 10:40 |
| mantisbot | New bug: Mantis is generating empty spaces in field description, summary (all textareafields) - http://www.mantisbt.org/bugs/view.php?id=10564 | 10:40 |
| [KK]Kirill | paul_: lo | 11:47 |
| nuclear_eclipse | people who use word documents to post screenshots should be shot on sight... | 13:37 |
| * nuclear_eclipse starts upgrading his server to Jaunty | 15:23 | |
| cudell | HI all. Got a question about a bug I think we've found in the latest nightly build. | 16:20 |
| cudell | Creating a user seems to fail with 500 Internal Server Error | 16:22 |
| cudell | the post request seems well formed... permissions on the script seem to be in order. the response to the post is empty. | 16:27 |
| markw_ | hmm. | 16:28 |
| markw_ | is there any "bulk" user adding tool? | 16:29 |
| cudell | resending the same request again via a refresh results in a Mantis Application Error 2800 | 16:29 |
| cudell | we are not using a bulk user adding script | 16:29 |
| cudell | simply: manage_user_create.php | 16:30 |
| markw_ | no | 16:30 |
| markw_ | I need to bulk add some users. | 16:31 |
| markw_ | I thought there was a "bulk" add script but it doesn't look like it. | 16:31 |
| cudell | it looks like the email validation in that post is broken. email_ensure_valid - line 433 of user_api.php in Core | 16:40 |
| nuclear_eclipse | what version of the nightly have you been testing? | 17:01 |
| jleb | Hi eerybody. I'm trying to get BT1.2 integrated with Subversion using the Source Control Integration plugin. Not having much luck, any one here who might be able to help? | 19:02 |
| nuclear_eclipse | what's the problem? | 19:03 |
| cudell | hi jleb | 19:11 |
| cudell | this is the nightly build version we've got: 1.2.0a3 2009-06-04-master-2b2ec01 | 19:12 |
| cudell | Schema Version 171 | 19:12 |
| paul_ | nuclear_eclipse: . | 19:36 |
| nuclear_eclipse | hi paul_ | 19:36 |
| paul_ | lo | 19:36 |
| cudell | can you guys verify that the email validation in that post is broken. email_ensure_valid - line 433 of user_api.php in Core | 19:52 |
| paul_ | lo daryn | 19:55 |
| paul_ | nuclear_eclipse: need you to review my stuff | 19:56 |
| paul_ | tomorrow | 19:56 |
| nuclear_eclipse | cudell: I think it might be | 19:57 |
| nuclear_eclipse | paul_: have you fixed dates yet? | 19:57 |
| paul_ | i can't have broken custom field dates | 19:59 |
| nuclear_eclipse | ok | 19:59 |
| nuclear_eclipse | but you *did* break the ability for users to input dates for due_date, version release dates, etc | 19:59 |
| paul_ | yep | 20:00 |
| paul_ | shouldn't versoin release dates show calendar? | 20:00 |
| nuclear_eclipse | I think that's rather beside the poitn | 20:05 |
| * paul_ wonders how one can apply admin checks to plugins | 20:07 | |
| nuclear_eclipse | facepalm | 20:07 |
| nuclear_eclipse | dates! | 20:07 |
| nuclear_eclipse | fix dates! | 20:07 |
| nuclear_eclipse | don't make me revert every change to dates in order to release 1.2 RC | 20:08 |
| vb1234 | nuclear_eclipse: hi | 20:08 |
| nuclear_eclipse | ti Victor | 20:08 |
| nuclear_eclipse | hi* | 20:08 |
| vb1234 | are you talking to paul_ ? | 20:08 |
| nuclear_eclipse | yep | 20:08 |
| vb1234 | so what's up with the rc. | 20:09 |
| nuclear_eclipse | assuming that Paul actually gets around to fixing the new date handling before tomorrow evening, I'm going to try to roll the release tomorrow evening and/or sunday | 20:09 |
| paul_ | +spl_autoload_register( '__autoload' ); | 20:10 |
| paul_ | that should be safe right? | 20:10 |
| nuclear_eclipse | no clue | 20:12 |
| nuclear_eclipse | why are you screwing around with SPL? | 20:12 |
| paul_ | to allow plugins to call autoload functions :P | 20:13 |
| CIA-61 | Mantisbt: jreese * rc6c18c57e4a6 /core/email_api.php: Partially revert 209070a7: "Remove old email_api functions...". | 20:13 |
| nuclear_eclipse | why would plugins need to call autoload? | 20:13 |
| paul_ | whats up with changing the mail regex's | 20:16 |
| nuclear_eclipse | the old version was slow/clunky/broken in some cases, and a simpler regex still covers 99.99% of all users | 20:16 |
| * paul_ has a headache | 20:17 | |
| paul_ | someone needs to fix tests | 20:17 |
| nuclear_eclipse | eg, rfc comments and domain literals are worthless and/or never used | 20:17 |
| paul_ | btw | 20:17 |
| nuclear_eclipse | paul_: you need to fix dates before you start finding other things to fix.... | 20:17 |
| paul_ | as it's stopping me from going through my automated test results | 20:17 |
| nuclear_eclipse | seriously, dates is higher priority atm | 20:18 |
| vb1234 | We should not have trunk at a broken state at any time. | 20:18 |
| vb1234 | that's why we moved to git :) | 20:19 |
| nuclear_eclipse | lies | 20:19 |
| vb1234 | ? | 20:19 |
| nuclear_eclipse | sarcasm | 20:19 |
| vb1234 | :) | 20:20 |
| nuclear_eclipse | the problem in this case is that paul_ developed in his public repo/branch, and everything looked fine, and then I found the breaks after the fact when testing something else | 20:20 |
| paul_ | the problem is more | 20:20 |
| vb1234 | then I agree with the focus on this, specially that this is a feature that affects the db schema. | 20:20 |
| nuclear_eclipse | eg, we were using git properly -- we're just not testing enough before merging features to master | 20:20 |
| paul_ | it gets confusing if you have lots of patches affecting different things | 20:21 |
| nuclear_eclipse | and tbh, I think our biggest problem is lack of a) developer time, and b) dedicated testers for looking at feature branches | 20:21 |
| vb1234 | When was this checked in? From memory, it was sometime ago. | 20:22 |
| vb1234 | correct? | 20:22 |
| nuclear_eclipse | lack of dev time results in just pushing to master because there's never enough time to thoroughly review/test | 20:22 |
| paul_ | nuclear_eclipse: actually one of the reasons I wanted to get dates out the way | 20:22 |
| nuclear_eclipse | about middle May was the merge | 20:23 |
| paul_ | is I was trying to test changes to bugdata + dates together | 20:23 |
| paul_ | and having two seperate branches was hindering that | 20:23 |
| vb1234 | can't you merge to a third branch? | 20:23 |
| vb1234 | or some local branch? | 20:23 |
| vb1234 | I feel we are stuck now that it is even not easy to revert. | 20:24 |
| vb1234 | given the schema change. | 20:24 |
| nuclear_eclipse | vb1234: I suspect paul_ is averse to learning how his tool works | 20:24 |
| vb1234 | and us / others may have upgraded to new schema. | 20:24 |
| paul_ | nuclear_eclipse: ? :) | 20:24 |
| vb1234 | :) | 20:24 |
| vb1234 | paul_: when do you think we can get these fixes done? | 20:24 |
| vb1234 | (not sure what they are by the way) | 20:24 |
| vb1234 | I just want us to cut the release as agreed earlier. | 20:25 |
| * paul_ nods | 20:25 | |
| paul_ | anyway, dates stuff came up mid week | 20:26 |
| paul_ | and should be easy | 20:26 |
| vb1234 | ok sounds good. | 20:26 |
| Heady| | when the release is planned? | 20:26 |
| paul_ | just probably not on a friday night :P | 20:26 |
| Heady| | lol | 20:26 |
| vb1234 | are the dates issues release blocking? | 20:26 |
| vb1234 | what is the bug #? | 20:26 |
| paul_ | apparently version updates on projects feed from a date string straight to db | 20:27 |
| vb1234 | nuclear_eclipse: will you get a chance to update docbook with the new plugin events / configuration options? | 20:27 |
| paul_ | john needs to look at my new plugin events too | 20:27 |
| vb1234 | btw, there is a swekey authentication plugin on the forums (see customization forum). It might be worth looking at that. | 20:28 |
| paul_ | I dont like it | 20:28 |
| vb1234 | I haven't looked at the code, but why? | 20:28 |
| vb1234 | do we need to add more events? | 20:28 |
| vb1234 | We need to use the community plugins as feedback into the events / infrastructure design. | 20:29 |
| paul_ | well, we dont support authentication plugins atm (As part of events structure) | 20:30 |
| nuclear_eclipse | vb1234: I'm already working on the docbook for events :) | 20:30 |
| paul_ | so it hacks itself in | 20:30 |
| vb1234 | agreed, but in this specific example, it is a good use case to consider in our design. | 20:30 |
| vb1234 | forget about the specific implementation. | 20:30 |
| vb1234 | basically this is the use case where there is a device involved. | 20:31 |
| paul_ | I'm also disappointed that they don't appear to release source code for their plugins. | 20:33 |
| paul_ | and/or customisations to open source stuff | 20:33 |
| vb1234 | interesting. So you have to buy the key to get the updates? | 20:33 |
| paul_ | actually ,tell a lie, they do | 20:34 |
| paul_ | I thought that the putty stuff was only the binary | 20:35 |
| paul_ | but it does contain source too | 20:35 |
| nuclear_eclipse | vb1234, paul_: bug 10565 | 20:35 |
| mantisbot | Bug 10565 - jreese - open - assigned | 20:35 |
| mantisbot | User input date strings are munged with new schema - http://www.mantisbt.org/bugs/view.php?id=10565 | 20:35 |
| paul_ | this is where it would be easier if we'd commited my bugobject changes branch ;/ | 20:37 |
| paul_ | $t_version->date_order = $f_date_order; | 20:37 |
| paul_ | is that field the date of a version? | 20:37 |
| nuclear_eclipse | yep | 20:37 |
| paul_ | (why was it called 'order' | 20:37 |
| nuclear_eclipse | no clue | 20:37 |
| paul_ | that makes me thinkg of ASC / DESC | 20:37 |
| nuclear_eclipse | well, it's the field used to order the versions by :P | 20:38 |
| mantisbot | New bug: Bug 10565 - jreese - open - assigned | 20:38 |
| mantisbot | New bug: User input date strings are munged with new schema - http://www.mantisbt.org/bugs/view.php?id=10565 | 20:38 |
| nuclear_eclipse | ty mantisbot | 20:38 |
| paul_ | lol | 20:38 |
| paul_ | this is where i'd like type checking on objects :P | 20:38 |
| nuclear_eclipse | paul_: tbh, I hadn't realized until two days ago that you hadn't merged bug objects into master yet... | 20:39 |
| paul_ | tbh | 20:39 |
| paul_ | I hadn't realised until 10 minutes ago | 20:39 |
| nuclear_eclipse | lol | 20:39 |
| nuclear_eclipse | I'd assumed you had done it at the same time as the date schema.. | 20:39 |
| nuclear_eclipse | esp considering you never brought it back up after that | 20:40 |
| paul_ | how can i delete local branches | 20:42 |
| nuclear_eclipse | `git branch -d <branch>` | 20:42 |
| nuclear_eclipse | time to head home; I'll try to be on again in about 30 mins | 20:55 |
| nuclear_eclipse | cheers | 20:55 |
| * paul_ yawns | 22:21 | |
| nuclear_eclipse | siebrand: why do we need to use `lang_get( 'word_separator' )` that returns ` ` that breaks a lot of things rather than just using ' '? | 22:57 |
| nuclear_eclipse | eg, on the roadmap, we use word_separator between the version and the filter link, but the browser doesn't render the space appropriately | 22:58 |
| nuclear_eclipse | ok, let me refine that, Chrome doesn't render it correctly | 22:59 |
| nuclear_eclipse | but still, why use " " instead of just " "? | 23:00 |
| siebrand | nuclear_eclipse: well, " " is so empty. At least #32 will show it's a space. But there is no issue with making it a space. | 23:04 |
| nuclear_eclipse | the other reason I ask is because of emails;   does not render correctly in our plaintext emails | 23:05 |
| nuclear_eclipse | it actually ends up as "word word" in the email | 23:05 |
| nuclear_eclipse | siebrand: is there any language where word_separator would *not* just be " "+ | 23:06 |
| nuclear_eclipse | ? | 23:06 |
| siebrand | nuclear_eclipse: well, then it should be rendered to plain text before being put in there? | 23:06 |
| siebrand | nuclear_eclipse: it can be made a 'real' space. | 23:06 |
| nuclear_eclipse | how? | 23:06 |
| siebrand | nuclear_eclipse: good question. I have no idea. Let me check how MediaWiki does that, if I can find out.. | 23:07 |
| nuclear_eclipse | lol | 23:07 |
| siebrand | hmm, i think I know how (hard coded transform) | 23:08 |
| siebrand | let me look it up | 23:08 |
| siebrand | nuclear_eclipse: yep: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/51453 | 23:09 |
| nuclear_eclipse | oh, well I could have figured that much out; I was looking more for a *real* method of converting HTML entities to plain text... | 23:11 |
| siebrand | hmm, intersting Google logo today. | 23:12 |
| nuclear_eclipse | ah, html_entity_decode() | 23:12 |
| nuclear_eclipse | looks normal to me... | 23:12 |
| vb1234 | normal to me! | 23:12 |
| vb1234 | Bing! | 23:12 |
| nuclear_eclipse | hi again Victor | 23:13 |
| vb1234 | hi nuclear_eclipse | 23:13 |
| nuclear_eclipse | siebrand: is there any language where word_separator would *not* just be " "? | 23:14 |
| siebrand | nuclear_eclipse: japanese, chinese, some other Asian languages. | 23:15 |
| siebrand | mediawiki has it for lzh, yue, zh-hant and zh-hant at the moment. | 23:15 |
| siebrand | it is an optional message, so few translators actually are aware of it. | 23:16 |
| nuclear_eclipse | ok, so would I be safe to convert any lang_*'s word_separator to " " as long as it's already " ", and leave it alone if it's something different? | 23:17 |
| siebrand | nuclear_eclipse: yes. There are only two options: a space or no space. | 23:18 |
| nuclear_eclipse | you lost me at the "two options" thing | 23:19 |
| siebrand | MediaWiki has the following separators, although using them in general is discouraged (although unavoidable at times): | 23:19 |
| siebrand | 'catseparator' => '|', # only translate this message to other languages if you have to change it | 23:19 |
| siebrand | 'semicolon-separator' => '; ', # only translate this message to other languages if you have to change it | 23:19 |
| siebrand | 'comma-separator' => ', ', # only translate this message to other languages if you have to change it | 23:19 |
| siebrand | 'colon-separator' => ': ', # only translate this message to other languages if you have to change it | 23:20 |
| siebrand | 'pipe-separator' => ' • ', # do not translate or duplicate this message to other languages | 23:20 |
| siebrand | 'word-separator' => ' ', # only translate this message to other languages if you have to change it | 23:20 |
| siebrand | and then there's the special case: | 23:21 |
| siebrand | 'and' => ' and', | 23:21 |
| siebrand | that's use in language specific 'running text lists', for example. | 23:21 |
| siebrand | "a, b, c, and d" | 23:21 |
| paul_ | nuclear_eclipse: whats the problem with 32/ | 23:21 |
| siebrand | paul_: that is was being put in mails as " " instead of " ". | 23:22 |
| nuclear_eclipse | a) it doesn't render correctly in Chrome, and b) it renders as " " in plaintext emails... :P | 23:22 |
| siebrand | oh, chrome has a bug. Interesting. | 23:22 |
| nuclear_eclipse | either chrome or webkit | 23:22 |
| nuclear_eclipse | I only have Linux, so I can't test safari atm | 23:22 |
| siebrand | nuclear_eclipse: have a sample URL, I'll check with Safari, too. | 23:22 |
| nuclear_eclipse | yeah, look at the mantisbt.org roadmap | 23:23 |
| nuclear_eclipse | on FF3, it shows "1.1.8 [ View Issues ]" | 23:23 |
| nuclear_eclipse | on Chrome, it shows "1.1.8[ View Issues ]" | 23:23 |
| paul_ | right | 23:23 |
| paul_ | 1.1.8</a><span class="bracket-link">[ | 23:24 |
| paul_ | there's no   in the source? | 23:24 |
| siebrand | using Windows, I see it wrong in both FF and Chrome. | 23:25 |
| nuclear_eclipse | lol | 23:25 |
| nuclear_eclipse | so, even more reason to move back to " " :P | 23:25 |
| paul_ | whats wrong with  ? | 23:25 |
| siebrand | >1.1.8</a><span class="bracket-link">[&nb | 23:26 |
| siebrand | expecting ">1.1.8</a>[space here]<span class="bracket-link">[&nb" right? | 23:26 |
| nuclear_eclipse | paul_: what's wrong with " "? :P | 23:27 |
| nuclear_eclipse | IMO, it's the "non-breaking" part of "non-breaking space" that I don't like about | 23:27 |
| siebrand | this is the line of code we are discussing, right? | 23:28 |
| siebrand | echo '<br />', $t_release_title, $t_scheduled_release_date, lang_get( 'word_separator' ), print_bracket_link( 'view_all_set.php?type=1&temporary=y&' . FILTER_PROPERTY_PROJECT_ID . '=' . $t_project_id . '&' . filter_encode_field_and_value( FILTER_PROPERTY_TARGET_VERSION, $t_version_name ), lang_get( 'view_bugs_link' ) ), '<br />'; | 23:28 |
| nuclear_eclipse | yep | 23:28 |
| siebrand | so where did that space go? What ate it? It's not in my HTML source. | 23:29 |
| nuclear_eclipse | that's a fantastic question; FF3 on Linux renders it correctly, but only shows " " in view source | 23:29 |
| * siebrand looks confused. | 23:30 | |
| nuclear_eclipse | I think I'd really prefer to just drop   -- it seems to be doing some really funky things | 23:30 |
| siebrand | nuclear_eclipse: and if you use a plain space it'll be better? | 23:31 |
| nuclear_eclipse | it'll at least be predictable :P | 23:32 |
| siebrand | nuclear_eclipse: you have server access, right? | 23:32 |
| siebrand | can you replace it in strings_english.txt for a second? | 23:33 |
| nuclear_eclipse | sure | 23:34 |
| nuclear_eclipse | changed | 23:36 |
| siebrand | no change in output. | 23:36 |
| siebrand | space still eaten (FF3) | 23:36 |
| nuclear_eclipse | hmm | 23:37 |
| nuclear_eclipse | try CTRL-F5 | 23:37 |
| siebrand | not changed in Chrome either. Did the hard refresh... | 23:37 |
| siebrand | checking safari on windows on another computer.... | 23:38 |
| nuclear_eclipse | hmm, not changed for me either in Chrome, although it fixed it on my local machine... | 23:39 |
| nuclear_eclipse | oh! | 23:39 |
| siebrand | also no space on Safari | 23:39 |
| nuclear_eclipse | it's APC | 23:39 |
| siebrand | apc is eating the space, or still using &32? | 23:41 |
| nuclear_eclipse | APC is the opcode cache | 23:41 |
| siebrand | yep, I knwo. | 23:41 |
| siebrand | that should invalidate on file change, shouldn't it? | 23:42 |
| nuclear_eclipse | hmm, tried clearing its cache, and that didn't fix it | 23:42 |
| siebrand | OK, so whatever it is, there's no space where we expect it. That sounds like a challenge :) | 23:42 |
| siebrand | try putting a in word_separator (just for testing! :P) | 23:43 |
| siebrand | that must really appear.. | 23:43 |
| nuclear_eclipse | the *real* oddity is that it looks right in FF3, both before and after the change, and wrong in chrome, both before and after, but *right* in chrome after I make the change on my local test install.... | 23:43 |
| siebrand | I don't know how to create roadmap/changelog entries, so I cannot check on my local install. | 23:44 |
| nuclear_eclipse | add versions to a project, and then target those versions from issues | 23:45 |
| nuclear_eclipse | I've reverted live, just fyi | 23:47 |
| siebrand | This is my local output: | 23:49 |
| siebrand | project2 - 1.1 (Scheduled For Release 2009-06-06) [ View Issues ] | 23:49 |
| siebrand | Let's get rid of that date... | 23:50 |
| siebrand | ehr: project2 - 1.1 (Scheduled For Release 1970-01-01) [ View Issues ] | 23:50 |
| * siebrand grins. | 23:50 | |
| siebrand | Looks like leaving the scheduled release date empty isn't an option. | 23:51 |
| siebrand | date_order = 0 in db (Mysql) | 23:52 |
| siebrand | Is that expected behaviour? | 23:52 |
| nuclear_eclipse | that's also currntly a bug in how dates are (not) working atm | 23:53 |
| siebrand | anyway, it looks like "word_separator" works for me in local version. | 23:53 |
| nuclear_eclipse | same... | 23:54 |
| siebrand | looks OK in Chrome, too. | 23:54 |
| nuclear_eclipse | this is really weird, because it wasn't working earlier... | 23:54 |
| siebrand | and our own tracker is git master head, too? | 23:54 |
| siebrand | well, my preliminary conclusion is that it's not as broken compared to " " as you made it sound :) | 23:56 |
| nuclear_eclipse | ah ha! | 23:56 |
| * siebrand listens carefully. | 23:56 | |
| nuclear_eclipse | siebrand: in your local, do `git checkout live` and test | 23:56 |
| nuclear_eclipse | you may need to fetch first if you haven't recently | 23:57 |
| siebrand | error: pathspec 'live' did not match any file(s) known to git | 23:57 |
| nuclear_eclipse | you may need to fetch first if you haven't recently | 23:57 |
| siebrand | I need some other git magic first? | 23:57 |
| nuclear_eclipse | `git fetch` | 23:57 |
| nuclear_eclipse | it's a new public branch representing where the live site is | 23:57 |
| siebrand | still won't work. | 23:58 |
| siebrand | Anyway, sounds like you can reproduce it. | 23:58 |
| siebrand | So this was fixed somewhere recently? | 23:58 |
| nuclear_eclipse | I don't know | 23:58 |
| nuclear_eclipse | git-bisect to the resuce! | 23:58 |
| nuclear_eclipse | rescue even | 23:58 |
Generated by irclog2html.py