| ../irclogs/#mantishelp.2009-05-13.log | ||
| --- scribe started --- | 00:00 | |
| rtyler | An internal server error occurred. Please try again later. | 03:16 |
|---|---|---|
| rtyler | I can't see any errors in the apache logs | 03:16 |
| rtyler | and I also turned on php_value display_errors 1 in my .htaccess | 03:16 |
| rtyler | is Mantis catching exceptions I don't know about? | 03:16 |
| nuclear_eclipse | Mantis has its own error handler; see core/error_api.php | 03:16 |
| nuclear_eclipse | fatal PHP errors will "break" the custom error handler; you can disable it at the top of the top | 03:17 |
| rtyler | set how? the documentation in the file doesn't say what you can disable | 03:23 |
| nuclear_eclipse | just comment out the call to set_error_handler | 03:24 |
| rtyler | still get the same respons as above | 03:25 |
| rtyler | nothing in the logs :/ | 03:25 |
| nuclear_eclipse | do you have xdebug or zend debugger installed? | 03:25 |
| rtyler | nope | 03:26 |
| nuclear_eclipse | then I don't have any clue why it's doing that :P | 03:27 |
| nuclear_eclipse | using fgci, or mod_php? | 03:27 |
| nuclear_eclipse | and are you using a php optimizer? | 03:28 |
| rtyler | mod_php, and no I don't think so | 03:35 |
| rtyler | (shared hosting) | 03:35 |
| nuclear_eclipse | hmm | 03:36 |
| nuclear_eclipse | I'd open a support ticket with your host, maybe they can help you debug the error | 03:37 |
| rtyler | it's run by a friend of mine :P | 03:39 |
| nuclear_eclipse | so open a support ticket with your friend :P | 03:40 |
| giallu | paulr, had fun with the centos friends? ;) | 08:23 |
| [KK]Kirill | giallu: hi | 08:45 |
| _insect_ | hiho @all | 10:46 |
| _insect_ | I can't figure out the right config of email notification. | 10:49 |
| _insect_ | I am struggling with the email notification, if the issue is assigne to somenone | 10:50 |
| _insect_ | I receive email for the assigned user only on new issues | 10:51 |
| _insect_ | and not if the user is assigned afterwards or change | 10:51 |
| _insect_ | using v1.1.7 | 10:52 |
| _insect_ | with mail() | 10:52 |
| mantisbot | New bug: Bug 10485 - aysha - open - new | 11:07 |
| mantisbot | New bug: i can see the given error when i open my matis url ,it occured on login, even once i get logged in - http://www.mantisbt.org/bugs/view.php?id=10485 | 11:07 |
| mantisbot | New bug: Bug 10486 - melisik - open - new | 12:33 |
| mantisbot | New bug: Display of assigned to user name in view all bugs page - http://www.mantisbt.org/bugs/view.php?id=10486 | 12:33 |
| leetcode_52855 | hi, i try to integrate mantis with svn from http://leetcode.net/blog/2009/01/integrating-git-svn-with-mantisbt/ | 12:49 |
| leetcode_52855 | i have problem with installing plugin | 12:49 |
| leetcode_52855 | I can't see Repositories link in mantis, is there some help how to install plugins? | 12:51 |
| nuclear_eclipse | leetcode_52855: first, make sure you have the latest development release of 1.2.x, then go to Manage -> Manage Plugins and click [Install] next to the plugins you want to enable | 12:52 |
| nuclear_eclipse | I gotta go to a meeting; I'll be back in ~1 hour | 12:53 |
| leetcode_52855 | can i use mantis 1.7? | 12:54 |
| nuclear_eclipse | no | 12:54 |
| nuclear_eclipse | I assume you mean 1.1.7? | 12:54 |
| leetcode_52855 | yes | 12:54 |
| leetcode_52855 | there is problem probably | 12:55 |
| nuclear_eclipse | you need a development release of 1.2.0 | 12:55 |
| leetcode_52855 | allright i will try and then let you know. | 12:55 |
| leetcode_52855 | thank you. | 12:55 |
| nuclear_eclipse | you're welcome | 12:55 |
| [KK]Kirill | nuclear_eclipse: hi | 12:56 |
| [KK]Kirill | John, I need you | 12:56 |
| nuclear_eclipse | [KK]Kirill: wait an hour, gotta go to a meeting | 12:56 |
| [KK]Kirill | go to privat? | 12:56 |
| [KK]Kirill | ok | 12:56 |
| leetcode_52855 | with this version it goes | 13:17 |
| leetcode_52855 | just 2 errors: APPLICATION WARNING #2400: Event "EVENT_ACCOUNT_PREF_UPDATE_FORM" has not yet been declared. APPLICATION WARNING #2400: Event "EVENT_ACCOUNT_PREF_UPDATE" has not yet been declared. | 13:17 |
| dhx_m | lol @ "can i use mantis 1.7?"... "no" | 13:30 |
| leetcode_52855 | can you answer to my question or you can just laugh? | 13:35 |
| dhx_m | use http://git.mantisbt.org/?p=mantisbt.git;a=snapshot;h=e21a1dfa72d0b642915c43f436816c46960e31dd;sf=tgz | 13:51 |
| dhx_m | http://git.mantisforge.org/w/source-integration.git?a=snapshot;h=2432968ad1d6c9ae14539492a95ef60e1dcbb5fa;sf=tgz | 13:52 |
| dhx_m | and | 13:52 |
| dhx_m | http://git.mantisforge.org/w/meta.git?a=snapshot;h=0b9760e77133d7daf83bda485d6f28b7ec0f05e0;sf=tgz | 13:52 |
| dhx_m | all of those are the latest development snapshots of mantis, sourceintegration and meta | 13:52 |
| dhx_m | unpack the last two plugins to the plugins folder within mantis | 13:53 |
| dhx_m | then login to mantis as an admin and go to 'manage -> manage plugins' | 13:53 |
| dhx_m | and install meta as well as the source integration plugins you want to use | 13:54 |
| leetcode_52855 | allright everything works fine now without errors. thank you dhx_m | 14:02 |
| dhx_m | np, must have just been a case of using the wrong versions together :) | 14:03 |
| leetcode_52855 | i hav good source-integration and meta but maybe older mantis snapshot | 14:03 |
| leetcode_52855 | when developer commit resolved bug he must write to the description fixed issue: #000001. mantis then automatically give that bug as resolved? | 14:07 |
| dhx_m | no need for the zeros | 14:09 |
| dhx_m | and you can change the trigger via a regex | 14:09 |
| dhx_m | you need to configure the plugin to your liking | 14:09 |
| dhx_m | it won't resolve by default AFAIK | 14:09 |
| dhx_m | linking and resolving are different things too | 14:09 |
| leetcode_52855 | what is linking? | 14:10 |
| dhx_m | where you assign a commit to one or more bugs | 14:13 |
| dhx_m | when you open the bug, it'll show all the commits linked to it | 14:13 |
| leetcode_52855 | in my company we assign some bug to developer, developer can give to bug comment, or he can fix bug (commit and then sign as resolved) when bug isn't resolved tester can reopen that bug. is it right, no? | 14:13 |
| dhx_m | depends on what you choose to do with your software development | 14:19 |
| dhx_m | mantis doesn't force that on you | 14:19 |
| dhx_m | but it can certainly do what you described | 14:19 |
| leetcode_52855 | allright, sorry but I have to go. thank you once again. | 14:20 |
| nuclear_eclipse | ugh, that meeting drug on for forever it seems... | 14:24 |
| dhx_m | fun times :) | 14:27 |
| nuclear_eclipse | http://xkcd.com/583/ | 14:28 |
| dhx_m | haha yeah I saw that one :0 | 14:28 |
| dhx_m | :) | 14:28 |
| slestak | hey guys. I am looking for a good place in my mantis ticket to place research notes that by default (or by config sertting) does not create a notification | 15:03 |
| nuclear_eclipse | slestak: either use wiki integration, or create a plugin that does that sort of thing :P | 15:04 |
| slestak | I have wiki integration, not a problem. | 15:04 |
| slestak | just wondering if it was possible of advisable to make Additional Information in the header a non-notify field. | 15:05 |
| slestak | the wiki s good though, then my research is indexed | 15:05 |
| slestak | just a note, i was going to update the mantis wiki, the mediawiki integration also works for dekiwiki (since it is a fork) | 15:06 |
| nuclear_eclipse | slestak: like I said, you could make a plugin that stored a separate field without notifying, but it's not possible to not notify for specific core fields | 15:10 |
| laotseu | gi | 15:40 |
| laotseu | hi | 15:41 |
| nuclear_eclipse | howdy | 15:41 |
| laotseu | i've a small notification problem : i've got 4 status "in developpement" (assigned, on hold, awaiting client, in progress - from 10->30) and 5 statuses "done" (developped, approved, on prod, cancelled, closed - from 40->90) if i change the status from everything "in developpement" to "developped" it sends me a mail, which is great, but if i choose for example "on prod" directly no mail is sent | 15:45 |
| nuclear_eclipse | what version of mantis are you using? | 15:46 |
| laotseu | 1.1.6 | 15:46 |
| nuclear_eclipse | hmm, standard canned answer: upgrade to 1.1.7 and re-test :P | 15:48 |
| laotseu | :) | 15:49 |
| nuclear_eclipse | otherwise, I'm not sure off-hand; could you somehow attempt to debug what it's doing that makes it decide not to notify? | 15:50 |
| laotseu | nuclear_eclipse: i don't know ... the resolution is updated correcty (set as fixed) | 16:07 |
| laotseu | in fact, it'll be perfect if each time the resolution status is changed an email were sent | 16:08 |
| nuclear_eclipse | howdy giallu | 17:38 |
| giallu | hi John | 17:41 |
| paulr | lo | 17:47 |
| paulr | giallu: when it next breaks | 17:47 |
| paulr | << :) | 17:47 |
| paulr | giallu: you saw I asked? | 17:47 |
| paulr | nuclear_eclipse: lo | 17:47 |
| nuclear_eclipse | hi paulr | 17:48 |
| paulr | seen daryn? | 17:48 |
| nuclear_eclipse | nope, only dhx_m | 17:48 |
| paulr | you dont use date custom fields do you? | 17:48 |
| nuclear_eclipse | I've used them for testing the fixes I committed on Monday, but other than that, no | 17:48 |
| paulr | still got that db? | 17:49 |
| nuclear_eclipse | I did notice that date fields in 1.1.x looked really nice, with dropdowns for each portion of the date, while 1.2.x just gives you a generic text field... | 17:49 |
| paulr | huh | 17:49 |
| paulr | 1.2 gives you drop downs... | 17:49 |
| nuclear_eclipse | maybe it's vice versa :P | 17:50 |
| paulr | anyway | 17:50 |
| paulr | if you still have db | 17:50 |
| paulr | can you do a select * from custom_field_string_table or whatever it is | 17:50 |
| paulr | and show me what db stores | 17:50 |
| nuclear_eclipse | gimme a sec to load some data into the fields | 17:50 |
| nuclear_eclipse | for the two bugs I set a date for: 1176350400 and 1373342400 | 17:52 |
| nuclear_eclipse | that's in 1.2.x, you want me to check on 1.1.x? | 17:53 |
| paulr | yes pls | 17:53 |
| paulr | as erm | 17:53 |
| paulr | daryn said we stored date as a string | 17:53 |
| nuclear_eclipse | hmm, 1.1.x is a nice set of dropdowns too | 17:54 |
| nuclear_eclipse | maybe I was confusing some custom fields | 17:54 |
| nuclear_eclipse | 1241496000 | 17:55 |
| nuclear_eclipse | so both 1.2.x and 1.1.x seem to store custom date fields as integers | 17:55 |
| * paulr wonders what daryn is talking about | 18:00 | |
| paulr | :P | 18:00 |
| giallu | paulr, yeah, had a look at the backlog | 19:34 |
| giallu | in case you're asked again | 19:34 |
| giallu | we're running a stock centos 5.3, all official packages apart for kernel. | 19:35 |
| paulr | giallu: i've wget'd debug symbols, installed gdb/strace via yum | 19:49 |
| paulr | and now waiting | 19:49 |
| paulr | for it to happen again :) | 19:49 |
| paulr | I still think the model is somewhat flawed in that 5.0 is now *old* | 19:50 |
| paulr | although to be fair | 19:51 |
| paulr | mysql 5.4 looks like it will be an interesting release | 19:51 |
| giallu | paulr, I'm not going to show you how this is exactly the thing a lot companies pays for RHEL | 19:51 |
| paulr | as from what I can tell | 19:51 |
| paulr | mysql 5.4 == 5.1+googlepatches | 19:51 |
| paulr | http://dev.mysql.com/tech-resources/articles/mysql-54.html | 19:52 |
| paulr | the graphs look quite impressive at least | 19:52 |
| paulr | giallu: dont get me wrong - I make a choice at work whether to run win2k3 or win2k8 on servers | 19:53 |
| paulr | and when to upgrade etc | 19:54 |
| paulr | the only difference is that with windows, you basically get a release of the whole suite every 2 years | 19:54 |
| paulr | or 3 years or whatever | 19:54 |
| paulr | with linux apps, you seem to get releases for each individual app every few months | 19:54 |
| giallu | paulr, again. that's why you pay RH, to insulate yourself from that. | 19:55 |
| paulr | nod | 19:55 |
| paulr | the downside/problem of this model ofc is | 19:55 |
| paulr | as different OS's ship different versions | 19:56 |
| paulr | i.e. ubuntu ship 5.0.77 or whatever, redhat 5.0.45 | 19:56 |
| paulr | it gives the impression that redhat dont maintain their version | 19:56 |
| giallu | ehehe | 19:57 |
| giallu | the keyword here is "backport" | 19:57 |
| giallu | if one can't see the value in backporting, he better stick with ubuntu | 19:57 |
| paulr | backport strikes me like the equivalent of a MS hotfix | 19:59 |
| paulr | i'd rather run a servicepack then a hotfix ;) | 20:00 |
| paulr | if I get an email that says 'security bug in <5.0.67' of mysql for example | 20:00 |
| paulr | i'd do mysql --version on my boxes | 20:00 |
| paulr | to see which ones would be affected | 20:00 |
| paulr | in the case of centos, alarm bills would ring | 20:01 |
| paulr | -> i'd need to confirm with centos that 5.0.45 included the 5.0.67 changes | 20:01 |
| paulr | that does't strike me as value but more work :) | 20:02 |
| giallu | paulr, my last reply on the topic: there are 2 differences with hotfixes: 1. I (and you) don't know what't in a hotfix, it's closed source 2. RHEL _always_ includes the security related fixes plus a everything that fixes bugs without introducing API/ABI break. | 21:09 |
| * paulr nod | 21:10 | |
| [KK]Kirill | giallu, paulr: hi | 21:14 |
| paulr | lo kirill | 21:19 |
Generated by irclog2html.py