labofsahil/github-event-dataset-2012 huggingface dataset:
oozie seems to be find with filter="", which is better since nulls are evil. And it'll also make it easier to add other filters, e.g. user= in the future.
> But wait, all is fine. If not preloaded no copy of self._data because it
doesn't exist.
else it in fact gets sliced to the events selected by the key. Where is the
issue?

self.copy() makes a deep copy of self, including self._data. For consistency with numpy this seems a good idea. However, when indexing this entails a lot of unnecessary copying (especially since you're going to discard most of the copied data anyways when you index).
one way would be to have an xyz stc i.e. inverse methods that return
all directions. We'll just have a problem to save them on disk as the
pb was not solved in finland ...
Just throw an IllegalArgumentException here saying that null values are not allowed
Hmm...., i don't see how it will affect the test given the default transaction propagation is set to required which means the inner transaction scopes when calling saveEncounter or saveObs will still be mapped to the same outer transaction irrespective of whether it was started in the test or mergePatient.

However, I will still add the annotation
Well, not sure it is required to log with the `warn` level here.
Should be good to add a comment for translators explaining the context of the string.
you should use ``::`` at the end of the previous paragraph instead
设置状态码为200和302的响应的缓存时间为10分钟，为404的响应的缓存时间为1分钟。
->
设置状态码为200和302响应的缓存时间为10分钟，404响应的缓存时间为1分钟。
Nice! Just a hint: When looking for a single element, you can use the **find*** methods. You could better do the following:

```java
template = vdc.findAvailableTemplate(VirtualMachineTemplatePredicates.name(name))
if template:
    log.info("Found compatible template: %s" % template.getName())
else:
    log.info("No compatible template found")
return template
```

I'll merge the pull request this afternoon. If you want to commit the change it would be perfect! :)
Document API change in CHANGES
Эти два метода уже не нужны, в `Util` они есть (`util/passutils.h`).
Just make_node (RECORD_TYPE) will do here, no need for fakeStructType function.  The node is initialised to zero by default.
I dislike the lack of verification using this method.  But if this is what is being moved towards then I guess it's the best way.
If I don't select anything, the params[:choice_id] is null, and .to_i becomes 0.... so you get ugliness. Ideally you'd either be OK with 0, or redirect back to tell them to do it right! :)
Is this file been removed ?
Sorry, missed that in earlier review. This class behaves like a function. We should use a lower-case name here too. However, I'm pulling it in, let's sort things out in later commits :)
CamelCase Folder (2 times)
what does this change do here? :)
Changed this. Now if the poll_until times out or the server gets into an error state, no delete=True for you.
looks like I'm not allowed to start a multiple digits number with '0', unless I avoid using digits '8' or '9' ??

I'd KISS and allow for leading zeros.
@mmarkus I think we missed something here: the prepare command may be forwarded to other nodes, but the rollback command won't be forwarded (because the StateTransferInterceptor is the one doing the forwarding). We may be able to fix this without injecting the TransactionTable in the StateTransferInterceptor, by checking the txComplete flag on the transaction itself.
Same for the other calls - the `git_diff_list **` ought to be the first parameter now consistently and the `const git_diff_options *` ought to be last consistently.
uri always is NULL
Keep this pull request just for PEP8 compliancy. As @mdboom points out, we should not only implement the changes for this docstring, but for all the other docstring inconsistencies as well.
Does this trigger the exception your fixing? Might be worth making this a numpy array from the off?
@NelleV You need double back-ticks (as in @pelson's example) surrounding the inequality so sphinx will render it as a code snippet.
element needs a var declaration
Better as a one-liner "return unless keypress"
Unnecessary!
i'm not sure this is needed - JS comparisons work on strings too - e.g. "a" < "b" == true
ISO format dates would therefore be in alphanumberic order already - can you test?
No need to specify this.
@arnodeclercq Can you lowercase the hex color values in this file? `#ddd`
What exactly does this function do/solve?
This is where it gets weird. Having to call the sakai.api.Util.getTemplates first, just so the global variable is there. The getTemplate function should use the getTemplates() function, and should return the template. In this file, we wouldn't have to use the sakai.api.Util.getTemplates function then.
All parameters need to be registered, not only these for model selection -- with MS_NOT_AVAILABLE.
This has to happen for every class and every variable in it. (m_labels, m_mean, etc)
It's using the underlying Config:: functionality, so I'll let Hamish answer specifically, but my understanding is that Config::get() returns configuration defined values, only falling back on class declared statics if nothing is defined via config.
This should already be happening inside install.php before it's outputted.
__wt_txn_read_int is so short, I wouldn't call it from __wt_txn_read, just repeat the two (one?) lines of code from __wt_txn_read_int you want.
Are you sure that you can pass ``get_headers($path)`` to ``current()`` as the parameter ``$array`` expects a reference?
Let's still support it but no longer document it, e.g. deprecate it? May save some code later...
The `push` event gets triggered for every push, including merges.  There is a `pull_request` event that gets triggered, with an action value of 'merged' in the payload.  It's not necessary if you just want to receive events when the repository is updated.
Heh. Want me to add a [beautifier](https://github.com/evocateur/js-beautify) step to the makefile?
I *think* the idea is that Persona will catch its own errors, and report them to the user, so that receiving a null assertion from persona always means "the user closed the persona pop-up without a successful login". However I feel like there are errors that can happen that don't necessarily behave that way and the user is a lot more clueless as to what's going on.

I guess until I understand all the persona error conditions better, it's hard to come up with a better message, but at the same time as a user I'd feel a little like "Ok, why are you telling me this?"
you are right, should I null it anyways or we trust the gc to go over it?
@bryanwb  it would be much less confusing if version was called jdk_version. I speak from the last 10 minutes of experience.
Right, ok. Let's keep it in temporarily. The feature tests are going to be extracted soon anyway.
Should be static. Fixed and renamed to ReceiverBehavior.
Deprecating things is kind of important. I think it's generally bad practice to say "we deprecated some stuff, but we're not going to tell you everything we did." However because we haven't had an official final release yet, we're probably off the hook for now. FYI for the future.
In any case, than just that task will fail. If we see that happens often, we could wrap some exception handler so that only that one user who has `None` there is skipped. But let us see if this will be happening.
We don't use spinner anymore?
Better: *Password (again)* ? What do you think? Because confirmation could be also answer *yes*. :-)
Don't be lazy. This is not good parent form. `get_initial` method is for example completely redundant.
What do we do? Activation or confirmation? ;-)
No, I'll remove it from a model.
No, MongoEngine could fail. When it tries to create an embededobject out of it. MongoDB does not care for `None`.

But even with MongoEngine we are just adding to the list or checking the length, not really reading the values in there. It should work. But we will see.
I like `users.push(data)` more.

BTW, you have to check if user is already in there.
It seems it need to have `set`. :-)
Use dict.
Compare with `django.po` and sync style/header.
No, just store `twitter_auth.request_token` into `self.request.session['request_token']`?
I am thinking you could have two documents. One for that data for which we know exact time. And one precipitation, which have an interval. This can be stored in the same collection, you just define two subdocuments, extending one base document.

So:

```
class Weather(Document):
    created = mongoengine.DateTimeField
    latitude = mongoengine.DecimalField
    longitude = mongoengine.DecimalField
    model_name = mongoengine.StringField

class Precipitation(Weather):
    from = mongoengine.DateTimeField(required=True)
    to = mongoengine.DateTimeField(required=True)
    precipitation = mongoengine.DecimalField
    symbol = mongoengine.IntField

class State(Weather):
    at = mongoengine.DateTimeField(required=True)
    ...
```
I would have file for all PiplMesh JavaScript. Except search. Maybe we could name it based on page view name? So `home.js`?
No, choices is not a type of field, but an argument of allowed values for a given field. For integer field, this could be a list of integers, for string, list of strings.

That is a good idea to create a custom field, like we have done for gender. If you want. I think it will be some work because I will require a general type chooser field which will you then have to configure for our set of classes. (The reason is that you will get otherwise an import cycle, fields importing from models to get a list of models, and models importing from fields to get the field.)
Needs a comment about why this is necessary
(palette colour) wouldn't work since it's a keyword argument on a vector, what was intended here?
Not if it is just a little block. It has been like this before and nobody had an issue with it being in one line. I don't see any problems with that :)
The transparent redirect step "redirects" to that url and tacks on the token we need for the next step. Since we don't follow the redirect but instead parse out the `Location` header, "example.com" is just a handy placeholder that is essentially ignored.

In short: I don't anticipate any brittleness due to using it here.
Why not use Applicative here? you already use Alternative in the last part.
m_isWalkingBeforeCharm -> _isWalkingBeforeCharm
Sure it still is, but you would do it now this way

```php
'find_method' => array(
    'name' => 'findBy',
    'params' => array(
        'criteria' => array($criteria),
        'orderBy' => array($orderings),
    ),
),
```
rather than use `headers || {}`, we should just set `@headers` in the initializer.
Nice. This looks much better.
staticmethod — не нужен
"clinicaltrials" sounds good to me as a replacement for linkedct_trials.

I think we should recognise the novel contributions from both dbpedia and linkedct.

For example there are dbpedia.org/ontology/ entries that we may want to support, as it may be better in the long term to have them in a namespace called "dbpedia_ontology" rather than "wikipedia_ontology", again incase wikipedia or another third-party has an ontology attached to it without reference to dbpedia in future.

Linkedct also has manufactured some of its own identifiers, although I am not sure how stable they will be. In either case, we may want to keep namespaces like linkedct_locations. From looking at the list of namespaces at http://data.linkedct.org/, we may end up keeping the linkedct_ prefix for namespaces that are MD5/SHA1 type hashes and convert some of the others to use a clinicaltrials_ prefix. The key to the decision for each of the subnamespaces inside of linkedct and other databases is where the identifier was created. I have not looked at the raw clinicaltrials.gov data dumps for a while, but I think there was more than one namespace internally, so we will need the clinicaltrials_ prefix for the non-trial identifiers. It seems fairly straightforward that the clinicaltrials: namespace could be for the trial identifiers (including the NCT prefix?) in this case, in a similar way drugbank: is for drug, and drugbank_... is for the other parts of drugbank.
If there was an automatic way to do that (as I think is currently done for the commands) that sounds like a good idea. But I don't know how to do so ...
I think "copy_env" is the right name here
No, I don't think so, I've changed some stuff.
Sorry, I meant that it should be "Request" and not "Rquest".
The current plone.app.theming (planned for Plone 4.3) can have it's Diazo configuration stored in the ZODB only, that's why I included the objects-list in there.

I could be mistaken though.
Sorry, let me expand. "Why are you mutating the global class object???" (Here and on the next line too.)
ahh ok. I see what's needed. done. 

note that i've left the default value in the signature unchanged.
using names strings would be more robust and informative  "%(returns)s " % dict(return=.... )
Ha, right. Typo I guess.
哦，看起来是我看错了，这个是tag。
One empty line before `load`, to have a separate section for loading.
Hmmm, this put my line note in slightly the wrong place.  I meant to discuss lines 321-323.
Suggest `...galaxy images, building a config dictionary in Python to specify the image properties and reading in many of the relevant parameters from an input catalog.`?
The idea is you put libraries and things you want on the classpath for an application in there. I got thois from Qpid, where we have lib and lib/opt where extras get installed. I agree dot is probably not required. We should possibly only do the lookup on ROOT if BROOKLYN_HOME is not set
There is a problem when using the "tests" prefix:

* tests/res/animations/animation-2.plist uses "res/animations/grossini.plist" as a path of spritesheet.
In a couple of tests I have found that tpl can be undefined, on TodoApp when editing an item, and on modelApp when selecting "Repeat Data Binding".  I think this is because there is a parent view which is only used to hold the inner views, so it does not have a template.
<%- if you don't want Vaisili(tm) bugs:
require {
   "alert('popa!')" { 
           1 == 2
     }

}
Actually it looks like the other custom exceptions defined in this SDK use the `Exception` suffix, so `AmbiguousEntityNameException` might be better than `AmbiguousEntityNameError`.
fwiw, I agree that this stuff would be better suited on the /dev.html page (make that one useful!)
Never used in the template.
Again, "effect/effect", is this correct?
remove dictionary as it's irrelevant and just left over from the cookbook example
Side note but we should really factor some of these into a common place.  They have no need to be board specific.  Maybe even into pios_wdg.h
"Board configuration panel for instance? Like the pipx configuration? That's not possible to put into a config file, and adding it to the xonfig gadget is just dirty..."
It is possible to use ui files at runtime, and if used with the object to widget relation framework it would just work. Also if using qml the same goal can be achieved.
I'm not going to turn this into an argument. For the record I'm against this infrastructure, but it is 2 against 1 so let us continue.
I wrote a comment in front of the function to indicate this possibility and added a commented within the while loop to indicate where this could be done and what condition to check.  For _this_ implementation it's completely appropriate and cleaner.
This file is unneeded
Would the done have the rounded corners on the right when it's full?
Лучше изменять DOM 1 раз, а в цикле набрать шаблон в аккумулятор.
Can we make this a configurable setting as well?  Let me know if I can help with that.
Не будет работать команда: java ... "mkdir" "test"
Всё проще -- anInterface.isAssignableFrom(targetClass)
is только для типа boolean
harish has made comment
We should add a description to this block.
I can't find a search result for which this would not return true. Is it a problem with the database (ie the image not present on the server?) 

I think we should also check that the span is visible as the name of the property suggests checking it's visible to the user. At the moment it just validates the HTML a bit.
sorry about the 254 it was a typo...
the 255 limit is from the address  
the address field one has a limit off 255 chars... the rest must be added to the next field
what if the root name is not empty ? you would need to pass a prefix here in such case (but it may require an additional property in the annotation to pass it)
This is debatable: we have bugs in deprecated methods, and we might miss them by not testing them.
x_min and x_max should be in init
You don't need the decorators if you have already put the pragmas at the beginning of the file.

That said, I prefer the decorators to the file-level pragmas, as I find them more visible and explicit.
Yes indeed. For this specific file please add @robertlayton as first author as he contributed the original python version if I remember correctly.
there is math support in sphinx... but if this is only internal, then nm.
Can images ever be disabled in the app or can the app be used with a screen reader of some sort? if so we should add alt text for accessibility reasons.
Seems to be 
'''"terms": "<p>Puedes hacer lo que quieras</p>""""
Cette anomalie n'apparait dans le doc original
ここもbefore_filter化できるとおもうんだけど、よくわからないから変えなかった。
I thought you were Michael Greifeneder, not Eric Kok :)
BouNding Box
I still don't see any reference to normalTrans, so how could it possibly be being used??

I would have expected a line like
args.replace(1, *normalTrans.getClear());
precisely - when you don't have the debug information around to be able to decode it.
It is unfortunate to keep doing the division and the scaling.  Could you instead comapre elapsedCycles() against msToCycles(1000)?
Will this be localizable?
I think we should encourage explicit form: `require('./geolocation')`.
I'm getting
Error: undefined local variable or method `model' for Facter::Util::Processor:Module

After adding
model = Facter::Util::Resolution.exec('model')
before this line, it seems to work.
Finally, you can rename this to `getParameters`
with all composer changes lately please make sure you check again to update composer.json
Will bring this into dev tonight.
Nit: I'd suggest surrounding `key` with double quotes to improve the message readability. For example, imagine if a user have connection string key called __key__, the message now will look like this

>Invalid connection string setting key key

Where if double quotes added will be like


>Invalid connection string setting key "key"
Guess you'll get a warning here about header and line not being equally long.
Ah, never mind. I just saw your comment in the other PR.
Instead of returning null you should throw org.jboss.resteasy.spi.BadRequestException with a descriptive reason.
It looks like this transforms 1.2.3-dirty into 1.2.4-dirty but leaves 1.2.3 as it. Is that the intent? And this is so a build after 1.2.3 will be seen as higher in semver than 1.2.3 so it can be installed/upgraded to? This looks sane if I'm understanding the problem correctly.
or you can just do:

'uri' => datastore['URI']
Actually functionality was removed here. The data you keep refering to was not used anywhere else in the code. to compromsie I have in the msot recent commits output some of it to screen again where appropriate. And that can still be done without having to have 7 different identical methods. For the record, data that is not used anywhere in the logic of the module or stored anywhere is not functionality. 

I focus on clean code because I, and others will have to maintain this code going forward, and so clean, readable code is important to that code's maintainability. It's also key to that code functioning in a sane manner.

I have been working all weekend to make this code clean and maintainable while still reflecting your opinions and desires here.
res should be checked against nil before accessing it here I think
Please use the `define_class` spec helper method, which will undefine the class after the test is done running.
Please change this to just ``from django.utils import simplejson as json``. IIRC this goes back to 1.2 (please double-check) and does everything the right way for us.
cool -- I was splitting it to match `super_filter` below.
Every page should have a parent.
@kristiancalhoun when this branch comes into master, you'll want these changes in your new Sandcastle examples.
Less is more.  Why say `This block of code determines...` when we can say `Determines`?
Given that the `PolylinesWrapper` constructor function is `@private`?  Does each of its functions also need to be `@private`?  How does the doc tool work?  CC @kristiancalhoun
reordered operations to overcome issue with tempArray out of bounds. Same change in 3 places.
This is going to create a bunch of repeated styles, bloating the code size. Cache it in a css rule in the header. Same goes for the other styles. Inline styles are generally considered a no-no in the web.
I was unable to guarantee that the default profiles are there all the time. It might be that they are, but I wouldn't say I understand the rse code well enough to guarantee it. Most of this code was copied from teh UI, and the irrelevent bits were removed. So, this is what I was left with. 

This helps to guarantee that there is at least one profile available. I could rename the method getOrCreateProfile.
Should be `if (`, also wrong in the if below, let's fix both. I had started to fix that, but -- see below.
Ок. Но для чего?
This is a change of behavior, which means it either fixes or introduces a bug. Which?
> static immutable T i;

`@disable this()` problem.

> And what advantage does this hold over the memcpy thing? That seems the most direct to me.

It compiles with current dmd.
What that's comment supposed to 'mean'?
//memcpy *always* works great!

It doesn't in CTFE and otherwise this feels like arbitrary noise.
I think this function should contain an assert(t !is null)
This readonly stuff is only useful for form-based apps.  I wouldn't include it in the generic startapp.
this will cause the module to break on redhat.
ok so now, probably use if-let: 

(if-let [handler (:lookup-fn @config)] (nil? handler) the-rest-of-the-forms)
`Chronic::parse` is smart and will understand `today` just fine. :)
the period is unnecessary.
Nice catch, will definitely make this change!
Looking at the master branch of zf2 I don't seem to see this class?  Potentially it was consolidated?
you should typehint the interface instead (available in Doctrine Common)
@author :-)
The doc is in "man sigaction" .

auto is much simpler here. such properties are simply shortcut to deeper fields. Any modification to such field would require a modification of the property for no benefit. It could happen for instance to port druntime on new plateforms.

Such property isn't the authoritative place where the type is lying, and so it is duplicating of knowlegde. It is known to be a bad practice.
At one level, you're right, but appearances do matter.
MINOR: Comment should add (as defined during construction).

Declare as const?
Attributes were named after strategy interfaces so for whatever reason i thought we have MongoDbTemplate, but now I see I was wrong so it has to change
Those two imports could be combined.
include_path should likely be rendered as monotype, as it's a directive.
Namespace separators in heading need to be escaped in headings with a backslash so sphinx can render it.
Couldn' this be done with just a `fs.writeFileSync('dest', fs.readFileSync('dest'))` ?
I'm not an expert on iptables, is it valid to have `COMMIT` in the rules file twice?
Unshift, right?
"manifestement" selon quoi ?
J'ai bien changé les propriété de retour chariot, les problèmes d'encodage de fichier.
Je vois pas d'indice qui va dire si ça vient de l'édition, du client git à l'emission, du dépôt git, du client git à la récupération, ou de la gestion par la console/ l'éditeur avec le quel tu vérifie :

http://fr.wikipedia.org/wiki/Retour_chariot
http://www.commentcamarche.net/forum/affich-1219530-remplacer-un-caractere-m-en-vi
https://www.google.fr/search?q=%5EM&aq=f&oq=%5EM&aqs=chrome.0.57j0l3j62l2.720&sugexp=chrome,mod=18&sourceid=chrome&ie=UTF-8#hl=fr&gs_nf=3&gs_rn=0&gs_ri=serp&tok=qYOzWp7A5JVctCJiC-w9cQ&pq=%5Em%20bad%20interpreter&cp=4&gs_id=21&xhr=t&q=%5Em+vim&pf=p&tbo=d&sclient=psy-ab&oq=%5Em+v&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=ab5b7205c5e84f25&bpcl=39314241&biw=1920&bih=955
https://www.google.fr/search?q=%5EM&aq=f&oq=%5EM&aqs=chrome.0.57j0l3j62l2.720&sugexp=chrome,mod=18&sourceid=chrome&ie=UTF-8#hl=fr&tbo=d&sclient=psy-ab&q=%5Em+emacs&oq=%5Em+emacs&gs_l=serp.3.0.0j0i30l3.3859.4467.5.5518.5.5.0.0.0.0.114.395.4j1.5.0...0.0...1c.1.K-cCSSkTstA&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=ab5b7205c5e84f25&bpcl=39314241&biw=1920&bih=955

Y'a plusieurs fois des histoires de conversion "dos2unix" mais j'utilise pas le cmd ni le powershell. Et comme déjà dis, le retour chariot est bien en mode Unix sur l'édition de fichier. De même le client github laissait les lignes write() d'origine au moment du commit.
this exception would result in a 500 error whereas a 4xx would be better
Do I put standard resolution if the resolution selected is not supported ?
Yeah we can change it back. Novaclient was doing it in a very messy way and also the documentation points to using tokens, it might just be easier for users to copy paste that rather than, whether they must provide or not provide tokens.
Yes- thanks for the catch! Updated.
These initializations are not really necessary, so could be left out. Also please use names that cleary indicate what the difference between these two is.  E.g.: translation_status_message and translation_levels or something along these lines.
shouldn't 'EDIT' be a constant?
moved the edit public profiel button down, although it still looks pretty ugly because it has a lot of text on it.
Is _getter_ actually well enough defined in the spec? Is it enough to just refer to "JavaBeans read properties"? What is the definition? The method has to start with _get_, _is_ or _has_ and it has to be w/o parameters. Is that it?
I introduced an overridable `build_tokenizer` factory and also the ability to pass a fixed `tokenizer` callable directly in the constructor.
maybe array_key_exists?
Add `python_instances` and `python_type` default values to this base class?
I actually didn't change this from the original pom.xml. 
it shows a change because eclipse autoformat the xml.
The path is relative, so this must never hit. Should I change to an ```assertex```?
Please update the documentation at https://github.com/mozilla-b2g/gaia-email-libs-and-more/blob/master/data/lib/mailapi/mailslice.js#L642 to include contentId and make name clear that it's always a file name.
Please include this class in the pull request.
Is there a valid use case of closing the first window in a tab stack? In the future, could we consider it an exception in trying to do so?
please typehint the interface instead of the implementation
При каждом удалённом посте будет прогонять все посты ниже. Удаляют посты не так часто, можно стерпеть.
Can't use filter because `featuresArray` is not the same format as `features`, so simply filtering out entries in `featuresArray` isn't enough.
your comment say "options file should NOT contain -devmode"
and the 
expect simply cares that it is being called. Is there a way you can improve this expect?
Same applies to this function as well [`utils.js`].
Give it a more descriptive name
We have now refactored to a very different API
Turns out the !!allowSubDomain doesn't work as expected. It actually returns true when allowSubDomain is "true" or "false".
Do you know an alternative method for string to boolean conversion that works?
We could always do something like;

if (typeof allowSubDomain === "string") {
    allowSubDomain = allowSubDomain === "false" ? false : true;
}

or if you want it all on one line maybe;

allowSubDomain === "true" ? true : allowSubDomain === "false" ? false : allowSubDomain;