| 02:10.13 | *** join/#asterisk-dev sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com) |
| 02:57.37 | *** join/#asterisk-dev sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com) |
| 06:25.34 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:b749:768d:ed77:7c9a) |
| 07:05.52 | *** join/#asterisk-dev pchero_work (~pchero@dhcp-077-249-058-090.chello.nl) |
| 07:06.10 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.60) |
| 08:25.58 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 12:42.04 | pchero_work | Hi team, I have a problem with taskprocessor. One of taskprocess doesn't process correctly. So the queued task getting increasing. |
| 12:42.35 | pchero_work | core ping taskprocessor <task id> return 5.0000 second which is timed out. |
| 12:43.01 | file | then you'd need to get a backtrace, find the thread, and determine why it is blocked |
| 12:43.07 | pchero_work | the only 1 taskprocessor has this problem. |
| 12:44.24 | pchero_work | file: \ |
| 12:44.32 | pchero_work | Thank you for answering. :) |
| 12:44.54 | pchero_work | How do I get backtrace? |
| 12:45.10 | file | https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock |
| 12:46.07 | pchero_work | Thanks! Ah⦠it's not possible now, then. I didn't turn on the those options. It's production⦠|
| 12:46.23 | file | depending on how it was built it can still yield info |
| 12:47.29 | pchero_work | okay, I will try it. Thanks! :) |
| 14:06.02 | seanbright | so i think ASTERISK-28426 is invalid |
| 14:06.50 | file | continue! |
| 14:06.52 | seanbright | actually... delay that, i need to look at something |
| 14:07.07 | file | conversation suspended |
| 14:07.24 | seanbright | yes, i am wrong |
| 14:07.41 | seanbright | the address of a struct and the address of its first member are the same, correct? |
| 14:08.37 | file | oui |
| 14:08.44 | seanbright | yeah. k. carry on! |
| 14:09.31 | file | I like trains |
| 14:10.33 | seanbright | that's what i hear |
| 14:17.03 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-dmpkkebnlucdxnvb) |
| 14:17.03 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 14:18.03 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-crwpftuukoxlgqtk) |
| 14:18.03 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:19.54 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.101) |
| 16:30.09 | *** join/#asterisk-dev elguero (~miguel323@74-95-21-41-Connecticut.hfc.comcastbusiness.net) |
| 18:43.03 | seanbright | csavinovich: dumb question that is not directly related to your changes |
| 18:43.36 | seanbright | i assume that a postgres password can contain a space |
| 18:43.50 | seanbright | and maybe the 'application_name' too? |
| 18:45.56 | seanbright | from the documenation it looks like they need to be enclosed in single quotes if they have spaces. probably outside the scope of your patch, however. |
| 18:46.58 | csavinovich | @seanbright, hi Sean. Correct, it is okay if there is a blank after the value, it will be ignored... and the space is necessary if there is an additional value pair added |
| 18:47.34 | seanbright | csavinovich: what i mean is this - if my password is "sean is awesome" this will get rendered: |
| 18:47.45 | seanbright | host=127.0.0.1 user=sean password=sean is awesome |
| 18:47.49 | seanbright | which is clearly wrong |
| 18:47.53 | seanbright | but it was wrong before your patch |
| 18:47.59 | seanbright | so it probably doesn't matter |
| 18:48.02 | csavinovich | @seanbrigth can you use password with blanks on it? |
| 18:48.35 | seanbright | i don't know postgresql well, but i would say 'yes' unless their auth is completely brain dead |
| 18:53.21 | csavinovich | I could add the single quotes but I would have to touch the part where the first connection string is created (this one is reconnect), and just afraid to stir it too much |
| 18:53.40 | seanbright | yes, and you would also have to escape single quotes too |
| 18:53.49 | seanbright | don't worry about. just something that i noticed |
| 18:53.59 | csavinovich | good to know |
| 19:05.03 | seanbright | we should just allow the administrator to set the connection string directly rather than trying to build it ourselves, but whatevs |
| 19:12.09 | *** join/#asterisk-dev CELYA_ (~Thunderbi@lfbn-1-5196-243.w90-105.abo.wanadoo.fr) |
| 19:42.20 | *** join/#asterisk-dev CELYA_ (~Thunderbi@lfbn-1-5196-243.w90-105.abo.wanadoo.fr) |
| 22:07.55 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-ioasmcsfjegchhzr) |
| 22:07.55 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |