labofsahil/github-event-dataset-2012 huggingface dataset:
The idea was to do the delete's on the created Button and not have to create a properties object, so that the `var b3 = Titanium.UI.createButton` call could remain in the same place in the code, making it easier to revert the BB code by only having to remove the extra BB lines.

It will need to be done now or later when functionality has been implemented.  I think it would be easier to make the change now while it's fresh.

The code would be like this, with only the BB specific code having to be removed rather than changing lines around :

```js
        var b3 = Titanium.UI.createButton({
                color:'#fff',
                backgroundImage:'/images/BUTT_grn_off.png',
                backgroundSelectedImage:'/images/BUTT_grn_on.png',
                backgroundDisabledImage:'/images/BUTT_drk_off.png',
                top:110,
                width:301 * scaleX,
                height:57 * scaleY,
                font:{fontSize:20,fontWeight:'bold',fontFamily:'Helvetica Neue'},
                title:'Click Me'
        });

        // BB specific code 
        if (isBlackberry)
        {
                delete b3.backgroundImage;
                delete b3.backgroundSelectedImage;
                delete b3.backgroundDisabledImage;
        }
```
I have tested only on the BB emulator - and for this case when width is larger button is not enlarged. When starting testing on real device we can find some more accurate scaling mechanism - this is just simple approach to have some scaling coefficients which can be further developed to be more proper.
for Height it is actually affecting space between buttons. but I don't know how to find nicer solution. 
if giving height less than some certain value it is truncated if more than extra padding is seen (though button border always is in the same only the background part is enlarging).
`%d`?
Try to stick to 1 empty line :)
Extra new line isn't necessary.
To save disk space.  :P
I think you're missing to fill in something for %s here.
s/obejct/object
C'est ce que j'ai mis dans le message de commit, mais effectivement c'est difficile à voir dans l'interface de GitHub (ou alors j'ai pas encore trouvé comment le montrer).
Dans une requête avec DISTINCT, PostgreSQL a besoin que tous les champs utilisés dans les critères de tri (ORDER BY) fassent partie des champs du SELECT, même si c'est une version modifiée du champ (ici, modifiée par la fonction lower()). MySQL fait le raccourci à ta place.
L'erreur retournée est "for SELECT DISTINCT, ORDER BY expressions must appear in select list".
So we will have to compare current datetime with fetched time in a django template to group these situations properly. How to   import datetime in a django template?
And as just described, node should know its backend. So you should not retry getting this information from session.

We might even allow node to know if it being mocked?
```
which is set to `next` from request GET argument
```
And just `smart_unicode(desc)` is not enough? ;-) Or just `unicode(smart_unicode(desc))`?
Sure. Just write `station` instead of `st`. Use indentation correctly. Order them in some meaningful way (maybe by distance from the node).
True. From the description I got a feeling that you have to set it.

OK, then leave as it is.
How will you make sure that someone facebook username is not the same like some username in our database ?
`CONFIRMATION_TOKEN_VALIDITY = 5 # days`
Please have only those lines changes, where you really changed something. Now, it looks like whole file was changed.
Creating issue for that. @mtipnis likely to resolve that and is currently finishing the work for cooked tests execution.
As I said: I indeed forgot one test that verifies the return value. But in my opinion that should be a new test and not wedged in one of the existing ones.
that's the reason to port it to this place ^^
It might simplify things if we aren't using this_week_qs anywhere except the exists() query later, to just create a boolean here such as:

week_has_hours = self.get_hours_for_week(date).exists()

then line 1646 could read:

if not week_has_hours:

This is just a thought on how to make it read a little easier. I'm not confident that chaining onto a function call like I suggest is terribly clear either.
this can cause NPEs too.
namespace ;)
What is this? Should probably a CONST, or maybe be read from styles?
No reason to use underscore here.
pretty sure we use zero instead of NULL
No, it doesn't work for Poisson. There was one refactor victim that's fixed, so the effects are right. I need to generalize a bit more and add margeff_se stuff to the classes. It should be simple enough to also add the methods to MNLogit and get this to work too.
You don't even need to store``dist_name`` I think, just find the right distribution from the provided name and store it, just like now. Preferably with less ugly code than this (from scipy):

    try:
        ppf_func = eval('distributions.%s.ppf' % dist)
    except AttributeError:
Yes. This is correct. The normalization is done at the end. Since it is a sum it doesn't matter. 
I believe it is exactly the same as section 2.3.4 in Racine's primer. See the equation at the top of p.16
It might make sense to add an option for whether or not to upload cookbooks.  Hopefully you would restore cookbooks from your local source code repository rather than a backup.
I see, but what if we gradually change this convention across the project? I used to use instance variables myself but recently decided to learn what rspec's `let` actually is and eventually started using it in my projects. The reason is that `let` has a number of advantages over instance variables. If you're interested you can find most of them in the answers and comments to [this question](http://stackoverflow.com/questions/5359558/when-to-use-rspec-let) at StackOverflow.
The problem with that is that the page loads almost the whole way, but then errors before the spinner is removed. The general demo spec does actually pass, even though the page doen't completely finish loading. Hence the existence of the spec and for testing the absence of the spinner.
Is it OK if I use footer also on the search result page?
agreed. this was just me copy/pasting the visualsearch stuff. didn't get much further than this.
OK, I can see the benefit in having `getShear` use the same physical units as our interpixel separation, which is really the bedrock scaling for the whole problem.  

For that to work now then, I think we should here simply say that in the docstring that the k values in the `*_power_function` should be strictly given in units of inverse physical units of `dx` / `pixel_scale`, adding a TODO to handle conversion once we've thought of the clearest `kwargs`-specification prescription for the conversion ratio.
Hi guys,

Yes, and sorry for being offline all-day Saturday!  This config file actually isn't currently used (and comes with an warning about it being unfinished at the file header), but was my first go at laying out such a thing.  Given the new syntax that Mike came up with, this whole file is a couple of evolutionary stages behind what we now use in the Demo scripts, for example.  I intend to rewrite it, so it might be worth transferring this to a new branch... I'm not sure.  It's still a useful placeholder, and doesn't break anything, but it's worth flagging further that it's very much still "in development."

The way we read it in, however, in galsim/config.py, probably won't change too much (although I might dispense with the automatic/default reading in of a default config file first).
It would be good to have unit tests to catch this.  I think making two different instances, and changing them in different ways, would work...
What changed here, spacing? 

Perhaps we can eliminate this chunk from the commit if the change is only cosmetic, my standard practice is to isolate it in a single commit.
Better.  get_slug is only called from Sherif's reporting code, so not risky as it stands now.  But I don't like returning a static string "Untitled exercise" when you can't find a slug, would rather return None and let the calling code figure out what that means.
Exceptions.propagate
Should be `id` or `cocoa.id`.
No problem. Thanks  for the contributions!
to put approved true
Put these in metadata?
This one doesn't pass/fail correctly because the return value of the block is not evaluated for truth. If we change it to `{|e| e.name.should eq "things"}` it fails because the name is a symbol, so this should be `{|e| e.name.should eq :things}`, which I took care of in 694cbf1423bb2ba23d6acf5fe5c131252432d1db.
Se você simplesmente deixar a exceção explodir, ela será exibida no stderr e o fluxo do programa será encerrado. Da maneira que o código está, a mensagem é exibida mas o programa continua a execução... não me parece fazer sentido continuar a execução.
Title is a bit funny; I was thinking "Building the challenger" would be nicer and more informative :)
Nit: Either terminate both or neither lists with a trailing comma.
Done. Yeah for multiple options it makes sense. But for single ones, its probably easier in one line.
Sorry, about that. I just fixed it for the 3 templates in the dashboard.
Should this say <name | search>  or <name | filter> ?  Or something to convey that it doesn't have to be the full note name
Correct, fixed in cfa67f806b2d1422049a2f5115b0fe253d59e804.
The guileline if there is a if/else is to use brackets even if they are one-liner
The #end-call button is in the initial markup so this would always be true.

You can check if the #call-screen has the oncall class.
|document.getElementById('call-screen').classList.contains('oncall')|
Do we really want to remove the 'paused' class every time the player is shown/hidden?
If it is only called on init then performance doesn't matter - clean code wins.
Could you please put function on the same line, and a put a space after `()`?
Ah good.  Just checking.
Remove the actual appeal address, so that anyone who forks our code does not end up sending a load of tards to our forums.
e.g. # APPEAL_ADDRESS >YOUR ADDRESS HERE<
I'm -Infinity on extending HashMap - let's find a better way to handle this
#FFFFFF ->  #fff
Это copy-paste. Во всех программах надо использовать один вариант этого класса.
Я скорее про ResultList. И как формируются List1/List2? Туда ведь делается много добавлений.
По-прежнему некорректный формат даты (дата через точки должна быть)
Используй BigInteger.ONE
И ты не исправил название директории.
Здесь беда с пробелами.
Странные отступы.
Why `wrapRootUri` is called with that name here and in previous method called `serviceBusWrapUri`?
This is how I would do it:

```
let inspectorPanel = …inspector;
let target = inspectorPanel.target;
if (StyleEditorDefinition.isTargetSupported(target)) {
  let toolbox = gDevTools.getToolboxForTarget(tab);
  toolbox.selectTool("styleeditor");
  let seEditor = toolbox.getToolPanels().get("styleeditor");
  if (seEditor.isReady) {
     seEditor.selectStylesheet()
  } else {
    seEditor.once("ready", function() {
     seEditor.selectStylesheet();
    });
  }
}
```

It's sad that `selectTool` doesn't return the panel. Maybe you can fix that at the same time.
Removed the construction link.
Ignore the last comment, this looks good, but I'm not sure what it's used for..?
Not yet, but we will in the following pull.
Sorry to be a pain over this pull but I just noticed this action chain. Now we want to run on Aurora which does not support native events can you just make this a regular click? I tested it and it worked so should be easy to finalise this pull now.
> これかな http://jira.grails.org/browse/GRAILS-6462 意味的は Grails 1.2.2 からは@Test@のサフィックスもサポートしています。 ですかね。今2.1.2でためしたらちゃんとTestで動きました。

そのチケットは別件ですね。名前の解決ロジックにバグがあっただけかと。

http://jira.grails.org/browse/GRAILS-4099  /test/unit/**/*Test.java files are ignored

こっちですね。
1.2.2からTestもサポートしてる、ってことでFAのようです。
Add TODO to investigate this.
This is not that important, so we can can also leave it as it is, I think. But you could rename `rank.py` to `rank.pyx` and make them Cython source, so you already get access to the cdef functions and can leave out the wrappers.
This is actually tested in ``test_common`` afaik. It is also tested whether the prediction is actually the argmax of the probability.
Not sure if there is a test for ``predict_log_proba`` but if not, I'd rather add it there than here.
I tried a few C values by hand and it didn't improve accuracy. I thought iris is linearly separable so I might haven't tried the right values.
I'm not so familiar with this module but if the ``y`` wasn't preprocessed before, you should probably do an "unique" with return_inverse (use the one from utils for backward compatibility) so get integer labels from whatever what put in.  Not sure how this fit is called, though, so maybe you should wait for Jakes opinion.
Wlog?
Good point. We should probably rely on the underlying `base_estimator` to do that if needed.
We avoid post-`if`s. Can you please make this a multi-line `if`?
Password is used also for simulator, so --password will be more correct.
Short options updated.
Somehow V8 is safe enough to not crash on this.  Added explicit length check to make it explicit..
Est-ce que je fais un aussi ? 

POST /bugs/:id/edit  controllers.Bugtrackers.editBug(id:Long)
Please fix the french
It doesn't make sense to have a default value here. It should be:

```java
public @interface CustomTitle {
  int value();
}
```
I think it is... you could alternatively say return resolved.getLink() (slightly less efficient). But just returning resolved would return a pointer to an object that was about to be released and potentially freed.
Not sure I agree about that...
It wasn't being used before, so I removed it. Maybe that was a different bug.
If we use `%w{}` or `<<-`, we'll get extra whitespace. Is that OK?
```datatype``` not used.
Add 		background-image: linear-gradient(top left,rgb(112,138,144),rgb(211,211,211));
		/*Opera Gradient*/ 

For Opera Gradient support. (Also needs to be added in body div as well.
OK that makes sense.

I just had a look at the `FormExtension::renderLabel` method signature and that passes the optional label as the 2nd arg:

```js
symfony.bridge.twig.extension.FormExtension.prototype.renderLabel = function(view, opt_label, opt_variables) {

}
```

So in theory, using this method in userland would be OK because you don't pass the label with a key `"label"`. However, consider userland code (i.e. uncompiled code) calling it like this:

```js
formExtension.renderLabel(view, null, {"label": "The label"});
```

Perhaps this would be discouraged anyway, because users are given the `label` argument, but there's nothing stopping them from doing this. If they did get away with this code and it was compiled down to `opt_variables.a`, then they'd have an error or at least a hard-to-find bug: "why isn't my label showing?!".

So perhaps we can leave this how it is, no? But thanks for making me aware of the issue here.
I thought about it. If every chain will be decorated by this one, it would not be the case
So instead of writing a new wrapper - use my_fixture_read ... this will give you a relative lookup based on the original spec file that called it.

    my_fixture_read("i68pc")

Will get it from:

    spec/fixtures/unit/util/processor/i86pc

Also - 'readlines' is not valid in this case anyway (rspec test breaks), probably should be 'read' (even though the other example _does_ work).
Indeed, thanks for spotting this. I was sure I considered this, but fumbled it in the end.

Added a new commit that fixes this. @jswartwood, care to review and pull to 'dev' as well?
I have tried alot with chained css locator but somehow it chained does not work with driver.This is the reason we could not use chained css locator till yet. 
However, I am able to locate in IDE with following chained css :  css=#recent_read_review>table>tbody tr , div#recent_read_review.p-body table.data-tbl  tbody  tr  td:nth(4).
getting following error:

The given selector div#recent_read_review.p-body table.data-tbl  tbody tr:nth(2) td:nth(4)  is either invalid or does not result in a Web
use cc-left here as well
This shouldn't block the merge, but for future reference: I have no problem with whitespace fixes sometimes piggy-backing on functional changes in a file, but prefer not to have a file change committed purely for whitespace change -- that's where the history log really starts to seem confusing.
You could just check `(= (sort (vals (frequencies (map rank hand)))) [1 2 2])` and the `(four-of-a-kind? hand)`.
One extra space in `",  "` that makes the `book->string` tests fail. No worries, you still get the points from both.
filterille voi antaa alive? funktion suoraan parametrina: `(filter alive? authors)`
Does not use destructuring.
A better question is 'Was the original code tested?'

It has been tested on Linux and Windows. If someone sends me a Mac...

There are two changes. The first makes Windows the same as Linux and Mac (path.replace("/","\\"))

The second (if ... Windows) breaks the buildserver on Windows.
Same here, it should be "invert" instead of "inverse"
We need to come up with a generic description for all default recipes.
whitespace around operators (PEP8)
The contents of the method need indenting by 4 spaces.
oks naiwan lang hehehe
There is nothing wrong with `{% set %}` and pep8 doen't apply to html.
Do we need the negative in the name `nonWaterColor`?  Perhaps `landColor`?
I personally can live without it for a few days or weeks, but I bet every person authoring a CZML file with an external image will run into it, so it's probably better to do sooner than later.
We can do this directly, and we have to factor in insets (which are set when there's a keyboard about)
On IOS currently only supported on Ti.XML.Element
I think we should name this "function-bind" to make it more clear that this is only for functions
should just say document here, this inner function should not depend on knowing initialized or not.
You mean extracting from `options`, and then reusing `options` as something different?

That is confusing, will fix.
Polluting the namespace with a 'good' variable name. Why not [c for c in configs if not ...] ? If you do not use c in the rest of the code, it'll be fine :-D
On second thought, if you look at the Redis spec, you *can* supply `"10"` as a valid amount. Hence, we need to check that the given value can be parsed into an int. If it can't (equals NaN) then we should throw.
The goal was to dynamically satisfy dependencies of gems on the list, not to change the way we decided what gems were installed on the system.  Given that installation uses the full mirror, any dependency resolution on *install* will be handled by the `gem` command.

(...and, yes, it is stupid that they don't have a command to save locally a gem, and all dependent gems.  It was only that specific stupidity that this was aimed at combatting.)
Ideally, I'd like to see this formatting:

    this.http.get(
        "http://www.httpbin.org/get", [],
        {a: 1, b: {c: "ab", d: 12}}, 0,
        function(err, res) {
            var args = res.data.args;
            test.strictEqual(args.a, "1");
            test.strictEqual(args.b, "ab");
            test.strictEqual(
                res.data.url,
                "http://www.httpbin.org/get?a=1&b=ab&b=12"
            );
            test.done();
        }
    );

But, we can do this during the merge if you'd like.
если хоть один невалиден, тебе нужно экцепшн кидать
Nope. I preferred to keep the method as DRY and concise as possible, over preventing silly syntax constructs; app.removeBack(4); still compiles with @property. I can make the signature more restrictive if it's a concern.
Wow. Is that Digital Mars Make-specific?

Anyway, if it's intended, ignore me. :)
same here (I'm just worried about the mandatory tests for a rare case)
This is missing a couple of checks - there must be constructors for key and value accepting t[0] and t[1].
Maybe we could special-case allSatisfy for lambdas instead of adding Lambda. Overall I think it's a poor approach to define a new abstraction whenever there's a new particular need that current abstractions should handle but don't. That's a bug, not an opportunity for a new concept. There are limits of course but in this case I think allSatisfy should be modified and made satisfactory. Besides the proposed abstraction is mightily confusing in the first place - people who see Lambda!((a) => a < 7) may think that (a) => a < 7 itself is /not/ a lambda etc.
Do you meant to add it in *druntime*? I'm tired to tell that currently we have no templates in *druntime*. And I'm not the one who thinks it should be there so you will have to move *all* required templates in a consistent way out from *Phobos* first.
It's a good idea to wrap long lines at 120 chars especially for public repos.
If things get really crazy, you could try and subclass, yes. But EasyBuild would have to be aware of version-specific easyblocks, since it auto-determines whether an easyblock for a particular software package is available or not.
Seeing as you're in the file could you update this please? Thankies
For release almost all of these messages should be logged at trace level rather than debug.
Could you revise the PR to not include this change?
Any reason this doesn't encapsulate the class or can be removed?
this does make some sense, is_numeric use case cannot be extrapolated to other types.
don't need `points_total` now. just use `count` later.
can we add a comment here why we overwrite, so we are not too confused when reading this code in a few months.
Ahh, I hadn't thought of using set this way, but that makes sense.  That's cool.  I hadn't really thought of set to set comparisons, but this works nicely.  Thanks for the tip!  fixed.
Hmm, I guess you're right.  it ends up with more wrangling in the suiteimporter, which makes it less clear anyway.  removing it.
Concerning conditional statements, I believe it's good practice to enforce Yoda conditions.
"... but the fact that we are injecting name now..."

That's my point; if you look at the parser, you are STILL injecting by reference - that's why I am totally confused - we are not doing any runtime resolution anyhow.
Maybe we can do away with this para?
Maybe now it will be enough to use here just 'LIST_MESSAGEIDS_BY_GROUP_KEY' ?
Also can you explain what is the reason to use here AtomicReferences ? If have time, of course.
Finally! A poll that returns 1 record from the DB :-)

And this looks right; and certainly easier to read than the last go-around :-)

However (there's always a however :-) ...

It would be nice if this was the __default__ poll query, and allow them to override it via a setter. That way, for large groups, users can write an optimized query for their DBMS (e.g. ... ORDER BY LIMIT 1 for MySQL). Of course, there would have to be rules (they have to return MESSAGE_ID and MESSAGE_BYTES) and we couldn't enforce it.

Part of the reason for my nervousness here is, are we __sure__ all the supported databases support sub-selects (MySQL does, but only fairly recently).

Hence I wonder if we should continue to distriubute the legacy message store in addition to this one, at least as a fall-back.
I know, but what I'm talking about is how we determine the *default* ConversionService instance when it's not provided. It should be consistent with IntegrationContextUtils, right?
"speical"? Perhaps run the changelog through spellcheck would be good.
If you go up a few lines, you'll see

> user = form.save()

This means that Userena has created the user, who now has a username.

So,

> authenticate(username=user.username   ...

Makes sense.

Can you give more information on the issue? What are the values of user.username and request.POST['password'] when a new user tries to sign in?
you can refactor 314-321 int something like this
```
    raise "Position and file not saved!" unless master_info['Master_instance_uuid']
    raise "FATAL: snapshot was taken from a different master! snap_master was:#{master_info['Master_instance_uuid']} \
      != current master: #{node[:db][:current_master_uuid]}" unless master_info['Master_instance_uuid'] == node[:db][:current_master_uuid]
```
please don't introduce CS issues. Symfony CS ask for an empty line before return statements
I think it might be very common to have company wide DNS recursors. Maybe those are highly available already. We aim to completely remove DNS from all but one smart proxy. It should also solely be an authoritative nameserver and transfers the zones to our public nameservers. Not sure if it's an edge case but it's one we value very much.
missing schema in the URI `http://`
We will not have a sitemap on this portal. ;-)
yes, we changed that once the parent (actually parent + nodename)
strategy worked. its the most natural way to do, as with assigned, its
much less obvious that there must always be a direct parent document.
This will be fixed in my branch. Currently sysadmins/server-tables.txt
Can you remove the extra line return to respect CS ?

thanks
can you create a specific function ? and throw an exception if subclass is set but the key does not exist ?
OK, agreed. Now is like that.
This makes testing it difficult, as neither mock nor fudge have a way of mocking out _removing_ an attribute. With the None check, I can mock out the setting by setting it to None.
How about `class Foo extends Record { val x = ... }`? I'm not sure if this is actually supported right now, but we may want to support case classes in the future. Would `m: Manifest[_ <: Record]` work for the constraint?
I think it would be better if we used proper dashes (ASCII #150) – like so – instead of hyphens to wrap such insertions (I know that's quite nit-picking :-).
would be removed soon, just for debugging
zaim put the print
Лучше так: "ТехЛид и архитектор в секретном e-commerce проекте, специалист по широкому кругу клиентских технологий, разработчик мобильных приложений."
That looks odd, but I assume intentional?
Ещё опечатка, *многогие*
use ``findDefinition`` here instead of assuming it is an alias of a service (it could be a definition directly, or an alias of an alias, and both these cases are broken with your code)
Does this actually return nil if no root is found?
Why downgrade findbugs? This might cause trouble for our jenkins findbugs integration
Should check for movie != nil
This is not correct. includeSystemResources indicates whether or not `getResource` will look in the system (Android) resources bundle, if the resource is not found in the application's resource bundle.

If the resource is not found in either location, than an exception is thrown (regardless of whether or not `includeSystemResources` is true)
@Eric-Brison coucou !
Seems like this could be overly broad.  Is it fair to assume that this parameter is sufficient for differentiation?
It should be named fully after the bundles name: `blowfish-password-encoder-bundle`.
again, `pull` before.
Should we be calling this here?  When the event thread calls StopEvents, it's calling pthread_join on itself.
Ooh! Good tip. I do the same!
I don't think we should default the URL, it's the one required argument, specified seperately from opts.

E.g. the signature of the plugin is:

$('#container').spwWidgetize(url, opts); // url is the url (duh), opts is the dict of options.