search for: 19996

Instead of using numeric I created the field "unit_price" as PostgreSQL type money. Now when I try and add a row I get the following. How do I override AR default behaviour to cast numeric post data to money, or am I forced to only support database types that active_record knows about? RuntimeError: ERROR C42804 Mcolumn "unit_price" is of type money but expression is of

...r the ordered probit model, we use beta for the coefficients and tau for the vector of cutoffs, I think they are using beta = (1,.1,-.5), T=100, y* = beta'x + u, sigma(u) = 1, tau = (0, 1, 1.5). (They use 'z' for our y*). When I run this, I get: > summary(posterior) Iterations = 1:19996 Thinning interval = 5 Number of chains = 1 Sample size per chain = 4000 1. Empirical mean and standard deviation for each variable, plus standard error of the mean: Mean SD Naive SE Time-series SE (Intercept) 1.10010 0.1580 0.002497 0.003518 x1 0.09309 0...

...g these into the config files. The names are "matthew" and "serverroom" respecitively. However, Asterisk is throwing up these errors when logged into the asterisk console (using asterisk -r) Connected to Asterisk CVS-HEAD-05/01/04-12:25:43 currently running on asterisk (pid = 19996) May 6 17:18:00 WARNING[-1116775504]: chan_sip.c:492 __sip_xmit: sip_xmit of 0x8de4bec (len 371) to 82.145.32.73 returned -1: Bad file descriptor May 6 17:18:00 WARNING[-1116775504]: chan_sip.c:492 __sip_xmit: sip_xmit of 0x8dd92ec (len 453) to 192.168.1.107 returned -1: Bad file descriptor May...

I apologize for the first message. :) --------------------------------------- I have an FTP server running in the DMZ section of my home network. It uses port 23000 for connection and ports 19990 to 19994 for data transfer. I have setup the following rule for outside people to connect to it: DNAT net dmz:192.168.2.2 tcp 23000 I''m at work right now and I can''t use

Hello everybody, had anyone of you problems with winbind and tdbfiles, when upgrading from 3.0.14a to 3.0.20a? The Symptom was: After upgrading to 3.0.20a the idmapping was corrupt. Although 3.0.20a runs fine, none of the idmaping was resolved correctly. Downgrading to 3.0.14a "restored" the idmaps. tdbdump showed me the same idmappings, therefor i think winbind wasn't able

.../deep_thread_stack.cc -- Exit Code: 1 Command Output (stderr): -- /local/mnt/workspace/draco/compiler-rt/lib/asan/lit_tests/deep_thread_stack.cc:52:11: error: expected string not found in input // CHECK: AddressSanitizer: heap-use-after-free ^ <stdin>:1:1: note: scanning from here ==19996==AddressSanitizer CHECK failed: /local/mnt/workspace/draco/compiler-rt/lib/sanitizer_common/sanitizer_linux_libcdep.cc:244 "((*tls_addr + *tls_size)) <= ((*stk_addr + *stk_size))" (0xf612e030, 0xf612e000) ^ <stdin>:1:7: note: possible intended match here ==19996==AddressSanitizer...

On Thu, May 30, 2013 at 10:05 PM, Greg Fitzgerald <garious at gmail.com> wrote: > The sanitizer common and asan that mention 'thread' are failing for me > this morning. How are your bots looking? Last good commit here was > 512c616cacf70ca029a2bf719a482b902f3687cd. > Hm, our bots seem to be green. Could you refer to guilty svn revision? > > > You could try

The sanitizer common and asan that mention 'thread' are failing for me this morning. How are your bots looking? Last good commit here was 512c616cacf70ca029a2bf719a482b902f3687cd. > You could try preprocessing your report with perl or sed to fix paths > to your binaries. It would be great to have an option for that in > asan_symbolize.py. > > As for addr2line, we just

...-142.598~80-2~2 19990~Well_80-2~6/29/2000 6:00~-142.598~80-2~2 19991~Well_80-2~6/29/2000 7:00~-142.598~80-2~2 19992~Well_80-2~6/29/2000 8:00~-143.360~80-2~2 19993~Well_80-2~6/29/2000 9:00~-143.360~80-2~2 19994~Well_80-2~6/29/2000 10:00~-143.360~80-2~2 19995~Well_80-2~6/29/2000 11:00~-143.360~80-2~2 19996~Well_80-2~6/29/2000 12:00~-144.376~80-2~2 19997~Well_80-2~6/29/2000 13:00~-145.138~80-2~2 19998~Well_80-2~6/29/2000 14:00~-143.360~80-2~2 19999~Well_80-2~6/29/2000 15:00~-145.138~80-2~2 20000~Well_80-2~6/29/2000 16:00~-146.154~80-2~2 20001~Well_80-2~6/29/2000 17:00~-146.154~80-2~2 20002~Well_80-2~6...