labofsahil/github-event-dataset-2012 huggingface dataset:
I am backing @GaelVaroquaux on this one: we need to motivate and demonstrate practicality and usefulness of variants in examples. Otherwise the users are confused by the added complexity of the extra options in the API and furthermore it adds burden on the maintainers who don't necessarily know why this variant was introduced in the first place; especially years later when it might happen that maintaining both variants will make potential refactoring or third party dependency upgrade (e.g. arpack) more complex. Any source code line merged into master has a cost and needs to have demonstrated practical value.
This has been in `ext/standard` since PHP 4 times, so it's OK to rely on this for the moment. APP13 consists of more than just IPTC though, we might want to parse this in the future - see http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/Photoshop.html
There is a single ratio - ts.tr.gen. When the others are not necessary, it's possible to set just that one.
Hm, no idea what I was thinking of then…
In Javascript, the == operator is a loose comparison so "0" == 0 is true. The === operator forces a stricter comparison so "0" === 0 is false. It's the same with !== below.
I added a '_' to indicate that it is static and is reflected in the Javascript world. E.g. TiUIObject::createLabel_ = Titanium.UI.createLabel( ... ).
Below there are TiInternalEventListener
TiInternalEventListener::TiInternalEventListener()
{
    listener_ = NULL;
}
TiInternalEventListener::TiInternalEventListener(const TiInternalEventListener& listener)

Please add newlines between the functions for consistency.
A la place de @bugForm("@bug.id").value   il faut mettre   @bugForm("id").value
these tow line must be in the same line
Here, I also need to know the groupName which will be used to retrieve IP address for thor slave. Do you have a similar function like the getSize()?
getConfiguratioDirectory gets its information from a configuration file property tree, and this component does not have a config file
The function name should match the name of the operator.

buildDatasetAssignDatasetFromTransform
This is not good, maybe using ifs rather than a switch here would let me ```break``` to skip optimisation, rather than do that.
yes. I thought the two first tests would cover that, but they don't.
The change in indentation is a consequence of the actual change in the way the master lock is handled: operations that in the original implementation were performed after obtaining the only lock used are now safely performed before obtaining the lock for the master. That is why they refer to master* variables and are placed before the try block.
There are two more "if" in the same method that check if $this->configuration is null, so you should either change the other two or, better, leave the null checks and change this line:

```php
$this->configuration = $listener->getConfiguration($em, $meta->name);
```

To this:

```php
$conf = $listener->getConfiguration($em, $meta->name);
$this->configuration = empty($conf) ? null : $conf;
```
One problem with defining a default like this is that default args are only evaluated once, so it accumulates. Consider:

```
>>> def get(report_type=['any']): 
...      report_type.append('blah')
...      print report_type
... 
>>> get()
['any', 'blah']
>>> get()
['any', 'blah', 'blah']
>>> get()
['any', 'blah', 'blah', 'blah']
```

I'm not sure if it's an issue with the way this code is being used but it jumped out at me. If you always want to default to ['any'] then it's safest to do:

```
>>> def get(report_type=None):...   if report_type is None:
...     report_type = []
...   report_type.append('blah')
...   print report_type
... 
>>> get()['blah']
>>> get()
['blah']
```
Can we just say `projects looking to standardise their code` ? There should be some better sentence for all the fig guys have some standard code. @pmjones any different thoughts on this ?
OK. I added this sbt script and changed the other files accordingly. Great suggestion.
This process_select is new, it's clearly a feature change, not a code cleanup. Please remove, and file a new ticket for that - never mix cleanups and new features!
You should be HTML escaping value here, else it's vulnerable to XSS.
@raydavis 
Interesting, I didn't know the exact mappings but this is what I found out:

> The available log levels are: :debug, :info, :warn, :error, and :fatal, corresponding to the log level numbers from 0 up to 4 respectively. To change the default log level, use [ - source](http://guides.rubyonrails.org/v2.3.11/debugging_rails_applications.html#log-levels)

So if I'm not mistaken, it should be 3 = ERROR, right?
But I've set it to WARN (2) instead, the output still looks fine to me.
added a etc/metocean.config and ConfigParser
Otherwise, having this as a public property is a great idea, though.
this looks better, but there's still one thing I don't think that is right here:

display label "Nicola Niqt"
filter string "Nicola J"

it'll match, and it shouldn't - you need to search forward (in the display label components) after you find the first filter match, and make sure that all of the filter components match after that part of the display label
good catch. Also that output is horribly confusing on another glance. It is not at all obvious there that it found results locally. Need to do something about that.
Wrap, please.
Bad author field format
It raises an I18n::MissingInterpolationArgument exception - it happens when we include %{attribute} or %{model} in the translation string.  ActiveModel passes these values into the translate call via the options hash.  This pull request is to include these values in the shoulda matchers to prevent the exception being raised.  The tests do fail without the patched code.
General comments on the constructor:
1. It's hard for me to follow what properties are actually being set on `this` and what the object ultimately looks like.  The JavaScript optimizers are also very finicky about this.  For properties that are not set by a simple assignment at the top of the constructor, it is probably better to list them there anyway and assign them as `undefined` even if you are going to re-assign them later on.  This will not only make it easier to read and document the code, but it will also allow the compilers to better optimize the Material object.
2. The public instance properties (it looks like there are at least 2 (`shaderSource` and `materials`), need documentation.
Very nice.  In general, I was over-zealous with `@see` and `@seealso` in my youth.
Icons within WCF2 have a base size of 16px.
is this condition (and the one above) deserving of a log message?  I.e., has something gone wrong if we need to do these early returns?
Constant is a magic number and must either be documented, named-defined, or explicitly calculated via a method. Use of hardcoded values such as these in the past for animation/rotation purposes has led to synchronization issues.
IIRC, the correct check here is actually `refTableKey_ != 0` because java types are signed
Did you mean to comment this out? Seems we need this. Now, IE9 does not support he placeholder attribute, so perhaps we just roll our own placeholder? Or possibly shim placeholder for IE9 using a has block?
`MATH.parse( A + "( #{x} + " + H`...

Should be (x - h)? When plugging in for the second point in the hints, the sign is wrong in the (x-h) portion.
Agreed; if no units are necessary I'd rather they be omitted -- if only for style.
the only place you use this is [line 94](#L2R94), so I'm not sure you need this assignment in the first place
Since when is @trusted going anywhere?
s/As you can see, t/T/
@gruehle I'm all for keeping the console clean, so I'll take this line out.

However, because I love being pedantic: I thought about this when I wrote it. If the user hits the "catch" case, we are catching an *actual* bug that should be fixed. It seems to me that it's good programming practice to make sure that actual bugs have an outwardly-visible symptom. (Though it's not clear that this console.log is the right symptom.)
is 'example' a suggested name from pub? if not,  should we keep it singular or make it plural?
`and`ではなく`&&`を使ってほしい感じです。この場合は別によいのですが、`and`と`&&`とは結合優先度が違うので、たとえばgithubのコーディング規約だと`&&`だけを使おうということになっていて、個人的にもそれに従うのがよいと思います。

  * マニュアル: http://rurema.clear-code.com/1.9.3/doc/spec=2foperator.html
  * コーディング規約: https://github.com/styleguide/ruby
createDictionary...
This is now incorrect. Please remove.
Last divider isn't causing any rendering problems, we are a-okay!
There is something in stringfuncs for that already, namely `getUsableFileName`
This can just be empty, only one of files/dirs has to have something in it ;-)
The callbacks for these bindings should each be a separate function.
Calling `.ToString()` each time is bad practice.
2 options:
1) Use constants instead of ApiCommand Enum
2) Add wrapper-method to `YapiService` to call `.ToString()`
What for?
Who might use it?
I made it internal intentionally: hide from end-user.
My thought is following here:

A client should not care about authentication, it's a responsibility of the class user and authentication providers,
If the class user provided an authentication mechanism - great, if not - no problem.

So if class user not provided authentication provider when it needed, the application should fail with "not authentificated" exception, but not with "provider not specified".
Ugly or not, `@@@BUG@@@` is used quite a bit in Phobos. IIRC, it's what Andrei favors, though I don't remember what reasons he gave (something about emacs? I don't recall). Though you could actually argue that it _should_ be ugly, since it's indicating that there's something that needs to be fixed.
Good catch. Will mark it `@system`.
FIX ALL THE TABS :D
Do we really only care about ThreadPoolTaskExecutor here? The hierarchy of TaskExecutor is pretty extensive and I am assuming you wanted to specifically stop any Spring TaskExecutor here. Also, however unlikely if the executor is a Proxy than it won't be part of the executors map
Had considered using <code>SpringJunit4ClassRunner</code> but that ,means i add a new variable each time i need to add a new test going forward which i didn't want to. It can be encapsulated inside the method but the setup method call looked much shorter and clean to me ;). 
Anyways, this is how it was in the JPA adapters and followed the same approach to be consistent. Wouldn't mind changing it what you are suggesting others feel so too.
s/~~OutOfMemoryException~~/OutOfMemoryError/
Do we even need this at all?

Given that we now support an expression, what is the point of providing a fixed header in this way.

Why wouldn't we just initialize the expression to "headers['" + JdbcHeaders.STORED_PROCEDURE_NAME + "']", if they set allow-dynamic ...   ???
s/~~On the other side, a~~/An/
When I implemented the model on the front end I have a button that the user clicks to look up an address on google maps and fills in the coordinates.  Originally, I wanted to include this functionality with the Armstrong contribution by using http://mapstraction.com/.  Mapstraction would allow you to switch between map providers.  However, I never got it to work right and had to finish with a quick implementation of just google maps in the client's code.   Now that I have sometime, I could probably revisit it if you think it is appropriate to include with the contribution.
@ddeboer the reason i've put it inside the writer is that you probably want to execute that logic only during an import, and not every time an entity is persisted in the live application.

in our case it was the following: We've imported users from another system into FOSUserbundle. The legacy system had no constraint on the email adress, so there could be users without emails. In that case during the import - and only during the import - we needed to generate random email adresses for imported users, to avoid errors thrown by FOSUserBundle.

Of course you could try to add some logic into the native doctrine2 event handler, but that would clutter the production code with stuff that's probably only needed once when a legacy system is imported.
I ensure it before calling this method.  I've added the asserts you were looking for and have fix the reference counts so Xcode analyzer now likes me.
debugger - Should not have been committed
I don't mind one way or the other, but we haven't made a general decision on "no contractions" so it's probably not the time to be changing all of them.
because of at least **one** cross-parameter constraint
nitpick Does this even need its own function?
此文件应是一个真正moodle php，包括所有moodle界面元素，只是中间内容显示diff。你太糊弄了
Actually do me a favor and clean up the unused imports. This code looks great, it deserves to have the imports cleaned up.
Word wrap, so I can review this easily.

Javascript needs caps

Let's try:

    You will also need to include Javascript for the BrowserID popup form. 
    You can use django form media at the bottom of your page 
    (see `Form Media`_ and `Managing static files`_ for more information)::
It is bad practice to use the property within the init because subclasses could have overridden the accessor and it may being dong some work that is assuming the instance is already fully initialized. I believe the code is correct as is.
> I don't think "Mark a property for cascading validation" is proper english actually, that's why I changed it. Is it?

I thought the same about "validation cascading" :)

I just checked with the spec, in most cases we use "cascaded validation" or just "cascaded". So how about "mark a property for cascaded validation" or "mark a property as cascaded"?
I would make this a separate code example and add it just above the second table. This way the example is closer to the table which refers to it
А можете выложить под тестовым пользователем, вашу версию данной задачи? хочется научиться чему, то хорошему.
це переносимо в репо LiveStreet
тільки давай в тестах будемо ставити англійську мову, бо ```Then I should see "Добро пожаловать на наш сайт!"``` якось дивно виглядає
do you prefer
opacity in dot.color && ...
instead of hasOwnProperty?
faghat avalin image ba akharin image mikham radius dashte bashan
I think zaim should answer this I only created  to helper function get hep with saving and did the saving bit... 
def get_questionnnaire_obj(questionnaire_id):
def get_question_obj(question_id):
and the saving  bit 
if request.method =='POST': 	
    form=questionForm(request.POST)
   if form.is_valid():
    formdata=get_answers(form)
 for question,answer in formdata:		
this_answer_set= AnswerSet(user=request.user,questionnaire=this_questionnaire
this_answer_set.save()
this_question_answer=QuestionAnswer(question=get_question_obj(question),answer=str(answer),answer_set=this_answer_set)
this_question_answer.save()
Un mixin utilise déjà dans Twitter Bootstrap.

.border-radius(5px);
No because we redirect to either `/` or `/welcome/something` depending on whether the user has completed the on-boarding process. It's a bit general, but I haven't had any issues in Safari. 


On Monday, July 23, 2012 at 18:24, Jamu Kakar wrote:

> > @@ -433,7 +433,7 @@ chrome.tabs.onUpdated.addListener(function(tabId, changeInfo, tab){
> > if (oauthAutoCloseTabs.hasOwnProperty(tabId)){
> > // This tab is a candidate for automatic closing after successful
> > // OAuth login.
> > - var dashboardURLPrefix = 'http://' + fluidinfoHost + '/dashboard/';
> > + var dashboardURLPrefix = 'http://' + fluidinfoHost;
> > 
> 
> 
> If we keep the `/dashboard` link alive I guess this will need to
> change, right...? Also, even if it doesn't, does it need a trailing
> slash?
> 
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/fluidinfo/obrowser-chrome-extension/pull/119/files#r1220483
> 
>
XPath has ancestor-or-self axis so if anything, I'd prefer that rather than something that sounds like querySelector but acts in opposite way.

But I don't think it's important enough to change it either.
@seth look at the document as a whole (not the diff). All the columns align, which makes vertical text selection a breeze in most editors.
seems like this might break if I try to reset a branch that doesn't have a ```last_known_good_``` variant
Hhmmm... maybe Connection.disconnect should just reset the pool instead of chucking it and creating a new one?
why is this a bitwise OR ( | )?
This file seems to use it all over the place, I don't think there is any reason for it. I don't there is any point changing it at this point but I would like to understand why its using bitwise operator instead of just the standard OR ( || )
I would prefer `locale` instead of `language` as directory name
How is this different from ERROR_DENIED and/or AUTHORIZATION_DENIED, above?
I get the before "send" bit, but requiring the user to wait until after the connection is opened is arbitrary. With some clever coding you can get around this. No sense in us limiting the developer when we don't have to.
The only catch is that we have to check against both '5 cm' and '5cm', so it might be that after breaking it up, we iterate checking for -[hasSuffix:], which would be faster than searching.

Orr this might be moot altogether: iOS is smart enough to ignore spaces in getting the floatvalue [@"   5   " floatValue] ==5.0f. In other words, we could just check for hasSuffix, and if so, remove that bit and get the floatvalue, with no space handling needed.
This looks kinda familar :)
Trialforce URL are org specific.
See http://developer.force.com/releases/release/Spring12/branded+logins
I usually do not split simple properties that just return values, into multiple lines. Keeping such properties on a single line results in denser code, which is not a bad thing, too.
We don't want to upload updatesite:zip separately as it's already in droolsjbpm-tools-distribution. Every zip we offer for download must contain documentation, binaries and sources (and examples and javadocs if possible).
Controller should autocreate if it doesnt exist.
Should be `if (session.appdesc && !path.existsSync(session.appdesc)) {`
@nukulb Yea, this makes sense. i will move it and rename it.
the start of the { bracket is inconsistent within the file, it should start on a new line if it is the beginning of a function. The example should be as clean as possible since it will be used as a reference point for other devs
I didn't understand what the behaviour should be:
Should the alarm stay on after the tyre pressure returns to normal?
Should the alarm turn off after the tyre pressure returns to normal?
It is a generic worker, we want any and all exceptions to be caught. If not, undefined behavior from unintentional restarts can occur.