labofsahil/github-event-dataset-2012 huggingface dataset:
Should read `sets the current playback volume`
This is not true for mobile web, should be marked as Android and iOS only, assuming it applies to both platforms.
Describes what this variable actually is.
Should be able to do "var output" here.
No comma before "in".
так нужно ;(
So adding e.g., LLVM will amount to more than just implementing the toolchains.compiler.llvm ? It will require people to add stuff all over the place? (well, that's a bit harsh, perhaps, but it does detract from the modularity, I think.)
The payload file name is passed in via the program args: http://dev.iron.io/worker/code/packaging/

Should read that arg to get the file name/location.
Did you want me to remove the travis task?
это точно должен быть id?
Этот показался самым адекватным, но я не очень усердно искал. Еще поищу.
Yeah is true :)
Well, as the original HTML for the forms is quite awful, the CSS cannot be good either. So, I guess my planned frontend improvements need to be finished. (Well, "started" is closer to the truth.) I would like to keep the TODO in there, because at the moment the CSS won't be the same quality as the others. Maybe I could explain it better in there? Something like "TODO: this file is not up to the best standards and will be fixed after an overhaul of the form code"
I think it should still be done the other way, this way it isn't even thread-safe.
> Good suggestion, but |$(LREF normalRNG)| would be better, as it'll create a link
> to the function.

Just to note, normalRNG is currently grouped with all the other functions in the 
documentation.  I can separate it out if that's preferable -- what about the 
Normal struct implementation, should that also be covered separately?
that would be great, thanks, can't find any documentation on this feature.
it'd be good to document what ID is for. Also "name" and "scopedVariables" could use doc comments
> Ok, but I mean if "Inc." is the current name I think that's the one we should use for new files.

Sure, we should try to use Inc. If for some reason I move classes and use some older ones as template for new ones I won't guarantee that we get another LLC.
I just checked and its in the phpBB 4.0.x coding guidelines. I don't have a strong feeling for ether so I'll convert them into lower case in a following commit.
Can we do some more experimenting to find if we CAN resolve the error? If we want to be able to use REPLACE functionality  going forward, then we should see if we can get it working now instead of dealing with it later. Did we look down the database collation angle at all?
You are  right. One is always learning something new. :-)
It was changed.
The owner of the PR will be the user passed to GitHubRepository, no?

```
self.repo = gh.get_user(user_name).get_repo(repo_name)
```

The head option will choose whose branch is used ``joshmoore:somebranch``.
Good call. I'll add that as well!



On Feb 28, 2012, at 15:23, Jeremie Miller
<reply@reply.github.com>
wrote:

>> @@ -202,6 +203,17 @@ locker.get('/core/:svcId/at', function(req, res) {
>>     res.end("true");
>> });
>>
>> +var collectionApis = serviceManager.getCollectionApis();
>> +for(var i in collectionApis) {
>> +  locker._oldGet = locker.get;
>> +  locker.get = function(path, callback) {
>> +    return locker._oldGet('/Me/' + i + path, callback);
>
> is there a way to plug in a try/catch here to make this safer?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/LockerProject/Locker/pull/878/files#r499188
I would use ``if (null === $this->params) {``
I removed the $user Parameter or should it be available in the method for custom logic?
No need to put a magic serial number that changes behavior into shared test code. You can mock cmd.cp.unbindBySerial to throw an exception when called extremely easily.
5.4 will have `<?= ?>` always enabled, regardless of the short_open_tag directive.
Fair enough, but I can't shake the failures. My rspec related gems:

rspec (2.8.0, 2.5.0)
rspec-core (2.8.0, 2.5.2)
rspec-expectations (2.8.0, 2.5.0)
rspec-mocks (2.8.0, 2.5.0)
rspec-puppet (0.1.2)

Aside from that, the unit tests look great so I'll likely merge this today. Thanks for working on it blkperl!
It's easy to grep and consistency is king for tooling, so please stick to `@@@BUG@@@ 1234` or change them all.
MINOR: If you happen to alter this file, I presume cann == call.
renamed js file, so toggle js is added as new
May be its just a personal preference but I am not a big fan of getters that perform some logic of determining what needs to be returned based on some condition. I'd change it for 'obtain*' which is essentially what you are doing. And we sort of being pretty consistent about it ever since i raised this as a concern a long while back, so wonder what you think. Basically IMHO getters should simply return a value of an instance variable; everything else is 'obtain' , 'build' etc. . .
`, pero funcional,`
I also recall you suggesting getting rid of this required redundancy, still thinking about how i want to do it also waiting on other feedback.
phpdoc is located in implemented interface ReceiptDataConnectorInterface. IDE uses phpdoc of implemented method.
If you wanted to use an array - and honestly, i don't understand why you would want to do that with a CollectionView - you would have to provide a custom render method to make this work. That means you would have to decide for yourself when to render the empty view (if at all). So a built-in behavior of rendering the empty view when there is no collection wouldn't affect your custom view implementation, anyways.

Are you actually doing that? If so, what code have you changed within your CollectionView's instance to make this work?

It seems more intuitive that a collection view without a collection would render the empty view. If I were in a situation where my collection variable were somehow undefined, i'd rather see the empty view than no view at all.
And can this class just be automatically generated when `acts_as_google_authenticated` is called?  That way the caller doesn't really need to know anything about it.
btw, no need to compute the hash. Simply compare the objects with ``===``
All taken care of.
I commented the actual method, should I do it at the call site too?

Basically it changes RDC at runtime so when you do create, delete, reboot, or resize it writes this to report.log. It's another to see what state the instance is in when the tests are over.
Why spaces around `=`? Can you add one empty line between docstring and code? Do not indent docstring.
please don't change the file permissions
Added in 3458e897022ed066fed64cdc4f6012dd825332ae as `php-fpm-restart` as I wish to keep version names out of function names.
Is ``!important`` needed?
Progressive enhancement not only forces the developer to prove their DOM skills (vs something that merely relies on JS, which could mean building the entire interface with JS), but it also leads to more accessible, and SEO-friendly code.

Something better? Silverlight? If you're referring to the data interchange format used, that's not dictated by the term `Ajax`, as would be inferred by `AJAX`. I purposely didn't specify `AJAJ` however, because I left it to the developer to show us a bit of their style.
please remove the trailing '/' on void tags. I would suggest you check all the files and drop this on everyone
That would be fine, but we will discuss API point renames separately from this PR
I guess my point is, puppetversion.rb (sorry I meant this one) already attempts to load puppet and 'do stuff' in a clean simple manner and if it fails it returns nil. I could be mistaken, but what you are doing does seem more complicated and perhaps not entirely necessary for the majority of people. Although I can see the value in a block doing a yield as your doing now, your saving maybe 2 lines of code when users go to use it, but adding something that seems harder to read to me.

I'm really focusing on the code where you use the function you have created. So your code below:

    Facter::Util::PuppetSettings.with_puppet do
      Puppet[:vardir]
    end

Compared to what I'm suggesting:

    begin
      require 'puppet'
      Puppet[:vardir]
    rescue LoadError
      nil 
    end

I would vote number #2 is much more readable as users don't have to have prior knowledge of your wrapper.
This bundle is just returned to ClientManager. And yes, it is used in memory (AccountManager caches the auth token in memory). Three lines above, the setUserData() call persists the auth token in the DB, which is stored encrypted.
why are the following lines commented out?
`(not (teen? age))` ajaisi saman asian.