| 01:20.55 | *** join/#asterisk-dev sustav (~vpp@76.73.166.16) |
| 01:21.50 | *** join/#asterisk-dev robl^ (~robl^@pdpc/supporter/active/robl) |
| 04:30.52 | *** join/#asterisk-dev Korolev (~Korolev@c-50-140-71-78.hsd1.fl.comcast.net) |
| 06:47.47 | *** join/#asterisk-dev bulkorok (~bulkorok@85.183.36.36) |
| 08:22.51 | *** join/#asterisk-dev alsuren (~dlaban@80.169.133.251) |
| 09:08.43 | *** join/#asterisk-dev tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 09:08.44 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 10:55.13 | *** join/#asterisk-dev caio1982 (~caio1982@189.125.242.3) |
| 11:09.18 | latv | where can I change Provisional Response keepalive interval, if needed? |
| 11:33.22 | *** join/#asterisk-dev italorossi (~textual@189.124.183.175) |
| 12:00.48 | *** join/#asterisk-dev latv (~latv@109.238.244.73) |
| 12:06.00 | latv | ok, PROVIS_KEEPALIVE_TIMEOUT |
| 13:00.16 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-ablwxinuotoenvyk) |
| 13:18.55 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-czwotforuofgobjp) |
| 13:18.55 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 13:39.17 | wdoekes | leifmadsen, mjordan: agree with paul's assessment that the debug/warning changes should go in trunk only? |
| 13:39.59 | leifmadsen | wdoekes: I guess the question is, "is the way it presents it now a bug?" |
| 13:40.15 | leifmadsen | I'd almost say yes, but mjordan gets final say on that |
| 13:40.15 | wdoekes | no, just an annoyance |
| 13:40.31 | leifmadsen | I think pabelanger is likely right, it's a trunk only thing |
| 13:41.01 | wdoekes | yes.. but paul always leans on trunk, so I'd better get a second opinion ;) |
| 13:41.09 | mjordan | hrm |
| 13:41.12 | mjordan | what issue? |
| 13:41.24 | wdoekes | r2167 |
| 13:43.00 | mjordan | yeah, that's a little tricky |
| 13:43.41 | mjordan | it is technically more an improvement than a bug fix, and while I completely agree that the messages are wonky in the release branches, that doesn't mean that they're actively causing a problem (other than annoyed people and some confusion) |
| 13:43.50 | mjordan | so I'd go with trunk as well |
| 13:43.57 | mjordan | I'm open to counter arguments :-) |
| 13:44.41 | leifmadsen | unless wdoekes wants to actively debate it, I suspect we're mostly in agreement with trunk only :) |
| 13:45.39 | wdoekes | I'd call the cdr_odbc and the rtp-read-too-short a bug, but I'm not splitting the patch in two over those, so I'll go with trunk for the whole thing |
| 13:45.54 | mjordan | kk |
| 13:47.55 | wdoekes | ta :) |
| 13:49.45 | wdoekes | <PROTECTED> |
| 13:49.46 | wdoekes | <PROTECTED> |
| 13:49.48 | wdoekes | <PROTECTED> |
| 13:49.57 | wdoekes | I'm going to go a head and make an ast_debug(2, out of that |
| 13:52.27 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:52.27 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 13:53.02 | mjordan | wdoekes: option_debug > 2 == ast_debug(1,...)? |
| 13:53.11 | mjordan | :-/ |
| 13:53.52 | *** join/#asterisk-dev sustav (~vpp@nat/digium/x-sbnkxdceruleziqy) |
| 13:53.59 | wdoekes | that's the code in trunk |
| 13:54.07 | mjordan | Oh, I believe it. |
| 14:12.18 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 14:12.18 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 15:42.01 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 16:16.30 | *** join/#asterisk-dev caio1982 (~caio1982@189.125.242.3) |
| 16:50.56 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 16:50.56 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 16:59.24 | *** join/#asterisk-dev cklimos (~Claude@209.5.121.227) |
| 17:12.00 | *** join/#asterisk-dev italorossi (~textual@189.124.183.175) |
| 17:16.02 | *** part/#asterisk-dev cklimos (~Claude@209.5.121.227) |
| 19:00.29 | *** join/#asterisk-dev anonymouz666 (~anonymouz@186-241-67-55.user.veloxzone.com.br) |
| 19:22.41 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 19:37.58 | jmls | ASTERISK-16420 |
| 19:38.22 | jmls | oh. what's the magic required to bring up the summary now ? |
| 19:39.13 | jmls | anyways, this is not happening in SVN-branch-11-r374932, so should I close it as I have the power? 8-) |
| 19:39.26 | file | let's see... |
| 19:40.03 | file | it was changed to debug with a level of 6 in 11+ |
| 19:40.09 | file | (thus why you do not see it) |
| 19:40.15 | jmls | yup |
| 19:41.20 | jmls | just wants to do his duty as a bug marshal and close some old .... down |
| 19:41.24 | file | and the code won't do a managed lookup if an IP address anymore, so sure |
| 19:42.00 | jmls | closes his first jira bug :P |
| 19:43.26 | sruffell | jmls: re DAHLIN-304, did you open a ticket with tech support? |
| 19:43.53 | sruffell | (I'm assuming that it's a Digium card you have in the system….) |
| 19:44.06 | jmls | I opened a jira - not the same thing then ? |
| 19:44.10 | jmls | feels stupid now |
| 19:44.23 | jmls | wct410p I beleive |
| 19:45.18 | file | the JIRA you see and have access to is for the projects, not for Digium related stuffage like technical support |
| 19:45.19 | sruffell | heh..no problem. If you open a case at support.digium.com they can check the card out first. |
| 19:47.25 | sruffell | jmls: unless you have any additional information, I'll close the JIRA ticket and you could feel free to send me the support ticket number and I'll check it for you. |
| 19:50.21 | jmls | sruffell: thanks - I can't seem to raise a ticket until I register the card (we bought it about 6 years ago!) and I can't do that until I have a serial number, which means taking the live server offline until I can prise the card out. That won't be for a good week or two ... |
| 19:50.55 | sruffell | :/ yeah…I understand. |
| 19:51.25 | sruffell | Is it in a new server? |
| 19:51.32 | sruffell | or the same server you've had it in for 6 years? |
| 19:52.32 | mjordan | jmls: thanks for closing that :-) |
| 19:56.26 | jmls | sruffell: the same server |
| 19:56.58 | jmls | mjordan: another one bites the dust. Makes up for the two I filed :) |
| 19:57.29 | jmls | well, at least the same server for the last 4 years |
| 19:59.16 | mjordan | woot! |
| 19:59.27 | mjordan | jmls: if you keep yourself at bug level parity, I'd call that a win |
| 19:59.36 | jmls | heh |
| 19:59.57 | jmls | jsmith is in awe of my bug findingness |
| 20:01.46 | jmls | sruffell: do you want me to try break it again ? We're going to move to a xenserver soon, so I will have the server to play with to try and reproduce it and you guys can have a test bed to track things down if you want |
| 20:04.39 | sruffell | jmls: I would like to….but unfortunately I can't spend too much time until the card is confirmed to be a genuine Digium card given the number of clones. Although, if it were me, I would run a bisect to find out when the crashing starts, and since it happens quickly on 2.5.1 that shouldn't take *too* much time. |
| 20:04.47 | sruffell | …for someone who is sitting at the machine. |
| 20:05.45 | jsmith | jmls: Yeah, you're almost as good at finding them as I am :-) |
| 20:10.41 | jsmith | mjordan: If I mark an attachment in JIRA as viewable by "Asterisk Developers", is that just Digium developers? |
| 20:11.08 | jsmith | mjordan: (uploading configs for bug 20227, but there is some sensitive information in there) |
| 20:11.31 | mjordan | jsmith: nope, Asterisk Developers is going to be those with commit access (bug marshals) |
| 20:11.58 | jsmith | OK, how do I mark is as more private than that? |
| 20:12.04 | jsmith | Or can I? |
| 20:12.10 | mjordan | There should be a "Digium Asterisk Developers" |
| 20:13.01 | jsmith | mjordan: Nope -- I see "Asterisk Developers" and "Community Asterisk Developers" and a few other groups, but nothing with Digium in the name |
| 20:13.04 | mjordan | hm |
| 20:13.12 | mjordan | probably because if you attached it, you wouldn't be able to see it :-) |
| 20:13.21 | *** join/#asterisk-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 20:13.21 | *** mode/#asterisk-dev [+o leifmadsen] by ChanServ |
| 20:13.41 | mjordan | I would do Asterisk Developers. We really don't like locking issues down unless there's no other choice, since that limits who can help fix it |
| 20:13.53 | mjordan | but if you really, really, really want us to we can |
| 20:39.15 | *** join/#asterisk-dev acidfu (~inetrio.c@69-196-137-242.dsl.teksavvy.com) |
| 20:45.16 | leifmadsen | basically "go ahead if you want less support" :) |
| 20:56.43 | *** join/#asterisk-dev leedm777 (~Adium@nat/digium/x-rgttxphukcnjhewe) |
| 21:52.55 | *** join/#asterisk-dev marv (~Adium@173-14-206-193-huntsville.hfc.comcastbusiness.net) |
| 21:55.16 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-czwotforuofgobjp) |
| 22:57.47 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 22:57.47 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 23:41.11 | *** join/#asterisk-dev sustav (~vpp@76.73.166.16) |