labofsahil/github-event-dataset-2012 huggingface dataset:
minor nitpick, but let's set this to `[4,0]`, since it is technically the fourth backwards-incompatible revision of the spec.
Indeed, but I see no other file that would fit better. If more things like this come around, we can still move it to a separate file.
I was just replicating the Fluent API, so I'd argue yes.
@carlosmn is indeed right here. I just checked to compile one of my projects for 32 Bit runing CMake from a 64-Bit MSVC environment. Giving cmake the right generator name is enough to make it work (It failed for me though, where _I_ expected to be in a 64 Bit Environment, but that is orthogonal here). However, I am using VS 9, not 10. Maybe there's a bug in V10 / CMake anywhere or it's an 'express' issue.

Btw. the correct generators are:
```
Visual Studio 10            = Generates Visual Studio 10 project files.
Visual Studio 10 IA64       = Generates Visual Studio 10 Itanium project
                              files.
Visual Studio 10 Win64      = Generates Visual Studio 10 Win64 project
                              files.
Visual Studio 11            = Generates Visual Studio 11 project files.
Visual Studio 11 ARM        = Generates Visual Studio 11 ARM project files.
Visual Studio 11 Win64      = Generates Visual Studio 11 Win64 project
                              files.
Visual Studio 6             = Generates Visual Studio 6 project files.
Visual Studio 7             = Generates Visual Studio .NET 2002 project
                              files.
Visual Studio 7 .NET 2003   = Generates Visual Studio .NET 2003 project
                              files.
Visual Studio 8 2005        = Generates Visual Studio .NET 2005 project
                              files.
Visual Studio 8 2005 Win64  = Generates Visual Studio .NET 2005 Win64
                              project files.
Visual Studio 9 2008        = Generates Visual Studio 9 2008 project files.
Visual Studio 9 2008 IA64   = Generates Visual Studio 9 2008 Itanium
                              project files.
Visual Studio 9 2008 Win64  = Generates Visual Studio 9 2008 Win64 project
                              files.
```
( from CMake 2.8.9 )
This constant is deprecated, so it would be an error to return it. I thought `assert(0)` wasn't a horrible solution, but it does probably need a comment explaining why.
Although that doesn't create the profile. So we also have:

```
from users.tests import profile
p = profile(user=u, save=True)
```
hmm, did this actually fix it when you had a global funfactory installed? It might need to be ``sys.path.insert(0, ...)``
in test 10, the address is in the position where a line number normally is. While it is highly unlikely, I just making sure that there is no adverse interaction between the line_number_killer and the addr_killer.
On Fri, Dec 21, 2012 at 04:45:09PM -0800, Rob Hudson wrote:
>Ok. An invalid path is when that happens. Would an admin message and a redirect could be more informative for the user?

I suppose I may as well.

-- 
Kris Maglione

The cardinal doctrine of a fanatic's creed is that his enemies are the
enemies of God.
	--Andrew Dickson White
"수정일시: "
should be
"수정일: "
@drak 

Loading this translation gives two entries into our internal $messages.
```php
array(
  'One sheep' => 'un mouton',
  '@count sheeps' => 'un mouton|@count moutons'
);
```
But the PoFileDumper should merge these back into one Gettext item. I fixed this in my latest push partly as the solution taken is searching for 'un mouton' then replace that while dumping into a single unit with its plural form. See PoFileDumper::extractSingulars.

But what if $messages contains to translation entries with 'un mouton'?

I hope I documented that code good enough.
You should remove the ``de3`` subdomain
maybe this should be array_replace_recursive()? then again maybe more surprising than helpful.
Use ```self```` instead of ```static```.  The method is declared as private. :)
Not totally sure I'm following the above conversation, but if we're to use this in production it will need to support some form of prepared statement substitution. Server-side prepared statements are slower for many use cases and much more difficult to resource-manage. It's quite easy to accidentally run the server out of prepared statement handles and then everybody loses. I generally recommend with MySQL Connector/J JDBC driver to always set useServerPrepStmts=false, causing the client-side to always do the substitution.
Newlines around the `expects` line
@joshuaclayton : What would the object that wraps the information look like? A little struct with three attributes?
Replace `ID` with `identifier`.
Replace by markdown array.
I thought we agreed that the ONLY cases where alpha would be assumed were (a) 3 channel, unlabeled: alpha = 1.0; (b) 4-channel unlabeled: alpha = channel 3.  All other combinations with no explicitly labeled alpha_channel should be rejected by "over".



On Jun 21, 2012, at 2:43 PM, StefanStavrev wrote:

>> +    
>> +	ImageBuf::ConstIterator<Atype, float> a (A);
>> +	ImageBuf::ConstIterator<Btype, float> b (B);    
>> +    ImageBuf::Iterator<Rtype, float> r (R, roi);               
>> +    for ( ; ! r.done(); r++) {
>> +        a.pos (r.x(), r.y(), r.z());
>> +        b.pos (r.x(), r.y(), r.z());
>> +
>> +        if (! a.valid()) {
>> +            if (! b.valid()) {
>> +                // a and b invalid.
>> +                for (int c = 0; c < channels_R; c++) { r[c] = 0.0f; }
>> +            } else {
>> +                // a invalid, b valid.
>> +                for (int c = 0; c < channels_B; c++) { r[c] = b[c]; }
>> +                if (! has_alpha_B) { r[3] = 1.0f; }
> 
> You mean assume alpha = 1.0 for all images without alpha channel? No matter how many channels they have?
> 
> Hmm, I think we agreed then to handle just those two cases if alpha is not specified. But let me know whatever you want me to change. At this point we handle the case where both input images have alpha channels specified in same positions, and we allow only for images with number of channels 3 and 4 not to have alpha channel.
> 
> 
> 
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/OpenImageIO/oiio/pull/381/files#r1029813

--
Larry Gritz
lg@larrygritz.com
Ah... I see, it's for the `from_epsg` function below. So now the question is, what are *either* of them doing here at all? :wink:
In a way, it's a lag test! You can check if your ping is high :)
This should be riak_cs for the branch.
javascript variable scoping doesn't work like this (there's no such thing as block scope, everything is function scope) so repeated `var`s are redundant.  It's probably better to just declare one `var tabToActivate` at the top level.
@ojii that whole for loop could be taken out actually.  What this is doing is writing out the first level of menu nodes, but making an empty ul inside of that element so that I know that it does have children and so that the '+' sign is added by jstree.

That's how I remember it anyway, been awhile since I wrote this.  But it does work with the whole loop taken out, I just tested locally.
嗯，那`_resultData`中如果存的就是`TableViewCell`的Array，那是不是不太好，比较占内存？
还是说只要这里先定义一个局部变量`tmp = [_resultData objectAtIndex:i]`，后面再把tmp中的一些数据赋给`cell`变量就好了？
Could this be a instance variable?
Since this is a public class, this change is going to break compatibility.
I don't think this path should be hard coded, it should be possible to modify it in standalone.xml
You do not need to wrap ConcurrentHashMap inside a synchronizedMap, just do:

transactions = new ConcurrentHashMap<String, Transaction>();
participants = new ConcurrentHashMap<String, LinkHolder>();
@jzaefferer This needs to be moved to `icons` and configurable. @sgharms ignore this comment for now, it's unrelated to the PR.
hah - I stopped reading at the part of the sentence I guess.

great, thanks
you can just do res.render("index");

no need for the data
Rewrote the description
I have the same thought while I was implementing. The reason why I haven't made this change is because, I am not sure which way to create different elements will be more efficiently and flexible.

Music app should have four kinds of list, which means four styles for list elements. I am thinking to use templates to achieve this. Something like put all the templates in HTML then use <code>element.cloneNode()</code> in JS to create different list elements, or I should just keep the common parts of JS codes then rewrite a new one, do you have any suggestion?
True,

Adding the search by company as well :)

Good catch!
Is it against your personal believe to not to use `d.getHours()`??
This file do nothing more than

- check mozSettings `bluetooth.enabled`
- if true, call `mozBluetooth.setEnabled(true)`

Have you consider moving this entirely into Gecko, hide the `setEnabled` API function, and have the web content to turn on/off bluetooth only with mozSettings? Have a mozSettings key that do nothing to the platform but only achieve cross-domain communication or retain a value for reboot is really bad.

If what this file does is temporary, move it into `bootstrap.js` hand have `// XXX Bugzilla #` on top of it.
toggle-selection? (most of the contacts.css rules does not use camel case)
I will check it and also I will try to get available 'edit-mode' in browser, because now it's not working properly. I would like to have dialer 'working' in Browser as in SMS, because we are going to optimize our development&testing time. I would like to work on it once Dialer will be fully functional.
Well, any suggestion @arcturus @etiennesegonzac  ? We have @gtorodelvalle and @albertopq waiting for getting dialer ready in next PR! ;)
Nit: as we already have a general-purpose `js/utils.js` file, would you please move this `FileSizeFormatter` object to `js/utils.js` instead of creating a new file?
I suspect we will encounter perf problem with this style, but let's see.
Is it working with negative id? Negative ID means user generated so they never checked by duplicates! So please check if just -5 is working. I think I introduced it in order avoid these checks. However I think -original.value should work fine.

Actually these could be an issue for MapGenerator. I still strongly insist to not use random at sll! One day it could fail.Please user static variable with negative counter. Negative will not be checked on the client side.
We also want a deprecation warning to be printed, so that folks using this notice that it has been deprecated (updating the docs isn't usually enough).  You can use `RSpec.deprecate` for this....something like:

``` ruby
def red(text)
  RSpec.deprecate("RSpec::Core::Formatters::BaseTextFormatter#red", "#failure_color", "3.0")
  color(text, :red)
end
```

(you should check the produced message to make sure it makes sense).

As a side note: do we think that this method should continue to color things red (regardless of the configured failure color) or should it start using the configured failure color?  (This question applies to all the other deprecated methods, too).
again with the spacing...
s/エクポーと/エクスポート/
fair enough, I'll make the required changes
I'd rather have

```
if g.BOARD is 'f'
  '9999'
else
  'new'
```

If you want to add another possibility, you'll just have to add two lines instead of changing everything:

```
if g.BOARD is 'f'
  '9999'
else if condition
  possibility
else
  'new'
```

Same applies to other ifelses.
intercaps meaning function names and variable names should be spelled with intervening capital letters, not underscores:
```
my_variable # bad
myVariable # good
```
This follows the convention in Buildbot.

I don't know about function names being capitalized, but if that's what jshint likes, that's fine.
You are right.  I will fix it momentarily, sorry for the error. 高明 ganhar :-).  More 勤奋  too.
you need to break the loop, otherwise you will use the last found, not the first one
hmm, actually, it looks like you are using a variable variable name, but this is confusing IMO. You should maybe write it ``${$linkType}`` to make it clearer that it is expected and not a typo (or find another way to achieve the logic avoiding such variable naming)
please add a use statement for the class. And you should probably keep it as a class attribute instead of creating a new one each time
simply use ``if`` instead of ``elseif`` as the previous ``if`` leaves the execution of this iteration of the loop
lineno = sqlite3_column_int(stmt,0); /* ID of signature */

ID of signature == lineno == primary key in database (sid)
what about server_msg?
El 05/12/12 21:46, Brian E. Granger escribió:
>
> Let's put the HTML code in a separate file and read it in. That would 
> allow us to use jinja2 to template over variables if we need to.
>
> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/ipython/nbconvert/pull/63/files#r2329548>.
>

I agree with you, I willl separate them.
Line break ?
I still don't understand why we register `nsICommandLineHandler` if we don't handle command line arguments.
cfx should return an exit code, here, it doesn't and ends up failing during `cfx testcfx`.
I'd suggest simply adding `sys.exit(0)` here, and, disable `testcfx` when `-f` is given.
You can do so by making this line conditional:
https://github.com/mozilla/addon-sdk/blob/master/python-lib/cuddlefish/__init__.py#L328
Something like `if not defaults['filter']:`
> So options.load is equal to require('api-utils/loader') ?

I think either you or me is lost. But `options.load` is equivalent of `require('api-utils/loader').load` but a different instance of that function. `loader` itself is passed as `options.loader` either way.
I would honestly prefer something like `serialize(harnessOptions)` omitting keys that should not be written than deleting properties all over the place. That way all property cherry-picking can be seen in one locations in contrast to how it's done now, where you have to look up of deletes all over the place.
I guess we should go and be consistent throughout state.js?  Maybe after this patch?
@benadida - should this be navigator.id.raiseAuthenticationFailure - when cancelling from the sample IdP, this errors saying
Yes, I think your right. What is that 0 for in front of Version?

I'll update Version to `0.2012.08.17` and Release: to `2%{?dist}_%{svnrev}`
it seems we need check support to return a signal if the IdP is explicitly disabled.  the test becomes `(r.type === 'secondary' && primarySeenRecently && !r.explicitlyDisabled)`.

@callahad nice find!  does this sound reasonable?

@warner I can't find the race in your reasoning.  If an idp is seen, `r.type === 'primary'`, in which case `primarySeenRecently` doesn't come into play, so the fact that it's out of date doesn't matter (and it should get up to date in ms).  Am I missing something?
(I realize that the original code was using this value, so I'm not criticizing this pull-request.)

Is there a reason why we limit the password to 80 characters as opposed to say 255?
Since gotVerificationSecret's hash argument was an empty string, then this block never executes, right?
All that is right, but `aBrowser.mCurrentBrowser.currentURI` is clearly wrong. `aBrowser` is already the current browser and shouldn't have an additionally `mCurrentBrowser` property attached.
You should import EventPage, instead of MediaPage
Any context where this flag would be used? Should we delegate this to the caller?
I think when I had this idea I was under the assumption that there wouldn't be a way to track the last time a warning was logged... but since these are running in daemons then a simple instance variable will do. I'll pull these out and add throttling logic to `Puppet::Network::Authentication`.
Uhm... I'm rather confused now :) do I need to check
"isDefaultPrevented()" or not?

In case... Can't you just fix it by yourself? The patch is damn small,
as it adds only 4 lines per each function (8 lines in total), and you
know the code and the APIs better than me!



Il giorno 04/giu/2012, alle ore 00:51, Richard Pickett
<reply@reply.github.com>
ha scritto:

>> @@ -145,6 +148,9 @@
>>           .css(tp)
>>           .addClass(placement)
>>           .addClass('in')
>> +
>> +          triggerEvent = $.Event('shown')
>> +          this.$element.trigger(triggerEvent)
>
> Since we don't need to use this event again (such as checking `isDefaultPrevented()`), there's no need to create a a `jQuery.Event` for it.
>
> You could simply write:
>
> ```js
> this.$element.trigger('shown')
> ```
>
> Same applies for hidden.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/twitter/bootstrap/pull/3691/files#r920243
might be worth refactoring this into an abstract IntShardWriter and IntShardReader that has two underlying implementations...
The above (addition to $list) should be implemented in the now removed addServer() method, adding an additional, optional argument ($weight).
lier
duplicate comment info and incorrect @package.
`La risposta è tramite` -> ```Ciò avviene tramite un cosiddetto `alias` che viene assegnato al controller```
The second parameter should be documented in the docblock.
Should you call wtu.create3DContext(newCanvas) or something. "experimental-webgl" is not really spec compliant
Why not just make this a regular function? 

private static AzureCache(IConfiguration configuration)?
Did this file get included accidentally?
a = asynchronous
@redhog mentioned something about this on Saturday to @Pita, not sure what the context was...  Something about allowing synchronous hooks being a bad idea or something//
Can you change this to `<h1>` and `<b>` (below) to `<h2>`?
(each div)
ack. I thought I'd ask because I don't like having two copies of the source code. I'm happy to leave it as you had it.
README.txt doesn't exist anymore…
There was a discussion of that in a recent pull request on the style guide and this was the decision that was made.

Even when you check in a Gemfile.lock it can be hard to understand which dependency changes "just happened" and which were the developer's intention.

With the ~> syntax it's pretty easy to pull in a change you didn't intend to while updating something else, and given that we need to be very careful in how we review new dependencies that's not something we want.
Same as above. You should probably check for summaryList presence.
There was tabs.
How should it be formatted?
what specifically do you need to know here? everything in there is an association. i assume you are asking more about ``$this->fieldMappings``? in there we afaik do not have any associations.
Zonder Toon Willems., he made no changes imho. Do reformat though.
Ah yes, now I see it. Maybe use some white space to separate pieces of this code?
It's just cleaner. Also, in plain text you do not put a space before the :, only after it. It makes things more readable.
docstrings all over this module
This @Default is uneeded, I'll remove it before merge.
Yeah I guess the trailing ? doesn't hurt too much in that case ;)
Wouldn't these all make more sense as IDs instead of classes? They only occur once, yes?
This is crappy. I should add `request` to the imports in `basket.__init__`.
You mean cue.

Yes, but I try to continue using the one that is in the file, until the whole file is updated.

File a ticket to go through and update all references of exec to cue?
@shalott Updated
and a space after `===` & `,`
Changed it in b63868cacd4de6cecaf0e95731735d810cd48d64.
What's is the alternative?
(Note that the reason we require ~> 1.4 is that pre-1.4 didn't support using your own CA file, or something along those lines. ~> 1.4 allows people to use any version above 1.4 but less than 2.0. We should probably add this to the README.)
@ohadlevy what's this pin-version for?
do you have an example for search param?
finally { something()? }
base.shutdown?
Log level?
should actually be kwargs.items()
値の比較に"==="を使用し、ユニークな値を要素とする配列を返します。事前に配列がソートされていることがわかっていれば、*isSorted* にtrueを与えることで、より高速に実行されます。ユニークな値を変形によって算出したい場合は*iterator* 引数に関数を渡して下さい。
So to accept this one, I would want to suggest to either:

1. Move the BYHOUR logic to FREQ=DAILY, Or:
2. At least ensure that it is not possible to write a rule that will crash servers
well, just because 49 cannot pass my test. 30 will do.
True this is
многовато параметров...
Pulling all the repos and iterating over them will get quite expensive. This query will actually try to hit the DB for every repo you have under your username :0 though I believe the sql response would be cached in rails, so it wouldn't be too bad. 

How about this instead:
The Repo create action already does a check to see if the repo exists first. We could just have a generic subscribe button. After a repo is "created" the user who tried to create it is automatically subscribed. What do you think?
I don't think this should be here...

this is already on master so you should update
That statement instructs git to detect text files, and normalize to LF at each commit
Is this message actually intended to be logged?
I think we can simplify the rest of this paragraph to just:

  To handle this, you can use `curl`'s `-G` and `--data-urlencode` options. Example:
`:else` isn't actually allowed here, it will just try to dispatch on the case where the value is `:else`. It should just be the default value at the end. And I guess that means this needs a test for the negative case. ;)
`i` is the instance of page and `id` is nil so this produces select tree with empty values for options. Can you fix it please? Thanks!
if a timeout is inevitable, it should be `setTimeout(callback, 1000, null, true)` or setTimeout(callback, 1000, [null, true])`. (Not entirely sure which one it is.)
Listing the dependencies only in bundleDependencies doesn't work (`npm prune` still deletes them), the npm docs say `bundledDependencies` and `bundleDependencies` are both acceptable.
When "Replace All" attacks? :)
This looks like an accidental extra space.
Has this been fixed or why is base64_encode used here instead of mail_quotedprintable_encode? Is that other code still needed or why is it there, commented out?
Something as basic as ```puts "N: #@facing, x: #@x, y: #@y" unless @x == @previous_x && @y == @previous_y``` will prevent a never ending thread of useless output to the console as the thread runs.
Метод isNotEqualTo: входит в протокол NSComparisonMethods, т.е. некий обобщенный протокол сравнения объектов. Но для строк пожалуй лучше использовать для них и предназначеный isEqualToString:
that actually is a different problem. This is some of the ancient code where galaxy did a lot of things "magically". Guessing the IP is one thing (at Ning, this always worked).

The whole || "http://..." block should go away and the rake targets should pass in the config setting explicitly as http://0.0.0.0 (or, preferred http://127.0.0.1/)
Might be worth noting in the doc block that you can pass in the search words as separate arguments instead of an array.
закомменченный код! фуфуфу :))
ну непонятно зачем это. Не работает - значит не надо заглушек. Кроме того это будет другой контроллер
Don't put questions in the code, please.
I did check the functions.  Here they are for your review, from room_data.h:

room_is_watery(struct room_data *room)
{
    int sect = room->sector_type;
    return (sect == SECT_WATER_NOSWIM ||
            sect == SECT_WATER_SWIM ||
            sect == SECT_UNDERWATER ||
            sect == SECT_ELEMENTAL_WATER ||
            sect == SECT_DEEP_OCEAN);
}

room_is_open_air(struct room_data *room)
{
    int sect = room->sector_type;
    return (sect == SECT_FLYING ||
            sect == SECT_ELEMENTAL_AIR ||
            sect == SECT_ELEMENTAL_RADIANCE ||
            sect == SECT_ELEMENTAL_LIGHTNING ||
            sect == SECT_ELEMENTAL_VACUUM);
}

Look good in light of that?
I'll go ahead and add the handling for these on the upload handler / work them into the netcdf
Drop "signifies".
:trollface: Could you add this back please?
How about "Hey! You need to set HUBOT_GITHUB_REPO and HUBOT_GITHUB_TOKEN before I can link to that commit." Otherwise, as a user it's unclear what that is for.
i keeped them to get feedback on whther the proposed change is valid.

On 19.10.2012, at 20:56, Martin Luessi <notifications@github.com> wrote:

> In mne/artifacts/ica.py:
> 
> > +
> > +    def _get_epochs_data(self, epochs, picks):
> > +        """Helper function"""
> > +        data = epochs._data if epochs.preload else epochs.get_data()
> > +        data, pre_whitener = self._pre_whiten(np.hstack(data), epochs.info,
> > +                                              picks)
> > +        return data, pre_whitener
> > +
> > +    def _pick_sources(self, sources, include, exclude):
> > +        """Helper function"""
> > +        mixing = self.mixing.copy()
> > +        pre_whitener = self.pre_whitener.copy()
> > +        if self.noise_cov is None:  # revert standardization
> > +            pre_whitener **= -1
> > +            mixing *= pre_whitener
> > +            # mixing *= pre_whitener.T
> is there a reason to keep the commented lines?
> 
> —
> Reply to this email directly or view it on GitHub.
>
after these assertions, modify cn1b to have higher priority (make it preferred), save it and try the search again -- cn1b should now be first.
You shouldn't log things that are then re-thrown. This causes duplicate log messages and is confusing.
Doesn't a node need to know its children edges?
Oh right. Was not aware of those constraints. I will use your example as an implementation.
总觉得心跳不应该有自己驱动下一次心跳，应该是在外面有一个setInterval 来定时调用心跳
@ricardclau I mean something like this:

    Before and after filters with ``kernel.controller``/``kernel.response`` events
note that this shortcut is only available in the base class proided in HttpKernel. So here, you should better write the actual code (maybe giving a tip about the method in the HttpKernel base extension)
I add just a note, but you are right. Maybe it should be better if instead a note I add a section, then I will be able to add the configuration block. What do you think?
可以创建一些和另外变量相关联的变量 -> 可以创建一些变量

下面这句跟这句重复了。
Version must also not be updated in a pull request. (Sorry, I don't want to be rude)
Country is a normal Backbone model, so we should use `country.get('abbreviation')` here
Why not just use Duration(...)?
Щто. Почему бы не написать

    auto userAgent = "LeechCraft Blogique " + Core::Instance ().GetCoreProxy ()->GetVersion ().toUtf8 ();

?
Reason?
It was exercising the broadcast query case.
Ya que estás checkenado por uno y sólo uno, acá podrías usar `.Single()` en lugar de `.FirstOrDefault()`.
Same here: There won't be any invalid fields due to the array_interset, so $succeeded and $failed are obsolete.
Can you change this to `opts.float && opts.bitDepth == 64` instead? I don't wanna call the option `double`, that's confusing.
array isn't defined here. I think I see where you were trying to go here. You may have wanted something like this given your test passes an array:
```ruby
def power(intnumber,powernum)
  square = 1
  (intnumber * powernum).each do |value|
    square *= value
  end
  square
end
```
why store this if it is used only once?
This short and boring source file just explicitly instantiates the virtual destructor.
`namespace.resources.map(&:resource_key)` is causing a test failure ("NoMethodError: undefined method `resource_key'"). What's wrong with leaving that part as `inspect`?
well spotted 
Here is how I'm thinking to solve this:

I don't think there's any point for the state transfer to migrate the local transactions that didn't leave this node for either prepare or lock acquisition. Why? because the tx state will be send across anyway when the transaction will either lock something remotely or it will prepare remotely, so sending the tx state before that is redundant
the LocalTransaction keeps a list with all the remote nodes where this transaction was sent: LocalTransaction.getRemoteLocksAcquired() (name might be a bit misleading)
modify the StateProviderImpl to only send a local transaction as part of the state transfer IFF the transaction left the node, i.e. LocalTransaction.getRemoteLocksAcquired().isEmpty() == false
Same thing here, class name and use of underscores.
If the changes are related to the same JIRA I'd agree to have them squashed, but AFAIK this is another JIRA.
How come a separate static block?  What was wrong with the original line?
This is ok. No complains about that.
Line 1440 of collections.py in my repo uses the same assumption:

    if len(self._offsets):
        xs = self.convert_xunits(self._offsets[:0])

Additionally, searching for all occurences of `_offsets`, I cannot confirm that they can ever assume a `None` value, instead `_offsets` are always an array.
I've only just learnt of the ```matplotlib.use('cairo.pdf')``` style syntax, and IMHO its pretty ugly.

One of the important things that this is doing is limiting the default format in a Cairo backend to ```'png', 'ps', 'pdf', 'svg'``` (I notice that this doesn't include the Cairo backend supported "svgz"), but, as far as I can see, this validation is handled automatically by the rcParams dictionary.

In which case, other than a few fewer keystrokes, I see no benefit to:

```
matplotlib.use('cairo.pdf')
```
over
```
matplotlib.use('cairo')
rcParams['savefig.format'] = 'pdf'
```

Therefore I propose that the Cairo backend be brought back into line with the other backends by removing the ```cariro.<format>``` syntax in ```matpltolib.use```, by exposing a ```get_supported_filetypes``` on the Cairo backend, and by validating the default format at ```savefig``` time (as has been proposed for all backends further down this pull request).
A crash? Can you explain?

Is this - a test issue? marionette issue? platform issue?
Classes and interfaces should be outside the public document root of your webserver, there's no need to clutter the code for this matter.
There should be at most 1 line separating blocks of code.
Actually has_secure_password enforces a validation on the password_digest, meaning it's not possible to save a user without a password really...

Either we work around that validation or we keep it that way.
I didn't change this.
Na tom neni nic těžkýho k pochopení, prostě v kalistu byla funkce schedule, která přeplánovala vlákno a nastavila si časovač na další přerušení. A ty, když jsi přidělal timery, jsi to nastavení časovače dal z tý funkce pryč, čímž jsi změnil její chování. Prostě otázka zní, proč jsi ten timer_start nedal do schedule (void), místo volání toho původního timer_setup, nebo jak se to jmenovalo. Protože tím jsi sice splnil moje přání, ponechat funkci schedule (void), ale ta funkce se stala bez toho nastavení timeru nepoužitelnou. Snad už je to jasný :-)
According to [the API documentation](http://developer.github.com/v3/repos/statuses/#parameters-1):

> State of the status - can be one of `pending`, `success`, `error`, or `failure`.

I guess `error` would be appropriate, at lease for `errored`.
Is it OK to bump the dsk_gen before the new chunk gets setup following the call?
Fixorz.
Would it be possible for the dialect extension to be able to specify this property? If so, this might make this kind of thing more declarative.
``$_SERVER`` does not seem to conform to the naming convention (``^[a-z][a-zA-Z0-9]*$``).
Are you sure the class "Zend\Http\PhpEnvironment\Response" actually exists, or did you maybe forget to add a USE statement?
Ist beerId hier immer sicher gegeben?
These look misaligned.
I think either we shouldn't do this or do the same with JUtility to be consistent.
Wouldn't it make more sense to error out right after the call to parse_url if it returns false? Or am I missing a usecase?
I knew some method like this had to exist. Thanks.
Space after `...`.

Move this to global configuration Ajax error.

http://api.jquery.com/jQuery.ajaxSetup/
When is change called? For every key press too?
Or for now just leave URL here, and add TODO. ;-)
Any reason why you're removing this?
Not an issue really, but I try to avoid negations wherever possible, you could change this to:

    assert response[:redirect].present?
Hmm probable patching error It should be used before sGuildMgr()->LoadGuilds()
I wouldn't use Elvis here... Make it explicit :)
Now that I look at the docs and the code.. this behavior still seems somewhat surprising. It's reasonable to expect some keys to occur at different hierarchy levels, and it would be surprising to have odd hierarchies show up when you think you are filtering them out. Say, you specify "user,id" to get the id of a user. But your records might have a top-level key called id (meaning, id of a record). You'll get some odd matches.

This isn't a made-up case btw -- that's actually what I suspect will happen if you feed Twitter's json representation of a tweet into this loader, it's got status ids, and a nested user object that has a user id also called "id". See https://dev.twitter.com/docs/api/1/get/statuses/user_timeline.  

What you really want is some XPath-like spec language (in fact, xpath might just work) -- but that sounds like a separate project, and shouldn't block progress on satisfying the specific narrow use case you have.

Still, I don't think it's a good idea to put an implementation with such confusing potential side-effects into the top-level JsonLoader.

Maybe make whatever methods you need to be protected, and have a specialized loader that inherits from JsonLoader and does this filtering optimization?
Only if this reporter is used to do anything.
Well as a matter of fact there is a difference between promise resolution and fulfillment:

Promise **A** can be resolved with a promise **B**, which does not necessary means promise **A** will ever be fulfilled. As a matter of fact **A** will be rejected if **B** does. This handler is intentionally called `onFulfill` since it's only ever invoked if enclosed promise promise is fulfilled. Changing name to `onResolve` would be misleading since handler won't be called on promise resolution.
Again, amazon platform support removed.
Probably to some method that was there and is not anymore. I pushed this branch in hurry, I hadn't cleaned up all that. And, after, well... I was distracted :-)
Old habits. Fixed.
You're totally right, neither FINDARG nor XARGSARG are used if this change is made. Pull request updated.
Should this be a `h3` instead?
missing jdoc
I just pushed a version that uses the latter.
The simple rule to remember is that if you declare any variables in the switch statement, you need to use the braces.

The reason has to do with scoping rules in C++.  Since switch statements (unlike basically every other kind of structure) doesn't use braces, technically, any variables defined in the switch statement are in scope from there until the end of the enclosing scope.  So including the next case statements and after the end of the switch.  But this is a problem since it is possible to jump past the declaration.  So what does it mean to use the variable if the run-time path never hit the declaration?  That's why most compilers complain about this with at least a warning if not an error.  And we upgrade all warnings to errors, so it's an error either way for us.
ditto re If's at the start of the lines.
No, definitely not reversing, that's good.  I added my own pedantic clarification just now...
I like all variables being consistently lower case.
load() is gone now.  The correct description should be:
```
@param key     The key name in config indicating which object to build.
```
yes because i think there is only one instance of `OmniAuth:: Strategies::Twitter`in omniauth, if else part is omitted, any subsequent requests will use `authorize` instead of `authenticate `
I caught this but hadn't pushed my commit yet. Fixed in 86b98ad
I see no reason to fix on version for master.
Better to use `Entities.destroy(tapp)`
Fancy CommonCommands.sudo interacted badly with CommonCommands.ok, swapped their order and I think all is well
If you do the refactoring above this could be simplified to material.full_title
sans le comparer a ce qu'ils avaient gagne en passant par la voie classique et sans donner le nombre d'albums vendus ca n'a que peu de poids. honnetement je trouve pas ca beaucoup pour un groupe aussi connu.
@octatone: All functions are callable. Non-functions, however, may be callable. 

* Callable things have `[[Call]]` defined.
* Functions have a [`[[Class]]` of `"Function"` and are callable](http://es5.github.com/#x13.2).

So the set of all callable things is a superset of the set of all functions.

> Also, isn't _.functions/methods purpose to return callable functions?

That was (kind of) my question. Does it return callable things or functions? I think it should return functions. And judging by the docs you quoted, that's what was intended.
Super picky, I know.. but..

Can we rather use HEREDOC for this sort of thing. That is:

```ruby
append_file 'Gemfile', <<RUBY
  group :development, :test do
    gem 'rspec'
  end
RUBY
```

I just find the spacing etc really weird in a single string. Totally personal preference though.
No because this is a new page. 
The same one but still a new updated page
If I was going to check the `RUBY_VERSION`, I'd want to check if it equaled `1.8.6` -- the point in my mind is to make it easy to ack/grep for `1.8.6.` and find lots of places where we can remove code.

I actually considered checking the version in that manner, but decided to use feature detection plus a comment that mentions 1.8.6...that still gives us the search-ability, while still performing the check in a more semantic manner.  Also, if anyone on 1.8.6 loads [backports](https://github.com/marcandre/backports/blob/master/lib/backports/1.8.7/method.rb), it defines `Method#owner` and they could potentially use this first implementation of `uses_generic_implementation_of?`.
Vc consegue fazer algo sem o tmp_dir?
The default Environment class uses a case-insensitive dict implementation. There's no need to lowercase. Same applies for jst_compiler, below, which can just be removed entirely and passed verbatim.
I think you meant 'mysearch'.
I'd rather put everything on one line then.
Erm, Oscar doesn't actually support fixed discount offers at the moment.  Not sure this button belongs here...
Why do we need this twice?
ok, I've removed it
Need it to create random users
I made the change. can you see the update?
in first place full body is chosen to be drawn in rows 235-346, that was before me. I made masks to remove those already drawn limbs. Previously they were masked out if body is husk but simple move of code haven't helped (it used Blend->subtract) and i had to alter it to use alphamask from image-procs.
Should allow you to, by moving, resist the pull of airflow.
Spelling: Layour in loc de Layout.
Yah.  That is actually a good point.  I've come across headaches with that in the past.  Why do we not open Galaxy::Region in consumer apps and override rather than inherit from it?
resStr лишняя переменная. Можно просто return builder.toString()
Вот в этой секции я тоже сомневаюсь. По идее, тут надо бы создавать новый Integer и потом складывать его с уже накопленным, но я боюсь, что так на самом деле не происходит.
`get_params(www_authenticate) if www_authenticate =~ /^Digest/`

No need to split and rejoin the same string.
Typo in MockUser
it is already in the composer.json
You got those reversed no? The RequestParam should be a requirement and QueryParam a parameter I believe.
then please keep it in your own repos, not here. see my note at the bottom
Ick, time.sleep(). Wee probably don't need that.
ça viens de l'api de Jenkins, pour créer un job, il faut passer la configuration xml du job. tu voudrais passer quoi dans le tableau ?
On Wed, Oct 03, 2012 at 03:33:51AM -0700, Andreas Mueller wrote:
> bias is the usual term in the community. before joining sklearn, I never heard
> the word intercept.
> Consistency with community or within sklearn is the question I guess ;)

In any case, the fact that the 2 terminology coexist needs to be stressed
in the documentation. I wasn't aware  that "bias == intercept" :)
Spaces before ":".
Also you have to wrap these into single backticks. Otherwise sphinx complains because they look like rst links.
do we want global seeding in the examples?
do we need ``'\r'`` for windows new lines?

I'm not really familiar with %g but AFAIK it does not ensure a common string length - it would make the output look much nicer if train and oob scores would line up in the same column (maybe we should use ``ljust`` in addition).
This looks like it was meant to be an affinity matrix, not a data matrix.
Maybe use ``generate_blobs`` or something? Iris?
I would rather use `n_columns` or `n_cols` to be consistent with the rest of the project.
Seems that there is an error in the TypeError. It should be 

```
TypeError("base_estimator must be a "
                  "subclass of RegressorMixin")
```
Please use 'set(...)', as this syntax requires Python 2.7.
please remove this extra empty line
This was due to a bug in hash_from_request_body_with_key. Fixed the actual source of the problem so this line can go away.
Yes, I remember thinking for 10s and going 'fuck it'. Will change if you can find something concise and suitable.
Yeah, you can. They just can't conflict; i.e. if the given address is not link-local.

It may not be worth it adding this now.
is there a reason not to catch the specific URLError and use a ui.warn/debug to ease debugging for users?
I know this isn't part of your patch, but is there a reason there's `metavar='ndk_location'` for `--test`?
Have some left over debugging code.
This part skips the cache mechanism for JClasses that we use in AA. CodeModel has its own cache, to return the same JClass instance when asked for the same name. This cache is used when resolving imports : two different JClass instances will lead to two different imports. The problem is that CodeModel doesn't cache JDirectClass instances (which we use a lot). To fix that, we have to use our own cache of String => JClass

The end result is that you end up having a lot of fully qualified name in the generated code, instead of using imports.
We should avoid `directStatement()` as much as possible. Let's use the DSL instead of plain strings, to prevent any mistake.
Licensing added for the implementation from Stack Overflow.
These are local property changes, alongside other local property changes. Probably only a few cycles each, inlined and optimised, so not much of a problem. Also, promotes are executed far away from critical execution and not too often on real code to matter.

IMO, the gain in clarity and robustness is orders of magnitude more important than the few cycles lost.
See if 63f196ba04b83d26e2cc334c1a19a0a32b8971d1 addresses that.
@Gozala, I don't understand this. When you say "explaining that it's loaded for each tab" are you referring to the second sentence "The following add-on logs the HTML content of every tab the user loads"? Because that's talking about the example that follows, not about content scripts. So unless you're asking to remove the example, I don't think this sentence can be removed really.
the property is never sued
I think this option is related to having two nvidia cards.
Other MBP users reported bumblebee to work because they were 2010+ laptops, weren't they?
I think that the two first lines are clear enough for non-techies. I just can't find better words at this hours : )
Sure, there are examples of re raising exceptions on msf, just do a grep from the modules directory: 

<pre>
grep -r "raise \$\!" *
</pre>

A smaller sample for reraise exception:

```ruby
def test
	begin
		a = 2/0
	rescue Exception => e
		puts "#{e.inspect}"
		raise $!
	end
end

begin
	test
rescue
	puts "hi!"
end
```

Its output:

<pre>
$ ruby test.rb 
#<ZeroDivisionError: divided by 0>
hi!
</pre>

Sorry for the basic example! I think that illustrates very well how to handle an exception from two points, and one can train with these small examples when trying to do more complex things :)

In my opinion, handling exceptions on every method is fine, but be sure to reraise it, and handle it also on run_host. In this way you can return and jump to the next host if an important method fails. 

Other option (if you don't want to reraise) is return nil in case of exception, and keep checking the returned value in the "run_host" function. For example, the famous API send_request_cgi in the Exploit::Remote::HttpClient mixin will return nil in case of exception:

```ruby
	def send_request_cgi(opts={}, timeout = 20)
		begin
			c = connect(opts)
			r = c.request_cgi(opts)
			c.send_recv(r, opts[:timeout] ? opts[:timeout] : timeout)
		rescue ::Errno::EPIPE, ::Timeout::Error
			nil
		end
	end
```

So modules keep checking the returned value is nil, for example:

```ruby
		print_status("#{peer} - Sending SQL injection...")
		res = send_request_cgi({
			'uri'       => target_uri.path,
			'method'    => 'POST',
			'vars_post' => {
				'commonJson' => 'protList',
				'q' => "#{rnd_txt}' union select 0x#{hex_payload},0 into outfile '../../html/d4d/#{php_fname}'#"
			}
		})

		if res and res.body !~ /No Results Found/
			print_error("#{peer} - I don't think the SQL Injection attempt worked")
			return
		elsif not res
			print_error("#{peer} - No response from the server")
			return
		end

```

Really both options will work, and there isn't one declared as "more generally accepted with MSF modules". Both options would be valid if are well done :) Hope it helps :)
Should use simply ```sysinfo``` which caches the result so you don't make unnecessary requests.
well if they already set the manually this code will not overwrite it.
yup n/m I was thinking it's the compute manger.
This is at the wrong level with respect to is opening element
Might want to explicitly declare `MyObjectInstance` in this example so it is clear where it came from.  Also it should probably be `myObjectInstance` so it doesn't look like a class name.
OK. Then I guess we don't need `fromArray` anymore, right?
fixes gang shop
The old code uses arguments and does a slice() on it, but it seems like the new code uses data which is initialized to arg[1].  Do we need to do something similar?
Can't this just be "self.js_changed or self.fastdev:" ?
Opie - animated rows is not supported on Android, is it?  I agree that appendRow is.
I don't mind having the declaration of `i` in the grouped `var`, but please keep the initialization `i=0`.  Not initializing in the `for` is awkward and, in my opinion, dangerous. (If the code gets moved, `i` is used somewhere else, etc.)
'since 3.0' is missing.
Also add defaults.
Can you follow the template used by the other examples?
Isn't that a huge amount of overhead every time `setvar` is called?

I'm not saying it's not a good idea, I'm just not sure what the best solution is here.
I don't think this is the default anymore
It is now necessary to specify an Http implementation for these tests to pass in the browser.

As mentioned in the PR comment:

> Context.init() now requires user to explicitly specify an Http implementation when run in a browser.
s/expendable/expandable
Missing `randRange()` here too. Getting $8.00 every time.
> Why on earth should you have to be destroying a variable? destroy certainly doesn't require it. Being able to set a reference or pointer to null after destroying what it points to makes sense, but why restrict it to only work with lvalues? Limiting it to ref is artificially restrictive, since the fact that you're destroying something doesn't have anything to do with whether it's an lvalue or not.

When we are destructing something by hands, it means that we have a reference to it which scope lasts longer than we need. And if we have no variable, we have no scope problems: just write `{ f(); }` instead of `destruct(f());`.

Possibly I'm loosing some useful cases, so I'm asking again for *practical use cases*.
Sorry. Of course it does (`a = l;`). But in this concrete case it doesn't. Is it a real problem or a nitpicking?
useThis
regexp? :)
would you mind adding here `(name == 'value' || name == 'checked')`?
hmm, I thought we were using the same version now. anyways, no problem really
I'd suggest that you switch both buttons to say "Call" or both to say "Ticket".  Use an uppercase letter for the first character of the chosen word.
Ok, sorry, thought, that repos are sorted by package name