03:48 <catepillar> hey

03:49 <catepillar> I seem to have this issue where if I use the plugin manager thing to reload a plugin

03:49 <catepillar> sometimes (if there is a bug in the runtime code it seems)

03:49 <catepillar> it will double load the plugin

03:49 <catepillar> if that makes sense

03:49 <catepillar> but if I run a command, the command gets executed 2x in 2 threads

03:50 <catepillar> is there a way to "fix" this

03:50 <catepillar> without having to reload the bot

04:11 <dominikh> can you provide minimal executable code that reproduces the issue reliably? -- and no, if it already happened, the best bet is to restart the bot. it would be possibly to manually remove the handlers if you had a plugin that evals ruby code, and knew which handlers to remove how, but restarting the bot seems easier :)

04:11 <catepillar> yea

04:12 <catepillar> my bot is getting so big that it takes a minute to load all the plugins now

04:12 <catepillar> probably need to start seperating features out again

04:13 <catepillar> i really dunno what is causing it other than the plugin unloads fine. stops executing, then on reload its getting loaded twice

04:13 <dominikh> are you sure you're not messing up somewhere else?

04:13 <catepillar> i could very well be

04:14 <catepillar> its only happened two times, but they were both tonight

04:14 <dominikh> because right now I can't think of a possible code path that would load the plugin twice

04:15 <catepillar> well, im gonna start looking through logs

19:39 <windowsrefund> hello

19:45 <windowsrefund> I'm having a really hard time getting my method to see the 2nd argument

19:45 <windowsrefund> http://pastebin.com/fgDhrErR

19:46 <windowsrefund> commits is always nil

19:52 <literal> I think the /.+/ part of your is matching to the end of the line since everything after that is optional

19:52 <literal> of your regex

19:53 <literal> you can make the + lazy by using /.+?/

19:57 <windowsrefund> perfect

19:57 <windowsrefund> thanks

21:57 <catepillar> 13:53 < literal> you can make the + lazy by using /.+?/

21:58 <catepillar> isn't that the same thing as /.*/?

21:58 <literal> nope

21:58 <literal> +? still needs to match at least one

21:58 <literal> it just tries to match as little as possible, instead of as much as possible

21:58 <catepillar> weird

21:59 <literal> the latter was preventing the optional parts of his regex from matching

21:59 <catepillar> i should probably look at his full regex

22:00 <catepillar> ahhh

22:00 <catepillar> he was trying to match all non-space entities

22:01 <literal> yeah he could have used \S+ instead of .+? if nonspace is all he wanted

22:03 <catepillar> yeah, im pretty sure that's what im using in my code