labofsahil/github-event-dataset-2012 huggingface dataset:
If we're using openmrs:message, the minimum requirement needs to be set to 1.8.4 or 1.9.1
Done, ticket is HLQRY-52
And i left that comment there to address precisely that.

Sorry, the test does run indeed. But it runs fine because of the bug described in 2610 ;) where we mapped Map to headers regardless of its types or the fact that the payload was already set.  And we did discuss on the very first call that all we need to do fix it is to check if the payload was already set via expression. 
Also, you can write another test against the master where your expression will be #args[0] and with that you'll get the duplication case which i've eliminated with that. 
Personally although I agree that this is a regression, I am 100% sure that it was not intentional giving the fact that we didn't have such test in the first place.
The real question here is the single argument method rule because we keep dancing around it while discovering more and more issues with the current state of mapping. This at least brings some consistency to what we currently have and that is - Single argument is always a payload unless expression already set the payload since expression takes precedence. And since first argument is ALWAYS a payload no conventional mappings will be attempted the payload. As to headers, based on the previous rule this argument could never be applied to headers and therefore will not be taken into account for conventional mapping anyway. 

If you still want take some of the parts of this argument and map it to headers than you can use header expressions to do that.
This test needs to be here and in line 36 because we need to handle to case where a reminder query question is set before the hook has been deployed. And we need to set hasCustomQuestion to false.
"фичи" звучит много понятней, но не по-русски :)
isset() is substantially faster than array_key_exists() ... and this function may get called a few times in an execution cycle.  Might consider changing it.
Ahh, yes. Good catch on ```CollectionView```.

Correct me if I'm wrong, but when specifying the ```itemView```, it's a reference to the view type and not an instance, right?
I'll merge for now -- it's not a big deal. You can add the option when you return on Saturday.
typically (in OpenMRS) we import Assert then reference the methods on it as Assert.assertNull() ... not sure why we do it that way, but just remember this for if/when you work on some core tests. :-)
what is a real thing?

On Thu, Nov 1, 2012 at 2:57 PM, Walt Askew <notifications@github.com> wrote:

> In providers/app.rb:
>
> > @@ -86,7 +86,23 @@
> >          end
> >
> >      end
> > -    Mustache::template_path = ::File::join(version_dir, 'gbtemplate')
> > +
> > +    context = node.to_hash
> > +
> > +    gearbox_data_bag = data_bag_item('gearbox', name)
> > +
> > +    (gearbox_data_bag['searches'] || []).each do |search|
> > +            matching_nodes = search(:node, "roles:#{search['role']} AND chef_environment:#{node.chef_environment}")
> > +            results = matching_nodes.map do |result|
>
> I think this is a real thing, though.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/NarrativeScience/gearbox-cookbook/pull/3/files#r2009392>.
>
>



-- 
Tom Howe
Senior Software Engineer
Distributed Systems Lab
University of Chicago/Argonne National Laboratory
verify links are the links passed in. (may be able to replace any(List.class) with links.
I was just thinking that it would be a more correct version?
will rename to communityUtil
> But then we need to talk about parameter value and property value and that's not what we want as we don't annotate values.

Ah, I see where are you coming from.

When speaking about the "return type" of a method `String foo() { ... }`, so far I would have had the definition of the type `String` in mind (which is not annotated here), but here "return type" refers to the usage of the type `String` in the method definition of `foo()` (which is annotated). Makes sense, I guess.
Mmm...well, @jmcanterafonseca i don't think so, we must show the exact examples provided by UX teams.
Anyone could extend this, is not that hard i think
"twitter": "_h4_"
Not quite sure which empty raise you are talking about, but I wouldn't think so. Should be a problem with a DLL probably.
Removed in last checkin.
Maybe it should be explained that the Dragonfly build that's to be tested doesn't need to have a host connected to it, for the test? It should probably just finish loading?
Yes it's needed, because after in the view `request` is used. Try removing, and you'll see that tests will fail !
this should not be a pointer, this is an uninitalized variable, right now it's a memory leak
I've added webworksutils.cpp and webworksutils.hpp into the json extension. I haven't renamed the extension yet.
I don't think so, its seems a little hacky and only QNX auto seems to be using it.
Not needed anymore. It was needed for LiveScript <  1.0 to be compatible with Spine.js.