labofsahil/github-event-dataset-2012 huggingface dataset:
In branch #148, I changed the functionality of this to subtract off the mean.  So `poisson.applyTo(im)` only adds the noise level associated with `poisson.getMean()`, rather than also having the average pixel value go up by this amount too.  This note is to point out that this doc will need to be changed on that branch after #237 is merged into it.
Do we want this function public?  I think it's ok.  But if we want to keep it hidden we can do so.  Just use
```
from base import _g1g2_to_e1e2
```
at the top of real.py and don't use the `galsim.` prefix where you use it in that file.
The FFT will always be either a power of 2 or 3 x a power of 2.  So this choice shouldn't cause large inefficiencies in the FFT.
Never mind on point 2.
Perhaps I can put that on the list of things to include in the issue I'll open about improvements and further development of the lensing engine.
On CentOS the service isn't enabled by default. Typically we expect this. It might be worth explicitly setting the action to `[:start, :enabled]` here
and tidied isDebug check (i upped one message to info ... good catch)
There's a scary amount of code!
I think we should stick with the names used in the Java code. It will be much easier to port future versions if the code has changed as little as possible.
Why do you need the line number in the message, Fabio? Doesn't it display next to the line with the problem? Is this for when you're reviewing debug output, or something?
line breaks in the t() cause problems for our translation scanner.  Also, it's best not to include markup in the translations.  I suggest you change this to:

<p>
  <?= t("Navigation buttons are hard to style and clutter the user interface.") ?>
  <br />
  <?= t("Use mouse wheel to scroll through the images.") ?>
</p>
That line needs to be deleted :)   -- It was a duplicate of line 22.
It's fine to have multiple `rescue` clauses I think. Also helps backward compatibility, if any is desired. Please merge...
Would `assert_field_eventually_equal` or similar be a better name?

It's not clear what this method does when looking at a call site only.
Should it not be ApS instead of APS?
I'm not 100% sure as I'm not that familiar with the inheritance manager.  I'm happy for you to do what you can now and I'll have a play around with the updated pull request.
I am just saying that we should see if JSON deserialization works with 10s.
Can you make a PR on symfony-standard as well for this change?
Sure, we can call it sexy-black-box or something
To answer your comment, @rstacruz :)
Достаточно только FileWriter
Corrected on 450783b7 commit
s/ot/of/ here and on line 256
Why update?
Works, but gonna put space.
I'll update the comment to make it more clear that this is a content binding.
The C-code snippet is small and self-contained, so we could translate it to Cython--I think that would make maintenance quite a bit easier.   @blink1073 would you be up for doing such a translation?  If not, @ahojnnes and I could tackle it.  Instead of simply translating the C to Cython, we should also see if we can extract any parts in which more Pythonic expressions or existing utilities can be used.  E.g., can we use the existing histogramming, clipping, bincounting, etc. functions?
``[2]``_
Hmm, I tried it with the matplotlib plugin on Windows 32-bit, python 2.6, numpy 1.6.2, and it also passed.
Interesting assertion :)
I would change  ``non-convex data`` to ``non-convex classes``.
Is it normal that you draw a bootstrap sample for each tree, even if forest.boostrap is False?
un typedef? On parle de valeur ici, pas de typage. C'est le constructeur de mpz par exemple.
временно нерабочий тест помечай как Skip. так делать не нужно
і цей
I'd put an instance of Boolean in the Model object... easier to read <c:if test="${hideAbstract}"> in the jsp.
Add comment for disabling copy ctor and assignment op
This has the potential for threading problems, among other things. Better to do the following:
```
static NativePlatformInterface instance;
return &instance;
```
pode ser, acho melhor tb
This is handled in doctrine/DoctrineORMModule/#71...
Isn't there a better approach than having an abstract factory and a concrete implementation extending it?
Strange indentation, and why is it here?
I think to avoid duplicate errors.  I'll move it + clean up the other issues
the diff report looks a bit odd, but both, if (notify) .. [above] and if (smartbuf) .. have moved into thread called IThreaded::main() below.
This should only be returning if the function returns false - same on line below.
The diff is changed now but I think I was referring to the StringIO import. Just run check.py on it and it should be clear.
honeybadger don't care about 1.8.7!

However, since several popular platforms ship it a default, this would be a sad test failure.
for consistency, we should double-space before this (and the next) heading.
Is there a race condition here? Is it possible that we get a `false` from this method and then it finishes before we call `connect` below? It's not clear to me how much of the reply behavior is asynchronous.

Another way to handle this would be to remove finished replies when we get the page load signal. Currently, the logic is "are there any replies left;" we can change that to "are there any unfinished replies left."
don't know how to mergre those, it will be the same 5 lines of code but on another lines
I'm a little confused here - why the settings variable? You only every assign it to appSettings, so it really doesn't do anything but save three characters. And you're updating the original object and then returning it, which doesn't actually help much. Were you intending to clone the appSettings instead of just referencing it?
It doesn't take 6 parameters, but just one of type aria.resources.handlers.LCResourcesHandlerBean.Configuration
Done: Added initUploadedImageElements() to get rid of xpath.
Done: Added initUploadedImageElements() to get rid of above concern.
@elicochran as we just discussed, it would probably be best if we figure out a different solution for this
@shacker: minor change, could you add a space after `:`?
@shacker Thanks for spotting this, created a follow up on #96
You forgot about this. No need to redo a pull request, just commit, squash commits and force push.
Good catch, that was old cruft.
@jnonon you could do a protected getCurl that checks if $this->curlHandler is initialized yet and otherwise initializes it.
There is no on_thread_dying.
This should also get applied to enum_domain.rb?
You can't use the full url. It wants the path only. I changed it to a variable though.
I like the idea of a warp method. This brings up a complication, though: For a *forward* warp, I'd want to pass the *inverse* coordinate transform, and for an *inverse* warp, I'd want to pass the *forward* coordinate transform. I think this would be confusing because, as a user, I would be wondering, "does forward warp pass the forward transform to `warp`, or does it pass the inverse transform so that `warp` goes in the forward direction (`src` to `dst`)".

One way to avert the problem is to drop access to the coordinate transforms. Then, forward and inverse would always mean the same thing. But if that gets dropped, it makes me wonder (again; sorry) why this should be implemented as a class. Here are my assumptions: users typically don't need to access the matrix or the coordinate transforms. Furthermore, they typically will only call the forward or reverse warp (but not both). I wouldn't be surprised if these assumptions are incorrect, so please correct me on this.

If the `Transformation` class stays and you incorporate `make_tform` into `Transformation.__init__`, I'd vote in favor of a slightly different name. Maybe `EstimatedTransformation`? (This assumes that the rotation transform is separated from the others, which seems right to me.) The name `Transformation` is very general; so unless all transformations would be moved into this class (e.g. `swirl`), it should have a more limited/specific name.

Sorry to be such a pain in the ass. Like I said, it might be a good idea to get a fresh perspective from the list so that we don't keep arguing the same points over and over again.
`event.getDamage()` is different from the nms code, and so you need a `// CraftBukkit` comment
Nitpicking the nitpick: Why? pep8 does not complain.
No, this was a mistake, thanks for the catch.
I think it's a function of the type of object, not what folder the file is in.  To me, Ellipsoid is fundamentally different from the coordinate/matrix types.  Here are some differences:
* It's really useful to be able to treat a thing with x, y, and z properties as a Cartesian.  But that's not really true with an ellipsoid, because its value is in what it does, not in its properties.
* Ellipsoid caches some if its derived characteristics.  In fact, every property other than radii can be viewed as a cache.
* No matter how you set the mutable properties of a Cartesian, no class invariants are violated.  As Ellipsoid is written currently, that will be extremely easy to do accidentally.  Because even cached values (like radiiSquared) are mutable, the mutability actually impedes future evolution of the class.  Like my example before, it would be difficult to add a radiiToTheFifth (if we ever needed one) without breaking everyone.
This object does not appear to be used anywhere throughout the codebase.  It and its specs shouldn't be included in this pull request.  I don't plan on reviewing it then unless there's another reason it needs to be here right now.
I dont understand why this is awkward. Can you be more specific? Please indicate the cons of such an approach.
What about the node being 'Titanium'?
Talked with Sabil. Old line of code that was from a previous attempt.
missing space again, also the preferred Log level for debug statements should be `Log.d` (also occurs more below)
var i = 0 should be grouped with the above var declaration
This seems like a lot of extra checks. Couldn't it just be a single if(![[TiApp app] windowIsKeyWindow])? The reason is that getting the windows array requires a memory copy that can be sidestepped.
Just to clarify, are you suggesting using a mirror invoke() (ie, ObjectMirror.invoke())?
Ah, you never said it was our convention :D haha
The `?` was a mistake though, fixing.
Alright, I'll keep this in mind going forward
This seems like a significant change. Can you please explain what you were thinking about?
i pushed a little fix to master. thanks again.
I'm not really mad on these two steps being joined together like this. They seem separate to me and thus should be so in the PO and in the test..
Justification ... first line
I'm thinking along the lines of C++, http://en.cppreference.com/w/cpp/utility/forward. That would apply to the arguments being forwarded (in our case the  entire parameter template). So for the example we'd have:

    void wrapper()(ref S s, bool doCall, auto ref int i)
    { if(doCall) s.f(forward(i)); }
`enum` should not be necessary.
Here would be the place for "and has empty range?"
It's just that it didn't fit on one line with foreach, so I thought spliting it out might be cleaner then:
foreach(S; 
TypeTuple!(string, wstring, dstring, char[], wchar[], dchar[]))
{
....
}
I definitely like the idea of unification and also the idea of facets. However, i am still missing symmetry here. So _ExecutableMetaData_ does not  implement _Validatable_ and provides access to _ValidatableParameters_. _BeanMetaData_ does implement the interface even though following your line of thought I would think that it just provides access to meta data. Unless of course _BeanMetaData_ is actually _ValidatableBean_. Do you see where I am coming from?
Replaced with runtime dependency rather.
spacw
$this -> cookie( $name )   is not correct styling... should be: $this->cookie($name)
you could use ``if ($config['query_fetcher_listener']) {`` as you will always have a boolean (the node is a booleanNode and it has a default value)
I refactored this method to be lastObsAtLeastDaysAgo
I've checked and found none
I've done a lot of ports. Those "else static assert(0,"unsupported");" are a godsend. What they do is quickly tell you every place in the library that's likely to need attention when doing a port.

It's one heluva lot easier than tracking down crashes caused by the default declaration not matching what the target machine does.
Is there any reason to make **import** for classes which are used only in the JavaDoc?
The repo variable is not being injected into the template, and so the above will not work:

```
template job_config do
  source "check-chef-repo.xml.erb"
  variables :git_root => git_root,
            :git_user => git_user,
            :git_email => git_email
  notifies :update, resources(:jenkins_job => job_name), :immediately
  notifies :build, resources(:jenkins_job => job_name), :immediately
end
```
lines 34-41 in recipes/checks.rb

You will need to add repo to the list of injected variables, and the repo variable value will need to come from somewhere, so you will need to add a new attribute to attributes/default.rb -- default[:chef_repo_name] -- and pass repo => node[:chef_repo_name] in the variables injection.
Yes, I have manually tested simple functions from all the APIs as of [this commit](https://github.com/brad/mailsnake/commit/a485c00f747bd419665bc55154e0d534af80ed00) and things worked fine. I'm not too familiar with writing tests, but yeah, that would be great.
this would not actually be a pull request, just a pull
'...with support for MySQL..."
But it should be. :-)
Are we no longer using this package?

The CultureHelper.cs and web.config.transform files have not been moved to other projects.
Not too sure on this one
This change should not have been committed. It is a local change relevant for the developer only.
Don't worry, I thought it was strange as well. ;-) Actually, their CSS code does not depend on using the <i> tag, so you could use span as well. In the CSS they just select icon elements by class name. But I think it might be better to follow the official documentation, for the sake of forward compatibility.
Pune și câte un `-` la începutul și sfârșitul macro-ului, să nu bage whitespace. Just to be safe.
Noted. The 2 classes SortingMapSerializer and SortingSerializerFactory won't be needed anymore as soon as soon as Jackson 2.0 is released.
I wrote to the Jackson mailing list and showed this implementation, Tatu Saloranta (one of the authors) is going to add support for sorting keys when serializing maps (same as the implementation here). Most of this code is to simply make it work with Jackson as available now in 1.9.5. I'll remove these 2 classes when Jackson 2.0 is released. At that point, we won't need any Java class added to linkedin-utils, we can use Jackson directly from groovy as-is. I don't know when Jackson 2.0 will be released though.

Here's what Tata said in hist last email on this:

Thank you for sharing this!

For what it's worth, I implemented the new feature
(SerializationFeature.ORDER_MAP_ENTRIES_BY_KEYS) for 2.0.0, will be
included in 2.0.0-RC2 when it gets out.
you are perdin terren with this.
Thats how they do it in tastypie. 
Also, I can check multiple fields like ('ComplexDateTimeField', 'DateTimeField') with one call. 
If I would use subclass or instance I would have to do:
	 if isinstance(f, fields.ComplexDateTimeField) or isinstance(f, fields.DateTimeField):
and I think this is longer and require additional imports

On 9. apr. 2012, at 14:20, Mitar wrote:
>> +        An ORM-specific implementation of ``get_object_list``.
>> +        Returns a queryset that may have been limited by other overrides.
>> +        """
>> +        
>> +        return self._meta.queryset.clone()
>> +    
>> +    @classmethod
>> +    def api_field_from_mongo_field(cls, f, default=tastypie_fields.CharField):
>> +        """
>> +        Returns the field type that would likely be associated with each
>> +        mongoengine type.
>> +        """
>> +        
>> +        result = default
>> +
>> +        if f.__class__.__name__ in ('ComplexDateTimeField', 'DateTimeField'):
> 
> Why comparing by names and not for example checking if it is a subclass or instance?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/mitar/django-tastypie-mongoengine/pull/1/files#r659812
Yes, I did. 
No more `dehydrate` in EmbeddedDocumentField.

On 9. apr. 2012, at 14:13, Mitar wrote:

>> +
>> +    def __init__(self, embedded, attribute, null=False, help_text=None):
>> +        '''
>> +            The ``embedded`` argument should point to a ``Resource`` class, NOT
>> +            to a ``document``. Required.
>> +        '''
>> +        super(EmbeddedDocumentField, self).__init__(
>> +                                                 to=embedded,
>> +                                                 attribute=attribute,
>> +                                                 null=null,
>> +                                                 full=True,
>> +                                                 help_text=help_text,
>> +                                                )
>> +    def dehydrate(self, obj):
>> +        out = super(EmbeddedDocumentField, self).dehydrate(obj).data
>> +        del out["resource_uri"]
> 
> How have you managed to get rid of this?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/mitar/django-tastypie-mongoengine/pull/1/files#r659803
True; without a setter, the setter attribute doesn't mean much, and since it's private, it wouldn't hurt to make it read-write.
Why do we need all these state variables for feature 1?
Missing DependencyManagement section with BOM to setup the versions required.
Whats up with the pre tags around the link? 

Also we should try to avoid the $base_url construct when we make links. Build them more like this:

<pre>
    $download_url = "islandora/object/{$islandora_object->id}/datastream/OBJ/download";
    $download_text = t("Download pdf");
    $variables['islandora_download_link'] = l($download_text, $download_url, array('attributes' => array('class' => array('islandora-pdf-link'))));
</pre>
std::move(r.next()-\>value)
I would reword this to say that size "always returns the size of the file, even if that file is an image on mobile web" or something to that effect. The current wording isn't immediately obvious (I had to re-read it before I got it).
This needs to be reverted.
d49e35 is the latest commit on Shared / unstable (f6d2cc was a few commits before)
See https://github.com/forcedotcom/SalesforceMobileSDK-Shared/commits/unstable
can you make it ``return parent::onKernelView($event);`` just to me sure?
Combination of `availHeight` and `availWidth` is necessary for mobile devices, because mobile device could be flipped.
Либо, тогда как-то включить в построение карты ответов xpath aib.xMsg, дабы эти ссылки игнорировались при поиске.
Just use `self.request`.  No need to replicate.
Use group1 from regex: ext\/(.+)\/client.js$
We pulled this from the browser, maybe @andchen would know better.
It is now fixed. Thanks!
No spacing before a bracket
You need to implement `boolean` youself instead of just calling the already implemented function from the standard library.
`divides?` could have been useful here.