labofsahil/github-event-dataset-2012 huggingface dataset:
Also the lorin method would look like: 
    def login(self, user='user'):
        self.click_browserid_login()
        if type(user) is str:
            credentials = self.testsetup.credentials[user]
        else:
            credentials = user
            from pages.register import ProfileTab
            ret =ProfileTab(self.testsetup)

        from browserid import BrowserID
        pop_up = BrowserID(self.selenium, self.timeout)
        pop_up.sign_in(credentials['email'], credentials['password'])
        WebDriverWait(self.selenium, 20).until(lambda s: self.is_user_loggedin)
        
        if ret:
            return
You don't need to do that. The event is already dispatched on the 'window' object which is what you listen in the WindowManager class.
@everzet I think we agree about the `final` method. But what about my 2nd questions (different paths in a bundle hierarchy) ?
events on refresh
And during said drawing colors robotic limbs gray.
Update this.  icore->idevice and it's phoenixpilot since it's new.
`Email.model_for` is consistent, right? Could leave off the "Email" part I think.
Do we still need this rescue? I think this is keith and probably not needed
I have a feeling we should move this and `randomNumbers` into another module or something... (not for this pull) just wanted to put it out there.
how about return "O_O"; ?

just kiddin'. (maybe)
We should use hover_over_settings_menu inside the click method.
Should this be moved into the try block?
Nope, both sorry i also had a offline discussion with him on that hence got to the conclusion of making it global and simplifying it so that we only have a single point of change so that we can test multiple apps-statistics if needed
We cannot use is_enabled() because it does not have that attribute.
Or are you thinking of this from a different angle?please do share your thoughts on this
`--framework` or `--template_framework`?
I implemented this several weeks ago, so the result of our discussion hasn't slipped in this PR yet.

But maybe I expressed myself unclear in the hough-peaks PR. I think it is totally necessary to filter out equal valued peaks within the same `min_distance` window. With "soft-threshold" I meant that the center-of-mass method may filter out peaks that are actually separated by more than min_distance or min_angle, because of the extents of two equal valued peak areas. It might happen that the "minimum distance" < min_distance/min_angle < "maximum distance" between those two regions... I hope, it is now clearer what I want to express? Otherwise I could create a small image to visualize what I mean...
Excellent... put that description there.
you don't need the ``()`` in this line if I see it correctly. If you close it after the ``norm_ones``, the ``\`` is not needed any more - usually it is good to avoid it and use ``()`` instead.
Fancy names are often good to hide the fact that something is a hack ;)

Text data is often multinomial, right? There is work on that but it's a bit more complicated.  Also it is very sparse, which this implementation is not.

Gaussian visible units do work. Check out Alex K.'s master thesis for his work on CIFAR.
'R' is a single-letter non descriptive name. It would be much better to find a better name that tells the read what the variable is. In addition, variables starting by a capital letter are supposed to be 2D arrays.
please use ``assert_less``
https://github.com/scikit-learn/scikit-learn/pull/710/files#r602479
про attr = 1 это пример, не надо наверное в ридми
Need to remove the `console.log()`
On iPhone, the VoiceOver screen reader system can I think read out alt or title text, so yeah that might need something added.
Is p used ?
Why does this have a dependency on JMX? (not just this line, but the rest of the patch as well). Is there no way to implement this without relying on JMX?
Ther has to be some interaction otherwise the map will be dragged at the same time as the point. Teh event can not be consummed by the PlanningLayer on a conditional basis.
As elsewhere better not to use real machine names and paths for the open source submission.
I'm sorry I didn't look at this with enough detail, but these were indeed deprecations, your comment is missing context:

                        if (!global.params.useDeprecated) // <<<<<<<<<<<<<<<< HERE
                        {
                            TypeFunction *tf = (TypeFunction *)fd->type;
                            if (tf->ty == Tfunction)
                                error("use of %s%s hidden by %s is deprecated", fd->toPrettyChars(),
                                      Parameter::argsTypesToChars(tf->parameters, tf->varargs), toChars());
                            else
                                error("use of %s hidden by %s is deprecated", fd->toPrettyChars(), toChars());
                        }

I'll create another pull request to fix this...
Do we really need a QDateTime here or should a QDate be used instead?
Did you mean DEFAULT_MAXMEMORY here?
Hmm, on 2nd thoughts, in OSS with no maxlength, and a variable record definition.
keyLen will become 4k (prior to this change it was the abs. max = 32k)

That's going to mean that we're back to where we were before, with keys being build with variable record defs > 4k - will fail.
Now with "key+payload exceeds max length".
[ That's unless they add a ,maxlength(N) qualifier again ]

I think need to ensure that it doesn't use keyLen anywhere as a hard limit here now.
I'd guess jutil is the best, yes.
This will still fail for brew versions before 9.2. grep is looking for "packagename:", but the colon was added with the format change. That could just be head -1 and work on both.

We could probably detect the older format with something like this, which would return the version for the old format, nil otherwise:

```ruby
info[/[^:]+ (\d.+)/, 1]
```
Did you mean not_if? only_unless isn't valid.
That sounds perfect.
That was my initial thought too as you could see, but it felt bit awkward to type `windowUtils.xulWindow(window)` so I thought this would make more sense.
Can we get rid of this method now?
That's brilliant to make the z-index -1 and opacity 0.5.  I was wondering how we would stay out of the way of output.
correct the class name.
log a bug for the slowdown for non-unique names.
remove width: auto
Would this be applicable for collections too?

    PUT /notifications
    {read: true}
Yeah I wasn't sure how to include psexec as a mixin.  Plus if you notice It is slightly tweaked from the original.  I proposed the question in IRC and HD suggested I just copy and paste.
`GeometricTransform.inverse_map` does not exist, should be called `ProjectiveTransform.inverse`.
No, your comments weren't offensive at all. I just wanted to make sure that *you* weren't offended by *my* comments.

I guess part of my issue with this implementation is that I don't understand the need to access the transformation matrix. In my mind, I would just want to warp an image or transform coordinates, but neither of these require direct access to the matrix. There are probably reasons to use the matrix directly; I just don't know any off the top of my head.

On the other hand, there are definite advantages to the class approach: it's nice to have a single interface for all the transforms. Also, I think factory functions are a bit more confusing for the typical user than a function that returns a class. Nevertheless, it's a bit unusual to pass a method of a class as an argument in a function (there's nothing wrong with it, it just may be extra thinking for some users).

If the class approach stays, the current API still doesn't feel quite right to me. Here are some random (possibly-conflicting) thoughts: 

* maybe `make_tform` -> `estimate_transform`.
* could `make_tform` be incorporated into the `__init__` method of `Transformation`?
* I think the rotation transform is quite different from the others (i.e. it has a different interface and isn't an estimate) and possibly deserves a separate function. Maybe the current rotation transform can become a `rotation` function that takes an image and a rotation angle and calls `warp` internally (similar to `swirl`).
* Should the user be required to create a `Transformation` object and then call `warp`? Maybe there should just be functions that warp images, e.g.  `similarity(image, src, dst)`, similar to `swirl` and `homography`.

It might be a good idea to ping the list to see others have opinions about the interface.
with 

```
borders = np.logical_xor(bw, cleared)
label_image[borders] = -1
```
you could display label_image with a pretty colormap, showing each coin with a different colour. I think this would show even better how `label` works.
This is not the proper way to set a default value; instead you should set the default in the DB schema. Does this matcher work with that methodology?
It's set the same way as all of the other `@global_options` https://github.com/tstmedia/rack-reverse-proxy/blob/abbd32bd8b921501d0410a3021c6fbd59bc55a9e/lib/rack/reverse_proxy.rb#L113-115

Example:
```ruby
use Rack::ReverseProxy do 
  reverse_proxy_options :preserve_host => true, :newrelic_instrumentation => true
  reverse_proxy '/test', 'http://example.com/'
end
```
You're right, this is a race condition. If the resize happens too quickly this test will fail. The assertion should be moved to "test_instance_returns_to_active_after_resize" in the function "is_finished_resizing", right before "return False".
You don't need to convert the canvas to a data url and reload it as an image.   Just use the canvas directly as the default texture source, I guess renamed to `defaultTexture`.
Not our convention, exactly; it's just a behavior-driven development thing.  Check out all the Jasmine examples on this page: http://pivotal.github.com/jasmine/.  All the `describe()` and `it()` calls form sentences.  @shunter scolded me once awhile back for not doing this, but maybe we've moved on.  I think it's a good convention, though - I've even started doing it for new tests in Components.
We probably should.  I've contemplated proposing we get rid of all "constant objects" because of this problem; I believe this includes IDENTITY, UNIT_X, UNIT_Y, UNIT_Z, and ZERO in the various Cartesian/Quaternion/Matrix classes.  This pattern doesn't work when the objects are normally mutable.  Each module can have a locally scoped constant if they use it a lot.
Shouldn't these constants be moved outside of the function scope and in the module scope; this way they aren't re-declared ever time the function is called?
What's the purpose of the branch? Both paths have the same code.
Sure, I couldn't decide wether to put this on by default or not. Fine with me either way.

Un-resolving a post after it's been resolved will re-open the comments already, so I think your second comment is moot. It would be cool to spin a post into another post, but that will be a bit harder to pull off and will be for another time ;)
Where does this file get stored? Might want to have a flag or setting for where the temp directory is
Based on feedback from the PowerShell team, in the near future we should settle on using System.Management.Automation for running and evaluating test scripts.  For now, this is a good stopgap
What could happen if the user specify by accident .from("/delorean").roles(). Will it throw a NPE?
All events are supported on all controls, meaning that pinch and touchmove are supported on TableViewSection and everything else in Ti.UI. Mobile Web doesn't distinguish between control types unlike the other platforms. For us, everything inherits from a single base control (Ti._.UI.Element) that provides gesture support, adding/removing children, layout handling, etc.
"it behaves" -- present tense. Period after true.
useless imports are useless, docstring doesn't make sense anymore (VERSION and VERBOSE_VERSION are in `tools/version.py`)
Can we get a more descriptive name?
Is the !args[:force].nil? necessary?
Nice catch, thanks.

Fixed in 5b6ff40
Actually just making it "Async" could be confusing.

You see, both "Regular" and "splunkjs.Async" are making asynchronous calls. The latter is just using our utility module to simplify those calls.

Having "Regular" and "Async" tab might imply that the "Regular" tab is not asynchronous, which would be incorrect. So I'll be leaving the second tab as-is for now.
если это все классы по три однотипные строчки то им точно нужно вместе быть
Infact the great @steveklabnik says it infinitely better than I can: http://blog.steveklabnik.com/posts/2011-09-09-better-ruby-presenters
You're right, the .save exposed by joiner only guarantees saving the state of the joined ranged itself, it says nothing about the state of the elements themselves. My bad.
Again, a (fairly) direct copy from TimSort for Android.
http://cr.openjdk.java.net/~martin/webrevs/openjdk7/timsort/raw_files/new/src/share/classes/java/util/TimSort.java
oops, the "disagree" is ambiguous. I mean to say that I think you should keep your triple quotes. FYI, triple single quotes is also an option if you want to make the inner and outer quotes look different (as Siggi asked for)
Actually, we need to remove all personal copyright lines, there should only be one for UGent.

Authors should be listed in another way, together with a maintainer (see https://github.com/hpcugent/easybuild-framework/issues/334).
Bon je corrige le constructeur et c'est fini :)


2012/11/6 Frédéric Hardy <notifications@github.com>

> In fr/Contents/chapter4.md:
>
> > +        )
> > +    );
> > +
> > +    $loader->register();
> > +
> > +    use mageekguy\atoum;
> > +
> > +    // A commenter si vous utilisez composer
> > +    require_once __DIR__ . '/../../../../../vendor/mageekguy.atoum.phar';
> > +
> > +    abstract class Test extends atoum\test
> > +    {
> > +        public function __construct(adapter $adapter = null, annotations\extractor $annotationExtractor = null,        asserter\generator $asserterGenerator = null, test\assertion\manager $assertionManager = null, \closure        $reflectionClassFactory = null)
> > +        {
> > +            $this->setTestNamespace('Tests\Units');
> > +            parent::__construct($factory);
>
> Attention, il n'y a plus de factory dans atoum, donc il faudrait mettre à
> jour le code s'y rapportant dans la documentation.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/marmotz/atoum-s-documentation/pull/10/files#r2039614>.
>
>
nit: grammar.
`System.currentTimeMillis()`.
Thanks, removing in favor of `thincloud-test`.
I don't like it; we need a better way to handle optional imports; a more general one; there could be always others more libs
I'm not too sure about using a dict here instead of the previously-used 'None' value.  What's the motivation to replace

    {"self.value = None", "self.value = somevalue", "return self.value"}

with the respective

    {"self.value = {}", "self.value['value'] = somevalue", "return self.value['value']"}

The latter seems to be both verbose on code and wasteful of memory.
Could this configuration be initialized by Arquillian from arquillian.xml, etc.?
You can take off the ```=nil```
Well. It seems that in extreme situations the current `escapeText` is faster, but in more normal situations, it isn't. I've put the results [online](http://176.31.254.73/tmp/bench.html).

The code I used is here: https://gist.github.com/3496913

In lieu of the `intercalate` code being easier to read than the `concatMap` code, I think I'll go for the former.
It's safe, but if B is connected, we want the later clause to do the special thing (to avoid accessing B if x==0).
there is not test for this parameter
Personally, I think I would rather see these tags done like so:

.. _gallery_tags::
    :key-event-handling:
    :foo-tag:
    :spam-tag:
Maybe what we do as add something like this 

```ruby
 if session_opts[:user]
  auth_parts = session_opts[:user].split('\')
  raise SomeException, "Username cannot be empty" if auth_parts.length.eql? 0
  raise SomeException, "The username #{session_opts[:user]} is an invalid format, i.e. There are too many \\" if auth_parts.length > 2
  
  if  auth_parts.length.eql? 2
     session_opts[:basic_auth_only] = false
  else
    session_opts[:basic_auth_only] = true
  end
else
  raise SomeException, "Username cannot be empty"
end
```

Something that I could use some guidance on is.

Should you throw uncaught exception and allow ruby to die? (I think that answer is no)
or
Should you write to stderror (through the chef UI constructs) and exit with an alternate exit code?
This seems dependent on the client's performance then - which gives me concern. So the issue is that you need validation style to be applied first, then you can run the animation? Can you trigger this on a callback then instead of running a timeout?
Also, there is no need to check for `elOffset` here, as it is contained inside of an `if` that checks that.
Ah, at first I thought you were asking me to change the amount of posts down from 3 to 2, so I committed that.

I've been viewing scopes separately from filters, so in my mind it's not an issue that filters don't affect the scope counts. I don't require it, but if it's something you feel the project needs, then `ActiveAdmin::Views::Scopes#get_scope_count` would have to apply current filters I imagine.
No blank line before docstring, format as shown in comment above.
MINOR: Refering to namespace, not log data in comment.
I don't entirely disagree with your basic argument.

However, putting a breaking change in a point release concerns me.

Regardless of whether we like it or not, the AbstractCorrelatingMessageHandler gets injected with a MessageGroupStore strategy implementation, and that strategy exposes methods that return MessageGroup, which is again a strategy. So, there is absolutely nothing stopping someone implementing an entirely custom MGS/MS combo.
After thinking some more, I don't think this is the right property name - we are not parsing anything.

unpackPayload?
splitPayload?
singleValue?
This is parimarily used for determine the address and port of endpoints on other role instances
Would something like ```Dir["#{fixtures_path}/unmodified/*.conf"].each do |file|``` work instead?
nvm I see
use more specific exception type
ここの戻り値の型は、明らかなので型推論でよいかと。
Explain to users that Java 6 is supported and recommended and support for Java 7 is on the way.
@apex13 Fixed
At least 1 per core. And 1 should be OK if we do not reach the limit of RAM usage by node, so that's I think that we should spawn at least 1 process per core and decide if more depending on the RAM memory we have.
Cred că putem numi `participant/create.html` pe acel template.
I just reinitialized my environment this morning and discovered that somehow this isn't working. I'm changing it back.
Your EmbeddedIndexedListField -> our EmbeddedListField.
Our EmbeddedSortedListField -> mongoengine's SortedListField.
https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/Compiler/RegisterKernelListenersPass.php

We even have this in FrameworkBundle ? Then it is logical that people copy it :disappointed:
should probably clean up trailing &
ino deram viewer namard zade :(
dg ba dream code nemizanam
I SWEAR :pray:
Fix is in master now.
Readonly property, not a method.
iOS seems not to have a click event on a slider.
This method mostly coerce database type when you have a schema, but since mongo has no schema I don't know how we can handle that? How are we supposed to coerce a `DictField` to a `ListField`?
Yeah, I think so - let's remove it
> 1. Скрываем по меню кнопки "Скрывать изображение"
...

Этот бодыль был и до этого пулл-реквеста. Сейчас отправлю патч.
this looks a a little weird for sure -
so the webworks.js creates XHR to framework and then framework back to client files.

Could you require this file instead in the framework? we basically use a custom version of require that @jeffheifetz wrote so I am sure if you have a special case you can handle it in the custom require.

I would like to move away from an explicit XHR from the framework to the client.
Request.Query cannot be null according to GrumpyDev
createWebview is redundant, or... it should be. This module is called webviewFactory. If it were called webview, I would still assume I use it to do things with webviews. IMO, I think `webview.create` is a more succinct API, and module name. If anything, I would call this module `webview/factory.js` instead of how it is now.