search for: l747

..._units(1:10, ?m)' #> Error: unexpected input in "units::set_units(1:10, ?" #> Execution halted However, if you use the first version, with quotes, in an example, and the package is checked on Windows, it fails too (see https://ci.appveyor.com/project/edzer/units/builds/22440023#L747). The package declares UTF-8 encoding, so none of these errors should, in principle, happen. Am I wrong? Thanks in advance, regards, I?aki

...ease() at testthat/test-scheduling.R:13 3: private$callback() 4: self$protect({ task() }) 5: private$refCount$release() 6: private$callback() 7: self$protect({ task() }) 8: force(expr) You can see complete logs on Travis here: https://travis-ci.org/rstudio/pool/jobs/217301804#L747-L771 In the test, a re-entrant function is called (self$protect, at levels 4 and 7 on the call stack), and in the inner call (7), a variable, `task`, does not have the correct value. It should be a function, but it isn't; it's either NULL or some other non-function value. That code is her...

...gt; Error: unexpected input in "units::set_units(1:10, ?" > #> Execution halted > > However, if you use the first version, with quotes, in an example, and > the package is checked on Windows, it fails too (see > https://ci.appveyor.com/project/edzer/units/builds/22440023#L747). The > package declares UTF-8 encoding, so none of these errors should, in > principle, happen. Am I wrong? > > Thanks in advance, regards, > I?aki > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/l...

Hi to all, The doc is telling me: ------------------------ To guarantee crash consistency some of the fops are blocked during a snapshot operation. These fops are blocked till the snapshot is complete. All other fops is passed through. ----------------------- I could not find which fops are blocked, can anyone tell me wich fops are blocked and wich are not? Second question: Is there a way to

...to block all the ops that modify the underlying file system from acknowledging the client. The list of file system operations that needs to be blocked should be listed here <https://github.com/gluster/glusterfs/blob/87ec6483324d76071f27cfa83e0a644e4a38ec41/xlators/features/barrier/src/barrier.c#L747-L761> . WARNING: My knowledge is like a decade old. This information is to the best of my memory. A very brief quick look at the git log of xlators/barrier tells me no major changes. So, in any case I would just read the code for barrier translator unless the current maintainer can answer this...

...() > 4: self$protect({ > task() > }) > 5: private$refCount$release() > 6: private$callback() > 7: self$protect({ > task() > }) > 8: force(expr) > > You can see complete logs on Travis here: > https://travis-ci.org/rstudio/pool/jobs/217301804#L747-L771 > > In the test, a re-entrant function is called (self$protect, at levels > 4 and 7 on the call stack), and in the inner call (7), a variable, > `task`, does not have the correct value. It should be a function, but > it isn't; it's either NULL or some other non-function...