search for: caed

I think you just attached the wrong (previous) version of the patch. Jean-Marc On 11/28/2017 12:24 PM, Drew Allen wrote: > Done! > > On Tue, Nov 28, 2017 at 12:12 AM Jean-Marc Valin <jmvalin at jmvalin.ca > <mailto:jmvalin at jmvalin.ca>> wrote: > > I only had a quick look, but your patch looks good except for the: >   output[output_rows * i] =

Hi Drew, The float code should also be doing float multiplications. Make sure tmp is an opus_val32 and the multiplication itself casts to float rather than int32. Otherwise, the float version is likely to overflow. Jean-Marc On 11/30/2017 12:06 PM, Drew Allen wrote: > My apologies. I forgot to commit the changes before creating that last > patch. Yes, some in-house control would be good,

Hello, I haven't received a reply since I sent my last logs in, so I thought I'd ask again and update the thread.? I had trouble getting the server to work properly on dovecot 2.3.2 so I rebuilt the server back on 2.2.27.? I've got the quota enforcement itself working, but the warnings still fail to fire. ? I've attached logs with mail_debug=yes for the period from the send which

Hello, Most of the work was done with dovecot 2.2.27 but I just upgraded to 2.3.2 and didn't see any change.? Some debug logs are below, is there something specific I could search them for? Sep 17 23:19:16 ezm11-pco dovecot: auth-worker(8299): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Sep 17 23:19:16 ezm11-pco dovecot: auth-worker(8299): Debug: Module loaded:

I only had a quick look, but your patch looks good except for the: output[output_rows * i] = (1/(32768.f*128.f))*tmp; For floating point, you shouldn't do the >>7 either. Just remove the >>8 from the floating-point calculation of tmp so that all the scaling is done in float. Cheers, Jean-Marc On 11/27/2017 04:01 PM, Drew Allen wrote: > Hi Jean-Marc, > > Attached is

Following the thread from outside, I think Drew should work on in-house quality assurance ;-) > I think you just attached the wrong (previous) version of the patch. > > Jean-Marc > > On 11/28/2017 12:24 PM, Drew Allen wrote: >> Done! >> >> On Tue, Nov 28, 2017 at 12:12 AM Jean-Marc Valin <jmvalin at jmvalin.ca >> <mailto:jmvalin at

In article <201908300952.37126.gary.stainburn at ringways.co.uk>, Gary Stainburn <gary.stainburn at ringways.co.uk> wrote: > On Thursday 29 August 2019 18:10:19 Alexander Dalloz wrote: > > > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's > > > Certificate issuer is not recognized." > > > 2019-08-29 17:23:18,117 retrycode (14)

Dear all, I have this set of data. I would like to sum the EnergykWh according date sequences. > head(dt1,20) StationName date time EnergykWh 1 PALO ALTO CA / CAMBRIDGE #1 1/14/2016 12:09 4.680496 2 PALO ALTO CA / CAMBRIDGE #1 1/14/2016 19:50 6.272414 3 PALO ALTO CA / CAMBRIDGE #1 1/14/2016 20:22 1.032782 4 PALO ALTO CA / CAMBRIDGE #1 1/15/2016 8:25 11.004884 5

I've solely addressed this concern here. Cheers, Drew On Fri, Nov 24, 2017 at 9:15 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Hi Drew, > > I noticed you reverted the > output[output_rows * i] = (tmp + 16384) >> 15; > from the previous patch. That's still good. What should have been > changed is the float version: > output[output_rows * i] =

Hi, I tried this: # extract date from the time stamp dt1 <- cbind(as.Date(dt$EndDate, format="%m/%d/%Y"), dt$EnergykWh) head(dt1) colnames(dt1) <- c("date", "EnergykWh") and my dt1 becomes these, the dates are replace by numbers. dt1 <- cbind(as.Date(dt$EndDate, format="%m/%d/%Y"), dt$EnergykWh) dput(head(dt1)) colnames(dt1) <-

Hi all, This is the data: > dput(head(dt1,20))structure(list(StationName = c("PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE

?s 01:49 de 03/11/2023, roslinazairimah zakaria escreveu: > Hi all, > > This is the data: > >> dput(head(dt1,20))structure(list(StationName = c("PALO ALTO CA / CAMBRIDGE #1", > "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", > "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", > "PALO ALTO

Hello mailinglist, I have a strange problem, which occurs sometimes on some WinXP clients. It is not 100% reproducable for me, but it returns regular. The problem is, that somehow a user can't delete a directory. All files in the directory will be removed successfully, but the directory itself not. Deleting with the Explorer or over the cmd-console returns in the same result. First the

I'm running Debian/Jessie on a server which is used as an AD DC. I'm getting errors like this: Hit http://ftp.ca.debian.org jessie InRelease Hit http://ftp.ca.debian.org jessie/main Sources Hit http://ftp.ca.debian.org jessie/main amd64 Packages Hit http://ftp.ca.debian.org jessie/main Translation-en Err http://ftp3.nrc.ca jessie InRelease Err http://ftp3.nrc.ca jessie-updates InRelease

Is this what you are after? library(tidyverse) library(lubridate) input <- structure(list(StationName = c("PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE #1", "PALO ALTO CA / CAMBRIDGE

How about send a 'dput' of some sample data. My guess is that your date is 'character' and not 'Date'. Thanks Jim Holtman *Data Munger Guru* *What is the problem that you are trying to solve?Tell me what you want to do, not how you want to do it.* On Thu, Nov 2, 2023 at 4:24?PM roslinazairimah zakaria <roslinaump at gmail.com> wrote: > Dear all, > > I

Am 2019-08-29 18:26, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote: >> rpm -Vv nss > > [root at stan2 ~]# rpm -Vv nss > ......... /etc/pki/nss-legacy > ......... c /etc/pki/nss-legacy/nss-rhel7.config > ......... /etc/pki/nssdb > ......... c /etc/pki/nssdb/cert8.db > ......... c /etc/pki/nssdb/cert9.db > ......... c

Aha good point! Im travelling this weekend but will submit another patch Monday morning. Cheers, Drew On Fri, Nov 24, 2017 at 9:15 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Hi Drew, > > I noticed you reverted the > output[output_rows * i] = (tmp + 16384) >> 15; > from the previous patch. That's still good. What should have been > changed is the float

Made a few minor tweaks to your patch (attached). Can you confirm you're OK with those and I haven't missed anything? Cheers, Jean-Marc On 12/04/2017 06:34 PM, Drew Allen wrote: > I've solely addressed this concern here. > > Cheers, > Drew > > On Fri, Nov 24, 2017 at 9:15 AM Jean-Marc Valin <jmvalin at jmvalin.ca > <mailto:jmvalin at jmvalin.ca>>

Done! On Tue, Nov 28, 2017 at 12:12 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > I only had a quick look, but your patch looks good except for the: > output[output_rows * i] = (1/(32768.f*128.f))*tmp; > > For floating point, you shouldn't do the >>7 either. Just remove the >>8 > from the floating-point calculation of tmp so that all the scaling is