labofsahil/github-event-dataset-2012 huggingface dataset:
Umm, I think there is no much difference between `lazy val` and `val` in its case.
Which is probably better...?
just tested with android - the default layout for android is Absolute layout, that is why i kept it
Je sais pas pourquoi mais cette ligne avait disparu, mais elle permet règle le problème :)
And another comment, we want a change.
Not if it returns false... otherwise no point in checking return type if success/or exception.
also below
In normal cases, a terminator is a non-printing char, so escaping it is weird, not sure if even possible.

But we allow the user to setup the terminator, so we should consider the option.
I think it's clearer as it is (not a lot in it either way though)
Bah - I had made the change but missed checking it in.
Worth asserting that the callback locks are zero ?
args and kwargs removed

refactor of models.py classes left to reLink branch
I'll get onto that a bit later.
Why not use ``datetime.isoformat()`` here instead?
тобто завантажувати фікстури не на початку сценарію, а при активації плагіну? який резон?
To clarify, master-dev recently became dev-master. You are not going crazy, it simply was changed.
IMO, the `th` tag is missing.
No need to format since the replacement value is constant. Just use the constant string `'luac is required'`. Fix that and I'll merge it.
use only testng annotations. merge my code down and you will get ti for free.
Or even better, combined with the other css =)
You can pass `alive?` straight to `filter`: `(filter alive? authors)`
your're right -  it's better to add the scope to specific actions in controller if needed.

BTW i was thinking of using `position` in categories to order guides, because it can be edited in refinery admin. but as you implied, if we have to maintain different orders in different places, we should use specific yaml file.
yes indeed, it works also in 2.2 (I copied this line from the imaginebundle)
can you please doc comment the return value?
Need to verify that name match `/[a-z_]+/`
oops, this part shouldn't be here
It's not a tiers issue, but it is a SAAS issue.
The change here is to enforce something that was already intended; flatpages were already only included in the menu if custom theming was allowed, but you could still access the editing page (and make use of it) if you knew the url.
According to symfony 1.x CS, the opening bracket should be on its own line
I would prefer a boolean here.

if ! bind_address
Lies.  The payload handler will have already been started by the framework
This should be enforced in report_service, not in modules. Otherwise, everyone will get it wrong.
ah, sounds good, i didn't like the for loops myself.
I can't think of a single reference that would be good. I could put references to some books there?
##### `numpy` casting change

fixed by replacing the above 2 lines with:
```python
result = dtype(np.maximum(image, 0))
```
I'm guessing this introduces a copy.  There may be a better way.
@meloniq : They're _doing_it_wrong() :) If you look at the source code of _deprecated_function(), you'll see that the error message doesn't include any information about the plugin triggering it. That function is to be used by WordPress core only. Plugins should have their own functions, like what @pippinsplugins linked to.
I agree. Either that or just make the connection somehow and save the connection instance to self so it can be tested later, in "test_make_sure_mysql_is_dead_during_resize". If its not easy enough to access the bit from RebootTestBase that creates the connection maybe we can extract it to a stand-alone function or class.
Similar change also needed for albums, btw
Despite the paper's terminology, in our rendering terminology, a vertex can be several attributes, e.g., position/normal/color.  Since we are only dealing with positions attributes, we should just call these `positions` throughout as we do elsewhere.
These are polylines now, not billboards, right?
Yes.  Good eye.
アイコンのファイル名が標準的な名前じゃないときに使うんでしょうか？
ちなみに僕は`app.icons`はまったく指定していないです。AppStoreにも公開できてます。
_rowCount, and add a space after the colon
I actually agree that the old presentation was better, but I wasn't able to get the formatter to format it like that =(   I normally only format the specific code that I modified instead of the whole file
You care more about the fact that it isn't null that that it's a function. Hence, it'd probably be clearer and mentally simpler to write:

!= null
Can you turn this into a normal nested function:

bool success(List<Entry> entry) {
    ...
}
calling the file `bin/java` could get confusing with the Java executable. maybe something with `jdk` in the name?
Stub here as well?
Nao saquei o porque desse include. Me esclarece aew. =D
This should `notify => Service['httpd']` to ensure this mod is available before the service restarts
What about to create two instances with different attributes and check if they are different?
Мне кажется, что ты сам создал себе эту проблему, решив в `addTab` почему-то возвращать из свича классы.
"sellers make" or "seller makes"
agree with Zac here.
Ideally we should also make sure that the template constraint disallows statically tuples for which this doesn't apply. This is nontrivial so probably we could leave it for a future release.
OT: I'm surprised to see a lot of `: bool`-style checks on Phobos checking for implicit conversions. Shouldn't this be `== bool`?
Are there any subtle differences between two other then typeof() refusal to accept types as parameters?
I had closed #827 because it wasn't really even sure if or if not `skipWhite` was desired, or if it had too much duplicate behavior, or where we'd even put it. I closed it because I wasn't passionate on the issue, nor did anybody else. If there is a request for it, I can re-open no problem.

There is a "major" difference between `skipWS` and `skipWhite`:

`skipWS` is an internal parser function, and will only parse through legal source code whites (aka: ASCII white).

`skipWhite`, on the other hand, is a end user function, so will parse through all forms of white.

We'd have to discuss which of the two (or both) we'd want to expose publicly, and where, while making sure the intended purpose is correctly understood.
How is this different from the original code?
> ValidatableParamters, ValidatableReturnValue

+1; going to change that.

> Maybe that should just be ValidatableBean?

My thinking was the following: We have the elements of the aggregated model (`*MetaData`) and these model elements implement several facets such as `Validatable` or `Cascadable`. Sometimes a meta data element also doesn't implement such a facet directly itself but provides access to it (e.g. `ExecutableMetaData` provides access to `ValidatableParameters`). A model element might also implement several facets (e.g. `BeanMetaData` migh also implement a `Describable` facet which provides access to the element descriptor), therefore I thought the model element and facet names should be orthogonal.

The general idea is to pave the way for a unified validation routine which just operates on the facet types and doesn't care whether the underlying element is a bean, the arguments of a method call etc. For cascaded validation this already works, as `ValidatorImpl` doesn't work with `Member`s anymore (which wouldn't work for parameters) but with abstract `Cascadable`s. I think we can achieve the same for validation of actual constraints by providing the required methods on `Validatable`.
Please ensure that we use the native events if possible.
whitespac is wrong
you know, some comments aren't too bad :-)
Maybe it would be nice to make a check if the given class is really a model class (if OpenEngSBModel is assignable) and print a warning otherwise? WDYT?
Yes, I agree, I think it could be used for lots of things outside of rectangle land.
This stuff is only useful for form-based apps. I wouldn't include it in the generic startapp.
Translated messages shouldn't contain HTML if at all possible, the `<p>` tags should be concatenated outside of `_t()`.
How do we get in this situation and how does the developer fix the issue?
Same comment as on the blog, maybe have newPost just do the conversion from params to Post.
its not a bug !
but anyway ...
@stof Ok, replaced the alias and used the new alias in my templates
Because it looks prettier for when we get to 0.3.10.

I've just bumped it to 0.3.02 btw
Comment says it's a private method, but it's actually not in the code.
stof told me it's not necessary as composer could handle it itself
You mean a command option to choose wether or not we want to flush the dm?
This test fails. The Digest header above looks valid...
Can you clean up this one as well? `icc` should go on a separate line, and the `(` should start one column more to the right than the `[`.
Ok, moved them. But shouldn't the Version tests also be there?
Apologies, not sure how I messed that up!
Moved this out into an API funciton.
It's not a barrier it's a latch! :-)
TxDependencyLatch perhaps?
Add option to accept result limits from the URL
Should we reject a converter when they supply a template? Converter is only used if we construct the template from a mongo factory. ??

Will fix if you agree
It is scary to see that the change is (on paper) to replace everything. Can you explain what happened here?
Yes, please use `resource`, it's the proper way.

If necessary, use `:only` or `:except` to restrict the actions: http://guides.rubyonrails.org/routing.html#restricting-the-routes-created
Honestly, because I hadn't paid attention to the fact that it did that. I'll work on another commit that uses that one instead.
一行に普通に収まるのであれば、 expect(1) { mp.id } というスタイルの方が簡潔では。
LzoBase does this.
1) Since we've already released 1.0, maybe maintaining BC would be better here? Not sure, never had to worry about BC before.
2) Would it make more sense just to pass in the view here? What other reasons for needing the request are there?
If this is going to be changed anyway, you could consider using Point or tuple instead of x and y, since those would be more common than plain x and y and easier to use. By default usually Point is used, and tuples in case performance is an issue, which probably isn't the case here.
Latest commit does simple setters . Eclipse tried to trick me .
Should we say that an exception is raised in case the annotation is used without _@Valid_? Or is it jsut ignored in this case?
if you want insert right after the personal_id_field comment you can then do this:

```
i.insert(personal_id_index+1, 'yes')
```
done this, one of it, I changed it to 'handle_first_questiongroup_form '  since putting only questionnaire_id will return the first questiongroup anyway
This seems to be a bit over complicated.... you could just do :
for question, answer in form.cleaned_data.items(): and get rid of the function get_answers ?
@pivanov we should kept the `<meta name="target" content="html">` in BB repo (not for gaia merge) for still having the "switch background" behavior
Yes, this is the only place when :size is used currently. I will change it to 100.
The `|` here winds up isolated when viewing a single diary entry because nothing has been printed before it.
Could you please split this huge `if` into smaller readable conditions?
Should be message
That doesn't allow us to exclude the userAgent header.
Should include mobileweb
The Router::url('/') does not return an ending slash ? 

Without ; at the end of the line
`@puzzle.ratings.build(:user => current_user)` should be done in the controller. If you make a method on `Submission` that could be really easy:

```ruby
class Submission
  def rating
    @rating ||= Rating.where(:puzzle_id => puzzle_id, :user_id => user_id)
    @rating.first || @rating.new
  end
end
```

```ruby
class SubmissionsController
  def show
    @rating = @submission.rating if @submission.correct?
  end
end
```
I want it to fail when the expression has text
I would add a quick comment as to why we are doing this.
This check has been added.
(just a remark on style) .. i find this ambiguous and therefor prefer the original form:

```
>>> False is not None
True
>>> False is (not None)
False
```
Actually, gonna keep these.
Yeah, it's on the third commit, I forgot to change the object_name to:
```ruby
object_name = "/#{name}#{ext_name}"
```
Changing the constructor so you can inject a Sensor makes the code testable, and means Alarm is more likely to fulfil the Open-Closed Principle
Onnistuu myös helpommin näin:

~~~clojure
(if x
  true
  false)
~~~
Except that "values" don't have naming rules, whereas "functions" do. Values don't even have names. And actually, I don't think that it makes any sense at all to say that an eponymous template which results in a value is conceptually similar to a value. It _results_ in a value. But values just are. They don't take arguments. They don't have names.

The bit about "similar to functions" is there to indicate that because you use it like you'd use a function, you give it a name like you'd give a function, so it makes perfect sense to me to say that they're similar to functions.
This (and other) inline code tags are using Markdown, not ReST.  You can use [restview][] to preview the file.

[restview]: http://pypi.python.org/pypi/restview/1.2.2