Thursday, 2011-04-07

*** Joins: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net)01:02
*** Quits: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net) (Ping timeout: 258 seconds)01:38
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino)02:25
*** Joins: giallu (~giallu@fedora/giallu)02:32
*** Joins: Ragnor_ (~Ragnor@dslb-178-009-050-181.pools.arcor-ip.net)02:45
*** Quits: Ragnor (~Ragnor@dslb-178-009-050-181.pools.arcor-ip.net) (Ping timeout: 252 seconds)02:47
*** Joins: Rixie (~Rixie@188.177.20.182)02:57
*** Joins: kirillka (~Miranda@195.242.142.17)03:02
*** Joins: soustruh (~Miranda@firewall.czech-tv.cz)03:12
*** Quits: siebrand (~chatzilla@535392CA.cm-6-4c.dynamic.ziggo.nl) (Quit: ChatZilla 0.9.86.1 [Firefox 4.0/20110318052756])04:20
*** Joins: rolfkleef (~rolfkleef@92.254.21.180)04:41
*** Joins: siebrand (~chatzilla@188.200.34.66)06:18
dhx1jreese: there was a reason for sending the original and updated bug (and then returning them both)07:57
dhx1it allows a plugin to determine what changes will be made if the plugin does nothing07:57
dhx1and it allows a plugin to overwrite those changes if needed (including the ability for the plugin to fake the original state of a bug so the notifications can be silenced)07:57
jreese... I think that's a very hacky thing to do08:03
jreeseif it wants to silence notifications, just do config_set_global()08:04
dhx1the faking of the original state?08:04
jreesethat way it's just a temporary override08:04
jreeseas for faking original state, I think that's bad too08:04
jreeseespecially since plugins have no guarantee of what order they'll run in08:04
dhx1actually I don't see where we return the original state08:05
dhx1oh nm I was looking at 1.2.x08:05
dhx1event_signal( 'EVENT_UPDATE_BUG', array( $t_existing_bug, $t_updated_bug ) );08:07
dhx1we're not doing anything with return values08:07
jreese? yes you are08:08
jreese$t_event_updated_bug = event_signal( 'EVENT_UPDATE_BUG_DATA', array( $t_existing_bug, $t_updated_bu>08:08
jreese$t_existing_bug = $t_event_updated_bug[0];08:08
jreese$t_updated_bug = $t_event_updated_bug[1];08:08
dhx1oh yeah08:18
dhx1that allows you to cancel user field change requests08:18
dhx1so a user may ask to change the priority to 'high' but your plugin may perform other checks that don't allow that to happen08:24
dhx1and instead of a fatal error it has the option of automatically doing things08:24
dhx1I'm not sure I like that idea much08:25
jreesewell, ok, but they plugin shouldn't need to return the original state of the bug to accomplish that08:25
jreeseI mean, I already have custom plugins doing that in 1.2 just fine08:25
dhx1$t_text_field_update_required = ( $t_existing_bug->description !== $t_updated_bug->description ) ||08:25
dhx1required for things like that08:25
dhx1admittedly there is quite a lot of code to fix there now I look at it again08:26
jreesestill, it's one thing to pass the existing bug as a third parameter to event_signal, but to make plugins able to modify and return it imo is silly08:26
jreeseesp since with the old behavior, where plugin sjust received the new state and a bug id, the plugin could query the original bug state just by calling bug_get()08:27
dhx1the difference is that the bug hasn't been committed by the time EVENT_UPDATE_BUG_DATA is called08:28
dhx1and we'd be moving towards passing the bug object by reference as we move to OO08:28
dhx1so it's not an issue of performance08:29
dhx1I do agree that returning the existing/reference bug is silly08:30
dhx1I can't remember why I added both return types08:30
dhx1I seem to recall it being in response to that method being used elsewhere08:30
jreeseok, so then if you change it to event_signal( "...", $t_updated_bug, $t_existing_bug ) I would be perfectly happy with it08:30
dhx1and return the updated bug... :)08:31
jreesethat way plugins only have to return the updated bug08:31
dhx1yeah08:31
jreeseeither way, the whole reason this was all brought up is: bug_assign.php doesn't match bug_update.php in how it uses the events, so it needs to be brought in line08:31
*** Joins: ericbarnes (~ericbarne@rrcs-98-101-76-249.midsouth.biz.rr.com)08:32
dhx1yep I see, I'll fix it now08:32
dhx1does it have an issue #?08:32
jreeseummm08:32
jreesesec08:32
jreeselet's go with no08:33
dhx1ok no problem08:33
dhx1bug_assign.php is likely deprecated by bug_update.php too08:35
dhx1the idea was to try and standardise the code we're using to update bugs08:35
dhx1because it was very different in parts before08:35
jreeseok, then if bug_assign.php is never used, it needs to be dropped as well08:35
dhx1almost done08:46
dhx1does the assign to dropdown need the "operation successful" redirect page?09:00
dhx1I suppose it makes it clear to the user that their action was saved OK09:01
*** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net)09:02
dhx1jreese: it seems EVENT_UPDATE_BUG_DATA is returning an array with 2 objects anyway09:19
jreese?09:20
dhx1$t_event_updated_bug = event_signal( 'EVENT_UPDATE_BUG_DATA', array( $t_existing_bug, $t_updated_bug ) );09:20
dhx1var_dump($t_event_updated_bug);09:20
dhx1die(1);09:20
dhx1is there some place where the return values of events are specified?09:20
jreesethat's because of the way you're triggering the event09:20
dhx1ah figured09:21
dhx1so removing the array :)09:21
dhx1ok fixed09:22
darynmornin09:23
jreesehowdy09:23
dhx1daryn: howdy09:23
dhx1jreese: I take it event_signal() can accept variable numbers of arguments and the last one is returned in the default "do nothing" plugin event handler09:24
jreeseno09:25
jreesewell, yes and no09:25
jreeseevent_signal( event, parameters, static_parameters )09:25
jreesethe event naem is obvious09:25
jreesethe parameters are passed to the plugin hooks, and in the case of chained events, represents the parameters that must be returned by the plugin for use by the next plugin in the chain09:26
dhx1in that case it should be:09:27
jreesestatic_parameters is only used for chained events, and represents parameters that should be passed to plugin hooks, but won't change from hook to hook, and don't need to be returned by the plugin09:27
dhx1$t_event_updated_bug = event_signal( 'EVENT_UPDATE_BUG_DATA', $t_updated_bug, $t_existing_bug );09:27
jreeseright09:27
dhx1?09:27
dhx1aha09:27
jreesethen the plugin's function would do something like:09:28
jreesefunction foo($event_name, $updated_bug, $existing_bug) { ... return $updated_bug; }09:28
dhx1yep09:28
jreesealso dhx1, have you seen the dev list emails regardin some upgrade/install issue in 1.2.5?09:29
jreeseiirc you were the one who committed the patch that's supposedly breaking things09:29
jreesebut I can't reproduce the issue09:29
dhx1jreese: yeah probably ADOdb handling the _connect() call differently in MySQL/PostgreSQL backends09:29
dhx1I'll check in a moment09:29
jreeseok09:29
dhx1can't wait to scrap ADOdb09:39
CIA-35Mantisbt: d * r73493e22ed81 / (2 files in 2 dirs): Remove unnecessary return value from EVENT_UPDATE_BUG_DATA09:47
CIA-35Mantisbt: d * r79ffdb847a9e / (45 files in 2 dirs): Remove bug_assign.php (use bug_update.php instead)09:47
CIA-35Mantisbt: d * r57db68ce737e /bug_assign.php: Delete bug_assign.php09:49
jreesedhx1: a) you didn't update the developer documentation, and b) I think it would make sense to have the standard UPDATE_BUG event use the same parameter order09:56
dhx1I did :)09:56
dhx1agreed09:56
*** Quits: kirillka (~Miranda@195.242.142.17) (Quit: kirillka)10:01
*** Joins: tmckeown (~Adium@64.191.211.43)10:03
*** Joins: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net)10:09
CIA-35Mantisbt: d * r7b456a546c24 /admin/install.php: Tidy list of database types in install script10:29
CIA-35Mantisbt: d * r41fddb772b94 /admin/install.php: Remove MySQL database version check from install script10:29
CIA-35Mantisbt: d * ra8864b082b1a /admin/install.php: Fix #12675: Do not attempt connection to non-existent database10:35
CIA-35Mantisbt: d master-1.2.x * rc749c0cdd763 /admin/install.php: Tidy list of database types in install script10:36
CIA-35Mantisbt: d master-1.2.x * ra4774043a804 /admin/install.php: Remove MySQL database version check from install script10:36
CIA-35Mantisbt: d master-1.2.x * r1e1c073be272 /admin/install.php: Fix #12675: Do not attempt connection to non-existent database10:36
jreesedhx1: should that fix the issue that roland brought up?10:43
*** Parts: rolfkleef (~rolfkleef@92.254.21.180)10:46
*** Dreksypoo is now known as JonMarkGo10:53
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 252 seconds)10:55
*** Parts: Rixie (~Rixie@188.177.20.182)10:56
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...)10:59
dhx1jreese: yeah, but the original bug still remains (see my ML post, I'll try to fix it shortly)11:04
*** Quits: dhx1 (~anonymous@60-242-108-164.static.tpgi.com.au) (Ping timeout: 240 seconds)11:22
*** Joins: dhx1 (~anonymous@60-242-108-164.static.tpgi.com.au)11:29
*** Quits: soustruh (~Miranda@firewall.czech-tv.cz) (Quit: visit http://wormscesky.cz)11:57
*** Joins: Github (~Github@sh1-ext.rs.github.com)12:30
Githubmantisbt: master-1.2.x David Hicks * c749c0c (1 files in 1 dirs): Tidy list of database types in install script12:30
Githubmantisbt: master-1.2.x David Hicks * a477404 (1 files in 1 dirs): Remove MySQL database version check from install script ...12:30
Githubmantisbt: master-1.2.x David Hicks * 1e1c073 (1 files in 1 dirs): Fix #12675: Do not attempt connection to non-existent database ...12:30
Githubmantisbt: master-1.2.x commits 0772787...1e1c073 - http://bit.ly/g4of2i12:30
*** Parts: Github (~Github@sh1-ext.rs.github.com)12:30
*** Quits: JonMarkGo (~Jon@ool-18bfe16f.dyn.optonline.net) (Ping timeout: 246 seconds)12:34
*** Quits: deepy (~deepy@c83-248-154-79.bredband.comhem.se) (Changing host)12:40
*** Joins: deepy (~deepy@wrongplanet/deepa)12:40
*** Quits: siebrand (~chatzilla@188.200.34.66) (Ping timeout: 246 seconds)13:14
*** Joins: siebrand (~chatzilla@188.200.34.66)13:24
*** Quits: siebrand (~chatzilla@188.200.34.66) (Ping timeout: 260 seconds)14:37
*** Joins: giallu (~giallu@fedora/giallu)15:51
*** Joins: siebrand (~chatzilla@188.200.34.66)16:00
*** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat)16:03
*** Quits: siebrand (~chatzilla@188.200.34.66) (Ping timeout: 240 seconds)16:05
*** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net)16:08
*** Quits: tmckeown (~Adium@64.191.211.43) (Ping timeout: 258 seconds)16:11
*** Joins: tmckeown (~Adium@64.191.211.43)16:14
*** Quits: tmckeown (~Adium@64.191.211.43) (Read error: Connection reset by peer)16:32
*** Joins: tmckeown (~Adium@64.191.211.43)16:32
gialludaryn, there?16:56
daryngiallu, lo16:56
gialluhi :)16:56
*** Quits: tmckeown (~Adium@64.191.211.43) (Ping timeout: 258 seconds)16:57
gialludo you know if db_result should be killed or not?16:57
gialluall the db_prepare_* are amrked as deprecated16:57
gialluso I wondered16:57
darynhm...not sure off the top of my head.  let me see what paulr was doing16:58
daryngiallu, he's using pdo and modified db_result to call p_result->fetchColumn16:59
gialluok. same here for now16:59
darynwould be nice to agree on an interface for db...17:00
darynso either your work or paulr's wouldn't change the rest of the app17:00
daryni guess database_api is the...adapter?17:00
gialluwell. for now I'm keeping the current API17:00
gialluso no changes are needed17:01
gialluhowever, it seems db_num_rows is not really portable across backends17:01
darynbut it isn't a drop in change for both.17:01
darynright, he came across the same issue17:01
gialluso I'm removing that one17:01
gialluI should feel guilty for doing basically the same work. too bad I stopped to care some time ago :)17:03
*** Joins: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net)17:03
darynheh17:03
gialluhowever, filter_api is killing me. a lot of db_prepare_* calls17:04
darynyeah...i pretty much gave up on filter until the foundations are better.  it just needs to be rewritten from scratch17:05
giallupossibly, but right now I need them to be functional. Don't want to keep manzen untestable17:07
darynright17:08
daryngiallu, any thoughts regarding configuration?  I've run across an issue where config_api is dependent on db and db is dependent on config.  needs to be separated somehow17:08
gialluwell. I think we need to have a configuration file with maybe 5 settings, all the rest in the database17:11
giallujust try to install wordpress to see what I mean17:12
darynyeah...there are 30 'global_settings' some of which are regexes so would be more than 5...17:13
gialluhey, that's far more than I used :) but you know, I tend to dramatize...17:16
gialluhow many do we use?17:16
* giallu checking17:16
darynis there any reason they shouldn' t all be in the database?  on install you have to specify db settings anyway17:16
darynand configurations have access levels17:17
giallugrep '^$g_' legacy/config_defaults_inc.php |wc -l17:17
giallu42617:17
darynso would prevent unauthorized users from reading them17:17
darynyeah...17:17
gialluyeah. right now I can't think about any reason for not putting everything in the DB17:18
darynjreese?17:19
daryndoh...17:20
darynthat doesn't fix my dilemma17:20
jreeseiirc, the rationale for keeping certain values out of the database was to prevent "snooping" on critical values  from custom functions and/or plugins, but imo I couldn't really care17:20
jreesethe biggest reason I have for keeping configs in a file is because a) it takes a lot of effort to create a usable UI to edit all those options, and b) I like being able to grep the file for config options17:21
darynright17:22
daryneither way db configs still require a file as config api depends on db access.  i don't know what i was thinking17:23
jreesedaryn: I think the biggest thing to note is that db api only relies on "config_get_global()", which doesn't rely on db api17:24
darynright17:24
jreesethe other option would be to make config_api only use the database, and extend db_api to be able to read the 4/5 values it needs from the config file17:25
jreesebut the *real* problem with that sort of change is how to handle users upgrading from older versions17:26
daryni think that one is easy...17:26
daryninstall script require config_inc.php.  adds db records for configs17:26
darynthat aren't db configs.  db configs stay in config_inc.php17:27
jreesehave fun implementing that :P17:27
jreeseone more problem17:27
daryni'll be done "shortly" :P17:27
jreesesome of what the configs do atm is more than just static values17:28
jreeseeg, $g_path and friends17:28
darynmost of the path stuff is moved out of config17:28
jreesedaryn: just be careful, there are still cases where users need to be able to override the values that are guess/inferred at runtime17:29
jreeseeg, some installs are accessed from multiple host/domain names, so they need to be able to define a canonical url for things like generating emails, while still using relative paths in hyperlinks17:30
daryni think i'm ok for that one17:31
darynonly problem would be if they need to set a different base url and don't have access to the webserver config.17:31
*** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat)17:40
*** Joins: siebrand (~chatzilla@535392CA.cm-6-4c.dynamic.ziggo.nl)17:44
*** Quits: ericbarnes (~ericbarne@rrcs-98-101-76-249.midsouth.biz.rr.com) (Remote host closed the connection)17:49
CIA-35Mantisbt: giallu * r09aa4a0d919a /core/logging_api.php: Fix XHTML markup17:55
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 258 seconds)18:05
*** Joins: Github (~Github@sh1-ext.rs.github.com)18:30
Githubmantisbt: master Gianluca Sforna * 09aa4a0 (1 files in 1 dirs): Fix XHTML markup - http://bit.ly/e3n2to18:30
*** Parts: Github (~Github@sh1-ext.rs.github.com)18:30
*** Quits: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net) (Ping timeout: 260 seconds)18:34
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)20:00
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)20:00
*** Joins: Dreksypoo (~Jon@ool-18bfe16f.dyn.optonline.net)20:26
*** Dreksypoo is now known as JonMarkGo20:50
*** Joins: tmckeown (~Adium@pool-173-73-138-227.washdc.fios.verizon.net)21:05
*** Parts: tmckeown (~Adium@pool-173-73-138-227.washdc.fios.verizon.net)21:14
*** Joins: tmckeown (~Adium@pool-173-73-138-227.washdc.fios.verizon.net)21:18
*** Quits: tmckeown (~Adium@pool-173-73-138-227.washdc.fios.verizon.net) (Quit: Leaving.)21:23
*** Joins: daryn (~daryn@h191.67.29.71.dynamic.ip.windstream.net)21:58
*** Joins: hardyNH (~hardyNH@c-24-128-17-162.hsd1.nh.comcast.net)22:02
*** Quits: daryn (~daryn@h191.67.29.71.dynamic.ip.windstream.net) (Quit: Ex-Chat)22:06
*** Joins: daryn (~daryn@h191.67.29.71.dynamic.ip.windstream.net)22:07
*** Quits: daryn (~daryn@h191.67.29.71.dynamic.ip.windstream.net) (Quit: Ex-Chat)22:44
*** Quits: hardyNH (~hardyNH@c-24-128-17-162.hsd1.nh.comcast.net) (Quit: hardyNH)23:47

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!