labofsahil/github-event-dataset-2012 huggingface dataset:
perhaps clarify which consumer here - "... where the consumer of the sent message..." "... where the consumer of the request message ..." " ... where the remote consumer ..."

I realize you say request message on the next line, but the first time I read this I though you were talking about the reply consumer
comments like this in the code like to get lost, we should track them in issues instead of code.
The benefit of setting forkMode to always is to protect maven process, why do we want to set it to never here?
There is not nightly snapshots in ZF2 only releases and the possibility of clone the repository with git
Try to make field names as what they actually do.
The below seems more readable.

'shipping_register: fields.many2one('ups.shippingregister', 'Shipping Register', readonly=True)
How? How can use submodel like 
<code>
public function getExportFields()
    {
        return array(
                'id',
                'name',
                'user.email',
                ...
        );
    }
</code>

Thanks
Added. also updated the getBreadcrumbs' doc block.
Use `$event->getTarget()`, at least it is in the interface :)
If this function is only for windows, I think it should be also enclosed in the  #ifdef WIN32 statement.
I'm not sure "traditional polling" means anything to anyone, better to omit it.
this is awesome! :-)
You should push a commit to Django repository to change the default template ;-)
And I will change it here.

On 9. apr. 2012, at 14:06, Mitar wrote:

>> @@ -0,0 +1,35 @@
>> +# Django settings for tpme_tests project.
>> +import sys, os
>> +sys.path.append(os.path.join(os.getcwd(), '../'))
>> +
>> +DEBUG = True
>> +
>> +# Make this unique, and don't share it with anybody.
> 
> Remove dot at the end.
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/mitar/django-tastypie-mongoengine/pull/1/files#r659785
I also vote for renaming the `:oauth` key to `:oauth2` in the request map.
Might be worthwhile to print object.getClass().getName() in this exception message?
It is already scoped in the this example, but if your callback function is defined elsewhere and just passed in then you wouldn't have the zip.
Now is a list box, where should we place the role option? @jmcanterafonseca
How would you feel about making a global "geturls" function (e.g. ecep.geturls(endpointName, options))?  I try to avoid hardcoding urls for endpoints if at all possible, as it makes changing your api a maintenance nightmare.  In past projects, I've made a global geturls function that takes a string for the name of the endpoint, and an object representing any necessary parameters.  The function amounts to a switch statement that generates the necessary url for the given endpoint name and options and returns it.  This makes changing your api dead simple.
```return false```, ```return null```. что-то конкретное возвращай
Typo: clearoOverride
`S`pecial
Chatter can call this version to the get the Url. I can put this log into Chatter, but I feel OAuth2 isn't used directly by anyone, so it should be ok.
The constructor is used by deserialization, and it cannot take any parameters. The Initialize method is called right after the object has been deserialized, and allows the object to get some extra parameters from the atom container it was enclosed in.
It doesn't allocate a string on every "turn_into_nop".  It allocates a string every time it finds a specific assignment to turn into a nop for this particular optimization case.

But I see a quick way to fix the issue.
"Open the TC and open Dragonfly", what is not clear with that? It's not more complicated than any other test?
The hook is terminated at start when  `$this->useTemplateHook` is set to  `false`
Nejak nechapu k cemu je tato linka
Should do a `if (attribs)` check before accessing attribs.name, in case the user provides a rim:category element with no parameters.
okkey sure, so you mean to add "expect(session.keepSource).toBe(true)" line just before this one "configParser.parse(configPath, session, extManager, function () {}); "  ? Am I understand correctly?
If we want to remove it completely, we have to go through all APIs in the ext folder and remove those references.
set Cover is a little weird I feel.

newCover or updateCover are better names
``if (``
I'm curious why exactly this was added to the list
On utilise . plutôt que : pour séparer les namespaces dans la nouvelle version du toolkit.