John,
I'm going through and trying to fix all the places where storage breaks the
functional test. I'd like to work at these issues with you, if you don't
mind. We can do it in the forum, or through email.
In any case, here's one. the failing test_pause_workers in ft_0_worker.rb.
It fails because at
@dashboard.context['worker_state_enabled'] = true
In the code context code the method []= looks for the engine configuration,
and if it finds it, it adds this worker_state_enable = true to the
document. If it can't find the engine, get_conf returns an empty hash: {}.
And attempts to save the empty has in the storage mechanism. With means,
outside of a document type (like, configurations, or msgs). (So, Dynamo DB
fails, because there is no ide key, but that problem I can deal with).
Looking closely, though, saving this to the storage also means placing a
document in the storage that doesn't even have a type. That's strange.
Does this make sense? And is this what Ruote is supposed to be doing?
Chad
On Thursday, August 9, 2012 6:29:49 PM UTC-4, John Mettraux wrote:
>
>
> On Thu, Aug 09, 2012 at 03:08:23PM -0700, Chad wrote:
> >
> > My company has allowed me to opensource my DynamoDB ruote storage
> > implementation.
> >
> > The code is on github: https://github.com/mdsol-share/ruote-dynamo
> >
> > It's rough, and not production ready, sort of a port of ruote-sequel,
> with
> > DynamoDB calls. It's not currently passing ruote's extensive unit
> testing
> > suite. But it's probably 90% there. I have no ETA on when it will be
> > finished.
> >
> > Contributions, help, advice, and code reviews are greatly appreciated.
>
> Excellent!
>
> I've added a link to it on
>
> http://ruote.rubyforge.org/source.html
>
>
> Many thanks!
>
> --
> John Mettraux - http://lambda.io/jmettraux
>
>
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
