labofsahil/github-event-dataset-2012 huggingface dataset:
Thats the first link provided below.
Ah... But now we're back to the square one argument: That is just the element type of the "RoR" that we are iterating over. They are just elements, but not part of our range interface. This "third level" range is just as irrelevant to us as the "second level" range is irrelevant to `array.save`.

We were tasked with transforming the RoR into a R. The fact that those elements are also themselves ranges is *not* our problem, and *shouldn't* be our problem. Maybe the user *wanted* to have a RoR whose elements are mutable `char[]`, which are *not* meant to be duplicated. What do we know?

If the user felt he had a RoRoR he wanted joined, then he should call `RoRoR.joiner().joiner()`.
I don't have to use this now. instead its mvn clean deploy
Docstring!  (Look above.)
See comment on `blog/core/category.php`
Ascraeus -> 3.1
This should be changed to autoload.php, and other requires should be removed throughout the app. Keep ones for you're personal includes directory.
I'd need to check on the rest of the app, but we try to steer clear of inline javascript in most cases. Is there any way this could be externalized in a seperate .js file, and then be triggered on document load similar to other parts of the javascript found here?
I would really be appreciative if these could be more descriptive. Lets pretend that I have no idea what an alert_app_name is :)
Posso inclusive comentar as linhas de código...
s/acme.registration.form.types/acme.registration.form.type/
okay cool - tell me then i'll merge - thanks :)
Do not try to convert anything. it it is a 16/32-bit codec, then tough luck. Just ignore those. All important 8-bit codecs are based on ASCII and the xmlns detection requires just that, so no need to detect/convert anything
log(LOG_ERROR, ...) something here. That would have probably caught the peices typo above.
If you need something to test this:
MirrorBrain produces nice meta4 documents you may import load into DownThemAll! and then re-export, e.g.:
http://download.documentfoundation.org/libreoffice/stable/3.5.4/mac/x86/LibO_3.5.4_MacOS_x86_langpack_de.dmg.meta4
Are you sure ``$name`` has the correct type as "*" is not a sub-type of "string"?
`s/evelove/evolve/`
The Javadoc does't seem to match the code. Am I missing something?
actually not sure this check is correct: if writeSkewCheck is enabled then the versioning is enforced, see EntryMetaFactory.construct::useVersioning. So the if can be dropped.
Numpy must be imported inline - not at the class level because some developers have not or will not install it.
@croby : Pushed fix.
Пароли мы храним через secman — посмотри, например, в snails или netstoremanager или Azoth Astrality как с ним работа сделана.
`RangeError`.
The convention is lower case for enum members.
render date range parameters a bit different. More individually.
If you do it this way, then every obs that is a member will have an OBR before it.  I think you only want one OBR for the grouper, then OBX for each member:

OBR (the first obs group)
OBX (1st member)
OBX (2nd member)
OBX (3rd member)
OBR (next obs group)
OBX

etc.

As the code is now, you will have:
OBR (first obs group)
OBX (1st member)
OBR (first obs group)
OBX (2nd member)
etc
etc
MIssed the finally - I'll take care of it during merge
As I said, it has no reason to be protected Its not like its by design, but rather leftover from what was there before, so I'd rather not leave it out
But why not leave it in the XSD? It should still work (as "POST" here), and it's more descriptive that way. Same applies to the other default removed below.
There is lost logic about `this.messageConverterSet = true;` in this class like in the `AmqpInboundChannelAdapter#setMessageConverter`.
Yes, although it's getting so long, I wonder if it belongs in the top class-level doc. There you could really explain the different combination of options, e.g.:

* no correlation-key with named reply destination
* correlation-key and named reply destination
* no correlation-key and temp destination
* correlation-key and temp destination

and possibly even the interaction with cachedConsumers values
Sorry, I don't know how do this.
I used this variable instead of full delegating to wrapped item to reduce the overhead of instanceof checks in isChecked() method that is called every time the list item is going to be rendered.
I don't see anything in the rightscale_tools that needs a cloud parameter there.
`CSP_REPORT_ONLY` is only for testing out CSP, it actually disables enforcement. Plus, we won't be using the reporting mode anyway.
Similar thing here:

```ruby
let(:time) { Time.parse("2012-08-07 11:11:11 AM +0700") }
before do
  Time.stub!(:now).and_return(time)
  @user = User.create(:email => "test@example.com", :user_name => "test_user")
  @user.google_secret = "test"
end

context 'code validation' do
  subject { @user.google_authentic?(472374) }

  it { should be_true }

  context 'within 5 seconds of drift' do
    before { Time.stub!(:now).and_return(time + 34.seconds) }
    it { should be_true }
  end

  context '6 seconds of drift' do
    before { Time.stub!(:now).and_return(time + 36.seconds) }
    it { should be_false }
  end
end
```
I tested coverColor and it never seems to be passed in to the pdf, however, other params like profileOs are. I added coverColor to the pom.xml in git@github.com:dwcramer/xinclude-example.git and it has no effect on the pdf made by PdfBuilder but works on the pdf made from PdfMojo. For comparison, I also added a test of os="linux" and profileOs="linux" v. profileOs="windows" and that works fine.
«Весь код по работе с отправленным файлом находится в модели» → «, в которой находится код, отвечающий за работу с файлом»
this should point to the origin/master
BTW, the doc sais this:

To indicate which fields must or must no be returned fields value can be used. For example the following fields value
```
{
    "name": true,
    "title": true
}
```

so you need to put: `{ _id: true, URL: true }`
yes that works for you :)
Could we please stick to the behavior previously mentioned in #403.

CreateModelMixin should call something like .get_success_headers(serializer.data)

By default that would return {'Location': {url}} if there's a key named url in serializer.data, but developers could also override that implementation.
This comment should be one line below.
We should probably make the type that's taken in be a `scala.collection.Map` and explicitly instantiate `immutable.Map` or `mutable.Map` where needed.
This is the only failure I'm seeing now.  This assertion is coming back as false.
Ok we can remove the classname and target the div as direct child:
https://github.com/telefonicaid/Gaia-UI-Building-Blocks/commit/056a532cd69a56537de78f5fb099cbb13819c5ff
Same comment as with the other lists

```<div>
      <input type="checkbox" role="presentation">
      <span></span>
    </div>
```
How important (given that it hasn't been done) is this TODO?
Instead of (or perhaps, in addition to) checking the ancestry, let's check for the `password` attr_reader, the `password=` writer, and the `authenticate` method. In short: let's check the behavior instead of whether we typed a specific line in our model.

This way we can refactor our model, perhaps removing the literal `has_secure_password` class method invocation, but still retain the behavior.
Should this be fixed also?
While I mostly agree with the reorganization of the code in this file (as far as moving methods to different place), the diff came out really, really weird.  I'd be a little concerned about the history being left this way; it might be worth doing a rebase to break the offending commit into two separate commits.  It basically looks like git got confused by you both deleting methods from and adding methods to the same file in the same commit.
PD license.
This is probably what it should look like, since "icon.png" is a default resource.
If you make it so that env vars can be used in the file name like "gerrit-$BUILD_NUMBER-error.txt" then the problem with preexisting error files in the workspace from previous builds can be avoided if the user wants to.
Myös sekvenssiin `cons`:aaminen tekee saman:
~~~clojure
(reduce (fn [l x] (cons x l)) '() a-seq)
~~~
hmm, indeed. It's true that SAB can know it will have jQuery 1.7+
This test case should, at a minimum be in `tests.layout_helpers` instead of here, good catch.  It appears from the changes later in the PR that this `setUp` and `tearDown` are only used in one test case.  If that's the case, moving these methods into the one place they're used is a good idea.
No spacing before both brackets.