| 00:15.31 | Entomologist | *** CLOSED (16950) [General] PRI i-frames sent out of order, causing REJ supervisory frame |
| 00:15.31 | Entomologist | Assigned to: mattf |
| 00:15.32 | Entomologist | Reported by: alecdavis |
| 00:15.32 | Entomologist | https://issues.asterisk.org/view.php?id=16950 |
| 00:15.33 | Entomologist | ********************************************************* |
| 01:18.48 | *** join/#asterisk-bugs infobot (ibot@rikers.org) |
| 01:18.48 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Test bugs marked Ready For Testing! -=- http://xkcd.org/583/ |
| 01:20.05 | russellb | seanbright: agreed |
| 01:20.08 | russellb | you can quote me, too |
| 01:20.59 | russellb | though there is quite a bit of feeding the troll going on, too |
| 01:21.02 | russellb | looks at Qwell |
| 01:21.07 | seanbright | heh |
| 01:21.23 | seanbright | they guy wasn't reading what was being written and then flaming people |
| 01:21.36 | seanbright | s/hey/he/ |
| 01:21.39 | russellb | nods |
| 01:21.51 | seanbright | anyway |
| 01:27.43 | *** join/#asterisk-bugs infobot (ibot@rikers.org) |
| 01:27.43 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Test bugs marked Ready For Testing! -=- http://xkcd.org/583/ |
| 01:38.25 | *** join/#asterisk-bugs infobot (ibot@rikers.org) |
| 01:38.25 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Test bugs marked Ready For Testing! -=- http://xkcd.org/583/ |
| 01:52.50 | Marquis42 | seanbright: I just put a note on that bug, but I tried a ridiculous number of permutations of terminal app, TERM type, and asterisk version on F12 and I can't get the behavior he claims he's seeing. |
| 02:00.51 | file | Marquis42: thx! |
| 02:01.44 | Marquis42 | No problem. It seemed like a pretty specious claim anyway, but I figured since my main system is F12 I could easily run a few tests and see. |
| 02:15.08 | leifmadsen | Marquis42: hey! |
| 02:15.14 | leifmadsen | holy fuck is jw-asterisk a complete asshole |
| 02:15.18 | leifmadsen | and you can quote me on that |
| 02:15.47 | leifmadsen | actually, qwell did a lot better in terms of not feeding the troll than I have seen in the past :) |
| 02:16.57 | leifmadsen | anyways, I'm not sure what set this guy off... all jtodd and I said was, "we're not seeing it on OUR systems" -- he could have then come back with some additional information about his platform, and how he was able to reproduce it instead of getting all defensive about it |
| 02:17.10 | leifmadsen | ok, I've had my rant, and now I'm done with that issue |
| 02:30.54 | Entomologist | *** CLOSED (16955) [Addons/General] In dialplan (extensions.conf), subdirectories are not respected |
| 02:30.55 | Entomologist | Reported by: ruddy |
| 02:30.56 | Entomologist | https://issues.asterisk.org/view.php?id=16955 |
| 02:30.56 | Entomologist | ********************************************************* |
| 02:31.46 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 03:37.56 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 05:08.53 | *** join/#asterisk-bugs file (~file@asterisk/developer-and-muffin-lover/file) |
| 05:08.55 | *** mode/#asterisk-bugs [+o file] by ChanServ |
| 06:31.11 | *** join/#asterisk-bugs corretico (~laguilar@201.201.46.106) |
| 06:53.52 | *** part/#asterisk-bugs codefreeze-lap (~murf@mail.parsetree.com) |
| 07:19.28 | *** join/#asterisk-bugs infobot (ibot@rikers.org) |
| 07:19.29 | *** topic/#asterisk-bugs is Asterisk Bugs Discussion -=- http://issues.asterisk.org/ -=- http://asterisk.org/developers/bug-guidelines - Discussions not related to reported issues should be in #asterisk -=- Test bugs marked Ready For Testing! -=- http://xkcd.org/583/ |
| 08:31.31 | *** join/#asterisk-bugs codefreeze-lap (~murf@mail.parsetree.com) |
| 08:44.11 | *** join/#asterisk-bugs codefreeze-lap (~murf@mail.parsetree.com) |
| 09:51.57 | *** join/#asterisk-bugs bzing2 (~dr105@dhcp-194-66-208-236.canterbury.ac.uk) |
| 12:32.56 | *** join/#asterisk-bugs Victor_Yure (~victor@unaffiliated/victoryure/x-837844) |
| 12:36.57 | *** join/#asterisk-bugs caio1982 (~caio1982@CAcert-br/caio1982) |
| 12:40.24 | *** join/#asterisk-bugs leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 12:40.25 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 12:43.34 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 13:11.10 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 13:30.40 | *** part/#asterisk-bugs bzing2 (~dr105@dhcp-194-66-208-236.canterbury.ac.uk) |
| 13:43.12 | *** join/#asterisk-bugs TheDavidFactor (~chatzilla@nc-71-0-16-133.dhcp.embarqhsd.net) |
| 14:16.50 | Marquis42 | Wow, that jw-asterisk guy is a real dickbag. Whatever, I'm done feeding the troll I guess. |
| 14:36.49 | russellb | suggests someone accidentally hitting the delete issue button |
| 14:36.56 | russellb | that will really feed the troll |
| 15:04.39 | seanbright | no one is able to reproduce |
| 15:06.37 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 15:06.37 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 15:10.38 | russellb | he provided a straight forward explanation of what he thought was wrong |
| 15:10.50 | russellb | seems straight forward to evaluate from a code perspective regardless of having to reproduce it |
| 15:10.58 | russellb | has anyone done that? |
| 15:13.39 | seanbright | i am in the middle of doing that |
| 15:23.18 | seanbright | strangely, on my system, there is no space encoding going on |
| 15:23.26 | seanbright | spaces are stored literally in the history file |
| 15:24.06 | *** join/#asterisk-bugs Deeewayne (~dwayne@75.76.254.162) |
| 15:24.07 | *** mode/#asterisk-bugs [+o Deeewayne] by ChanServ |
| 15:25.43 | seanbright | ahhh |
| 15:26.49 | seanbright | i call your attention to http://svnview.digium.com/svn/asterisk/branches/1.6.2/main/editline/history.c?view=markup |
| 15:26.54 | seanbright | lines 666 and 667 |
| 15:27.35 | seanbright | strvis is called on ev.str (and the result stored in ptr), but then ev.str is written directly to the file, instead of ptr being used |
| 15:28.11 | russellb | oic |
| 15:28.56 | seanbright | so the encoded version of the string should not be written to the file in the first place |
| 15:39.04 | seanbright | http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libedit/history.c#rev1.20 |
| 15:39.24 | russellb | over 7 years ago |
| 15:39.25 | russellb | nice |
| 15:39.28 | seanbright | yeah |
| 15:40.04 | seanbright | i'm guessing the reporter is using a modified version |
| 15:40.38 | russellb | hm? |
| 15:40.45 | russellb | or our version is insanely out of date and doesn't have the fix? |
| 15:40.58 | seanbright | our version is insanely out of date and doesn't have the fix |
| 15:41.08 | russellb | right.. |
| 15:41.21 | seanbright | but the "fix" is what would write 'core\040set\040verbose' instead of 'core set verbose' |
| 15:41.33 | *** join/#asterisk-bugs leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 15:41.33 | russellb | oic! |
| 15:41.33 | seanbright | so in asterisk today... we DON'T encoding the string when it is written |
| 15:41.33 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 15:41.56 | russellb | osnap! |
| 15:41.59 | seanbright | so he must have "fixed" it |
| 15:42.02 | seanbright | or something |
| 15:45.01 | Entomologist | *** CLOSED (16962) [Applications/app_userevent] Automatic add UniqueID to user event |
| 15:45.02 | Entomologist | Reported by: jlpedrosa |
| 15:45.02 | Entomologist | https://issues.asterisk.org/view.php?id=16962 |
| 15:45.03 | Entomologist | ********************************************************* |
| 15:57.48 | Entomologist | *** CLOSED (16628) [Resources/res_clioriginate] [regression] Originate not launching secondary channel when primary is a Local channel |
| 15:57.49 | Entomologist | Reported by: kobaz |
| 15:57.49 | Entomologist | https://issues.asterisk.org/view.php?id=16628 |
| 15:57.50 | Entomologist | ********************************************************* |
| 16:19.44 | *** join/#asterisk-bugs morex (~m@5ac4bcaa.bb.sky.com) |
| 16:19.53 | morex | Hi Leif are you there? |
| 16:20.05 | leifmadsen | morex: yes |
| 16:20.08 | morex | Thanks |
| 16:20.24 | morex | OK well this is the local channels bug which does not open a secondary channel if the first is primary |
| 16:20.25 | morex | Number |
| 16:20.26 | morex | 16628 |
| 16:20.27 | morex | and |
| 16:20.34 | morex | 16717 |
| 16:20.35 | morex | and |
| 16:20.36 | leifmadsen | M16628 |
| 16:20.38 | leifmadsen | M16717 |
| 16:20.38 | MuffinMan | [closed] [Asterisk] Resources/res_clioriginate 0016628: [regression] Originate not launching secondary channel when primary is a Local channel reported by kobaz https://issues.asterisk.org/view.php?id=16628 |
| 16:20.40 | MuffinMan | [closed] [Asterisk] Applications/General 0016717: Orinate calls using AMI on version 1.4.29 broken. reported by flujan https://issues.asterisk.org/view.php?id=16717 |
| 16:20.48 | morex | 16729 |
| 16:20.55 | leifmadsen | morex: ok... what is your question? |
| 16:21.18 | morex | So I know these bugs are fixed in the BRANCH code |
| 16:21.34 | morex | But everyone who's been downloading asterisk from asterisk.org for the last month has faulty code |
| 16:21.40 | leifmadsen | agreed |
| 16:21.50 | leifmadsen | and it will be fixed as soon as the next release candidate is created |
| 16:21.53 | morex | We've got several users who have come to us asking why their asterisk has suddenly stopped working |
| 16:22.06 | morex | It's not something we've had to deal with before |
| 16:22.20 | morex | I know you guys apply high security fixes between bug fix releases |
| 16:22.28 | leifmadsen | yes, that's true |
| 16:22.42 | morex | My question is: How broken would a release of asterisk have to be, before you'd consider applying high-priority bug fix release? |
| 16:22.56 | morex | Because it's been that broken for the last month IMHO. |
| 16:23.19 | leifmadsen | security fixes took up my time over the last month, and the next set of release candidates will contain the fix. Otherwise, you're welcome to apply a patch if you need it for your customers, or you can run code from the branch. |
| 16:23.39 | morex | OK, do you have an ETA you can share? |
| 16:24.03 | leifmadsen | Well the issue has been fixed, and it wouldn't be practical to put out a release every time someone had an issue they needed fixed (that was fixed in the branch) |
| 16:24.16 | morex | Our customers won't run Branch by the way - they only download official releases from asterisk.org |
| 16:24.18 | leifmadsen | I plan on creating release candidates this week |
| 16:24.34 | morex | Hence all the support queries we're fielding |
| 16:24.47 | leifmadsen | OK |
| 16:24.59 | morex | Sure I'm not suggesting that every bug warrants a fix release |
| 16:25.07 | morex | I'm suggesting that this particular one does |
| 16:25.35 | morex | Anyway that's all I got |
| 16:25.38 | morex | Thanks for listening |
| 16:26.21 | leifmadsen | Well the security issues took up a great deal of my time, and I'm only one man, so I'm sure you can understand I'll get releases out as soon as is practical |
| 16:26.28 | morex | OK thanks Leif |
| 16:27.00 | Deeewayne | s/man/boy |
| 16:27.19 | morex | I just wanted to make sure you know this one is causing real problems in the field, but only because the fix hasn't made it to the asterisk.org releases yet. |
| 16:27.42 | leifmadsen | We've previously only released every 3-4 months at one point, so attempting to release every month is a fairly new concept, so you'll have to come up with a better method of supporting your clients rather than relying on a release number. |
| 16:28.09 | leifmadsen | I understand everyone wants their fixes in a release as soon as possible, but I can't give any guarantees as to how often releases will be made. Our goal is to have one once a month. |
| 16:28.11 | morex | What's happening is they're trying to get a fix for a specific feature |
| 16:28.28 | leifmadsen | The fix has been available, so you're welcome to apply it to your current version of Asterisk. |
| 16:28.28 | morex | So they think 'OK, I'll upgrade to the latest version', thinking it's going to have a fix |
| 16:28.43 | morex | And then they're finding it's broken |
| 16:28.46 | morex | And then they call us... |
| 16:28.56 | leifmadsen | Then they should read the releases announcements and look at the summary files and the ChangeLogs -- then they would see what issues have been resolved in a release. |
| 16:29.03 | morex | Yeah I know |
| 16:29.05 | leifmadsen | They should read more carefully before calling you. |
| 16:29.23 | morex | The assumption they make is that each successive version works better than the one before |
| 16:29.27 | morex | Which is usually true... |
| 16:29.29 | morex | ;-) |
| 16:29.34 | leifmadsen | Assumptions, Ass, You, Me... ya |
| 16:29.50 | leifmadsen | that is a dangerous assumption |
| 16:29.52 | morex | Yeah, we don't manage these customer's asterisk. They just call us when it's broke. |
| 16:30.02 | leifmadsen | Unfortunately that is not a problem I can solve. |
| 16:30.24 | morex | What sort of regression testing do you guys do before making a release? |
| 16:30.38 | morex | Just out of interest... |
| 16:30.56 | leifmadsen | We have a test framework that is getting built. You can view the tests and their stats being run from http://bamboo.asterisk.org |
| 16:31.46 | leifmadsen | Creating a larger testing framework for Asterisk over the coming year is a goal of the project. Beyond that, testing from the community is the best indicator and looking at the currently open bugs in Asterisk. People deploying Asterisk should be developing their own regression testing for the features they are using. |
| 16:31.52 | leifmadsen | IMHO |
| 16:32.03 | morex | Yeah that'd be good |
| 16:32.11 | morex | Trouble is, production users won't run Branch |
| 16:32.29 | morex | So there's no way to catch regressions like this until they reach the official release sites |
| 16:33.17 | morex | Bamboo looks good by the way. It looks like it's only checking for successful compile right now though. |
| 16:34.01 | leifmadsen | morex: there are tests being run as well |
| 16:34.30 | morex | OK so how would a user submit a test for Bamboo? |
| 16:34.41 | leifmadsen | I didn't suggest they have to run from the branch; you can always backport the patch into the currently running version or go back to a version that was working for them |
| 16:34.45 | morex | You know what I should check the documentation rather than waste your time |
| 16:34.49 | file | define 'a test' |
| 16:35.21 | morex | In this case, dialplan code plus an Originate action, and a check on the log output would have caught this one |
| 16:35.31 | morex | Hang on support call... |
| 16:36.42 | leifmadsen | morex: that sounds like a practical test vs. a unit test (which is what is implemented in bamboo right now) |
| 16:37.01 | morex | Yeah that's what I'm talking about |
| 16:37.05 | morex | Functional testing |
| 16:38.12 | leifmadsen | morex: you should read this thread: http://lists.digium.com/pipermail/asterisk-dev/2010-February/042387.html |
| 16:40.45 | leifmadsen | One of my tasks this month will be to write some documentation and blog posts to centralize information about the newly developed test framework and how people can create and submit tests. |
| 16:41.15 | leifmadsen | As always, things are progressing and you can watch the mailing lists and IRC channels to try and stay up to date. |
| 16:46.43 | morex | Sorry about that |
| 16:47.05 | leifmadsen | no worries, I've said pretty much all I need to say |
| 16:49.13 | morex | Is there documentation on how to add a test to Bamboo? |
| 16:50.18 | morex | I'd like to add a test that picks this up to prevent future regression. |
| 16:52.46 | morex | Anyway thanks for your time today, and good luck with the next build. |
| 16:53.20 | leifmadsen | morex: as I noted above, additional documentation needs to be created. The testing framework is relatively new (only a couple of months old). The documentation is in the code at this point, and the testing you're thinking of is likely different from what the testing framework has right now. The testing framework right now contains an API for unit tests in code, not externally like you described above. |
| 16:53.35 | leifmadsen | Please read the mailing list post I gave you as it should explain what is available right now |
| 16:53.57 | morex | Yes I read it. It looks like we're a few months away from full functional test capability |
| 16:54.07 | morex | Which is not your fault |
| 16:54.21 | leifmadsen | of course it isn't :) |
| 16:54.27 | morex | Anyway, asterisk broken...needs fixing...yada yada... |
| 16:54.30 | morex | Have a great day |
| 16:54.43 | leifmadsen | the perpetual cycle. We all want things done yesterday, but they won't be done until tomorrow. |
| 17:34.20 | *** join/#asterisk-bugs jpeeler (~jpeeler@asterisk/digium-software-dev/jpeeler) |
| 18:32.12 | *** part/#asterisk-bugs morex (~m@5ac4bcaa.bb.sky.com) |
| 20:17.37 | *** join/#asterisk-bugs davidbrillert (~aragon125@h216-235-8-130.host.egate.net) |
| 21:04.01 | *** join/#asterisk-bugs corretico (~laguilar@201.201.46.106) |
| 21:17.40 | *** join/#asterisk-bugs The_Boy_Wonder (~vossel@asterisk/batman-developer/dvossel) |
| 21:43.44 | *** join/#asterisk-bugs TheDavidFactor (~chatzilla@nc-71-0-16-133.dhcp.embarqhsd.net) |
| 21:51.51 | *** join/#asterisk-bugs elguero (~miguel323@ns1.nashuacs.com) |
| 23:48.54 | Marquis42 | leifmadsen: ping |
| 23:49.04 | leifmadsen | Marquis42: pong-ong-ong-ong! |
| 23:49.18 | Marquis42 | :) |
| 23:49.51 | leifmadsen | what can I do for you sir? |
| 23:50.06 | *** join/#asterisk-bugs codefreeze-lap (~murf@mail.parsetree.com) |
| 23:50.11 | Marquis42 | About 16876, I think we'll need some opinion from someone with more knowledge of the intent of the event subsystem to figure out the right course of action. |
| 23:50.45 | leifmadsen | M16876 |
| 23:50.47 | MuffinMan | [acknowledged] [Asterisk] Applications/app_voicemail/ODBC 0016876: setting pollmailboxes=yes will crash asterisk on startup reported by marcelloceschia https://issues.asterisk.org/view.php?id=16876 |
| 23:51.30 | leifmadsen | Marquis42: huh, good answer. I wonder who would be the best to comment on that. |
| 23:51.41 | leifmadsen | I'm thinking putnopvut potentially |
| 23:52.34 | Marquis42 | Yeah, perhaps. I only bring it up specifically because after tomorrow I'm going to be in the jungle for a couple of weeks. So if you needed anything from me now would be a good time to get it. :) |
| 23:52.44 | leifmadsen | wait, is this ODBC or IMAP? |
| 23:52.57 | leifmadsen | for some reason I thought this was IMAP |
| 23:53.02 | Marquis42 | Neither, necessarily. |
| 23:53.12 | leifmadsen | ah gotcha |
| 23:53.25 | leifmadsen | ok, well we'll see what mark has to say, and if nothing, then we'll find someone |
| 23:53.39 | leifmadsen | tilghman is going to be doing some code review on your XMPP stuff this month, so that might be something to look into |
| 23:53.52 | leifmadsen | Literally in the jungle?! |
| 23:53.53 | Marquis42 | Excellent. I look forward to that. |
| 23:54.00 | Marquis42 | Yes, literally in the jungle. |
| 23:54.04 | leifmadsen | crazy! |
| 23:54.14 | Marquis42 | Well, not the *entire* time I guess. But at least *near* it the entire time (Belize). |
| 23:54.20 | leifmadsen | so ya, when you get back hopefully there will be some stuff for you to work on from the review |
| 23:54.24 | leifmadsen | neato |
| 23:54.31 | leifmadsen | welp, I'm gonna finish getting these release candidates out |
| 23:54.33 | Marquis42 | I'm sure there will be. |
| 23:54.41 | Marquis42 | Ok, take it easy. |
| 23:55.02 | leifmadsen | you too! |
| 23:55.06 | Marquis42 | thanks |