labofsahil/github-event-dataset-2012 huggingface dataset:
I don't think it's a big deal for these files, but here's a way to do something fancier (will edit history, but I think that's okay because we're on a branch:
 - Move the commit that deleted things you want to undelete to the top ("git rebase -i").
 - Do "git reset --soft HEAD^".
 - Use "git add" and "git reset" and "git checkout" to eliminate the parts of the commit you want to revert.
 - Commit again.

See also:

http://stackoverflow.com/questions/7214039/how-do-you-move-a-commit-to-the-staging-area-in-git

I'm happy to do the first part if you'd like.
Is this really the right way to go?  In your two measurement function, the m's are the direct measurements, and the e's and sigma are derived quantities.  It might be cleaner to have the m's stored here, and have a `getE1`, etc. that calculate those.  Unless you think that these moment values are really not something that anyone will ever want to look at directly, so it's worth doing the conversion from the start.

But even in that case, I think the conversion from (mxx,mxy,myy) -> (e1,e2,sigma) should happen in one place, namely the constructor for HSMShapeData, rather than separately in the two things that make this.
std::pow?  Or does it not matter?
Pushed... Changed the way the numbers are input to `assert_almost_equal` so that the *relative* error is that which is tested to be less than `10**(-decimal)` too in this case.
Bracing style change.
I see you nuked the existing gdata recipe, I think because you found a better way to not needing to patch (that's great).  But I don't see where you now want to install gdata from the standard places.
yeah, json_score_data has a specific format that you're not following, i can help you fix.
This println needs attention, but I'll merge with it in as presumably you want to know something about the jenkins machine?
Will leave it with you to remove or improve message when appropriate.
It looks like you did a global replace of all straight single quotes to apostrophes. This is one case where it might be better to switch these with matched single or double quotes.
[`null` is a primitive value itself](http://es5.github.com/#x4.3.11) so I think this could just be "Returns *false* for primitive types."
Nice. You still have to change the `app/views/pages`' partials
Forget it. It works
Interesting, will take at doing that today.
Removed whitespace to bump the build
This must cast it to a long, a user can easily assign $mongocollection->w = array(...) or whatever
> It's more a development dependency. It doesn't come along for the ride when gem install is used

I understand, it's just yet another thing to know about, maintain, etc that I personally don't use, and isn't strictly necessary for development of the project.
There are no other supported parameters to this endpoint besides the name (passed as __conf), so kwargs would be completely ignored.
What happened to kwargs?
Can you revert this change, this was done on purpose to demonstrate how to use the `render` method?
I think ``= true;`` is missing here. It's turned off by default atm, no?
The old way was standards compliant :)
Oh, because they aren't registered with the autoloader... if they are PSR-0, you can add them to the $loader object below.
Is it not possible to write the alarms as a separate widget to the telelmetry monitor?  It seems like their logic should be pretty independent.  However, if they can't be separated out this object should probably change names.
Надо закрывать в finally.
https://github.com/WindowsAzure/azure-sdk-for-java-pr/issues/271
When changing this to:

if(true) return comment; 

the test still passes.
Don't use that. Just make sure that the command buttons "stretch" (basically, remove the height, and make sure the parent is `align="stretch"` or `-moz-box-align:stretch`. I'm not even sure it's needed.)
We should set the iframe location and call `build` in a lazy way: only when the tab is selected.
Adapt the message if move is True
We should fix the PEP8 issue: test_statistics_page.py:16:5: E301 expected 1 blank line, found 0
eureka it works...
I will update the pull
ここは意図的に省いているんじゃないかな。空のconstraintsだけ入っていても、ここで説明するわけでもないし、なるべく説明のノイズは取り除く形で。
Used to build a request pipeline?
We can leave this test out--it's for functionality higher up in the module (I guess this comes from the pil_plugin tests, so we can move those as well).
>    fixed

Could you push, please
how about the random state modification
Random State.
there is an extra line here
Can we assume that we don't have to worry about synchronization?
You need to set your editor to truncate trailing whitespace. There's a million of these...
Proposition : Retourne un enregistrement de la quarantaine sélectionné par son identifiant
Met à jour la description du panier sélectionné
I noticed this typo ages ago, I hadn't realized it was never fixed. Well, it doesn't make much of a difference, but it does make life easier in certain cases.
```checkProtectAttr``` was all ```cannotModify``` was doing, so that could very well come inside. But CLightW uses it, so we need to wait.

Since that class is scheduled for removal, I'll wait until that happens.
Not only that, but I seem to have lost the ```OUTPUT_VARIABLE``` bit... I still have to get my head around testing CMake... :/
Can't really do that, as the `Locator` interface doesn't define any `instanceManager()` method.
Shouldn't be modified.
Yes you are right about this. This was from a pull request from another fork, i think

I have to create tests for every class so i can check better if a pull request breaks the code.
You can write this regex as `@[ ]{2}@` but what you have works well too.
should this be a map of String -> Object? Or are the things that get parsed necessarily going to be CMObject
That was my thought too.  There's still [a partial service outage](https://status.github.com/).  It might work once they resolve.
Same as the one in event_controller.py. What common area makes sense?
I'm OK with adding packaging to the source tree, but please add the YAML as well, since there is one - otherwise I forsee possible pain in the future
It's testing that superusers are explicitly excluded when checking the number of admins.
What happens when you try to compile this on different platforms, or when openmp is missing (or different compilers)?  I have no experience using openmp.

Also, I've read that funroll-loops is almost always a bad idea--comments?
What if the view contains unsaved changes?
Can we do this a better way? Including the super everytime is weird and seems repetitive. I don't get what's happening here maybe...
I'm still confused by this check.  When is it needed?  Right after a morph?
Talked with Bryan. The existing description looks good. Will make some modifications regarding iOS.
This should not have to be recalculated each time. If you have to write a method to count the number of rows, you're doing it wrong.
Error, changing to return code 0 and adding comment
Any reason these metrics aren't case classes like StatusMetric.  At first glance it seems like the semantics might make sense.
remove this line altogether
actually basestring is better here.
the second sentence should be removed (especially as I don't think it is still true now that thousands of bundles are out there including some very complex ones)
is this b/c self.instances was not implemented for debian? I would rather fail here than return incorrect results.
Don't need this comment :)
после if можно поставить фигурную скобку, тогда можно будет указывать более одного оператора.
This should be in the page object too.
Debugging output should not appear in patches you submit.
^_^ removed.
Checking for the type of the slice being exactly the same as the original doesn't work. I suspect that it's a compiler bug, but I don't know. In particular, `iota` fails with `hasSlicing` if I make that change. Asserting `static assert(is(typeof(r[0 .. $]) == R))`, `static assert(is(typeof(r[0 .. $ - 1]) == R))`, or `static assert(is(typeof(r[0 .. 2]) == R))` results in

> Error: static assert  (is(Result == Result)) is false

However, the code currently in the pull request works. So, I'm inclined to just go with what's here for the moment. And if we make it more restrictive later, it probably won't break much code (if any), since the main reason for a slice to be a different type would be is if it's a tail-const version of the original range, and that would presumably only be done if the range itself were `const`. And what's here tests what we really care about. The slice doesn't really need to be exactly the same type as the original so long as it assigns to the original and the original is constructible from it. It's not the same for arrays, after all.
Yah, generally it's been beneficial for performance to use assert instead of enforce or handwritten tests given that range primitives are intensively called. So let's go with this - calling front, popFront, back, popBack against an empty range is undefined but (a) guaranteed to fail in debug mode, (b) guaranteed to be as safe as the build mode.
Make `newLen` `immutable`. The compiler should be smart enough that it doesn't matter, but better safe than sorry. Actually, you should probably just shorten the whole thing to

    r = r[0 .. r.length - min(n, r.length)];

I don't see any reason to use up the extra lines or bother with declaring a variable. But if you're going to declare it, you should hint to the compiler that it's not going to change (and thus is potentially unnecessary) by making it `const` or `immutable`).
[According to the spec](http://dlang.org/type.html), `real` is the

> largest hard­ware im­ple­mented float­ing point size (Im­ple­men­ta­tion Note: 80 bits for x86 CPUs) or dou­ble size, whichever is larger

So, `real.sizeof` is guaranteed to be greater than or equal to `double.sizeof`. Also, `float` is guaranteed to be 32 bits, and `double` is guaranteed to be 64 bits, so the sizes of `float` and `double` don't ever vary and can never be the same.
Hum... For a range (from what I understood), value semantics means that if you pass it by value (say, to an algorithm), then modifying the passed range (popFronting it), won't modify the original range.

Ref semantic means you must save before passing, even by value, or popFront-ing the passed range will modify the original (the case of class-ranges).

Do I have the wrong definition? Or do you think the wording is unclear?
Oh brother. This should be deleted. We don't support opApply in std.algorithm.
can you rename this html5parser? that's the name i'm using in my change :)
No need to respecify this, it's in the parent.
пробел после запятой нужен
Oops, I left comments on the commits, not the PR. When talking about needing further clarification earlier, it was for `users` and `groups` parameters here, and on `createComment` below.
The correct form of this URL is `"https://github.com/SubZane/Sublime-Snipt.net/tree/master"`, but since master is the default branch for your repo, you can simply put `"https://github.com/SubZane/Sublime-Snipt.net"`.

Also, you forgot to end the line with a comma.
Actually, after looking it up, it seems you can only alias a namespace the compiler has seen a declaration for already. So the right substitution to make would be something like:

`namespace llvm {`

becomes:

`namespace LLVM_NAMESPACE {} namespace llvm = LLVM_NAMESPACE; namespace LLVM_NAMESPACE {`

This seems to me like it should be a simpler patch than looking for `llvm::` everywhere in the code, but I hasn't looked at how llvm is written ...
Could you rename these instances as well? Should be a fast search/replace.
Überprüfen, ob die gebaute URL dem erwarteten Wert entspricht
Perhaps follow the output scheme w/ something like "MEM UNKNOWN -"?
Again, we have a flip-floppy abstraction here. Are these importers that happen to maintain a map as part of their internal implementation, or are they maps? Decide on what the abstraction is that they present to the outside world, and stick with one or the other, don't flip-flop back and forth.
Should this method live in a mixin a'la https://github.com/rescuedcode/StaffPlan/blob/master/lib/staff_plan/shared_finder_methods.rb?
Should we single-quote this like the other arguments?
TypeInfo.next is a property function, so `()` is not necessary.
Would it not have sense, to check here, that you are not registering a `ValueTransformer` of itself? If this happens, we will possible get infinite recursions when trying to use such incorrectly configured transformers.
Umm, it's kinda minor, but shouldn't that be "Thread settings have been updated"?
Sorry, indeed it isn't. It turns out I was getting the errors due to a corruption in my local db. Some notes had no comments causing nil dereferncing and I didn't check it thoroughly enough where it was coming from.

I'll redo this commit to remove this bogus fix.
This method ends up returning `nil` if it falls through the `case` statement.  Would raising an error be a better behavior?
I was just trying things out and forgot to take it out.
Yeah, I was going to suggest exactly that.   Convention over configuration, as long as the api_key is documented, that's a better way of doing it.   

Maybe it makes sense to do this in a more generic way that other Mailer things could handle?  Maybe a params hash or something (authentication_paramaters?), so that a mailer that uses a username/password/server  could put those in params and work in a similar way
verion -> Version
could you make this an absolute dir?
A bit confusing to have the newline inserted explicitly here but have an implicit ending newline using println. Can we move the \n to here and just do prints instead?
Should we have our wrapper of mysql instead of getting it from springsource
then?
cheers,

Javi



On Thu, Aug 16, 2012 at 12:34 PM, Romain Deltour
<notifications@github.com>wrote:

> In pom.xml:
>
> > @@ -591,5 +632,15 @@
> >        <name>Eclipse Gemini Maven repository</name>
> >        <url>http://download.eclipse.org/gemini/mvn/</url>
> >      </repository>
> > +    <repository>
>
> Can you comment on what each of this repo is used for ? We should minimize
> the use of 3d-party repo (in an ideal world we would only depend on Maven
> Central), so having such info will help maintaining the list of repo, and
> removing those which are no longer needed.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/daisy-consortium/pipeline-assembly/pull/1/files#r1391608>.
>
>
no no no no. Don't swallow exceptions, at least log them.
Sure, I think it's good enough for now but I did think about that.  We're never sending a you are not the host event, so until we have that a toggle is fine, right?  We should only ever toggle it 'on'.
Yeah, and I just checked the hibernate sources. There the test is added in a commit of its own with the only comment being "added additional tests" (https://github.com/hibernate/hibernate-orm/commit/81f31939c5f3835f703c74c77b3e9ceac9d43759) so not very helpful.

Since I don't understand the reason for the test I'm reluctant to change it. I will bring in your changes, but revert this particular line and ignore the 2 affected tests on Firebird.
identá bien o te corto la chota.
4 espacios.
En python la identación bien hecha es obligatorio.
This is the Proxy representation of the Android Activity type:
http://developer.android.com/reference/android/app/Activity.html
`index` property will be the `cancel` property if set, else -1
Sentence fragments and a little awkward. Maybe should be:

> To prevent a layout pass each time a property is modified, use a layout block delineated by `startLayout()` and `finishLayout()`. 

There is also an `example:` section now in TDOC2 if I remember correctly.
Spelling: s/lnaguages/languages/
Why do we need $caret here ?

if $category has an url, it can't be a dropdown,

for me the category is a link or a dropdown but can't be both  so we could write it this way :

```php
<?php
<li>
    <a href="<?php echo url_for($category['url']); ?>">
        <?php echo __(isset($category['name']) ? $category['name'] : $name) ?>
    </a>
</li>
```

or if you want to force it to be a dropdown if the category has item then you need also to put ```data-toggle="dropdown"``` in the **a** tag
Perhaps you can use the built-in indexOf method to find out if an element is in the array or not?
unit tests are compiled seperately now, can you remove the line here and add it to the main cmake file in the root of the framework
If you check for "config && config.permission && ..."  then all the unit tests do not need to change signatures
I really liked it myself
Why is this done only for scm?
You pass in the desired orientation to lock, what would rotate do?



From: Nukul Bhasin
To: blackberry-webworks/BB10-WebWorks-Framework
To: Ken Wallis
Reply To: blackberry-webworks/BB10-WebWorks-Framework
Re: [BB10-WebWorks-Framework] Adds orientation API to the blackberry.app (#246)
2012-11-05 12:05:31 PM



In ext/app/client.js:

> @@ -50,6 +50,23 @@ defineReadOnlyField("name");
>
>  defineReadOnlyField("version");
>
> +function lockOrientation(orientation, receiveRotateEvents) {
> +    if (typeof receiveRotateEvents === "boolean") {
> +        return window.webworks.execSync(ID, "lockOrientation", {orientation: orientation, receiveRotateEvents: receiveRotateEvents});
> +    } else {
> +        return window.webworks.execSync(ID, "lockOrientation", {orientation: orientation, receiveRotateEvents: false});
> +    }
> +}
> +
> +function unlockOrientation() {
> +    window.webworks.execSync(ID, "unlockOrientation");
> +}
> +


can we please add a rotate function then?

then we meet the spec + one method.

\u2014
Reply to this email directly or view it on GitHub<https://github.com/blackberry-webworks/BB10-WebWorks-Framework/pull/246/files#r2031900>.



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
can we please add a rotate function then?

then we meet the spec + one method.
Of course I can, do you have a particular reason though? 
The offsetGet method is made to return a FormView, the children member variable may change, be renamed or scope changed.
Same here, all omitted args should default to `anything()`, right?