search for: upstream

...esiduals between the blue circles and green squares by adjusting the limits of the secondary y-axis. Thanks, Eric library(zoo) temp.dat<-read.table(textConnection("Well Meas_Date WTD ECgw GW_Project_Area Region Avg.EM.Survey.Value Avg.Soil.Paste.EC SD_EM_Survey 1 4/12/1999 1.75 2.27 LOWER-UPSTREAM US NA NA NA 1 5/11/1999 1.24 5.04 LOWER-UPSTREAM US NA NA NA 1 5/27/1999 1.27 4.45 LOWER-UPSTREAM US NA NA NA 1 6/3/1999 1.27 4.09 LOWER-UPSTREAM US 3.347069 3.126667 0.6347013 1 6/11/1999 1.52 2.84 LOWER-UPSTREAM US NA NA NA 1 6/18/1999 1.19 2.34 LOWER-UPSTREAM US NA NA NA 1 6/24/1999 1.21 2.48 LO...

..."? I'm guessing there is a function to do this? Thanks, Eric library(zoo) #example data and plotting commands follow temp.dat<-read.table(textConnection("Well Meas_Date WTD ECgw GW_Project_Area Region Avg.EM.Survey.Value Avg.Soil.Paste.EC SD_EM_Survey 1 4/12/1999 1.75 2.27 LOWER-UPSTREAM US NA NA NA 1 5/11/1999 1.24 5.04 LOWER-UPSTREAM US NA NA NA 1 5/27/1999 1.27 4.45 LOWER-UPSTREAM US NA NA NA 1 6/3/1999 1.27 4.09 LOWER-UPSTREAM US 3.347069 3.126667 0.6347013 1 6/11/1999 1.52 2.84 LOWER-UPSTREAM US NA NA NA 1 6/18/1999 1.19 2.34 LOWER-UPSTREAM US NA NA NA 1 6/24/1999 1.21 2.48 LO...

...f the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git mirrors only contain what's in trunk in the SVN repos. I think it contains branches of several previous releases: $ git branch -r llvm-upstream/master llvm-upstream/release_1 llvm-upstream/release_16 llvm-upstream/release_20 llvm-upstream/release_21 llvm-upstream/release_22 llvm-upstream/release_23 llvm-upstream/release_24 llvm-upstream/release_25 llvm-upstream/release_26 llvm-upstream/release_27 llvm-upstream/release...

...ectionf <- factor(Section) > startd=as.Date(startdate, format="%d/%m/%Y") > lm.r <- by(master, list(Sectionf=Sectionf, startd=startd), function(x) lm (tot.c ~ starttime, data = x)) Data: "Section","starttime","startdate","tot.c" "Upstream",0,04/09/09,0.17 "Upstream",0,04/09/09,0.19 "Upstream",0,04/09/09,0.14 "Middle",0,04/09/09,0.2 "Middle",0,04/09/09,0.13 "Middle",0,04/09/09,0.11 "Downstream",0,04/09/09,0.16 "Downstream",0,04/09/09,0.17 "Downstream&quot...

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

Hi folks, From the roadmap for Xen 4.3 development, Xen 4.3 will use upstream QEMU (partially done). So I''d like to confirm the following questions. 1. Will Xen 4.3 really use upstream QEMU by default ? I have the question because so far the xen.git tree still uses qemu-xen-unstable by default. 2. If ''yes'' for 1st question, which QEMU upstream...

Processing commands for control at bugs.debian.org: > tags 496359 secuirity Unknown tag/s: secuirity. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore. Bug#496359: The possibility of attack with the help of symlinks in some Debian packages There were no tags set. Tags added: > tags 496360 secuirity Unk...

...database i noticed that my process was running multiple times!. Looking at the nginx error logs below, I noticed that nginx restarted the same call couple of times on a different mongrel after each timeout. I had to kill the nginx processes to stop it all. 2007/08/14 22:18:40 [error] 1720#0: *129 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.102, server: factory, URL: "/opening_balance/post", upstream: " http://127.0.0.1:8013/opening_balance/post", host: "rs" 2007/08/14 22:19:40 [error] 1720#0: *129 upstrea...

Hi, We would like to upstream exception handling support for Windows on ARM64. Microsoft-published specifications can be found here: a) https://docs.microsoft.com/en-us/cpp/build/arm64-exception-handling b) https://docs.microsoft.com/en-us/cpp/build/arm64-windows-abi-conventions We propose the following approach: 1...

Processing commands for control at bugs.debian.org: > tags 430778 + upstream Bug #430778 [xen-utils-common] xen-utils-common: NAT scripts not generic enough, and made for DHCP ? Added tag(s) upstream. > tags 430676 + upstream Bug #430676 [xen-utils-common] xen-utils-common: network-nat creates insecure nat POSTROUTING MASQUERADE ? Added tag(s) upstream. > tags 603366...

Hi All, We did some testing for Xen-unstable tree with upstream QEMU. We covered basic guest booting up, power management, VT-d, SR-IOV features. We found 4 new bugs which only exist in upstream QEMU not in qemu-xen. We followed the below wiki page to use upstream QEMU. http://wiki.xen.org/wiki/QEMU_Upstream test tree: xen-unstable-tree.hg: C/S 26193 (about 2...

...infrastructure) use the git >> mirrors exclusively, aside from git-svn for committing. >> >> I believe the idea is to continue to maintain the read-only independent >> git repos for each project. The only change is instead of sourcing those >> commits from the official upstream(independent) svn repos, they will be >> sourced from the official upstream monorepo. >> >> Thus downstream developers can continue to use the read-only view of >> the independent projects if that is easier for them; but people hacking >> on llvm/clang itself get the be...

On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote: > On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server. While I agree bootstrapping a new mirror from scratch is time and resource consuming,

...39;ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices here or these are just genuine mistakes. Anyway here are the ones I saw in passing. ``` /home/dsl11/dev/llvm-upstream/src/lib/MC/MCParser/DarwinAsmParser.cpp: In member function ‘bool {anonymous}::DarwinAsmParser::parseVersionMin(llvm::StringRef, llvm::SMLoc)’: /home/dsl11/dev/llvm-upstream/src/lib/MC/MCParser/DarwinAsmParser.cpp:962:3: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] if...

...inbound calls to DIDs which are assigned to us by our wholesaler but not yet assigned to a downstream customer get caught in a routing loop. ** For example: we get assigned DID block 1230-1239 and only 1230-1233 are given to our customers, then our routing logic sends inbound calls to 1234 back to upstream, which bounce back to us again, tying up all our trunks before emitting an error. When we recognized the problem I automatically added ael commands to route all known unassigned numbers to a friendly error message, but that is a clumsy approach and the larger issue remains that if we get routed a...

Hi! > Reassigning to Debian Xen team, since I that makes more sense. We > totally missed this on our (release) radar. > > And indeed, we're shipping the upstream completion file now. Adi, I see > how you're improving it, and I like it. I'm happy you like it... > So, we should probably ship this instead, but at the same time, the > right (tm) place to move this is upstream. We're activetly trying to get > rid of "adjusted copie...

...or further investigation. (I omitted it to avoid manually packaging a whole set of object files - I think --reproduce=<repro> doesn't work on Windows yet). For reference, here's the segfault: #0 0x0000000000500999 llvm::sys::PrintStackTrace(llvm::raw_ostream&) /ssd2/pirama/ll$ m-upstream/llvm/lib/Support/Unix/Signals.inc:488:11 #1 0x0000000000500b49 PrintStackTraceSignalHandler(void*) /ssd2/pirama/llvm-upstream$ llvm/lib/Support/Unix/Signals.inc:552:1 #2 0x00000000004ff1d6 llvm::sys::RunSignalHandlers() /ssd2/pirama/llvm-upstream/llvm$ lib/Support/Signals.cpp:66:5 #3 0x000000000050...

I owe you a gala dinner at your favorite restaurant. Really. A few questions: Why did you 'git pull --rebase' when the branch was up-to-date? Is this just a safety habit? I don't understand the pushing upstream. Since we use Phabricator, isn't that the job of the person who commits the patch? Does git keep all my branches up-to-date with the origin? Say I come in tomorrow and start working on a branch. Should I make sure I do a checkout on it again? Is it sufficient to do a 'git show' and su...

...k-policy drop #set require-order yes ############ SHAPING goes here ############################### altq on $intif cbq bandwidth 100Mb queue {etherdown, downstream} queue etherdown bandwidth 96% cbq(default) queue downstream bandwidth 4% cbq altq on $extif cbq bandwidth 100Mb queue { etherup, upstream} queue etherup bandwidth 99Mb cbq(default) queue upstream bandwidth 386Kb cbq pass in quick on $intif from 172.16.0.0/16 to 172.16.0.0/16 queue etherdown pass out quick on $intif from 172.16.0.0/16 to 172.16.0.0/16 queue etherup pass in on $intif proto tcp from 172.16.0.0/16 to any port 80 keep...

Hi all, I talked to our oVirt developers who use CentOS for upstream development. And that's what makes their lives hard because it takes a long time before they can start using new features of libvirt. The latest released CentOS version is 7.2 with libvirt 1.2.17, which is pretty old. But even when CentOS 7.3 with libvirt 2.0.0 gets released, it will already be...