labofsahil/github-event-dataset-2012 huggingface dataset:
Do you mean draggable() vs resizable() (not sortable?)  

No, I have not tried that. Now that you mention it, is it because the ui.mouse thing will call the capture methods in another order depending on the order the widgets are initialized? I havnt considered that before...
`document.getElementById('battery-remaining').firstElementChild`
Please add a comment to note this function is called by external (BluetoothTransfer)
Same as above. Use a string.
better to use ECMAScript 5 syntax Object.keys(unSelectedContacts).forEach(function(key) { } )
del->delete
btn->button
> Long press on the landing (search) page => wallpaper picker
> Long press on icons => edit apps
> Long press anywhere else on the grid (grey-ish transparent area) => nothing

I worry users will fail to understand the distinction between Launch page and grid, try to invoke the menu on the later, and feel rising annoyance as their fingers press against the screen without response. "Must be broken". 

I _sort_ of get the spatial model being implied and can follow the rationale, but I really think users are going to be confused on this one.

That said, it's not the End of the World, so I won't cause a fuss over it.
why do we have a now a much longer latency?
I guess this will go once we have the proper code isnt?
use defer?
Seems like this file and the related /dialogs/ dependency can be removed?
We can simplify indentation:

if (!navigator.mozContacts) {
    return;
}
...
Could we just use `#keypad-delete > div` ?
Can we leave this block commented out?
and add semi colons as it's a list
Onde fica a definição desse `getScript`?
I added this because often times when some error occurred when processing a resource (which is logged on level info), it wasn't clear what deployment it was in, so this info has been quite useful to us. It seemed logical to me to log it at the same level as the message about the resource inside the deployment. I'll put it on fine :)
Add in an `__email__` tag.
right now it is usable after error since i `$.on` it now
а почему не new? это же ожидаемое назавание метода
```
return self.assertFailure(d, sa.exc.IntegrityError, sa.exc.ProgrammingError)
```
?

Otherwise, this looks good.
These dicts look like the could be generated or something.
No `unless-else`, please. They’re hard to read & prohibited by the official coffee style guide (https://github.com/polarmobile/coffeescript-style-guide).
ok, so why not calling the env varibale GITOSIS_CURRENT_USER instead. That's clearer, isn't it?!
m_nValue -> m_fValue?
Please revert all changes to findClasses, the idea of the try catch is that if anything goes wrong in there, you get a decent error message that enables debugging of issues. Otherwise we don't know what file caused the issue.
hmm this is another place where i was convinced a use case was behind this
This will likely fail if the node is inserted via `insertAfter` instead of `append`.
`-1` is really convenient here, since I can restore that state by simply decrementing the `multi_bulk_level`
Git bare repo didn't have repo's source code in the file system.

If we have a `GIT_WORK_TREE` variable, the work tree will be there. just like a unbare repo.

Linguist works will unbare repo(work tree).
modified for gesture detection
thanks you are right. In factory it is correct
default should be nil
I just noticed this `eval` here. Do we need to do that? nodejs can `require` json files just fine.

`var json_data = require(path.join(json_dir, l, 'messages.json'));`
tabbrowser is not necessary to declare in both cases. For SeaMonkey does it mean gBrowser is available in each of the windows?
I think we want a logger for sure. But I'll think about it and put it in later. It definitely needs to be something the user can hand us. Maybe we don't log UNLESS the user hands us one. Something like that.
Seems like that could pretty legitimately be a regular, boring function, rather than a proc.
Please add a doc.
Why did you remove the .sql extension check? This opens the way for all kinds of problems. Please see #18 and #19.
this part should move below the `if (this.async)` from what I can see, because `this.async` is already `= fn && fn.length`
There's no point in asserting the Behavior attribute.
The setter for this has a type hint on the $userMapper parameter of UserMapper - should be changed to UserMapperInterface
This is not required, it's set to this by default.
you already have it from the line 48
I commonly use the double-dispatch mechanism, but this seems good too. Do you have any reasons for preferring this way?
Tällästä kyselyä ei voi tehdä oikein näin. Haetaan lasku taulusta kaikki laskutetut tilaukset ilman mitään rajausta. Se resultti voi olla pari miljoona riviä ja siihen vielä joini. Tähän pitää tehä joku fixi.
When I started working on this PR you told me this would happen somewhen later.. I can include that anyway :)
Can't you create a switch for this?

```php
switch (true) {
    case ($global instanceof \Symfony\Component\Console\Helper\HelperSet):
        // ...
        break;

    case ($global instanceof \Symfony\Component\Console\Command\Command):
        // ...
        break;
}
```
This looks like a debugging line. Better to just use the logger for this kind of debugging.
you could also add 'html' and 'htm' to the list (which are supported by the ``HtmlReader``).
maybe you meant to define label and data here? -- they're implicitly declared down on line 219
Single #
Yes, I only want to have a copy of the array structure. (the robot removes items out of the array, does not modify them)
you can write this as
try:
    self.runstep('sanity check', [self.sanitycheck], skippable=False)
finally:
    self.runstep('cleanup', [self.cleanup])
Might read better as: This example demonstrates the deployment...
W391 is a blank line, that is, two consecutive \ns. meaning there is no conflict. Some editors like Vim add newline automatically. Please fix your PEP8 test to ignore W391 errors.
https://raw.github.com/tallowen/tallowen.github.com/master/blog/_posts/2012-04-26-Code-Quality-and-Why-You-Care.markdown
Hrmph, there's also a way to create your own opengraph objects https://developers.facebook.com/docs/opengraph/define-objects/#define which is probably what we ultimately want to do. As we won't be able to aggregate stuff easily if we don't have a custom object. Aggregation & custom objects both require an app. Which we might be getting from a contractor in the next couple of weeks. COMMUNITY! WE CAN USE YOUR HELP! (they hear me, right?)

Anyway, yeah, that looks fine. We can always re-push badges when we have a full blown app up...i think.
We should use Popcorn.dom.find() here. 

https://github.com/mozilla/popcorn-js/blob/master/popcorn.js#L1638
In person result: there is not unnecessary whitepsace here.
This is going to error - if you look at the code a little more closely, you can see that there's not always a user. You probably want it to be either the user login or the recipient name.
Do we really want to be adding the comments to the search? We probably should have talked about this in one of our meetings. I don't remember a story card about this.
The name is misleading. Just name the private method `_login()` and do something like:

```
self._login(is_staff=True | False)
```
A {{yield}} sort of construct could work. Basically include a function
on the context object named yield that returns the inner content and
handlebars should be able to exec.

Thorax on Phoenix master has this impl but that's a bit more complex
than might be necessary as the scope requirements here are lessened.

Sent from my mobile device

On Jul 13, 2012, at 6:07 PM, Ryan Eastridge
<reply@reply.github.com>
wrote:

>> @@ -162,6 +162,18 @@ The scopes are somewhat akin to CommonJS modules, generating a `module` instance
>> general input from plugins and the `exports` or `module.exports` variable allowing for the module to
>> expose functionality to the outside world.
>>
>> +The output of a module can be customized with two templates each of which will receive `scope` (the current module scope) and `name` (the current application name) as variables.
>
> I'll make the change. In terms of the later I couldn't find another way to do it. What would be really nice is putting the start and end into a single template, but I didn't see an easy way of doing it.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/walmartlabs/lumbar/pull/64/files#r1163045
Ah... No javadoc. Will add.
I think this line makes more sense if you keep the variable and number in the same order as above, and switch the direction of the inequality.
Как вариант можно заменить на
``` ruby
def can_turn?(x, y)
  turns[x][y].empty?
end
I don't like the name of the function though ;)
Thanks for consolidating this! :thumbsup:
Very good point - this requires some more thinking. I think it would indeed make sense to allow apertures and PSFs to be optionally defined in world coordinates.
This might bite us, it probably shouldn't really be something you check downstream as it's already set in the manifest. At best here we're just going to cause someone irritation, would probably be better to leave it to the manifest creator to enforce a rule like that.
+1 on @andrerom 's comment
![haha](http://ibankcoin.com/chessnwine/files/2011/06/finish-him.gif)
Looks like this should be

`username == (ENV['ADMIN_USERNAME'] || ENV['ADMIN_USER']) `

and `if (ENV['ADMIN_USERNAME'] || ENV['ADMIN_USER'])`

- no?
Will always be empty, but good idea for consistency.
I'd have to look again, but there were a lot of places that accessed it by path, though maybe those don't apply after your changes. Still, the clearer we can be about what these path strings mean, the better.
Can you elaborate on this yaw calculation?
I went ahead and just changed it back to the previous behavior of swallowing the exception.  I don't really like it--but to do anything more intelligent I would have to branch on whether the exception was a PSQL exception or an HSQL exception.
Let's use 'application' here, since 'app' has additional connotations to non-developers.
there are two spaces before 'Rails way'
Here too: s/got_to_page/go_to_page
Use 2-space indentation throughout this file.
Just checking for a 200 status code is not a very strong test. It should at least validate the response as well
My initial thought was a function without a callback that just wraps `JSON.parse`:

```javascript
function parseResponse(body, req, res) {
  try {
    return JSON.parse(body);
  } catch (err) {
    console.log('An error happened parsing a response and we collected more information for you: ');
    dumpRequestHeadersResponseHeadersAndBody(body, req, res);
    throw err;
  }
}
```

Not sure if you can get the request information with headers from this library though, so that might put a damper. Although, the JSON that you passed in to the request would be helpful if you just passed that in:

```javascript
{
  'url': 'http://' + context.baseUrl + '/api/group/create',
  'method': 'POST',
  'form': postData
}
```
This is due to the fact that the version numbers of the maven project and the generated bundle doesn't match (the error message is not clear at all). I'm moving this option to the projects that really need it (feature and update-site).
Once you get rid of the hardcoded variables, you can remove this line entirely, and loop through your list/array. BTW, if you ever find yourself creating variables and naming them "var1", "var2", "var3" etc, you're pretty much always doing it wrong, you should be using an array instead, even if the array has a hard coded fixed length, that's better than naming your variables like that, because if that length ever increases, you have to go back through and change all the usages.
indentation problems here, please make sure it stays to 3 spaces everywhere. I see 2 spaces and no spaces around here.
I would ignore the `tags` file. 

I think it's `--ignore-dir=tags` but I'm not positive.
Someone put windows path in my .classpath. D'oh.
this stuff is all good, thanks
I can (should) probably remove this function; I had planned to reuse it between Get and GetAll but the type of `getResponses()` differs between them.
We should use code or countryCode for the code and name instead of desc
There is no need for the quotes around the keys - let's drop those
That would be an alternative approach, certainly. I opted for simplicity, and copying only what we know we need to copy. I generally tend to avoid doing "generic" object copies, because you end up having to either make assumptions about the contents of the objects (making it not fully general) or deal with things like circular references.
Use `microtime(TRUE)` (on each such instance).
Видимо ничем. 
Я подзабыл C, и потому решил что для выделения памяти просто огалисть "type arrayname[size]" недостаточно, обязательно нужно вызвать какой-нибудь new/alloc. Спасибо что указали на это.
И вот ещё - зачем нам хранить количество символов в последовательности в отдельной переменной?
Есть вероятность, что замена будет бесполезной. То есть A заменится на A. Надо заменять на любой другой элемент.
Да, выставил. Заходишь на страницу описания проекта, справа жмешь на Submission Details. Сверху справа Show Rubric
Спасибо, не дошёл до такого метода, это заметно всё упрощает, да.
You shouldn't change `engines`. I'm sure we'll want to support v0.6.x for a little while longer.
Any reason why this rm is commented out?
Is this file being renamed? I don't see it as part of this pull request.
please use official template
Ah, quite right. I misinterpreted that search.

I'll revert this change.
Actually, my view is that one doesn't have to have be very _strict_ about it, namely the common sense always suggests the "correct" answer depending on the context: for example, if it is a complicated enough `for()` like this:

```
/* standard macro for walking the list while skipping its head */
#define list_for_each(p) \
    for (p = &pcaps_head; (p = p->next) != &pcaps_head ; )
```

then spaces are in order. But if it is a trivial one like `for (x=0; x<width; x++)` then, imho, there is no need for spaces.
my bad you're right. I read too quickly I tought you were using SUBJECTS_DIR rather than setting it. sorry
why don't you just reject the entire relationship type instead of a property because it's not always aIsToB that is a duplicate
Please use hashrocket syntax for hashes.
I wanted to make sure the symbol was good and bound. ;-)
Why not having them both? Give first a simple example and make it more complex and the second one.
I think it is better to place it in a note.
传给
发送给
same as above replacing `are` with `and`
Can such a scenario exist such that both connection and reconnectionFuture is Some(...) ? If not, you might want to encode it as Option[Either[Connection, Cancellable]]
note hear that some interfaces will always run independent of the state of this flag
Не самое удачное название для переменной. `s/exists/existing/`, ну и то, что это вектор, не так важно же.
Umm, don't you mean = unwrap?
What do you think about integrate_prepare_display_context so that is consistent with the name of the function?
Hmmm...looking at this whole chunk of code, including the `if (imageScaling === CPScaleNone)`, it's pretty messy. And I can't even see where CPScaleToFit is handled. I think the whole section needs cleaning up.
gc-api being deprecated: 'nova bless'
ya thatll prolly fail too, ill update
You can get away with using if here instead of elif I bet
cool this sounds familiar from what paul saw as well. Nice!
Might as well complete the todo
Please use logging framework.
Style: explicitly compare against `nil`
`.get()` without a second argument returns `None` if the keyword is not found. We need to distinguish between a keyword not being supplied (`kwargs.get('transform', False)` returns `False`) and being explicitly set to `None` (returns `None`).
This should be fixed as well.
Might "format" be a better name?
```os.path.join``` is the preferred way to do this, but then, I'm not sure that a Windows build can ever get to here...
It's still ideal to do this, and I've removed the unnecessary scanning for available networks, and have found the connect/disconnect to be reliable and quick for me. I'd prefer to leave this in for now, and adjust it if we see issues with it.
Думаю стоит переименовать в IListable см #96
А здесь-то чего :-) ?
reqeusts -> requests
Why `emergency` and not the [usual keywords](http://en.wikipedia.org/wiki/Syslog#Severity_levels)?
Hmm.  I assumed that we were already keying off of id's rather than the actual term spelling.  Foolish assumption. 

Seems like IDs would be a more stable way to go .... do you think?  

i have no strong opinion --- which approach would be best able to weather editorial tweaks?   (that is, non-substantive changes)
It's probably easier to just pass in the data object and loop over `results` in the template.
Should the selector be modified so we can avoid .find?
@dooremont Instead of adding `French`, can you change it to something like `préférences du compte` ?
Please do this for the name/description and the other config.json files.

There should also be a space after the `:`:
All of these new constructors are only added to support unit testing, right? I don't think Nakamura has an agreed policy for handling dependency injection in tests, but FWIW I find them a bit misleading.
Qual o objetivo do uso excessivo do método `pop` do objeto dict?
That sounds important to point out :) Can you please add a comment in the config? Maybe just take the Wordpress one quoted in the link?
-1

There is a protected field on purpose.  I don't see any reason why a method call is needed to get a logger instance.  Its added overhead w/o any benefit.
I don't understand why we're continuing in the face of failure in this code: if any func() call fails, the checkpoint fails, right? Why keep pushing forward?

It's also a little odd -- we quit if we can't get a particular key, but keep going if we can't get a particular btree, or the underlying func() call fails?

Ditto __wt_conn_btree_apply().
In case there is some other puuppa library with Services_ namespace, could this be made more specific? Services_Zencoder_ ?
That will make the function impossible to be used outside the MCP as you can't include `mcp.php` in _(like this case)_ `viewtopic.php`. `phpBB/includes/functions_content.php` is probably a better place to stick the function.
Are you sure that the method "rewind()" exists?
ScriptOrder is so you can select between all the different orderings, I left /searchallinsteadoftraverse in there for backwards compatibility. ScriptOrder only accepts a fixed set of strings: traverse, recurse or specified, so that if somebody adds another ordering later they can just add a possible string to this option. (maybe it should be an enum?).

I could change /specifiedorderfile to automatically select the specified order option if it is set?
suggest does not expect a version constraint but a string displayed to the user. so you could make it better by using ``"riak/riak-client": "to use the Riak storage"``. This will output ``"doctrine/key-value-store" suggest installing "riak/riak-client" (to use the Riak storage)``
On a future refactor, please use `radio_button` instead of `radio_button_tag`.
Could you please remove this line?
and we should probably send the $this->ErrorInfo back as the exception message.  Nearly there :)
Will this line be uncommented at some point? Or could it just be removed?
linspace, s/if/is/
Yup, we can do that. I'll add that.
это поле вообще не нужно. имя всегда можно вытащить из юзера.
Oops, the title somehow slipped my attention. I see now.
Don't construct URL manually like this. Read (documentation or our code) how absolute (full) URLs are made.
No need for temporary variable here?
As you are not really interested in resulted object, you could simply do an upsert here? Check how this is done in horoscope. So it is the same trick, you tell for what you query and what are values you insert or update, and database inserts new or updates existing one.
Django has some utils for json, use its wrapper (it knows how to serialize datastamps for example).
Rewrap/indent better (see how we do it elsewhere. Check XHTML compliance.

Don't have newlines in blocktrans.
Why `default` parameter to `mongoengine.MapField` above is not good enough for this purpose?
I mean that already `fetch_data` should assure that returned values are proper unicode. Not that caller have to do this.
Please add TODO that it would be better that we would handle signal just before result is send to the client, not when object is created. And that we should try to use the same serialization as Tastypie does.
#main is used all over the site so I will avoid to change its css if possible (unless you check that it looks good on the other pages.)
i will need to make mod for music playing later on(tought not sore if I am that intrested but we will see).
String in strings.xml
Jose,
  When using php-lib, you *must* validate all namespaces against those listed in ns.php;  The current namespace for NCBI gene is : geneid.
bad7c81
I'm not sure this is the best way to solve the problem related to filtering agencies. Creating two filters means according to your refactoring, duplicate all the different `queries`.
The text is now configurable.
I'd use onResolve and onReject here, that seems to be the terminology used elsewhere.
vocaulry => vocabulary
This inclusion from latest bootstrap version
Space around the combinator, so: `.ev-rt-list > li`.
I like this boxed in look.
I looked at the Hawkins paper again, for there pairwise swapping of observations algorithm they have 16% going to the best and 34% going to the third best solution. Not as bad as I remember, but my impression was the set of converged solutions is larger with the RVD LTS algorithm.

some back of the envelope calculations
"So 18 random starting subsets will give a 95% chance of having one lead to the global optimum" quote for aircraft data. 7 convergence sets cover almost 90 % of the starting values, that's about an 18 % chance of converging to the best. To have a 99 % probability of converging to the best solution, we would need roughly 23 starting values.
So if there is a good chance of getting many reasonably good estimates in the first stage, then it might not include the best case for the second stage if n_keep is too small.  Also using additional c-steps in the first stage might not help a lot in this case, it just weeds out the awful cases but not the pretty-good-but-not-best cases.

side remark: besides the Hawkins and other traditional datasets, I would have liked to get a collection of models for generating data and test cases that have been used in different papers. I doubt the same settings will be very good for all test cases.
A class-level comment on this fella would be nice.
I'd build a string using UseClassNameAsTestName.class.getName(), for future-proofing against renames.  (Similarly down in CreateFinishedEvent, others?)
In this project, all opening-braces should be on a new line, like this:

```php
public function quit()
{
	// method body
}
Good, I just pushed a fixed version.
Fixed and pushed.

On Jul 4, 2012, at 11:55 AM, Mike Jarvis wrote:

>> @@ -215,9 +214,8 @@
>>     /**
>>      * @brief An interpolant that is product of same 1d `Interpolant` in x and y
>>      *
>> -     * Note that it only refers to the 1d function, does *not* own it, so the 1d must
>> -     * be kept in existence.  Typically will create a given `Interpolant` once and use
>> -     * for the whole program.
>> +     * Note that it only refers to the 1d function, does *not* own it, so the 1d must be kept in
>> +     * existence.  Typically will create a given `Interpolant` once and use for the whole program.
>>      */
> 
> This last comment is also obsolete.  The 1d Interpolant is now passed by shared_ptr, so the shared_ptr "owns" it.  No need to worry about keeping something in existence elsewhere.
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/GalSim-developers/GalSim/pull/213/files#r1100925


-------------------------------

Rachel Mandelbaum
http://www.astro.princeton.edu/~rmandelb
rmandelb@astro.princeton.edu
Good point. I had changed a later part of the paragraph and then automatically "fixed" the line lengths, but I didn't notice that I split up the equation.  Fixed now.
This should be zendserver/zend.sh so it's compatible with a puppetmaster and with vagrant right?
Perhaps, will check that out.
`raise NotImplementedError` instead? Or is this never going to get implemented?
let's use this:  `'/atC0($|/.*)'`

three changes:
* nginx prepends the "~ "
* $ is not escaped because we are in groovy java string not groovy gstring (single quote)
* dot is not escaped (because it shouldn't be)

now path is a normal familiar regex
Odd non-ASCII CAPITAL_E_CARET here?
There is a special Select helper class with WebDriver:
http://selenium.googlecode.com/svn/trunk/docs/api/py/webdriver_support/selenium.webdriver.support.select.html

It will allow you to select and deselect within Select elements.
Why are we removing links?  Is it because the iframe stuff doesn't work yet?
Sounds awesome. Thanks. :)
Why leave these lines commented out here?
Just out of curiousity, why did you change from ``Voucher.objects.create`` to this way of creating a voucher?
The current version of context manager intercepts RPC messages in order to keep track of both the request and the response. So if RPC is not recreated (perhaps if you switch from connected to virgin mode) then line 50 seems like the good old way we used to inject context manager. Note that the context manager reads the configuration and enables or disables itself in its codebase so there is no need to do any checks there.
True, in most cases that is the expected behaviour.
Spacing before and after brackets fixed.
(except for actually equal to 0)
what do you mean by not use tables?
Please add the namespace "t:Sensitivity"
I'd like to stick to response or exception... lists can return empty arrays, but single value functions should either work or throw an exception.
On 10.8, X11 is no longer shipped with OS X. That's why I am asking.
I would prefer not to delete, all the lib has IFDEFs which I use to debug the thing. Just delete the offending value.
I still don't see the point. All those examples, image, widget for config, etc, don't require a new class for each board and can be dynamically found and used. I don't see any benefit on this, I only see one more think to remember and handle for each new board.
В случае цикла не создаётся лишнего листа.
Non-blocking comment out of curiosity: I wonder if it's worth DRYing this up.
but we can call the two setters to do the updating.
`return target.type == DevTools.TargetType.TAB` would be a lot shorter, but it'll change anyways when Joe's target stuff lands, so no big deal.
s/PayPall/PayPal
+1 too. Otherwise CC-Attribution would be better than BSD as BSD is for software rather than data. The By clause of the CC-Attribution could be to include a link to the original website in the documentation (which is already the case in this PR).
Although this is not a line that you changed in your PR, using sklearn.utils.validation.assert_all_infinite would be better here, as it is faster on big arrays.
huh. interesting. was not aware of that. What is the shape of ``classes_``, then? Number of estimators?
I think lcfirst() should be used instead of strtolower()
In order to make the doc reflect the actual implementation, let's list the other platforms for properties/methods that we don't yet support in BB but are supported on all the other platforms.  Then when we implement them in the future, if they are supported on all platforms we can simply remove the platforms line.
Certains paramètres de la route
Yes, you are right...
I wouldn't use normalTrans as the name of the variable that contains the dataset Transform.  I would either rename the variable to newTransform, or I would most likely say
IHqlExpression * normalTransform = expr->queryChild(2);
LinkedHqlExpr newTransform = normalTransform;

Otherwise when you read the code the variable names confuse you as to what is going on.
ugg "from the about link" should be "from the above link"
please use the short class name as you added a use statement
Break this up on multiple lines instead. You can have newline characters between `<` and `>`. 

Also, do we really need the `[]` on the name? That's some leftover hangover from php which we don't need I think.
You mean the entire test or just the mock.patch bit?
What's the `|string` for?
copy & paste lazyness from previous code. :)
lan0      1500 192.168.1.0     192.168.1.2     26615854           0     49746143           0     0   
lan6*     1500 none            none            0                  0     0                  0     0   
lan5*     1500 none            none            0                  0     0                  0     0   
this is the sample for netstat -in
you can see the lan has '*' mark, if the lan card is standby in cluster configuration.
Got it..


What about ?

```php
<?php
$first  = reset($array);
//OR
list(, $first) = each($array);
```
Shouldn't be `this.initialized = true;`? Awesome pull, great work!
Seems like we should do some validation here to ensure that keyType is primary or secondary, throwing a good error message if not
Sorry I was a bit confused, for some reason I thought Django's paginator had a default value for `per_page`, but it doesn't – you were right. However I stumbled across the real reason I left `per_page=None`: it allows `Meta.per_page` to be used as a fall back.
Please don't uncomment recipes in the main recipe
switch to pixels instead of ems
Nit, but can you make key_name call this to avoid the duplicated code?
is this a bug, you are not appending multiple values for query strings, also, the string builder is never used here. I think a line was deleted
I think it's probably safe to remove this :)
This should get split up into smaller test cases.
print_info doesn't exist. You probably meant ```print_status```
I fixed the description - probably after you started looking at the file though.
wouldn't it be shorter to do ``out = np.dstack([L, a, b])``?
Not sure if any of the two is more efficient than the other one, though.
Sorry, I don't follow what you mean by "subsequent load operations". The change to `preferred_plugins` should just affect the default `imread` plugin, as far as I can tell. But I could just be overlooking something ...
I think it's better to break the `verts` into `y` and `x` - see my most recent commit.
I don't think the compiler actually enforces this correctly ... I'd rather just leave it as it was before, I think due to that.  Also, leaving it as it was demonstrates that the singleton is more specific than a bare object type which is useful.  (And that means removing the mention of ``limited`` in the html file...)
lang="fa-IR"
I see that too, and I don't like it, but I consider it personal-enough style that I don't comment against it.  The pragmatic reason I don't like it is because it is easy for the casual reader to miss one of the assignments and for the novice reader to not know what the line does.

The nostalgic reason I don't like it is back in my youth (my real youth) I was programming in Turbo Pascal, and I had a line like this, and the debugger stepped over it in one step forward.  Had it been two steps, I would have found a nasty bug much sooner.
This pull request includes breaking changes to the `camera` because of the frustum changes, right?  We should mention them.
Is it really okay for `mat2` `mat3` or `mat4` to be used as a non-array type?  Even if it's technically okay, should be issue a warning or error because it's not something someone would really want to do and probably indicates a mistake?  Just a thought.  @pjcozzi ?
If `createUniforms` and `createSubMaterials` do what I think they do with `count`, it will be cleaner to change them so we call them like
```
count += createUniforms(result);
count += createSubMaterials(result);
```
This makes the functions more cohesive and the effect on `count` obvious. 

Unless, of course, these functions rely on `count` for renames.  By the way, since we are only using a single `count`, do we rename properly if a function in one sub-material is the same name as a uniform in another?
Can this be generalized - generic type for formatter that deserializes based on type parameter?
The platforms field shows that it's an iOS only property.
Leading word needs capitalization; appears several times throughout document.
Should we add a declare() example, maybe commented out?
move var i = 0 into var series = []; In other words:

var series = [],
i = 0;
for(; i < driverIds.length; i++)
Well we were setting this twice. When this function returns, the parent function will call firePropertyChanged, which should do the trick.
I think I'd probably lean towards putting the link at the beginning of the string rather than the end, because some of the descriptions may be long and require scrolling.  Other than that this commit looks like what I was expecting.  Thanks for the submission!
Выравнивание имен переменных
```
 * @param {Number|Date} end                                Конец события
 * @param {Object}      participants                       Список участников и их контакты
```
This code comes from a larger code base. If someone adopted this code into their own project these functions are likely to be useful.
Also:
` Multiple calls to getLogger() with the same name will always return a reference to the same Logger object.` 
http://docs.python.org/2/library/logging.html
having the functions around during initial migration from toolkit to toolchain will give clean useful errors. leave it in, to be cleaned up in 1.0 release.

what this actually means is that we need a proper way to deal with legacy code
Ok, I see now, agreed.
move it to application_controller and remove from all controllers but make sure it won't affect the dummy app
remove line or cleanup comment (is oalready subclass of Toolchain)
Oh shi-- точно!

=(((

Очень жаль.
replace these with camelCase symbols?
Err... Wait.
Well, we <i>can</i> return a `const(T)[]`, but given the overload is meant to be used by const methods, trying to modify the slice itself is probably a mistake. I think it is better if it is fully const.
The plan is to release 3.1.3 around the time of 3.2 RC1, so within the next couple of weeks.

I'll make sure to backport this one to the 3.1 branch once Rossen reviewed it for the 3.2 branch.
I don't think this should be a separate section.
I think I know what it is give me a minute
I hope you guys solve this quickly, as I'm receiving a notification for
each comment now since weeks .. ;)


On 27 November 2012 17:07, Gunnar Morling <notifications@github.com> wrote:

> In
> engine/src/main/java/org/hibernate/validator/internal/metadata/aggregated/ParametersMetaData.java:
>
> > +* distributed under the License is distributed on an "AS IS" BASIS,
> > +* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > +* See the License for the specific language governing permissions and
> > +* limitations under the License.
> > +*/
> > +package org.hibernate.validator.internal.metadata.aggregated;
> > +
> > +import static org.hibernate.validator.internal.util.CollectionHelper.newHashSet;
> > +
> > +/**
> > + * Represents the constraint related meta data of the arguments of a method or
> > + * constructor.
> > + *
> > + * @author Gunnar Morling
> > + */
> > +public class ParametersMetaData implements Validatable {
>
> Yes, the names are better now. I find it very important to have good names
> for the elemens of a program, bad names can it make so hard to understand a
> code base. So thanks for your feedback :) I feel we're on a good way with
> the model. I'll push the changes later today.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/hibernate/hibernate-validator/pull/146/files#r2238170>.
>
>
Just make this `List<String>`.
Lift this out of the `try`.
I will check if I'm able to catch this exception somewhere in the scanning process
looks like the a starting point, but requires some work (fix packaging, maven-central, ...)
doesn't this make it hard for someone on 10.7 to use the legacy QT7 player/grabber if they have 10.6 SDK installed?
Isso roda?
Crap, I thought I had deleted that.
Good point :) I'll change to gquery-plugins
maybe delete this file since it doesn't contain any functions anymore ..
Death to you!
bzip2 was already in 0.8
Should the migration copy the internal names over to the display names (or pass them through a reasonable mapping)?
Changed copy and added link to credits.
`pre32` shouldn't be here.
Няша-умняша, мимими!
this string is created for debug purposes only but might not be used if traces is false. Would be better if it is inlined or only created if trace=true.
:+1:

Increases readability.
We should use `.on('resize')` to ensure our bindings are of the same format
supported in code now.
Yep, because it's `__KERNEL_NCCS`, here is the linux [definition](http://sourceware.org/git/?p=glibc.git;a=blob_plain;f=sysdeps/unix/sysv/linux/bits/termios.h;hb=HEAD). They actually copy the data before calling ioctl, see [here](http://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/tcgetattr.c;h=d05b5f3a0693110ce2893d9dc718520cc76ef787;hb=HEAD#l26).
Use null, or use a CONSTANT_VAR. No magic numbers.
Maybe here, we don't want to always replace the whole line, but replace it only if the hash has changed ?
Task isn't even used, so it can be removed.
Is this an FQN?
Want to add it to this list instead? These are CoffeeScript statements. They can't be used in expression position, and they don't trigger auto-return behaviour in functions.
Will need more slashes.
As with draftStatus, we also check the command line to see if security was passed in (see line 368 in PDFMojo.java):

	String sysSecurity=System.getProperty("security");
    getLog().info("adjustTransformer():sysSecurity="+sysSecurity);
    if(null!=sysSecurity && !sysSecurity.isEmpty()){
    	security=sysSecurity;
    }
@apex13 Can't we write something like this (didn't test it):

```ruby
@langs_used = used_languages.collect {|lang| lang.language_id}
```

It's also better use use complete names for global variabels: `@languages_used`
Guessing this is unused - can be deleted?
I'm not gonna block on this, but you should combine these selectors into one line:
$('.tooltip, a[rel="tooltip"]').tooltip()
hm, looks more like this is the place where we hit the problem because the model has changed. but i totally don't understand what part of the test causes the schema to change. once we set up the database, i don't see where we would change the schema. or is there some bootstrapping that updates the schema each time?
The thing is, that if one does exclude("url",) field for this serializer, there would not be a location header.
But i think this would be a good think to do, because one does not need the URL two times returned in the response.

I see there are big performance differences. If you still consider it to be better the serializer.data way. - ok
**Error:** Variable "pull_request" is not in valid camel caps format
And reassign them before each call to `fit` / `transform`? That could work. It just seems as weird as the current multiple inheritance to me. But at least it is simple for grid searching by naive users and the repr() will still be useful in a IPython shell.
Ok, that's what I suspected.  I'll try to remember to make this change wherever else I see it.  Thanks for the wisdom.
why is a task stack builder required for a simple intent
That can't happen, since the cache is (today) only used when the transaction is active and the cache is destroyed when the transaction is deactivated.

That means that, all files referenced by the actions of a transaction are the same pointers (thus locks) that in the cache, and all of them will be released (to none) by the ```retry()```.

If two transactions have the same file on cache, when both retry, they'll both release the read lock and whoever gets it first next is the winner.

Killing the cache doesn't clear the locks, since the actions still have them linked, so it doesn't even alleviate the deadlock problem. It was just legacy from long ago...
What about the generic version of dictionary `IDictionary<K,V>`? It is not implementing `IDictionary` interface
@domcleal 

According to the puppetlabs spec helper [README](https://github.com/puppetlabs/puppetlabs_spec_helper/blob/0.2.0/README.markdown) you want to make the change like this:

    require 'puppetlabs_spec_helper/puppet_spec_helper'

Which is exactly what you have.  =)
@senhorzinho i created the daisy (tdfp) and caterpilars(tcpp) reinforcement images and put them into the dropbox. we can re-use the daisy for the tdfm
Tys nikdy nic nezapomel :D
Hardcoded version and required attributes removed
See https://raw.github.com/cedriclombardot/cedriclombardot.github.com/master/documentation/form.markdown
Why do we have to calculate where the handle is now?
This is used to expose the API as a whitelistable api like all the others.
Can we make the function name more descriptive?  Something like prepareOutputFiles gives me a better idea of what the function is doing.
$('#waitingWheel').toggle(value !== 'complete')