similar to: TestableLogger plugin

hello rails folks, i recently launched my first rails based web app at: http://fr.ugali.st/ frugalist is a free service that pulls products from your wishlist(s) at amazon.com and lets you create customizable rss feeds that filter the products on those wishlists based on the criteria you define. for example, i can add all 5 of my amazon wishlists and set up a feed that will show me all

I like the idea of having unit tests make sure what gets logged. I found a plugin called "testable logger" at http://code.teytek.com/rails/plugins/testable_logger/ This promises to do what I''m looking for. But the code itself is not available through the links provided. The author hasn''t responded to my email. Does anyone know an alternative or has a copy of the

On Nov 4, 2019, at 4:00 PM, James Molloy via llvm-dev <llvm-dev at lists.llvm.org> wrote: > We'd be keen to help out what the community decides to do here. I personally feel it's reasonable that: > - LangRef/DataLayout is updated with semantically coherent changes. > - The midend optimizer is updated by someone who cares about those changes and tests are added that use

The path of least effort, as I previously stated, is to use Boehm-GC. Reference-counted smart pointers will require that you implement the reference counting in your language, in the generated code. e.g. a statement such as: p1 = p2 really compiles into: p1.refcount--; if (!p1.refcount) free(p1) p1 = p2 p1.refcount++ If you want your language to be thread-safe, then the increment and

Hi Marti, (Please do not send CC to my private account) Marti Markov <marti1234 at gmail.com> (Mo 21 Nov 2016 03:52:54 CET): > > Here is the router: > > virtual_aliases: ? > hide data = CHECK_VIRTUAL_ALIASES > local_user: > debug_print = "R: local_user for $local_part@$domain" > driver = accept > domains = +local_domains >

Hi again. I've though more about the full standard being too ambitious, and now I fully agree with that. So I had a go at choosing the useful subset of Fortran on which I would like to work on - my update proposal can be viewed at https://gist.github.com/hyp/5434845 . Focusing on less should also improve my productivity and lead to a better summer of code project by drastically reducing the

Thanks for the responses! > I might be wrong (I'd love to be wrong here!) but I think this is a bit > too ambitious > You might be right about it being too ambitious, it would certainly be wise to aim for less. A more polished, but less broad product is definitely better than a buggy standard compliant one, and I think that it would go better with the general philosophy of GSoC. I

On 3/17/20 12:34 AM, Christoph Hellwig wrote: > On Mon, Mar 16, 2020 at 03:49:51PM -0700, Ralph Campbell wrote: >> On 3/16/20 12:32 PM, Christoph Hellwig wrote: >>> Remove the code to fault device private pages back into system memory >>> that has never been used by any driver. Also replace the usage of the >>> HMM_PFN_DEVICE_PRIVATE flag in the pfns array with

Hi Alex, You may want to check the later versions of the standard also to check if some of your proposal is not deprecated there. The most important thing in the Fortran standard is the array support and it is a big task by itself. In my opinion, the I/O part is not the most important thing yet it is an enormous task. Usually, the Fortran routines are used externally in other computation and I/O

We seem to be creating an infinite loop in llvm while trying to implement the simplest possible code generation. Specifically, we are trying to emit code for the following program, as it is easily testable from the command-line: int main(int argc) { return argc; } We got our code generator to build and link with llvm. When we run it, it pauses when running the PrintModulePass and then

On Dec 25, 2014 3:15 PM, "Reindl Harald" <h.reindl at thelounge.net> wrote: > > > Am 25.12.2014 um 21:09 schrieb Benny Pedersen: > >> Robert Schetterer skrev den 2014-12-25 19:49: >>> >>> Am 18.12.2014 um 17:56 schrieb Robin Helgelin: >>>> >>>> We?re using dovecot 1.0.7 >>> >>> that version is total out

----- Original Message ----- > From: "Dmitri Gribenko" <gribozavr at gmail.com> > To: "Alex L" <arphaman at gmail.com> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Monday, April 22, 2013 9:00:51 AM > Subject: Re: [LLVMdev] GSoC project questions. > > On Mon, Apr 22, 2013 at 4:30 PM, Alex L <arphaman

Dear R-users I applied vegan's varpart function to partition the effects of explanatory matrices. Adj. R square for the unique fraction [a] is 0.25. Does anyone know why the decomposition by hand using rda gives me a different result for [a] (constrained proportion is 0.32)? I used cbind() for the conditional fractions, but it should be similar to condition()? Thanks very much

Hi David, On Fri, Nov 6, 2020 at 7:10 PM David Blaikie <dblaikie at gmail.com> wrote: > > The first observation: a significant increase in the byte-coverage statistic, > > meaning that we're able to track variable locations for longer and across more > > code. This was one of the main aims of this work, having better tracking of > > the locations that we know.

On 2020-02-28, James Y Knight via llvm-dev wrote: >Nice! > >Your plan sounds great, and it'll be awesome to finally have a good MachO >LLD available. > >On Fri, Feb 28, 2020 at 4:32 PM Shoaib Meenai via llvm-dev < >llvm-dev at lists.llvm.org> wrote: > >> Hi all, >> >> We’re planning to contribute a new implementation of LLD for Mach-O, using

I just checked in the latest version of my standalone nfsmount program. It works with NFS v2 and v3, UDP and TCP, compiling to 15K on x86. I still need to do some refactoring on ipconfig, nfsmount, and kinit so that they actually work sensibly, which is not quite currently the case. That shouldn't take more than a day, hopefully. By midweek, this should all be in a testable state from an

On Thu, Jan 19, 2006 at 08:38:47AM -0800, Bryan O'Sullivan wrote: > Yes. The code in the klibc tree has been sort of ready for that for > oh, about two years now. Thus far I'm very happy with it. I never originally intended to use klibc but I couldn't get the in-kernel DHCP code to work reliably in some cases and hacking it further didn't seem attractive at the time so I

On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote: > Tested with our custom models (*not* qemu). Could you look into updating qemu as well please? I'd like to make sure patches are widely testable before pushing them, to reduce the chances of finding issues after kernel is released. You can find draft patches for pci and s390 here:

Hi, > QEMU side is still undergoing polishing, but is already testable. Looked art the qemu side for now, commenting here due to qemu patches not being posted to the list yet (guess that is at least partly already on your todo list): * Both legacy and modern should be switchable. Modern needs to be switchable _anyway_ for backward compatibility with old qemu versions. But legacy

On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote: > Tested with our custom models (*not* qemu). Could you look into updating qemu as well please? I'd like to make sure patches are widely testable before pushing them, to reduce the chances of finding issues after kernel is released. You can find draft patches for pci and s390 here: