labofsahil/github-event-dataset-2012 huggingface dataset:
I don't know whether it makes sense. 
If i would use $storageName for the bucket. It will create for each object a new bucket. 
I think it's not fast enough

I will make a benchmark with :
 * one bucket for all objects
 * one bucket per object
why are these being repeated?
have pushed https://github.com/deepak/knife-solo/commit/25f319668049d42215508ead8ef059d8e8d6eeeb as well
have not made any changes to OperatingSystemNotSupportedError and its like
*30 characters or fewer.* part I would throw out.

What are error messages if string is shorter or longer then limits?
Do you have `id` field? Currently you have it named `number`. You should rename it to `id`. The idea is that `number` name is badly named.
You should probably disable submit button here? Or even immediately after submit, so that you don't get double posts?
Yes, TODO. :-), But indent one less this last `)`.
He he. I don't know either. :-) I don't like X.

But you decide. My main comment was that you should find something and that it should be consistent.
`minute` -> `minutes`.
I don't like floating here. It should be simple addition to the menu list in the header.
In my opinion, the easiest way to find reverse parameters is to use 404 error output to built it. So you do a request for unexisting page and Django will tell you what URL resolves exist. So after some playing you get to:

```
reverse('api_dispatch_list', kwargs={'api_name': 'v1', 'resource_name': 'post'})
```

Now you should move this in template `url` tag.

Please make API name a template constant (in context processor). Don't hard-code it into the template directly.
colour isn't a keyword; it's an index, as documented in grid.clj. The idea is that different devices have different capabilities, so trying to make a keyword colour such as :red work over the abstract protocol is painful. Instead, you state that a palette of colours exists, which is a fn from index number to concrete colour. A vector is just such a fn. MetaKeys should use the same palette, so it should take integers rather than keywords as colours. If you like, I can do this fixing for you.

That way, (led-set grid [4 4] 1) lights up red on a red monome, green on a green monome, and whatever colour you've set at palette index 1 on a launchpad, but by default red. The protocol only allows you to specify that (led-set grid [4 4] 1) sets a different colour than (led-set grid [4 4] 0).
Yeah it seems like there should be a more obvious way to do it, but apparently not.
needs on all envs
Надо если не коллэбл вызывать в противном случае передавать если там что-то другое то приведет к стринге просто в итоге или уже закричит addHeaderLine
incorrect. GetSpell() returns the spell class.
Textgrössen sollten afaik in `sp` statt `dp` angegeben werden.
Should this file be in .gitignore? Looks like a file we don't want in the repo (but correct me if I'm wrong).
I didn't knew that, thanks!

To be honest Composer changes the definition of dev a bit more that I'd like.
The authentication storage will automatically handle the conversion from saved data to managed entity and the opposite. It will avoid serializing entities since that is a strongly discouraged practice.
Where did this go? (Actually, this might have been superceded by the refactoring of the transport mechanism to support requests and urllib… I'll have a look at that once this patch is tidier.)
> A common place to store these indexes is the filesystem, and that is the default option for Hibernate Search

A common place to store these indexes is the filesystem which is the default for Hibernate Search
Please remove the phrase "liveness" wherever it appears, it is far too magical  This should be explained in the context of event bubbling, which always happens, so that events can be caught on elements that are added after the initial handler is attached to their container.
You should be noit_error here, not noit_stderr, but I see no reason for this message.

Also, it isn't that you couldn't, it is that you shall not attempt to.
Should maybe have something CONST for `5`.
I would like to let django-tagging as the main dependency and maybe create an optional 'multilingual' feature that has a dependency on django-tagging-ng (http://packages.python.org/distribute/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies).
Why replace z? Why not let people choose?
You might consider using 

`
weight = Series(np.repeat(['low', 'hi', 'low', 'hi'], 15), name='weight')
`

for aesthetics. There's a small problem with unnamed Series in that the name attribute exists but it's None and this shows up in plots. We don't account for that in this code yet.
Wil check that thanks.
Ok.  I will remove it.  I added that in as it was in the design wiki approach.
Please, insert more blank lines. I find those very appealing, to be honest.
I agree with Barney, but if we are changing it then I'd be okay with Jim's ```GaussianVariate``` suggestion.
You should remove this debug output
Am I missing something that's happening in the engine file TCAPIProcessor.cs around line 535 where it uses the "registration" param to create a context for an Activity State request?

In my testing, I removed the "reserved" params for all requests and I ceased to get reg-specific state info back from the LRS.

Also, note in the code that the params are only left out when the request is a POST _and_ when it is a reserved param.
* It's not good to have a dependency on Aloha from a util file.
* It's better to use the PubSub module for new events: ```define(['PubSub'], function (PubSub)```
* The new event should be documented in doc/guides/source/events.textile
how about implementing basic single quote escaping inside the function?
Ok, I see why you want to pass in null.
But instead would be better to have a super constructor that takes just class, so if someone calls the other constructor with a null entity instance we can fail fast.
Nope, there should not be a problem. It's just a clearer way to express the operation. If someone had never seen a programming language before, I believe it would be easier for them to understand, as the grouping is natural.
These lines that have "const" are strangely indented. Please fix them. Also, it's probably okay to drop the const in both cases.
You guys to silly/inconsistent things in the name of micro optimizations so your guess is as good as mine :D
Yep, easy thumbnails is an external dependency. Adding in to setup.py (In next pull request)
I don't think I would hard code this in here. There could be a quite a few cookbooks which need this recipe and it might be confusing if it's included all over the place.
it is intended to be a public API. It decorates a view to make some tests (with validators) and to do the cornice logic in here. I'm not sure of a better name, maybe "decorate_with_cornice_logic" or someth similar? (I don't like my proposal ;))
Is this the tautology club? This doesn't seem to test anything.
esta declaração de charset está errada.
deveria ser:

# -*- encoding:utf-8 -*-
ou
# encoding: utf-8
ou
# coding: utf-8
Não comparar strings Unicode com strings Utf-8
Deveria ser: 

```
self.assertTrue(u'Sua conta não está ativada. Por favor, entre em contato com a SciELO ou verifique seu e-mail' in response.content.decode('utf-8'))
```
ain’t a --> is no (?)

we want --> you want (makes the blog post more personal, relatable)
The correct way to include other gems when you are developing a gem is to use the `add_dependency` and `add_development_dependency` methods inside the .gemspec file. 

In this case, rspec is a development dependency while nokogiri is a hard dependency.

Checkout Yehuda Katz explanation for this here: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
Why do we want this?
This should follow PSR-2 style, most likely a space between the ternary parts and lower case `null`.
*burns have been salved
in fact, i think the first argument should be typed "const struct fpag_bits *const bits"
for maximum const correctness.
Updated to use a hash https://github.com/cwolferh/thor-cli/commit/4a1602cc02d4b33be4bc04662e34c56e1fe6193e
if it will be used in the future but not now, maybe we should add in the future?
We can just call `response.send(400)`, right? I don't think the client should expect an object for a 400 response.
Во-первых, использование ArrayList намекает другим программистам, что этот список модифицируется. Но это не так. Правильнее использовать просто интерфейс List.
Во-вторых, этот список инициализируется в конструкторе, зачем он инициализируется ещё и здесь?
Тут закрывается stdin?
Theoretically, the marker may miss IMarker.MESSAGE attribute. In this case you will get NPE here. Use marker.getAttribute(IMarker.MESSAGE, "") to avoid it.
It would be good to make a `target` getter, so you don't have to keep the variable up to date if the toolbox changes targets. Same for `tabTarget` and `chromeTarget`, though those will be solved by Joe's target stuff.
Are we scrapping the idea of Firebug being able to use this? It's weird to me to mix `gDevTools references in with `this`.
Are we really sure this is a remote "chrome window"? Feels like this is really a remoteGlobal.
remove the extra lines
As above, should be a table, or needs headings moving to the correct place.
I believe the only impact at the moment is in DimensionSwapper, which is pretty thoroughly exercised by the existing tests.

@rleigh-dundee may want to have a look, though, as he added the original ```clone()``` implementation and may have a different use case in mind.
Just add an if statement:

```python
if learning_rate < PAI:
    update = eta * loss.dloss(p, y) * class_weight * sample_weight
else:
   update = ...
```
What exactly did you need to do for that?
> I'm sorry I should have been more explicit about which code I'm talking.
> The int/int wasn't the problem in this case, but thanks for the reminder I still fall into
> this trap from time to time.
> I was referring to the out commented code in  your gist:
> https://gist.github.com/2979853

I don't have time to dive into the maths. Work formulas in
matrix/vector and try to understand what steps benefits from the
covariance updates : avoid multiplications by zeros et recompilation
of parts of the gram matrix.
+1 for `StandardScaler`
crap, that must have happened with the rebasing :/
> Все внутренности методов и работа с REST в рамках реализации должны быть черным ящиком, больше чем дает документация разработчик знать, по идее, не должен.
> Это не работа с REST, это определенный тип запроса к определенному сервису.

Почему? И то и другое – это предоставляемые нами АПИ. Первое в виде функций, доступных по HTTP, второе – в виде функций, доступных в PHP.

Если ты делаешь непрозрачную обертку, в этом должен быть какой-то смысл. Примеры смысла:

* обертка работает с разными АПИ одинаково (это не так для нас)
* обертка в чем-то лучше, чем Uploadcare-ский АПИ (в этом я лично сомневаюсь)

Какой смысл в данном случае?

Теперь, о проблемах, вызванных непрозрачными обертками:

* если они неидеально предоставляют все возможности, что есть сейчас, они мешают, а не помогают
* если они неидеально предоставляют все возможности, которые появятся, они мешают, а не помогают
* они требуют постоянного обновления вслед за обновлением того, что они оборачивают
* как и в любом коде, в них есть потенциальные баги, которые, в случае непрозрачности обертки, будут затруднять пользование обернутым объектом

У Uploadcare простейший (4 метода?) RESTful API (с рестом в среднем по больнице все умеют работать лучше, чем с кастомными функциями). То, что должна делать библиотека – это помогать выполнять рутинную работу (типа заголовков `Authentication`) и предоставлять shortcut-ы для особенно нужных методов (`store`, `delete`, ...). А не пытаться спрятать от пользователя пугающий, страшный API.
Which suggestion are you refferring to ?
It's not about the rules, it's about consistency. I agree single-char variables suck, as does code in the opening brace. But don't introduce even more funky code like blank lines between if/else (I never saw this before in DMD or elsewhere).
Remove commented code (it's dead).
type description needs to be updated since not all the types are supported
For now, this is an edge case that we can live with.

To accommodate this scenario, as well as someone canceling a request by calling `[request cancel]`, we should refactor this so the `RZWebServiceRequest` has a weak reference to the `RZFileManager` it came from so that it can do the appropriate clean up in these different cases.
This helps avoid the pesky warning when building for HWA.
I think it should be ok to call join() on a Thread object that was not started, though it looks as though jthread.cpp thinks it's worthy of tracing (with a stackdump) in debug builds. I can add a check I suppose.
the ipaddress check isn't necessary, only that the slavenum is within range.
Is this going to be right on Win32, where we might mix `/` and `\` together when loading things?

I would guess that we should have the autoloader sanitize data by replacing `File::ALT_SEPARATOR` with `File::SEPARATOR` on all platforms where the later is defined.  That would ensure that we can't reload twice by accident.

Might also be worth defining behaviour so that `../../util/foo` and `../util/foo`, and `util/foo` do the right thing - with a special view to `util/./foo` and `util/././foo` being handled.  Not that I know some people use hacks like that to bypass path uniqueness checks elsewhere in our (user DSL for our) product or anything.
You need to cast `token[0]` to `int`, i.e.: `isdigit ((int) (token[0]))`. Otherwise there are problems with some compilers.
Right I meant promise argument here, did not realized that it was shadowed by destructing.
@gquemener :heart:
Are we deliberately choosing to do nothing if the publisher is not found? That is, is this expected to happen for some requests? If not, I'd suggest we change this to 

Publisher publisher = Publisher.fromKey(pubKey).requireValue() 

and remove the conditional. If the exceptional case of the publisher not existing occurs, an exception would then be thrown
Sorry, I clearly didn't look at it properly :)
No, `span2` doesn't fit the words Gallery within it
Some of the new category calculations will need to have their definitions hashed out better. Does the definition of week look at an entire calendar week in reference to the current day, or from current day +7? On top of that, it'll make the calculations a bit more tricky, thus can we hold off on the redefinition of the sections until after I get the initial tasks feed merged in?
`(get muunna rank)` palauttaa jo valmiiksi numeron.
I would personally write this as `[values enumerateWithOptions:NSEnumerationReverse usingBlock:…]`, since `NSEnumerator` sucks, but it's something of a stylistic choice.
No really good reason:
http://stackoverflow.com/questions/8264973/why-are-anonymous-namespaces-preferred-to-static-globals

It's been the generally recommended way since C++98 IIRC, mainly to simply reduce the use of the overloaded keyword 'static', I think.

Matt

________________________________
From: Robin Burchell [notifications@github.com]
Sent: Wednesday, November 07, 2012 2:06 PM
To: nemomobile/nemo-qml-plugins
Cc: Matthew Vogt
Subject: Re: [nemo-qml-plugins] Various simple improvements to the email-related classes (#29)


In email/src/emailagent.cpp:

> @@ -19,7 +19,17 @@
>
>  #include "emailagent.h"
>
> -static int sRetrievedMinimum = 0;
> +namespace {


is there any reason to prefer "namespace { /* stuff i don't want visible */ } over using file statics?

(btw: this shouldn't in theory be a problem, since CONFIG += hide_symbols is enabled for all plugins, but still a good idea to follow good practice I suppose)

—
Reply to this email directly or view it on GitHub<https://github.com/nemomobile/nemo-qml-plugins/pull/29/files#r2051723>.
Same comment as earlier; why are we restricting the flatpages?
If you pulled in Msf::Exploit::Exe you could drop LPATH and use generate_payload_exe. 

If you want to use a non MSF exe you just use set EXE::Custom to the path?
split(' ')
For example, why would the convert function outright reject valid/normalized signals that have some overshot, which is common after filtering? This seems too limiting to me for a scientific imaging system. Maybe I'm missing something.
'P' -> 'N' for consistency with docstring
Good question, most likely a typo, but this is actually a decision point that we need to deal with it.  Does CZML processing give "best effort" service, or should it just pass everything through.  I.E. should we be coercing numbers/booleans/strings, or not?  I'm leaning towards 'don't coerce' anything, and I think @kring agrees with me on that, but I could be convinced otherwise.  Thoughts?
Probably don't need this `@see`.  Maybe one for `setPositions`, but I feel that I have overused `@see`, especially for functions on the same class.
I prefer the original code.  While the new code is a bit more efficient and mathematically identical, it is not numerically identical.  With the original code, adjacent tiles are guaranteed to exactly overlap at their edges.  With the new code, due to floating point rounding, there could be a small gap between adjacent tiles or they could even end up overlapping by more than just their edges.  I don't know offhand if this would make a practical difference (possibly some cracking or z-fighting artifacts at tile edges?), but in my experience it is very much worthwhile to defend against this sort of problem.
This works for regions greater than 3x3. The region doesn't have to be square and the dimensions don't have to be odd, but it'll waste loop iterations because it doesn't check the pixel. It works best if  `width === height && width %2 === 1`.
For morphs to/from all modes, is this always the right union?
We should probably mention 'before Ti 3.0, on iOS, playback time was in seconds'
data should always be non-null here based on the process from line 79 to line 89.
Can we reword this to something like "turn off text UI in landscape mode in 4.0 b/c Android numeric passwords are not masked correctly in landscape mode" ?
Add a blank line before this.
Excellent point. ok
Should it  be taken from instance, rather than from class? I think there should be @attributes hash in the model itself. Here you manipulating with class
ref in code font
We were debating this in another pull request (pull #688 IIRC). These dont' return either values or types. They return templates, so it's not at all clear whether they should be either camelCased or PascalCased. But they're specifically compile-time constructs, and most compile-time constructs are types, so it makes good sense that they'd use the same naming conventions. Also, if you camelCase them, they quickly start conflicting with functions. We already have `std.functional.not`, so making this `not` would` conflict with that.

I fully support the naming conventions of camelCasing templates which resolve to values and PascalCasing those that resolve to types, but I think that we should be defaulting to PascalCasing with templates like this which evaluate to other templates or for which it's not at all clear whether they're really evaluating to a value or to a type.
forget it; just reread the blueprint.xml :-)
As I read it, 14.1 only refers to the user-agent's Accept header, and there is nothing specified about whether a server can override it. I don't believe the server's capabilities come into it, except for generating a 406. Only where the client is agnostic to multiple media-types should the server's capabilities be considered. The code I've added allows the service author to use q values to give weightings to media-types in the case where the server prefers one over another. However, this design is in no way called for in the spec. - I've only chosen to use a similar 'q' system because it will be familiar to REST practitioners.
This is typically the kind of code that I think would be better expressed using an HTML template.
I would just try to createDynamically with the GraphDatabaseAPI and if that fails with the tx-manager as parameter, no need for version checking imho.
I definitely think it would be helpful for testing - as long as this is the official schema. Is it? Did you write it or does it come from JUnit or Ant?
Can you do `.off('hover').on('hover')` here to be consistent?
As the comment says, it's there for [bug# 8675](http://d.puremagic.com/issues/show_bug.cgi?id=8675). Apparently, dmd incorrectly complains about throwing Errors in nothrow functions.
`<emphasis>Spring Integration 2.2</emphasis`
Adding this worked...

    		maven { url 'https://code.lds.org/nexus/content/groups/main-repo' }

...but it's probably not Kosher
Those need to be updated if the image sprite changes, right?
k, also I thinking about dropdown menu for this input and 
update input description: "to set custom datasource user must override input value"
The whole export workflow should be probably re-factored if there are plans to have more export plug-ins.
We will have to decide how to do translations.

Maybe add TODO.
in model

default_scope :order => 'created_at DESC'
Maybe it's strange, I am spell script noob :( I've tried it this way and it works
Academically speaking, the sorting algorithm is stable.
Could just inject PortalGinInjector, and remove this class completely.
I don't understand why this docstring is here
What if purchase_arguments_t is not defined? Then you will have an error. 

Also are only string values accepted, because ```` 0 || "" === "" ```` 

Lastly purchase_arguments_t is not a very "javascripty" name but thats mainly a nitpick.
you can write it in a more compact way:

```
coef[j], _, _, residues[j] = sp_linalg.lsqr(X, y[:, j].ravel())
```
this `<archiveDirectory />` line seems superfluous.
nice.  that must be a fairly new git syntax.  i've never seen the --delete option!
If this is Android-specific, shouldn't it be in he Ti.Android namespace?

Quite willing to be wrong about this if we're planning on following up with iOS support.
`representing a font`
where I took out navbar from
or changed to class exist on guzzle
Please take a look at this discussion:
https://github.com/blackberry/BB10-WebWorks-Framework/issues/407#issuecomment-10911695

I found a problem with implementing contact picker callbacks. If cancel and done are registered under different event ids, since only one of them will get triggered, the one that is not triggered is NOT cleaned up. To make sure there is no leftover handler, should register cancel & done under one event id.
I thought according to @jkeshavarzi we set up the modules for them
the form component uses getter/setters to access properties, jms serializer uses reflection by default. The line was an attempt to synchronize behavior, however jms serailizer doesnt detect public properties and therefore fails when using "public_method" with my test objects.