| 00:15.06 | *** join/#asterisk-bugs mjordan (~mjordan@75.76.55.191) |
| 00:15.06 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 00:18.19 | file | mjordan, good DAY |
| 00:59.26 | *** join/#asterisk-bugs mjordan (mjordan@nat/digium/x-knecijkocbctbljj) |
| 00:59.26 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 02:38.13 | mjordan | it is a good DAY |
| 03:36.43 | *** join/#asterisk-bugs darkbasic (~quassel@niko.linuxsystems.it) |
| 16:35.54 | *** join/#asterisk-bugs mjordan (mjordan@nat/digium/x-krgcidfagbtnmtwh) |
| 16:35.54 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 16:53.08 | *** join/#asterisk-bugs tzafrir (~tzafrir@local.xorcom.com) |
| 18:28.29 | file | mjordan, GREETINGS COMRADE |
| 18:28.38 | mjordan | hello |
| 18:29.17 | file | welcome to Sunday |
| 18:29.28 | mjordan | indeed |
| 18:29.42 | mjordan | I've now read 450 of the 1000 open issues in my original filter |
| 18:30.18 | mjordan | how would you feel about updating the canned 'test with new branch' message to indicate a waiting period? If we don't hear back in, say, 30 days (twice as long as normal), we close it out? |
| 18:30.38 | file | I'm down with that |
| 18:31.00 | mjordan | I may tweak that up this afternoon and load it in. Which, of course, would result in the good ol' "and now I take forever to load" |
| 18:31.42 | file | hum - any others we want to add based on our perusal? |
| 18:31.57 | mjordan | I'm not sure. I may wait until Monday and let rnewton chime in |
| 18:32.01 | mjordan | but I'll take any suggestions |
| 18:34.35 | file | would a response for if an issue is filed against a non-core module detailing the potential time and such be useful? |
| 19:27.33 | file | mjordan, is ASTERISK-24567 an issue? based on your comment I don't think so |
| 19:28.19 | mjordan | well |
| 19:28.26 | mjordan | depends on your definition of 'problem'. |
| 19:28.36 | mjordan | There's a point in the module loader where it attempts to resolve global symbols |
| 19:28.54 | mjordan | There may be a WARNING that occurs as a result of that... but it ends up not causing an actual issue |
| 19:29.00 | file | aye |
| 19:29.08 | mjordan | that being said, if you use autoload = yes and don't see that WARNING, then we magi-fixed it at some point |
| 19:29.21 | mjordan | and I'm not sure it is really worth having an issue open for that |
| 19:29.40 | mjordan | i.e., it's sort of just the joy of the module loader, and until that gets overhauled, nothing much is probably going to fix it |
| 19:29.50 | file | nods |
| 19:45.22 | *** join/#asterisk-bugs superscrat (~asanders@173-17-133-2.client.mchsi.com) |
| 20:25.19 | *** join/#asterisk-bugs tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net) |
| 21:26.18 | *** join/#asterisk-bugs superscrat (~asanders@173-17-133-2.client.mchsi.com) |