| 01:33.19 | *** join/#asterisk-dev droemel (~droemel@p4FCAD3E5.dip.t-dialin.net) |
| 03:44.51 | *** join/#asterisk-dev mjordan (~mjordan@wsip-184-179-108-66.sd.sd.cox.net) |
| 03:44.51 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 06:25.39 | *** part/#asterisk-dev tm1000 (tm1000@2600:3c01::f03c:91ff:fe70:fce6) |
| 06:28.13 | *** join/#asterisk-dev tm1000 (tm1000@2600:3c01::f03c:91ff:fe70:fce6) |
| 07:00.10 | *** join/#asterisk-dev bulkorok (~bulkorok@85.183.36.36) |
| 07:34.00 | *** join/#asterisk-dev schmidts (~schmidts@vie-91-186-159-076.dsl.sil.at) |
| 07:34.02 | schmidts | good morning |
| 07:34.53 | *** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net) |
| 07:34.54 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 08:11.30 | *** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net) |
| 08:11.31 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 11:20.58 | leifmadsen | schmidts: morning |
| 12:38.33 | *** join/#asterisk-dev bulkorok (~bulkorok@85.183.36.36) |
| 12:53.38 | *** join/#asterisk-dev italorossi (~italoross@187.60.66.11) |
| 12:55.11 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-mdwbojvsypnnaiho) |
| 13:11.27 | *** join/#asterisk-dev bobse (53e91504@gateway/web/freenode/ip.83.233.21.4) |
| 13:39.52 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:39.52 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 13:40.04 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:29e7:b75f:6641:5a1a) |
| 13:57.37 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:29e7:b75f:6641:5a1a) |
| 14:09.34 | *** join/#asterisk-dev serafie1 (~erin@24.214.158.242) |
| 14:13.56 | *** join/#asterisk-dev italorossi (~italoross@187.60.66.11) |
| 14:20.25 | file | leedm777, <3 |
| 14:20.36 | leedm777 | blushes |
| 14:49.47 | file | VP8. Discuss. |
| 14:56.30 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 14:56.30 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 15:04.01 | jsmith | file: Still too early to tell what the fallout will be. That's my opinion, and I'm sticking to it |
| 15:04.16 | file | truth |
| 15:55.18 | *** join/#asterisk-dev rgagnon (~rgagnon@71.42.183.54) |
| 15:55.22 | *** part/#asterisk-dev rgagnon (~rgagnon@71.42.183.54) |
| 16:02.11 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 16:03.20 | leifmadsen | pjsip is on the VUC today |
| 16:31.28 | *** join/#asterisk-dev kesselklopfer79 (~kesselklo@astaro.starface.de) |
| 16:57.24 | *** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
| 16:57.24 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 17:52.00 | file | Woot a ship it |
| 18:41.17 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-penkqoyznfpewwcf) |
| 19:29.16 | *** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net) |
| 19:29.17 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 19:35.13 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 19:35.13 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 19:48.26 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 19:48.26 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 20:28.40 | *** join/#asterisk-dev bobse (53e91504@gateway/web/freenode/ip.83.233.21.4) |
| 20:29.08 | *** join/#asterisk-dev paravoid (~paravoid@scrooge.tty.gr) |
| 20:29.20 | paravoid | hello |
| 20:29.48 | paravoid | so an issue of mine, ASTERISK-21234, was marked as a clone of ASTERISK-21308 |
| 20:29.50 | LieutPants | [ASTERISK-21234] [Status: Open] [Assigned: paravoid] Deadlock when using two Local channels & fax gateway (local_queryoption) - https://issues.asterisk.org/jira/browse/ASTERISK-21234 |
| 20:29.56 | paravoid | when I try to access the latter though |
| 20:30.01 | paravoid | I get redirected to SWP-5577 |
| 20:30.06 | paravoid | and then get a permission violation |
| 20:32.14 | file | SWP-5577 is an internal Digium planning issue |
| 20:32.39 | paravoid | what is ASTERISK-21308 then? |
| 20:33.04 | file | ASTERISK-21308 was a temporary issue created as a result of creating SWP-5577 |
| 20:33.12 | paravoid | um |
| 20:33.14 | paravoid | okay |
| 20:33.17 | file | your issue was cloned to ASTERISK-21308 and then moved to the SWP project |
| 20:33.18 | paravoid | confusing |
| 20:33.42 | paravoid | in order to plan for it internally? |
| 20:33.47 | file | yes. |
| 20:34.00 | paravoid | I mean, I don't care about the bug that much, it's a corner case that's easily workaroundable |
| 20:34.09 | paravoid | I was just confused about the process |
| 20:36.46 | paravoid | thanks :) |
| 20:37.06 | file | eventually, hopefully, we won't have to do that and it'll just be done on the main issues without anyone knowing |
| 20:39.16 | paravoid | or have the internal digium planning in public :) |
| 20:39.22 | paravoid | maybe I'm just too spoiled :) |
| 20:41.09 | file | yeah, no |
| 20:41.10 | file | :P |
| 20:42.44 | *** join/#asterisk-dev zerohalo (~zerohalo@74.61.196.236) |
| 20:47.02 | leifmadsen | what file said |
| 20:47.12 | leifmadsen | paravoid: you aren't missing any information |
| 20:47.29 | paravoid | no worries |
| 20:47.47 | paravoid | and thanks again |
| 20:50.46 | bobse | Hi! My name is Robert and I am new to asterisk-dev. I was looking at cel_pgsql and found several issues with the code and I am trying to fix it (it still is a work in progress but I have it working on my test system). There are some asterisk specific things that I would like to discuss with someone. The first thing has to do with AST_RWLIST. Someone wants to help me? |
| 20:51.17 | file | if you ask questions individuals in here may answer |
| 20:52.23 | bobse | Thank you, file. |
| 20:55.41 | bobse | In cel_pgsql, line 162 AST_RWLIST_RDLOCK is called before AST_RWLIST_TRAVERSE. While it makes sense in other places the linked list in this file is created when the module is loaded and is only read from after that. Is it sill necessary to lock the list before traversing it? |
| 20:57.14 | file | the module can be reloaded probably, in which case yes |
| 20:59.54 | bobse | You mean that if the module is reloaded, it is possible for multiple instances of the module to access the same memory at the same time? |
| 21:00.19 | file | well, there's only a single "instance" shared across the entire process so multiple threads may try to access it, yes |
| 21:05.12 | bobse | Ok, now I see it. When the module is reloaded it is actually not flushed from memory and reloaded, it just reinitializes the instance that was already loaded. |
| 21:08.06 | bobse | I just realized there are more issues with the old code...I will try to address that too. |
| 21:11.31 | bobse | Thank you for your help. I will come back later. |
| 21:12.20 | file | good luck |
| 22:38.57 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 22:38.57 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 22:45.09 | *** part/#asterisk-dev kharwell (~kharwell@nat/digium/x-dzpadvpbaeaaljpv) |
| 23:32.17 | *** join/#asterisk-dev pabelanger (~pabelange@asterisk/contributor-and-bug-marshal/pabelanger) |
| 23:32.17 | *** mode/#asterisk-dev [+o pabelanger] by ChanServ |
| 23:58.23 | *** join/#asterisk-dev serafie (~erin@24.214.158.242) |
| 23:58.52 | *** part/#asterisk-dev paravoid (~paravoid@scrooge.tty.gr) |