| 03:42.33 | *** join/#asterisk-dev electronic_eel_ (~quassel@213.240.182.141) |
| 15:12.03 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-taohyhhepqwcoect) |
| 15:12.03 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:37.24 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-rpkhlpfohxzloxvd) |
| 15:37.24 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 16:49.41 | *** join/#asterisk-dev pchero (~pchero@211.178.226.108) |
| 16:49.41 | *** mode/#asterisk-dev [+o pchero] by ChanServ |
| 17:38.35 | kharwell | A deadlock's been reported on https://issues.asterisk.org/jira/browse/ASTERISK-29286. After looking into it it appears it might be a bug in pjsip itself. Anyone else have thoughts about that before I tell the reporter to create a ticket in pjproject's tracker? |
| 17:38.50 | kharwell | Or does it seem more like one we might want to investigate further? |
| 17:40.06 | kharwell | (I commented with my findings on the issue) |
| 17:40.06 | file | I think us |
| 17:41.18 | file | seems like something we should care about |
| 17:42.19 | kharwell | okay so probably a pjproject bug, but something we'd want addressed sooner than later? |
| 17:43.02 | file | yes, our threading model also makes stuff like that sometimes unique to us |
| 17:43.35 | kharwell | Should I suggest they report it to pjproject too as they might fix it before we do? |
| 17:43.52 | file | wouldn't hurt |
| 17:44.05 | kharwell | alrighty thank ya |