| 09:46.32 | *** join/#asterisk-bugs sander4040 (n=sander40@85.149.156.5) |
| 11:45.14 | *** join/#asterisk-bugs zerohalo (n=zeroHalo@pool-72-70-79-233.bstnma.east.verizon.net) |
| 13:04.27 | *** join/#asterisk-bugs blitzrage (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 13:04.27 | *** mode/#asterisk-bugs [+o blitzrage] by ChanServ |
| 14:40.56 | *** join/#asterisk-bugs putnopvut (i=putnopvu@nat/digium/x-1b8720b5586e2178) |
| 14:40.56 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 14:42.47 | *** join/#asterisk-bugs jsmith (n=jsmith@68.178.10.62) |
| 14:42.47 | *** mode/#asterisk-bugs [+o jsmith] by ChanServ |
| 14:46.45 | *** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982) |
| 15:07.28 | putnopvut | M10605 |
| 15:07.29 | MuffinMan | [new] [Asterisk] Applications/app_queue 0010605: 'Unknown' member status in app_queue reported by jfitzgibbon http://bugs.digium.com/view.php?id=10605 |
| 15:07.48 | putnopvut | filesystem: I was wondering if any change made in chan_sip might have possibly fixed this behavior. |
| 15:08.14 | jsmith | All I know is that it's been broken for a while... |
| 15:09.53 | filesystem | not that I can think of |
| 15:13.06 | putnopvut | All right. I'll make a note on the bug to say so, then. |
| 15:27.24 | *** join/#asterisk-bugs jcmoore (n=jcmoore@unaffiliated/tgrman) |
| 15:37.34 | *** join/#asterisk-bugs wunderkin (n=wunderki@ip72-223-86-126.ph.ph.cox.net) |
| 16:24.04 | *** join/#asterisk-bugs fakhir (n=fakhir@unaffiliated/fakhir) |
| 17:56.58 | *** join/#asterisk-bugs Corydon76-home (n=tilghman@pdpc/supporter/bronze/Corydon76-home) |
| 17:56.58 | *** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ |
| 17:58.41 | *** join/#asterisk-bugs Corydon76-dig (i=eleven@pdpc/supporter/bronze/Corydon76-home) |
| 17:58.41 | *** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ |
| 18:12.30 | *** topic/#asterisk-bugs by russellb -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.12 has been released (October 2, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: > 400 :( |
| 18:36.21 | *** join/#asterisk-bugs jsmith (n=jsmith@68.178.10.62) |
| 18:36.21 | *** mode/#asterisk-bugs [+o jsmith] by ChanServ |
| 18:45.43 | russellb | fyi ... 6100 something mantis accounts ... |
| 18:46.37 | *** join/#asterisk-bugs Corydon76-dig (i=four@pdpc/supporter/bronze/Corydon76-home) |
| 18:46.37 | *** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ |
| 18:49.29 | jsmith | russellb: That's good to know |
| 18:51.33 | Juggie | ya, and when you do a search of bugs by reporter |
| 18:51.47 | Juggie | it creates a select box of 6100 members |
| 18:52.21 | russellb | lol |
| 18:52.51 | russellb | jsmith: yeah, i just like to check every once and a while to watch the growth |
| 19:09.28 | *** join/#asterisk-bugs Corydon76-dig (i=one@pdpc/supporter/bronze/Corydon76-home) |
| 19:09.28 | *** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ |
| 20:05.01 | *** join/#asterisk-bugs Corydon76-dig (i=two@pdpc/supporter/bronze/Corydon76-home) |
| 20:05.01 | *** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ |
| 20:06.07 | *** join/#asterisk-bugs Corydon76-home (i=brown@pdpc/supporter/bronze/Corydon76-home) |
| 20:06.07 | *** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ |
| 20:52.38 | *** join/#asterisk-bugs Corydon76-dig (i=pink@pdpc/supporter/bronze/Corydon76-home) |
| 20:52.38 | *** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ |
| 20:53.11 | *** join/#asterisk-bugs Corydon76-home (i=gold@pdpc/supporter/bronze/Corydon76-home) |
| 20:53.11 | *** mode/#asterisk-bugs [+o Corydon76-home] by ChanServ |
| 21:41.36 | *** join/#asterisk-bugs jsmith (n=jsmith@68.178.10.62) |
| 21:41.36 | *** mode/#asterisk-bugs [+o jsmith] by ChanServ |
| 21:58.29 | putnopvut | M8844 |
| 21:58.30 | MuffinMan | [new] [Asterisk] Applications/app_queue 0008844: [patch] In Realtime Queues, dynamic queue members do not always load the members correctly reported by cthorner http://bugs.digium.com/view.php?id=8844 |
| 21:59.06 | putnopvut | Qwell: you made a comment back in July of saying that you didn't think the patch was the right fix. It looks fine to me. Could you explain the problem you had with it. |
| 22:00.30 | Qwell | so, the initial problem that this is trying to solve, has to do with column order |
| 22:02.33 | Qwell | iirc, the problem is that member_name won't necessarily be the first column.. apparently, it could be something else |
| 22:02.44 | putnopvut | Well, see that's what's interesting. |
| 22:02.52 | putnopvut | It's not an issue of column ordering. |
| 22:03.01 | putnopvut | In my setup, I have "interface" as my third column. |
| 22:03.19 | putnopvut | But Asterisk still correctly knows that this is the category for my member configuration. |
| 22:03.43 | putnopvut | It has to do with realtime backends somehow "knowing" what the category name should be for realtime lookups. |
| 22:04.11 | putnopvut | app_queue right now is written under the assumption that the category name for the queue_members table will be the member's interface. |
| 22:04.21 | putnopvut | The reporter pointed out that with res_config_ldap, this is not the case. |
| 22:04.41 | putnopvut | Now I don't know if that means that the issue is in the LDAP realtime backend or in app_queue's assumptions. |
| 22:05.14 | putnopvut | Either way, I'm looking to close this issue out. |
| 22:06.11 | Qwell | so what is ast_category_browse returning? |
| 22:06.13 | putnopvut | The patch works by working around the assumption that the category name will be the member's interface by seeking out the interface variable and using that as opposed to the category name. |
| 22:06.42 | putnopvut | ast_category_browse is (somehow, I'm not sure why) always returning the name of the member's interface. |
| 22:07.00 | putnopvut | Apparently the realtime backend is "smart" enough to know to do that. |
| 22:07.07 | Qwell | isn't that what the interface column contains? O.o |
| 22:07.28 | putnopvut | It is. |
| 22:07.45 | Qwell | so then is ldap not returning the interface? |
| 22:07.47 | putnopvut | But when dealing with realtime, recall that a category is a row of variables. |
| 22:08.13 | putnopvut | I think I'm confusing you. |
| 22:08.27 | Qwell | no, I think I'm remembering why I posted that comment :D |
| 22:36.48 | *** join/#asterisk-bugs miguel3239 (n=elguerom@ns1.nashuacs.com) |
| 22:44.04 | *** join/#asterisk-bugs miguel3239 (n=elguerom@ns1.nashuacs.com) |
| 22:52.55 | *** join/#asterisk-bugs jsmith (n=jsmith@68.178.10.62) |
| 22:52.55 | *** mode/#asterisk-bugs [+o jsmith] by ChanServ |
| 23:05.34 | blitzrage | oh hot idea... you can start and end a conversation relating to a bug on the tracker, where when the discussion is closed, is automatically attached to the bug tracker. Only issue is crosstalk I suppose. |
| 23:05.48 | blitzrage | ~start_8844 |
| 23:05.51 | blitzrage | ~end_8844 |
| 23:06.15 | blitzrage | or you could say: ~convo 8844 prev 10 (lines) |
| 23:07.38 | Qwell | blitzrage: the conversation ended up coming to my office |
| 23:07.48 | Qwell | without that, the above doesn't make a heck of a lot of sense |
| 23:12.26 | putnopvut | blitzrage: that sounds like an interesting idea. Let's get file to add that into MuffinMan! |
| 23:12.48 | Qwell | you guys realize that people will just say random things, in order to get them logged, right? |
| 23:13.07 | Qwell | like... |
| 23:13.12 | Qwell | I like cheddar cheese. |
| 23:13.16 | putnopvut | Yeah, but our administrative god-like powers can erase such garbage from the logs after they're posted. |
| 23:13.49 | putnopvut | I don't like cheddar cheese. |
| 23:13.57 | Qwell | Yes you do. |
| 23:14.00 | Qwell | everybody does |
| 23:26.42 | blitzrage | I prefer havarti |
| 23:35.49 | *** part/#asterisk-bugs zerohalo (n=zeroHalo@pool-72-70-79-233.bstnma.east.verizon.net) |