| ../irclogs/#mantishelp.2009-05-20.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10504 - elvinhau - open - new | 02:38 |
|---|---|---|
| mantisbot | New bug: New feature suggestion: Upload file in 'Add Note' ? - http://www.mantisbt.org/bugs/view.php?id=10504 | 02:38 |
| CIA-31 | Mantisbt: vboctor * r7106957595c3 /admin/install_functions.php: Fixed undefined variable warning in setup. | 06:00 |
| ruslan | hi all | 06:27 |
| ruslan | any hint how to setup integration of mantis to SVN like I see this on this bugtracker | 06:27 |
| ruslan | I use 1.2a already | 06:27 |
| CIA-31 | Mantisbt: vboctor * rac71e94db3a0 / (login.php login_page.php): Fixes #10505: On Login failure, keep user name populated and place the focus in the password field. | 06:32 |
| mantisbot | New bug: Bug 10505 - vboctor - fixed - resolved | 06:34 |
| mantisbot | New bug: On Login failure, keep user name populated and place the focus in the password field - http://www.mantisbt.org/bugs/view.php?id=10505 | 06:34 |
| mantisbot | New bug: Bug 10506 - vboctor - open - assigned | 07:19 |
| mantisbot | New bug: Provide the ability to disable the News feature - http://www.mantisbt.org/bugs/view.php?id=10506 | 07:19 |
| CIA-31 | Mantisbt: vboctor * rfe66a365f8b0 / (12 files in 3 dirs): Fixes #10506: Provide the ability to disable the News feature. | 07:37 |
| moto-moi | nice | 07:39 |
| moto-moi | that feature is of no use at all at our site :) | 07:39 |
| dhx_m | thanks! :) | 07:43 |
| dhx_m | also useful for me | 07:43 |
| CIA-31 | Mantisbt: vboctor * ra5e402bf6c35 /core/ (php_api.php relationship_api.php): Fixes #9086: email_queue_add fails with long UTF-8 relationship text. | 08:10 |
| paulr | giallu: can't until tonight :( | 09:04 |
| giallu | paulr, no hurry | 09:04 |
| * paulr wishes victor used irc ;/ | 09:05 | |
| giallu | ML is better | 09:05 |
| paulr | you'd get bored of 5 mails a day :P | 09:06 |
| paulr | i'm specifically thinking about the lines of: | 09:07 |
| * paulr sighs | 09:07 | |
| giallu | I'm subcribed to MLs with hundreds email/day | 09:07 |
| paulr | windows clipboard is broken | 09:07 |
| paulr | 2 days ago, I passed wiki_enabled() function in here and saying I saw want to get rid of functions like that e.g. wiki_enabled { return config_get_global('wiki' == ON) | 09:07 |
| kenguest | s/clipboard// | 09:07 |
| paulr | john said +1 | 09:08 |
| paulr | and dhx just lol'd | 09:08 |
| paulr | 48 hours later we have | 09:08 |
| paulr | news_enabled ( return news == on) | 09:08 |
| giallu | paulr, see peaple have a life. they can't be here all the time | 09:09 |
| giallu | if you have alternative, discuss them on the ML | 09:10 |
| paulr | sure, but one can read scrollback | 09:10 |
| giallu | yoi're dreaming | 09:10 |
| paulr | I get daily logs mailed to me of some irc channels | 09:11 |
| paulr | take the commit earlier fixing warning in install_functions.php | 09:12 |
| paulr | it alters | 09:12 |
| paulr | if( <foo> ) { | 09:12 |
| paulr | to | 09:12 |
| paulr | if ( <foo> ) { | 09:12 |
| paulr | i've not looked but i'd guess half the code base is if( and the other half is if ( | 09:13 |
| paulr | having said that | 09:15 |
| paulr | there's only 457 occurences of if( | 09:15 |
| paulr | and 3000+ of if ( | 09:15 |
| dhx_m | both the ML and IRC are bad IMO for discussing bugs in detail | 09:27 |
| dhx_m | the primary place IMO should be on the official Mantis tracker | 09:28 |
| dhx_m | I'm not sure if Mantis interfaces at all with email/mailing lists, but that'd be a nice idea for the future | 09:28 |
| dhx_m | so that it is a pseudo-mailing-list where you can use email clients (MUCH better than using a web browser interface) for discussing bugs | 09:29 |
| dhx_m | the Mantis tracker has the advantage of allowing you to merge all sorts of extra information into one place (not possible on the ML/IRC) | 09:29 |
| dhx_m | what commits are related to the bug? what other bugs are related/blocking/etc? | 09:30 |
| dhx_m | I know when I've been looking through LKML archives, I've found it hard to find the information I'm interested in | 09:32 |
| dhx_m | and it is much harder to create a timeline of events that occurred... ie. bug identified, someone made a patch, people reviewed it and called it a load of rubbish, someone fixed the patch, it got committed, it was closed for 2 months... someone then found a bug that resulted from the fix applied, etc | 09:33 |
| dhx_m | with a ML you have to manually search through the archives finding related emails... and you'll often miss stuff or stumble across a lot of things you're not interested in | 09:36 |
| dhx_m | with IRC the situation is even worse :) | 09:36 |
| [KK]Kirill | paulr: you around? | 11:21 |
| nuclear_eclipse | morning all | 12:32 |
| kenguest | afternoon :p | 12:39 |
| dhx_m | hi | 13:10 |
| dhx_m | paulr: I'm looking at ISO 9075.2:2005 now (on the SQL DATETIME data type)... what a headache! | 13:34 |
| dhx_m | paulr: I just thought about this... in the DB upgrade, are you checking for any dates prior to 1970? | 13:45 |
| dhx_m | paulr: The problem I see is what happens if someone wants to add a capability (via a plugin, etc) for Mantis to use dates < 1970 | 13:45 |
| dhx_m | birth dates, some custom date field that needs to store historical values, etc | 13:46 |
| * nuclear_eclipse slaps dhx_m | 13:46 | |
| dhx_m | :) | 13:46 |
| dhx_m | nuclear_eclipse: I want to write a source code repository plugin for my source code dating back to 1965 :p j/k | 13:47 |
| dhx_m | then I want to add a new birthdays feature into Mantis :p | 13:47 |
| nuclear_eclipse | don't make me get out my ban hammer..... | 13:48 |
| dhx_m | DATETIME just seems like a high overhead feature filled hack when a lot of the time you're only interested in the raw number (signed 64bit?) | 13:50 |
| dhx_m | especially if you're using something like sqlite where performance is more important | 13:51 |
| paulr | dhx_m: if you want to write a plugin | 17:49 |
| paulr | you can store dob as a string | 17:49 |
| paulr | in terms of dates <1970 | 17:49 |
| paulr | what I do atm | 17:49 |
| paulr | is if a date is between 0 and 86400 or something | 17:49 |
| paulr | I assume it's 0 | 17:49 |
| dhx_m | paulr: I was joking, not trying to be an ass :D | 17:49 |
| paulr | i.e. I need to deal with duedates being broken | 17:49 |
| paulr | ass = my job | 17:50 |
| dhx_m | I can't say I use duedates... but are you referring to people entering invalid due dates (< current time)? | 17:50 |
| paulr | no | 17:51 |
| paulr | +$t_due_date = gpc_get_string( 'due_date', null ); | 17:51 |
| paulr | + | 17:51 |
| paulr | +if( $t_due_date !== null) { | 17:51 |
| paulr | +if ( is_blank ( $t_due_date ) ) { | 17:51 |
| paulr | +$t_bug_data->due_date = 1; | 17:51 |
| paulr | +} else { | 17:51 |
| paulr | +$t_bug_data->due_date = strtotime( $t_due_date ); | 17:51 |
| paulr | +} } | 17:51 |
| * paulr thinks that might be what we want to do | 17:51 | |
| paulr | oh visiting cat brb :P | 17:51 |
| dhx_m | ah, so that broke after the merge? | 17:51 |
| dhx_m | ok :) | 17:51 |
| nuclear_eclipse | no, he's talking about the terrible date-handling code that somehow made it into the repo from a random contributer, that should have never made it into mantis.... | 17:51 |
| paulr | back | 17:52 |
| dhx_m | yeah the main reason I don't use duedates is because it looked unstable | 17:52 |
| dhx_m | (and I didn't have a need for it either) | 17:53 |
| nuclear_eclipse | it tried to do some over-clever, yet inherently broken, processing to emulate the use of "null" dates without just plain using a null value in the database, which just broke it for almost anyone and everyone | 17:53 |
| paulr | vs2010 beta1 today :) | 17:53 |
| paulr | nuclear_eclipse: I'm still trying to work out what i've broken/fixed | 17:53 |
| paulr | btw whats ISO 9075.2:2005 ? | 17:53 |
| dhx_m | SQL standards | 17:54 |
| dhx_m | was trying to work out what the best way of storing dates is | 17:55 |
| paulr | what did you conclude? | 17:55 |
| dhx_m | according to the SQL brains | 17:55 |
| dhx_m | I don't know lol | 17:55 |
| dhx_m | some crap about intervals? | 17:55 |
| paulr | anyway, I need to focus on dates a bit | 17:56 |
| paulr | and how we use them | 17:56 |
| dhx_m | I like the idea of using datetime... but unless it has an inbuilt integer conversion of some sorts... it isn't much use | 17:56 |
| dhx_m | computer programs don't internally work on plaintext data | 17:57 |
| dhx_m | ie. it'd be stored as a signed x bit value | 17:57 |
| dhx_m | where x is the number of bits you need to have your time span over | 17:57 |
| dhx_m | it may be 256bit if you're talking about theoretical physics or some other branch of science where you calculate times 1x10^(some large number) of years into the future | 17:58 |
| dhx_m | if you were wanting to store these "extreme" datestamps into a database, you wouldn't use datetime ;) | 17:59 |
| dhx_m | although one could argue time zones, leap years, etc don't mean anything in those cases, because you simply don't know what will happen that far in advance ;) | 18:00 |
| dhx_m | (or in the past) | 18:00 |
| dhx_m | and on the other end of the scale, I'm not sure how you're meant to store your experiment results (on the scale of nanoseconds) in a database using the usual timestamp data type | 18:01 |
| dhx_m | so I agree with you that using datestamp/timestamp aren't always a good option | 18:02 |
| * nuclear_eclipse waits for dhx_m to finish rambling... | 18:02 | |
| paulr | LOG_DATABASE | 18:03 |
| dhx_m | done :) | 18:03 |
| paulr | good idea? | 18:03 |
| * paulr slaps nuclear_eclipse | 18:03 | |
| nuclear_eclipse | paulr: eg, log every SQL query sent to the db? | 18:03 |
| paulr | wow | 18:03 |
| paulr | america woke up | 18:03 |
| paulr | ffs | 18:03 |
| dhx_m | logarithmic scale? :) | 18:03 |
| dhx_m | ohhh | 18:03 |
| paulr | nuclear_eclipse: yea | 18:03 |
| nuclear_eclipse | 14:03 < paulr> america woke up | 18:03 |
| nuclear_eclipse | ?\ | 18:03 |
| paulr | I'm trying to downlaod vstudio2010 beta | 18:04 |
| paulr | was getting 700kb/s | 18:04 |
| paulr | now getting 10kb/s | 18:04 |
| nuclear_eclipse | ah, lol | 18:04 |
| paulr | == people woke up | 18:04 |
| nuclear_eclipse | that's what you get for using garbage like VS :P | 18:04 |
| dhx_m | lol... they don't have many free 10Gbps mirrors around the world like Ubuntu does :) | 18:04 |
| paulr | so log_database=good idea? | 18:04 |
| dhx_m | I like the idea for debugging purposes | 18:04 |
| paulr | dhx_m: i'm sure they'd have them | 18:05 |
| nuclear_eclipse | paulr: I think not so much, log_db would grow log files *really* fast..... | 18:05 |
| paulr | they probably can't use them | 18:05 |
| paulr | nuclear_eclipse: you saw I added support for firebug? | 18:05 |
| paulr | as a log method | 18:05 |
| dhx_m | paulr: not as much I imagine (especially not in Europe) | 18:05 |
| dhx_m | I can't believe they don't just setup torrent distribution | 18:06 |
| nuclear_eclipse | dhx_m: you can't expect MS, best known for being the most proprietary and over-protective software house, to use a method where *anyone* could get a copy of beta software... | 18:06 |
| paulr | dhx_m: mirrorservice.org used to mirror ftp.microsoft.com years ago | 18:07 |
| dhx_m | nuclear_eclipse: you can setup the tracker to ignore peers that aren't signed in | 18:07 |
| paulr | anyway | 18:07 |
| paulr | log_Database | 18:07 |
| dhx_m | nuclear_eclipse: I suppose if they are just giving it out to "professionals", they're not going to help by using a torrent client | 18:08 |
| * paulr adds | 18:08 | |
| paulr | btw, I want to change logging api | 18:08 |
| paulr | need a info/warn/debug level for each section | 18:08 |
| paulr | :) | 18:08 |
| dhx_m | what is logged? | 18:08 |
| dhx_m | are we talking about "new account created", "bug note created", etc | 18:09 |
| dhx_m | or debugging information? | 18:09 |
| paulr | debug queries | 18:09 |
| dhx_m | nuclear_eclipse: BTW, I thought VS2010 was free for all? http://www.microsoft.com/downloads/details.aspx?FamilyId=922B4655-93D0-4476-BDA4-94CF5F8D4814&displaylang=en | 18:10 |
| paulr | it is | 18:10 |
| dhx_m | (that is the old link BTW) | 18:10 |
| paulr | 4kb/sec | 18:10 |
| dhx_m | oh ouch... no mirrors? | 18:10 |
| nuclear_eclipse | dhx_m: I assume the beta still requires an activation key, like all their other betas in the past 10 years... | 18:11 |
| dhx_m | nuclear_eclipse: yeah, but that doesn't affect distribution of the installation files :) | 18:11 |
| nuclear_eclipse | dhx_m: well, right, but my point is torrents remove the control from Microsoft | 18:12 |
| paulr | do you think that having a function | 18:12 |
| paulr | print_date | 18:12 |
| paulr | that calls | 18:12 |
| paulr | echo date( | 18:12 |
| paulr | is silly? | 18:12 |
| paulr | or useful | 18:13 |
| nuclear_eclipse | not if it automatically applies configured date formatting strings | 18:13 |
| dhx_m | nuclear_eclipse: they can kill whatever torrent tracker they are using... which pretty much stops distribution (with a longer delay I must admit) | 18:13 |
| paulr | <?php print_date( config_get( 'normal_date_format' ), $t_bug->date_submitted ) ?> | 18:13 |
| nuclear_eclipse | hmm, that seems much less useful | 18:13 |
| dhx_m | nuclear_eclipse: or they can use online activation (as they have in the past) to control installation... my point is that activation/license keys control distribution :) | 18:14 |
| paulr | only reason for keeping it would be if we wanted to do timezones within | 18:14 |
| paulr | but I think BIN | 18:14 |
| nuclear_eclipse | I was thinking `function print_date( $p_date ) { echo date( config_get( 'normal_date_format' ), $p_date ); }` type of implementation | 18:14 |
| dhx_m | paulr: I thought you were the one complaining about functions that return a single configuration value? :) | 18:15 |
| paulr | john is even better | 18:15 |
| dhx_m | except nuclear_eclipse's idea justifies a function for increasing readability of code elsewhere | 18:15 |
| paulr | he does | 18:15 |
| paulr | echo print_date( | 18:16 |
| paulr | so that's | 18:16 |
| paulr | echo echo date | 18:16 |
| paulr | <td><?php echo date( config_get( 'normal_date_format' ), $t_tag_row['date_created'] ) ?></td> | 18:16 |
| paulr | <td><?php echo date( config_get( 'normal_date_format' ), $t_tag_row['date_updated'] ) ?></td> | 18:16 |
| nuclear_eclipse | where do I do `echo print_date()` ? | 18:16 |
| paulr | dhx_m: I dont like stuff like that | 18:16 |
| paulr | nuclear_eclipse: c:\mantis\git\mantisbt\manage_tags_page.php (2 hits) Line 161: <td><?php echo print_date( config_get( 'normal_date_format' ), $t_tag_row['date_created'] ) ?></td> | 18:16 |
| nuclear_eclipse | oh, that's not my code :P | 18:16 |
| nuclear_eclipse | check the `git blame` on that one... | 18:16 |
| paulr | i'm also not sure about things like wiki_enabled as a function | 18:19 |
| paulr | part of me thinks that functions that just call config_get | 18:20 |
| dhx_m | no use for that | 18:20 |
| paulr | could just be config_get calls | 18:20 |
| dhx_m | it hides what those functions are really doing | 18:20 |
| paulr | well also | 18:20 |
| dhx_m | meaning you have to now find the wiki_enabled function to see what it does | 18:20 |
| paulr | if config_get('wiki_enabled' == OFF | 18:20 |
| nuclear_eclipse | paulr: the only reason for them was to maintain API compatibility with 1.1.x | 18:20 |
| paulr | we can skip require_once'ing the wiki api | 18:20 |
| paulr | anyway | 18:21 |
| paulr | I have a question for you guys about due dates | 18:21 |
| paulr | pay attention now | 18:21 |
| nuclear_eclipse | huh? what? | 18:21 |
| paulr | if something is due on the 16th May | 18:21 |
| nuclear_eclipse | who's talking? | 18:21 |
| paulr | when is it due? | 18:22 |
| paulr | I mean | 18:22 |
| nuclear_eclipse | paulr: that depends on who you ask :P | 18:22 |
| dhx_m | haha | 18:22 |
| nuclear_eclipse | I'd assume that means it's due by the end of the day on the 16th | 18:22 |
| dhx_m | managers: 1 second after the end of the 15th | 18:22 |
| paulr | GMT or localised? :) | 18:22 |
| nuclear_eclipse | others would assume it's due by the morning of the 16th | 18:22 |
| dhx_m | programmers: 1 second before the start of the 17th... in the most desirable timezone | 18:22 |
| dhx_m | it should be localised, but stored as GMT | 18:23 |
| dhx_m | so whatever you set it as, is converted and stored as GMT | 18:23 |
| dhx_m | then it is retrieved and put in local time for everyone else | 18:23 |
| dhx_m | ? | 18:23 |
| paulr | so | 18:24 |
| paulr | if i | 18:24 |
| paulr | GMT+1 set a dueday at 5pm for 17th | 18:24 |
| paulr | that might mean | 18:24 |
| paulr | 17th May 00:00:00 | 18:24 |
| paulr | or more we store "17th May 00:00:00" GMT | 18:25 |
| paulr | then account for the offset? | 18:25 |
| paulr | so your duedate is different to mine? | 18:25 |
| nuclear_eclipse | paulr: if you handle timezones correctly, due_date could be both a date and time, and then when localised, it could be 5pm GMT, and noon EST | 18:26 |
| paulr | my point is | 18:27 |
| paulr | we set 2009-05-19 => 2009-05-20 | 18:27 |
| paulr | for example | 18:27 |
| paulr | your 20th starts at different time to me | 18:27 |
| nuclear_eclipse | right, that's my point | 18:27 |
| paulr | or are we basically saying we should add/subtract timezone offset? | 18:28 |
| nuclear_eclipse | if you convert the user input for due_date to GMT based on their timezone, then all users will share the same due date, appropriately localised to their own timezone | 18:28 |
| dhx_m | this is the "use case" I'm thinking of: | 18:28 |
| nuclear_eclipse | I guess it would make it more of a due *time*... | 18:28 |
| paulr | so basically | 18:29 |
| dhx_m | 1) I am in GMT+1 and I set the due date for the 17th of May 5PM | 18:29 |
| dhx_m | 2) Mantis stores this due date as May 17th 4PM GMT | 18:30 |
| paulr | nonono | 18:30 |
| paulr | you dont atm though | 18:30 |
| paulr | :) | 18:30 |
| paulr | due times would be easy :P | 18:30 |
| nuclear_eclipse | paulr: I think our point is that's how it *should* work... | 18:30 |
| paulr | so we want to make it duedatetime? | 18:30 |
| dhx_m | I think that is better | 18:30 |
| nuclear_eclipse | that would *certainly* resolves any ambiguities as to whether "due on the 16th" means overdue on the 16th or overdue on the 17th.... | 18:31 |
| dhx_m | where there is a default due time? | 18:31 |
| dhx_m | maybe a config option to specify what the normal due time is? | 18:31 |
| dhx_m | and you can change it if you want | 18:31 |
| dhx_m | it'd be annoying having to set the time manually each time when your development team always has things due at the same time | 18:32 |
| paulr | erm | 18:32 |
| paulr | erm | 18:32 |
| dhx_m | ... that made no sense lol | 18:32 |
| paulr | erm! | 18:32 |
| dhx_m | too many "times" | 18:32 |
| paulr | dhx_m: find a good open source jscript calendar please | 18:33 |
| paulr | :) | 18:33 |
| dhx_m | there is one already in Mantis? | 18:33 |
| paulr | yep | 18:33 |
| paulr | replace it | 18:33 |
| dhx_m | not sure if you'd call it "good" heh | 18:33 |
| dhx_m | it'd still be possible to use it without javascript right? | 18:34 |
| dhx_m | by manually typing in the date/time? | 18:34 |
| paulr | dunno I just want to replace calendar atm :) | 18:34 |
| dhx_m | there are lots of them | 18:35 |
| dhx_m | also how would it handle due times? | 18:36 |
| paulr | http://cuwebd.ning.com/group/calendars/forum/topics/1763934:Topic:11683 | 18:36 |
| paulr | think we stuck with current one :( | 18:38 |
| dhx_m | this is very ugly... but a good idea of a time chooser: http://www.java2s.com/Code/JavaScript/GUI-Components/FancyTimePicker.htm | 18:40 |
| dhx_m | a lot of them manually ask you to type a time... which is stupid | 18:40 |
| dhx_m | I like the idea of having 30min increments shown | 18:41 |
| dhx_m | a more fancy example: http://pttimeselect.sourceforge.net/example/index.html | 18:42 |
| dhx_m | although I still find them hard to use (non-intuitive) | 18:42 |
| thraxisp | paulr: A couple of comments on dates: | 19:41 |
| thraxisp | we should use a long int (64 bits) so the 2038 problem isn't. | 19:42 |
| thraxisp | Can you also verify that all of the graphs still work. As I recall, they do some date rounding. | 19:42 |
| DirtyAl | nucler_eclipse are you here? | 19:49 |
| nuclear_eclipse | yo | 19:49 |
| DirtyAl | I've found and small bug on the souce pluin | 19:49 |
| nuclear_eclipse | awesome :) | 19:50 |
| DirtyAl | im funciont static function load_by_name( $p_repo_name ) { | 19:50 |
| DirtyAl | in the query to get the repo ID | 19:50 |
| DirtyAl | you use like | 19:50 |
| DirtyAl | i have to repos like this | 19:50 |
| DirtyAl | nagios | 19:50 |
| DirtyAl | nagios-plugins | 19:50 |
| DirtyAl | and | 19:50 |
| DirtyAl | the commit is not goind ot mantis because th elike query return the ID for nagios-plguins | 19:50 |
| DirtyAl | and it should be mnagios | 19:50 |
| DirtyAl | due to tje LIKE | 19:51 |
| DirtyAl | maybe it soulhd by = | 19:51 |
| nuclear_eclipse | ah, it's the wildcards from the the %name% that's bugging it up | 19:51 |
| DirtyAl | I was goind crazy here, everthing working great, just commits to the repo nagios would not show | 19:51 |
| nuclear_eclipse | DirtyAl: mind reporting a new issue on http://leetcode.net/mantis/ ? | 19:52 |
| DirtyAl | yes, that's it | 19:52 |
| DirtyAl | no problem, will do | 19:52 |
| DirtyAl | now | 19:52 |
| nuclear_eclipse | I should also be using db_like() for that as well | 19:52 |
| DirtyAl | I almost used Trac, glad I found your plugins, I like mantis very much | 19:54 |
| DirtyAl | I tried to register to yout mantis | 19:56 |
| nuclear_eclipse | I'm glad I helped save more people from Trac :P | 19:56 |
| DirtyAl | did get the email to set up the passwod | 19:56 |
| DirtyAl | clicking in reset password gives this message | 19:57 |
| DirtyAl | APPLICATION WARNING #2702: Your session has become invalidated. | 19:57 |
| nuclear_eclipse | are you behind a proxy server? | 19:57 |
| DirtyAl | transparent squid | 19:59 |
| DirtyAl | I am behinf 4 diffente links | 20:00 |
| DirtyAl | and the conection my switch between them | 20:00 |
| nuclear_eclipse | yep | 20:02 |
| nuclear_eclipse | that's why | 20:02 |
| nuclear_eclipse | I just disabled the session validation on my site; try again please | 20:03 |
| * nuclear_eclipse thinks proxy servers shouldn't load balance between different outbound nodes for a single endpoint; it's really ugly from a security aspect... =\ | 20:04 | |
| DirtyAl | its a linux box with multiple links | 20:05 |
| nuclear_eclipse | eg, all connections to site X should always go through proxy node A; connections to site Y always go through node B, etc | 20:05 |
| DirtyAl | the conntack does that | 20:05 |
| DirtyAl | but for HTTP | 20:05 |
| DirtyAl | it has a timeout for the connection on conntrack | 20:05 |
| nuclear_eclipse | DirtyAl: my point is that from a security point of view, multiple connections from the same user from multiple IP addresses looks exactly like a session hijacking attempt, and you really have no way of knowing if it is or it isn't ] | 20:06 |
| DirtyAl | i know, I switched to HTTPS and got to the lsto password | 20:07 |
| DirtyAl | now got this error | 20:07 |
| DirtyAl | APPLICATION ERROR #200A required parameter to this page (confirm_hash) was not found. | 20:07 |
| nuclear_eclipse | hmm | 20:08 |
| nuclear_eclipse | let me try updating my install :P | 20:08 |
| nuclear_eclipse | ok, try again :) | 20:09 |
| DirtyAl | hehe | 20:09 |
| nuclear_eclipse | it's apparently been a while since I synced my tracker to latest git... | 20:09 |
| * nuclear_eclipse makes a note to make session validation an option to the user at login time... | 20:10 | |
| DirtyAl | same problem | 20:11 |
| DirtyAl | APPLICATION ERROR #200A required parameter to this page (confirm_hash) was not found. | 20:11 |
| nuclear_eclipse | try doing a lost-password reset; I wonder if the session validation bit nullified your ability to use that hash... =\ | 20:12 |
| paulr | thraxisp: i'm tempted to say we do that in 10 years :) | 20:12 |
| paulr | (move to long ints) | 20:12 |
| DirtyAl | I did | 20:12 |
| DirtyAl | got the URL via email | 20:12 |
| paulr | (By then, OS's will be 64bit and it'll be clearer what (if anything) we need to do | 20:12 |
| DirtyAl | clickin on it gives me this error | 20:12 |
| nuclear_eclipse | DirtyAl: I'll just force it set for you; I wonder if the proxy is munging something weird... =\ | 20:14 |
| DirtyAl | it workd, submitting the bug | 20:19 |
| nuclear_eclipse | thanks DirtyAl :) | 20:20 |
| DirtyAl | done, isse 39 | 20:21 |
| DirtyAl | issue 39 with the solution I am using here. | 20:21 |
| --- scribe started --- | 20:32 | |
| paul___ | back | 20:33 |
| nuclear_eclipse | paul___: your server dead? | 20:33 |
| paul___ | no | 20:34 |
| nuclear_eclipse | ok, it was :P | 20:34 |
| paul___ | I rebooted host for kernel update | 20:34 |
| paul___ | is the sshd for git up? | 20:34 |
| nuclear_eclipse | jreese@iowa[/space/workspace/plugins/source-integration/Source] git fetch < 16:35 | 20:35 |
| nuclear_eclipse | ssh: connect to host git.mantisforge.org port 22: Connection refused | 20:35 |
| nuclear_eclipse | fatal: The remote end hung up unexpectedly | 20:35 |
| nuclear_eclipse | zsh: exit 128 git fetch | 20:35 |
| paul___ | @reboot /root/sshd.sh | 20:36 |
| paul___ | well | 20:36 |
| paul___ | obviously that attempt at a cronjob doesn't work | 20:36 |
| paul___ | dhx_m? | 21:47 |
| * paul___ sighs | 21:54 | |
| paul___ | I really hate the way mantis does stuff sometimes | 21:54 |
| * paul___ thinks | 21:59 | |
| paul___ | thraxisp: what did you ask earlier | 21:59 |
| nuclear_eclipse | @seen thraxisp | 21:59 |
| nuclear_eclipse | bah, stupid bot | 21:59 |
| paul___ | nuclear_eclipse: can I whinge at you? :) | 22:00 |
| paul___ | why do we allow users to customise date formats ;/ | 22:01 |
| nuclear_eclipse | because not everybody likes the ISO standard, unfortunately, even though I think it's the most logical date format available, and not just because it "sorts correctly" | 22:02 |
| paul___ | but :( | 22:03 |
| * paul___ carries on defining 2 more date formats | 22:03 | |
| paul___ | oh | 22:04 |
| paul___ | I also hate how our git repo is organised | 22:04 |
| nuclear_eclipse | what do you mean? | 22:04 |
| paul___ | to which bit | 22:04 |
| nuclear_eclipse | 18:04 < paul___> I also hate how our git repo is organised | 22:04 |
| paul___ | well | 22:05 |
| paul___ | it would be nice to have a project for adodb | 22:05 |
| paul___ | then have the central thing pull in the adodb thing (like a tree) | 22:05 |
| paul___ | I know you can do that in svn/hg | 22:05 |
| paul___ | now in an ideal world, you'd have something where you can filter what you include in that | 22:06 |
| paul___ | I also want to know how to edit manual | 22:06 |
| nuclear_eclipse | there is an ability to use "submodules" in git, but it's got a rather poor interface | 22:07 |
| * paul___ still wonders if it would be easier if we migrated manual to docbook5xml format stuff | 22:07 | |
| nuclear_eclipse | paul___: I keep telling you, the manual's a damn text file, just look at the the tags and you'll instantly figure it out exactly the same as html | 22:07 |
| paul___ | nod but the build setups i've got for docbook are all xml ;/ | 22:08 |
| paul___ | and editors i've found ;p | 22:08 |
| nuclear_eclipse | so use the build system we've already created for the sgml docbook; it's really not that difficult... | 22:08 |
| paul___ | mm | 22:24 |
| paul___ | how do you include % in a config variable | 22:24 |
| nuclear_eclipse | paul___: good freaking question :P | 23:30 |
Generated by irclog2html.py