search for: traceability

...s.to_xml } end end def show @bakery_output = BakeryOutput.find(params[:id], :include => [:recipe]) @recipe = @bakery_output.recipe @ingredients=@recipe.ingredients.find(:all) respond_to do |format| format.html # show.rhtml format.xml { render :xml => @traceability.to_xml } end end end Views The Index view show the list of recipes with a link called ingredients beside each one. Clicking on the link takes the user to the show method of the controller. The show view displays a list of ingredients for that recipe. I have got this working so far. I now wa...

hello, if i load the RSQLite package in addition to the RPostgreSQL package, i get various errors when trying to use RPostgreSQL functions. here is an example transcript showing one such error: ========================================================== R version 2.15.0 (2012-03-30) [...] > packageVersion('RPostgreSQL') [1] 0.3.2 > packageVersion('RSQLite') [1] 0.11.1

On Thu, Oct 5, 2017 at 6:06 AM, Steven Rostedt <rostedt at goodmis.org> wrote: > On Wed, 4 Oct 2017 14:19:56 -0700 > Thomas Garnier <thgarnie at google.com> wrote: > >> When using -fPIE/PIC with function tracing, the compiler generates a >> call through the GOT (call *__fentry__ at GOTPCREL). This instruction >> takes 6 bytes instead of 5 on the usual

On Thu, Oct 5, 2017 at 6:06 AM, Steven Rostedt <rostedt at goodmis.org> wrote: > On Wed, 4 Oct 2017 14:19:56 -0700 > Thomas Garnier <thgarnie at google.com> wrote: > >> When using -fPIE/PIC with function tracing, the compiler generates a >> call through the GOT (call *__fentry__ at GOTPCREL). This instruction >> takes 6 bytes instead of 5 on the usual

Hi, I am tracking down a problem and would like to know how I can follow a forked process with my dtrace script, or how I can trace a dynamic library. Here is the problem. I am tracing dtlogin, and specifically I am trying to determine what error libpkcs11`<routine> is returning. It turns out dtlogin forks a lot of processes, and I believe the second forked process is the one that winds

...urrent Location: Ready for Relocation: Rate: Total IT Exp: Total US Exp: SR QA Lead Exp: Quality Center Exp: Training, mentoring, and coaching Exp: Quick Test Professional (beyond "record and playback") Exp: Performance testing using Load Runner Exp: QA metrics reports Exp: Traceability matrices Exp: QTP Exp: Load Runner Exp: *Job Description:* We have a position opening for Sr. QA Lead Analyst. Consultant will be working on CAI Project Location of the Project is Owing mills, MD. Rate we are getting is $ 75/H (Some expenses will be paid) Hands on Senior/Lead QA Analyst...

My company is trying to manage R installations across a number large SMP machines. We're thinking out the best way to manage the packages installs and updates. They would be happy if we could work out RPM's for package installations (traceable, easily facilitated with existing sw management tools). I don't know a lot and RPMs beyond how to use them, but it seems plausible to write R

I have an environment consisting of: * Primary Workstation running Win2KPro * Secondary Workstation runing WinNTSP6a * Local Win2K Advanced Server * Local Solaris 8 system with Samba 2.0.7 * Remote HP-UX system at Site A with Samba 1.9.18p10 connected via VPN * Remote Unixware system at Site B with Vison(?) file sharing connected via VPN * Three remote Win2K server boxes at Site C connected via

...3. Would you like me to backport that? One thing that we need to remember is that every commit message on branches/Testing should refer back to one (or more) changesets in the trunk. Otherwise, it is next to impossible to figure out which changes still need to be merged. Another reason for this is traceability - if we don't know that a change on branches/Testing has actually been kicking around on the trunk for a while (at the very least, it should be run through buildbot, or be built on another developer's machine), then there is little reason to maintain the Testing branch (and I do think it he...

...owing works fine : /usr/local/bin/rsync -artlDPpv --acls /var/log/gdm /tmp However, when i try to backup a remote system i recieve some errors: /usr/local/bin/rsync -AaPv --delete --numeric-ids --rsh=/usr/bin/ssh --link-dest=/var/backups/trace/hourly.1/Data/ root@192.168.6.12:"/var/shares/Traceability/Trace\ V114/data/" /var/backups/trace/hourly.0/Data/ rsync: on remote machine: -vlAogDtpr: unknown option rsync error: syntax or usage error (code 1) at main.c(1084) rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (c...

...ed impact, and a larger issue that would affect a lot of people (the NSS bug). While I think that monotonic clocks are the right solution for polling timers in the long term, I would be surprised if a lot of NUT installations worry about time going backwards, since that has big implications for log traceability. I am prepared to suggest releasing 2.7.3 with the NSS bug intact, since it fails safe (although useless) and can be worked around with configuration (run upsd in foreground). Documenting the handling of non-monotonic time as a known bug (with a simple patch tested on Linux) is perhaps not equival...

On Thu, Jan 30, 2020 at 04:16:09PM +0100, Martin Kletzander wrote: > I know this probably got answered somewhere, but I've never gotten > any when asking myself. So let me use this opportunity. > > Because I really despise useless processes and duplicated > information I always hated the way all the "mandatory" file headers. > As far as I understand it's

Well, after many months of effort, my LLVM-based garbage collector is finally passing its unit tests. This represents a significant milestone for me in the development of my programming language, Tart. The collector itself is fairly rudimentary - a single-generation, copying collector. It does not yet support multi-threaded programs, but in practice there's no serious obstacle to supporting

Gordon Henriksen wrote: > Hi Mark, > > I don't think anyone will dispute that it's easier to hack up a shadow > stack (or plug into a conservative collector) to get up and running > with GC. That is absolutely the route to go if portability trumps > performance. Why? LLVM is all about portability AND performance. > > If you review the mailing list history,

Excuse dopey question. I'm not exactly clear about certificates. Apache2 default install has this snake oil certificate Can make a new one for apache Can make one for dovecot Can make one for ssl Is there supposed to be the one (self signed ) certificate pair in one place for the machine that each process hands out ? Can they be moved to another machine ? mick -- Key ID C7D6E24C

On Thu, Jan 30, 2020 at 08:16:30AM -0600, Eric Blake wrote: > On 1/30/20 8:05 AM, Richard W.M. Jones wrote: > >Fast testing whether the AIO buffer (or regions within it) contain all > >zeroes, which allows Python code to quickly do sparsification when > >copying. > > > >This includes the iszero.h header from nbdkit which is distributed > >under a compatible

SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't

Good Day all, I have a Fractional PRI connected to my Asterisk Box via a T100P card. When I initiate a call out to phone number 123-8888 the call sounds great no echo what so ever. If the person at 123-8888 hangs up and calls me right back (same handset on both sides) same trunk line The call always has echo on it. The Asterisk sip extension hears them selves echoing. The remote party

On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net> wrote: > > SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP > DL360p gen8, two six-core Thuban-II workstations plua their monitors, > and the network stack and KVM. > > The APC SU3000RM (3KVA) that blew up last week considered this to be > just short of 60% load. > The new

On Wed, 4 Oct 2017 14:19:56 -0700 Thomas Garnier <thgarnie at google.com> wrote: > When using -fPIE/PIC with function tracing, the compiler generates a > call through the GOT (call *__fentry__ at GOTPCREL). This instruction > takes 6 bytes instead of 5 on the usual relative call. > > With this change, function tracing supports 6 bytes on traceable > function and can