labofsahil/github-event-dataset-2012 huggingface dataset:
I think this example should include `id<Protocol>` _and_ `NSObject<Protocol> *` (to show the two styles), which is what I meant by my original comment.

@galaxas0 This guide is not meant to be as exhaustive as you're suggesting. We only want to list items that are non-obvious, and extending `<NSObject>` is very common Cocoa convention.
As above, this could probably go into an Expressions section.
No, it wasn't, see https://github.com/hpcugent/easybuild-framework/tree/master/easybuild/easyconfigs/b
Good call. I changed the defaults to None and use the rc parameters if None. I decided to use the color cycling mechanism (is there a better way than calling `axes._get_lines.color_cycle.next()`?) .

There doesn't appear to be arrowsize or arrowstyle defaults.
Symfony2 has 4 spaces. Symfony1 had 2. Regards.
Just an indication that it's a container for a template. I've removed it in my follow-up commit.
`elsif dump_header and verbose.nil?`
Well, that's true when the test passes but when it fails, the message is misleading...

org.junit.ComparisonFailure: expected:<[foo]> but was:<[bar]>

Also, it would be a better test if the context had 4 discrete serializers; this test won't catch an error such as...

````

	public void setKeySerializer(RedisSerializer<?> keySerializer) {
		this.valueSerializer = keySerializer;
	}

	public void setValueSerializer(RedisSerializer<?> valueSerializer) {
		this.keySerializer = valueSerializer;
	}
````

(Setters updating the wrong field).
Not sure but it feels like plural should be here 'after the retries are exhausted' right?
earlier code in attribute file is forcefully setting datasource_name depends on database provider even if end user wants to set his own datasource_name (which is already in his own applications web.xml). Hence we use set_unless in attributes file.
"app_tomcat/datasource_name" permits user to set datasource_name by choice, so to avoid the repeated code, we can safely remove the set_unless datasource name from attributes and change :required => "optional" to 'required' for datasource_name in metadata. 
 ':default => "jdbc/ConnDB"' still required to give example to user.
I prefer wraping it like:

```
$('#selectmetric').append(
    $('<option>', {'value': metric.id}).text($.datastream.metricName(metric))
);
```
The point of the exercises, as one might guess from the content of the chapter was to practice tail-recursion. No points from this one, but you are free to fix this.
updateAsset camel case is more clear
Hidden fields are in .not() method, so I would like to exclude there fields of the filter, as submit, reset and button inputs.
I see, but then you could still change the bootstrap file by using your own phpunit.xml, no?

So, I would say let's rename autoload.php.dist to bootstrap.php and remove this file here.
@stof I appreciate that you pointed that out, but a hidden requirement isn't very informative. I didn't notice the discrepancy between master and 1.2 so I may not have payed as much attention to a comment like this. What about the next line? Is that okay to point out that it does depend on a minimum version of another bundle?
That would be fine. Although, I like this better: "When assigned an empty value(``), it is assumed that the system default temporary directory should be used. Empty by default."
I prefer @ogrisel 's  way myself. Binary feature and frequency feature are usually viewed as two quite different representations. It would be OK to keep it explicit.
[`@cc_on`](http://en.wikipedia.org/wiki/Conditional_comment#Conditional_comments_in_JScript) is the script equivalent of `<!--[if IE]>`.
Yes, this was commented out in theoriginal.
Could you add 2 spaces to the beginning of this string? I ask only because it's easier to keep track of things in the command line when it's indented nicely.
Values for edge can be 'top_up', 'bottom_up', 'left_up' or 'right_up', from what I've seen 'top_up' and 'bottom_up' may appear when 'orientation' is a 'portrait'. 'left_up' and 'right_up' are for 'landscape'.
In addition to the fileds in the resizeRequest there should be an additional field 'id' that used later as a cardResizeDone argument and this is a mandatory parameter as per doc. ('id' description: A correlation id assigned by the sender that indicates that they expect a response and allows them to correlate the response).
Should be `tiapp.xml`
This is important - not a nitpick! ;)  Thanks for spotting it, Blain!
wiht
Split this into two methods: <tt>prepareSenderStages</tt> and <tt>prepareReceiverStages</tt>. No need for a boolean switch, and no need for the automatic start: each method should do one thing. Just call <tt>runNextStage()</tt> directly in the caller.
I removed this action because I figured out two redirects when a user click on sign in. And after we use `request.env['omniauth.origin']`, it caused all integration tests failed because it gets:

    Capybara::InfiniteRedirectError: redirected more than 5 times, check for infinite redirects.

Because the way OmniAuth set value to `request.env['omniauth.origin']` is from `request.env['HTTP_REFERER']`, and our case `request.env['HTTP_REFERER']` is going to `/login` first before redirect to `/auth/github'`, that's why it gets redirection loop to previous url `/login`.
The idea is that the 3rd party user may not know that the controller is the web view with id 1. Additionally, this allows us to in future give extra functions to just the controller if we desire.
All of our files are named with the camelCase convention. Please change this.
I see so you are using this as an abstract class. Can you fix the formatting comments?
Where do you suggest putting this function ?
I'm wary of adding any more pagination controls like this that attempt to show the page number etc, as they aren't scalable and we really need to work on getting rid of the ones we have.

I suggest just offering next and previous links, patterned on those on the main diary view page - look at the end of `app/views/diary_entry/list.html.erb` to see what I mean.
Odstęp między memberami.
you are not following the Sf2 CS here (one extra space) and you are not following the Doctrine ones either (one missing space) :)