labofsahil/github-event-dataset-2012 huggingface dataset:
add a docstring here to explain what break_when_n means
Will this be the one with sign text?
is that so area or zone update even in same zome\area?
If you could figure out how Hoptoad used to figure out a way to jump to the top of the middleware stack, we should do that for SSL.
Thanks - that is much nicer.  I'll update that tomorrow morning and resubmit the pull request.

On Feb 5, 2012, at 8:30 PM, James Turnbull wrote:

> You can shorten all of these by using a list of options:
> 
> $sensu_package      = $::operatingsystem ? {
>   /(scientific|centos|redhat)/  => 'rubygem-sensu',
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/jlambert121/sensu/commit/23bacbb64fdedc6d5ea1066f492bee887dd46313#commitcomment-935189
sow mmaps fertig, alle sinner core. npc gehen nach wie vor durch bäume und sonstiges durch... also irgwas astimmt da bei dir net xD
Wait, does Guard use Growl to show you the results of the tests or something? I couldn't find any other reference to Growl than the Gemfile before, which confused me.
This is a viable fix as the Function prototype as long as calling using Function.prototype.constructor is not used by any code that requires this module, instead of having a global side effect, it is much safer to not allow direct access to functions (as this may expose problematic implementation details from code translators or things that attempt to implement some form of inheritance via the .constructor property, both unlikely but they do exist). Also, Function and eval are still also available via the global which can be gotten at. So... people may end up passing a function that explicitly references these 2 functions and you will have the same problem.
@robinhouston, ok, just saw the link to the alaveteli-theme 'config-routes.rb': that file is definitely wrong, there's no need for a Dispatcher block. The AsktheEU one is different: https://github.com/dcabo/asktheeu-theme/blob/master/lib/lib/config/custom-routes.rb
I don't understand, why do you have that on_get_contact method and save the reference inside the menu? it should be just called "get_contact" and, in case you need to save the reference, it should be inside the handler, not the menu and it shouldn't be called with a signal, you could call it at __init__ or example. That self.contact variable is not really needed.

Also, you shouldn't connect to the same signal two things that are dependant, you could just use that on_copy_account_to_clipboard method, and get the contact inside that method.
My knee-jerk response is that social responses will follow very
quickly to an actual outage. If we have the data to analyze, we should
always crunch the data. I'm just offering my thoughts.

Sent from my iPhone

On Mar 4, 2012, at 12:53 PM, Andrew Butcher
<reply@reply.github.com>
wrote:

> @kelcecil, so we have an 1800 point data set in the data directory that needs processed before it's usable.  That set could be used to generate all downtime windows for the past couple years and has the potential for many graphs.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/tbielawa/py-prtstat/commit/9c932ee45f1857422779321cdf47a412bf8f3049#commitcomment-1040425
Very good job!! simple & work like a charm!

Seems your project will be used by a french java dev team.

Best regards,
@sitzm This should be fine since the older libnfs will have a soname major version of 0, so the library installed would be libnfs0.

I think you have to remove libnfs entirely from launchpad first, than add the lower version back in.
SQL ist drin
I'm out this week too but NEXT WEEK I AM IN for good :)
Should we abstract this into its own class? Maybe DetailDownloader, or something of the sort?
exelente video!... gracias por la info, en el siguiente commit quito el chequeo de LOS
> Если применять термин "Навигационная цепочка" то при программировани следовало-бы использовать 
> в качестве обозначения что-то вроде "NavigationChain" :)

Александр! Да, в веб дизайне термин "хлебные крошки" употребляется достаточно часто (один в шутку сказал, а другие повторили), но, Абсолютное большинство конечных пользователей никогда не поймут призыва: "Пользуйтесь хлебными крошками для навигации по нашему сайту" (а ведь мы же, в конечном счете стараемся именно для них!). Можно конечно возразить, что для конечного пользователя по-барабану, как называется та полосочка из ссылок, показывающая как глубоко он забрался на этом сайте... Но все-же как-то называть её конечно надо...

Я предлагаю не идти на поводу у абсурда и называть вещи понятными именами. Если честно, я не очень долго размышлял на эту тему, но появились примерно вот такие варианты:
- Линейное меню
- Строка навигации (http://usabili.ru/news/2009/09/23/breadcrumb_trail.html + краткие рекомендации необходимости)
- Навигационная строка
- Навигационная цепочка  (http://ru.wikipedia.org/wiki/Навигационная_цепочка)

Кстати, NavigationLine звучит может быть не так красиво, как BreadCrumbs, но зато сразу понятно о чем речь.


P.S.
Ради интереса поспрашивайте знакомых о чем сказка «Гензель и Гретель» и когда они ее последний раз читали или смотрели?   :-)
Am I missing a joke, or is the word "can" in the wrong place here?
Hi Spencer,

Thanks for the pull request.  I would like to commit a slightly different version so we do not allocate an extra void* on the stack during realloc.  This essentially just replaces _newData_ with the existing _data_ member.  Also, we'll need you to fille out the [Contributor Agreement](http://www.10gen.com/contributor)  before we can accept any pull requests.  As I already have a fix ready to push to master (temporarily frozen at the moment), I'd like to simply push my version and give you credit for your work.  Please feel free to contact us if you have any questions or concerns.  Thanks again for the patch!
@tomash can you revert this one? I have given up the push access.

Reverting the merge is not possible anymore, I think, but you can just delete the lines in question. If you want, I can make a pull-request which you can apply then.
:heart: :heart: :heart: :heart: :heart: :heart: :heart: :heart: :heart: :heart:
can we not use conditionals inside the function as well? So we can enqueue the ie stylesheet as well?
I think I can agree to that ;)
A static ```setL10n()``` could be an improvement. We could move some code from the initialisation in ```cgeo.init()``` into the corresponding classes.

The ```setL10n()``` is needed so far if the user enables the "Use english" setting which force a reinit of the localisation.
Arguably the original was better.
Wow, that was fast.

Also, I'm digging the meta-revert.
Change them to UnusedX where X is whatever number you want.

Since client doesn't need to know maxplayers, just don't do anything with the number you get. For name and desc, you can emit a signal for each telling the client xx changed.
Because it isn't a Scope I imagine.
A Scope can have members, it means it can have other declarations inside of it.
A Value doesn't fit that description.
@jcutrell no need to quote stats. 
We totally agree on IE6. I just think that this crosses the line from less-than-ideal to below-acceptable, if you have visual glitches over those visual elements that are key to your brand.
Also, I hope we don't start quoting low % figures to dismiss a11y next ;)
Firefox looks soooo good. "-moz-crisp-edges" is my new best friend.
Ok, I didn't get it the other day, makes perfect sense to do that here.
while (get()) {
      latch = new CountDownLatch(1)
      if ( setCallback { latch.countDown() } ) latch.await()
    }
Eye of Acherus doent work...
The most recent commit fixed the compilation issue as I referenced above. If you did not experience the compilation failure then you don't have anything to worry about as its already been fixed.
why char* not void*
Dette er en kommentar
Yes it is live. The problem you mention is that there are a conference + a workshop, with the exact same title. That's “all”.

In fact, I did not applied this in the speaker list. I will fix that (and reopen the issue).
You cannot use `before_install` for operations that involve Bundler. Switch to `before_script` (it is executed after `install`).
If you can fix this, I'll merge these guys in.
@Raptor399
Please be more specific. I tested this SRT and everything looked fine for me, exactly like local VLC playback. Only difference is that subtitles were displayed left-to-right not RTL. But I think its because of wrong codepage or something like this.

My PMS.conf settings

    mencoder_font = Ubuntu
    mencoder_subcp = utf-8
    mencoder_ass = true
    mencoder_ass_defaultstyle = true
вынесли бы эту штуку в отдельный блин партиал (вьюху)
чтобы не копипастить
ещё раз увижу копипаст, буду руки вам отрезать!!
Oh, I also changed the preferences dialog setting labels to right-alignment, for consistency with the modules interface and because it is easier to navigate.
Opcodes ported from 43x branch
:D ace work, this is kind of a cute app.
voir #2
I originally only modified the 2.x initializer, then went back and updated the 3.x railtie as well, but forgot to update the readme. :)
I suggest you move this underneath of instantiating the form
This definitly shouldn't be here - this is a global setting.
Wow lots of changes.
Hi,

I'm very new to git and github, , so thank you for the infos. I try another PR. BUT, as I wrote, there are some other changes needed that the adding of entities works again. Is it nevertheless ok to pull my changes?

Stefan
I appreciate the help, I think what I might do is split out the plugins into their own rpms instead of being sub packages. Especially if they are versioned differently. I will try and work on this this weekend.
Don't forget to add the icon-only example too.
You got it to tag.
Once again, I say why static?
Here assertion fails:

java.lang.AssertionError
	at vanilla.java.affinity.impl.VanillaCpuLayout.<init>(VanillaCpuLayout.java:49)
	at vanilla.java.affinity.impl.VanillaCpuLayout.fromCpuInfo(VanillaCpuLayout.java:120)
	at vanilla.java.affinity.impl.VanillaCpuLayoutTest.testFromCpuInfoOthers(VanillaCpuLayoutTest.java:70)
see above; OpenEngSB model objects should be completely sufficient
baaaaah. oops.
Ok. Works for me.
This came from the original code, I just made it clear for which stream it is about. Feel free to lift the limitation if this works for you :)
`its`使わない派ですか？

```
      its(:uid) { should eq you[:uid] }
      its(:provider) { should eq you[:provider] }
```
This should work for a mock but not in a real test.  You need to create a VPC and then create this security group.
(renamed -- used to be 'efscv') - can go
Could we say # Create an AssayData (cf. limma package) object...
I think this is a bit confusing… I'm curious what you're trying to do here. Also, technically `NaN` is a number :-/

```javascript
console.log(typeof NaN); // => "number"
```
You can use "array = $.merge([], design.getProperty(property)) to copy an array instead of using extend.
Does this docstring propagate through into the user-generated docs?
It is pretty close. The iter/list methods add some functionality.  I try to avoid using defaultdict as much as possible because it makes errors somewhat harder to debug.
This is waaay too expensive, put the call outside of the for-comprehencion
it starts here https://github.com/akka/akka/pull/703/files#L1L203
and diff only returns events, so I don't see the problem, I can move all this to a separate function to not mix up with the actor receive, which I guess is what you did
might be good to add a comment here that you have increased the leader-actions-frequency, so that Leaving is detected before Exiting
Please add to the docs what smaller value will have as effect or vice versa
import ckan.tests
I sorry, but technically this example is for writing a extension point and how to make CKAN "more pluggable".

Indeed, it is.
Having these strings here means people need to edit the core code if they want to change them, before they could just override a template file. Maybe not a big deal.

The docstring here should be something like "Return the given activity stream rendered as a snippet of HTML"
this line was duplicated so I removed the duplication
Weird that it differs this way. but if it's the way it's done in the movie settings we should do the same. but it should probably be fixed up.
Save two lines ;-)
Right. That is true. The navigator will take care of these stuff then, so we should not be trying to select anything here.
Let's have MRJobStep only take keyword arguments. `mr()` can continue supporting positional args for backwards compatibility (but it should emit deprecation warnings).
Just noticed: the parameter is `database` and not `db`.
this looks a bit suspicious.  do only numbers flow here, or is this code not really used?
btw. why is this in setTimeout?

also text.select should be in try/catch
cool. no need to add that function, then!
Alright, not a big deal
Point taken. :+1:
Are we going to fix this before 0.8 ?
ouais ok, jai vu visit `/` dans tes test alors je pensais que le routes marchais pas, my b
I think better way is extract factories generator from containerbuilder especially from `generateClass`. It's not `generateClasses`. Maybe move factories to separate file...
STYLE: rename to "AFNIBaseCommandInputSpec"
What is the `level=1` argument?
Also, if any pull request submitted an .idea directory with the contents normally found in one, I would reject it outright. 

With an explanation, of course. 

-- 
Ryan Bigg


On Tuesday, 12 June 2012 at 20:09, Philip Arndt wrote:

> > @@ -10,3 +10,4 @@ tmp
> > *.sw*
> > spec/dummy
> > *.rbc
> > +.idea
> > 
> 
> 
> Do you add it to every project you work on?
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/radar/forem/pull/238/files#r965946
> 
>
We could simplify this to a ternary 

```
content = self[0...stop] + options[:omission]
options[:html] ? content + options[:html] : content
```
Ah, one more thing, sorry! Two spaces here? Make the `R` line up with the `W`.
Yeah, like this:

```ruby
options           = {}
options[:ampm]    = @options[:ampm] || false
options[:start]   = @options[:start_hour] || 0
options[:end]     = @options[:end_hour] || 23

# vs

options         = {}
options[:ampm]  = @options[:ampm] || false
options[:start] = @options[:start_hour] || 0
options[:end]   = @options[:end_hour] || 23
```

The biggest one defines the amount of space to indent for all lines.
Use the `assert_deprecation(message) { }`
Hmm. Maybe extending range to support exclusive lower bounds falls to
ruby-core

On Thursday, December 20, 2012, bUg. wrote:

> In activerecord/CHANGELOG.md:
>
> > +    numrange, tsrange, tstzrange, daterange
> > +
> > +    Ranges can be created with inclusive and exclusive bounds.
> > +
> > +    Example:
> > +
> > +        create_table :Room do |t|
> > +          t.daterange :availability
> > +        end
> > +
> > +        Room.create(availability: (Date.today..Float::INFINITY))
> > +        Room.first.availability # => Wed, 19 Sep 2012..Infinity
> > +
> > +    One thing to note: Range class does not support exclusive lower
> > +    bound.
> > +
>
> Not so easy tho. Have to override a lot of methods to make it exclude
> lower bound (not only include?)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rails/rails/pull/7345/files#r2481685>.
>
>
Maybe this line is not correct since we already can use dynamic inclusion/exclusion values using proc/lambda.
Helpful. I'll add it.
It will build a deprecation warning message by calling `MyLib.deprecator.deprecated_method_warning(:foo, "this is a very old method")` then invoke the deprecator warning with the message and the caller's backtrace: `MyLib.deprecator.warn(warning_message, caller)`
This tests have wrong indentation.
of course that's why it was broken up like that :(  I was way more concerned about my commit message :)
There's a comma in the wrong place too.  Now I can fix that.
I've never updated a pull request.  Hopefully this just works.
changed this because i actually had abc123 as my API_KEY and it was failing.
Holy magic numbers, batman!   Is there no object we can hide these on as final val?
I don't think that's guaranteed on Scala's Set interface, but I can check.

Also, the clone interface doesn't enforce iteration order.   It's pretty much open ended what you do.....
What is this supposed to test? Referential inequality, structural inequality? Shouldn't it enforce a certain end structure?
I've put the `Hashing` in `math` because I saw `Ordering` there. But this might not have been the best decision - `scala.util` may be a better option.
Right, this result varies. What if you offset one point so the two choices aren't symmetrical anymore?
I felt this test need to be re-written to actually test against a real adjustment, but everything was so mocked out I wasn't sure how to best rewrite the test.  Opted to just prevent the test from breaking instead.
no its fine so long as we have tests.
why do we need a plot_simple command? why not put it all in show?
I'm suggesting.
On 26.06.2012 00:20, Aaron Meurer wrote:
>> @@ -0,0 +1,102 @@
>> +"""Tests for homomorphisms."""
>> +
>> +from sympy import homomorphism, QQ, S
>> +from sympy.abc import x, y
>> +from sympy.utilities.pytest import raises
>> +
>> +def test_printing():
>> +    R = QQ[x]
>> +
>> +    assert repr(homomorphism(R.free_module(1), R.free_module(1), [0])) == \
>> +        '[0] : QQ[x]**1 ->  QQ[x]**1'
>
> Why do you test repr instead of str?
>

Fixed.
Two things, mostly:
* Lining stuff up is a PITA.
* Hanging colons (with one or more spaces in front) feel like assignments, thus wrongly suggesting that there's a 'pretty_print' variable or attribute somewhere.
For the `Matrix` case, we should just compute the actual trace.  The problem with `Matrix` is that it is not a subclass of `sympy.Basic` so it can't go into `args`.
or `if not F.free_symbols.difference(V):`
On 13.04.2012 05:50, Christopher Smith wrote:
>>
>>       def key(self, monomial):
>>           return (sum(monomial), tuple(reversed([-m for m in monomial])))
>>
>> +class ProductOrder(MonomialOrder):
>> +    """
>> +    A product order built from other monomial orders.
>> +
>> +    Given (not necessarily total) orders O1, O2, ..., On, their product order
>> +    P is defined as M1>  M2 iff there exists i such that O1(M1) = O2(M2),
>
> this is a little confusing because I'm sure you don't mean that an order is defined as a boolean. Do you mean 'P is defined as M1 (>  M2)...'?
>

I don't understand. The order is not a boolean, but ... well an 
ordering. It is defined by what it does to monomials: M1 > M2 iff blah.
I do not understand the question. There is infinite recursion without
this. Adaptive sampling has nothing to do with it. Finally, if you
have an expression that raises this error there is a bug.

On 24 May 2012 14:54, Bharath M R
<reply@reply.github.com>
wrote:
>> +                  ('Symbolic value, can\'t compute' in str(e) or 'math domain error' in str(e))):
>> +                # Almost all functions were translated to python math, but some
>> +                # were left as sympy functions. They produced complex numbers.
>> +                #   float(a+I*b) raises "Symbolic value, can't compute"
>> +                #   math.sqrt(-1) raises "math domain error"
>> +                # Solution: use cmath and vectorize the final lambda.
>> +                self.lambda_func = experimental_lambdify(self.args, self.expr, use_python_cmath=True)
>> +                self.vector_func = np.vectorize(self.lambda_func, otypes=[np.complex])
>> +                results = np.real(self.__call__(*args))
>> +                warnings.warn('Complex values encountered. Returning only the real part.')
>> +            else:
>> +                # Complete failure. One last try with no translations, only
>> +                # wrapping in complex((...).evalf()) and returning the real
>> +                # part.
>> +                if self.failure:
>> +                    raise e
>
> Is there any particular reason why we are raising the exception. Repeated calls to to a vectorized_lambdify function will raise the exception when adaptive sampling.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/sympy/sympy/pull/673/files#r874451
how about `pretty(grid)`?
Is `@requires` an existing decorator, or just one that you are suggesting?
You don't use formattedDateString anywhere.
Sorry to be pedantic here but it looks like the indentation is off here.
Please use enumerations instead of strings to denote the mode. E.g.:


Vex.Flow.Modifier.Voice.Mode = {
  STRICT: 1,
  SOFT: 2,
  EASY: 3
};
Autoreleasing an autoreleased dictionary? Somebody forgot to run Analyzer.
Instead of surpressing warnings, why not something like this:

```
Iterator<?> keysToAdd = jsonObject.keys(); 
		while(keysToAdd.hasNext())
		{	
			Object nextKeyObj = keysToAdd.next();
			
			if(nextKeyObj instanceof String)
			{
				String nextKey = (String) nextKeyObj;
				try 
				{
					this.put(nextKey, jsonObject.get(nextKey));
				}
				catch (JSONException e)
				{
					e.printStackTrace();
				}
			}
		}
```
rename: notifyException. The only place this method is used is from the uncaughtException handler.
Actually internal + boundary? As you use total_number_of_nodes
This won't work for January 29 through 31.
This a little bit subtle, but unless a method needs to adhere to a certain interface, I don't think it's necessary/useful to test that the `__init__` method kwargs are certain values.  It's more important to test behavior of the object.

So in this case, wat's important to the `__init__` behavior is:

1. Omission of certain properties default to expected values.  I.e. leaving out the `port` defaults to `8098`.
2. When providing properties, it uses the user provided properties when constructing the connection.  I.e .I provide port `8000` and the connection is on `8000`.

I would test these by constructing clients with various combinations of default and provided properties and asserting state on the returned connection from `connect()`
Ab hier ist der Code redundant... oder??

Du erstellst hier eine zweite GroupRequest... und setzt nochmal alle werte...!!
I see the point, but those names are getting really long for something that's going to be used quite a lot. Let's take advantage of namespaces here:

    from astropy.coordinates.angles import Coordinates, Ra, Dec, Angle

I propose moving everything we have into an `angles` subdirectory. If someone wanted to do this:

    from astropy.coordinates.angles import Coordinates as AngularCoordinates

they can. In this scheme, the `Coordinates` base class would move up into `astropy.coordinates`.
I would prefer that it gets installed to ${includedir}/uv
Better to put this line after line 44 (after init has been called, since init could potentionally override this param value)
or this is your intent? to change the default value to 1 and let the user decide if to override it?
Create a link between start date and end date
Missed an f.object.credit here
Could this be documented as well?
I think the factoring might need a bit of tightening up here:

* The expression `WindowRefiner.forPeriodExpression(filter.periodExpression).withOffset(filter.offsetDurationExpression)` is duplicated in a few places in this class;
* Since `RollingWindowFilter` depends internally on `WindowRefiner`, could the RollingWindowFilter have an instance method to cover some of this code?
* It seems that there are many transitions from strings to dates and back again. Maybe this is unavoidable, but if it isn't it might be nicer to decide which way round suits the internal mechanics of the `WindowRefiner` best, given the handful of uses of that class.
This block is exactly the same as in the other file above and should thus probably be a function taking `$topic_id` and `$to_topic_id` instead.
There may be quotes, < or > in the path.
For the format. You can for example add `const FOO = 'https://secure.gravatar.com/avatar/%s'` and then use sprintf() when you use it.
Hiding is not simplifying. Say "hide".
this is good for now, but in the long term we probally want one sigar context for the entire process... we will get there eventually.
spațiu după %
Are you sure that this is safe to do. (Yeah, I know this code will be going away.) You might instead try changing the list ['first', 'second', ...] list below to ['first-addon', 'second-addon', ...].
I don't thick we should add a Procfile, because as @drewfish said this is Heroku proprietary.
Yes. Keep in mind that this gets executed once per process per view unless you use bypassCache.
On Windows the produced DLL files are located under `${EXECUTABLE_OUTPUT_PATH}`, so I'd suggest you use it for Windows CMD file.
I just build using MonoDebug and MonoRelease. No errors.
+ Private Location Location
These are the results we were getting from the patched grib api
Ok, let's discuss options.
Is there a precedent set for this kind of issue?
Why add the third phenomenon?
Can you explain this change? It seems unrelated to the adhoc work. Does it have something to do with merging Paul's code?
what if "back_office" appears later in the url?
Should this be default behavior? Should we at least log when this happens?
`return_val = getattr(self.lookup_function, 'none_is_true', False)`
Please revert this typo
You're right. I was calling handler_before_update where i should have been calling websocket_data instead. Good catch.
your point. Done.
This is causing problems on mingw :( over here, LTCXXCOMPILE is being defined witht just CPPFLAGS, CFLAGS and CXXFLAGS. However, the AM_*FLAGS and target_*FLAGS variables are not being used anywhere.

i don't know what exactly is causing that
Excellent. Does this mean that such aliases can avoid AST cloning with traditional "->" and "=>"?
```
overload call(closure, x) {
    alias a = closure.a;//injected
    alias b = closure.b;
    return x + a + b;
}
```

Then the last question I think. Call overload now constructed by https://github.com/jckarter/clay/blob/master/compiler/lambdas.cpp#L225. The first arg type is typeExpr. I should change it to the input type lambdaUnpack. What's the best way to do this?
You should remove this or else you'll call start twice if the initial request is successful. `done` !== `then`. Alternative: use `then` instead of `done` and don't `start` on failure for the second request.
According to this http://jsfiddle.net/rwaldron/hXMps/ in >=IE9, we don't need this condition at all :sunglasses:
Ah, wait.  I meant it's just a thought.  If we do it, we should probably do it for all modules, possibly in abstraction layer.  Need a right design.  Thus, I'm ok with the current one.
No need this table for classification. So you can see that we will drop the vertical table after we generated the horizontal table. Thanks.
```sql
    -- generate the horizontal encoded table.
    EXECUTE 'DROP TABLE IF EXISTS ' || enc_tbl_name;    
    PERFORM MADLIB_SCHEMA.__gen_horizontal_encoded_table
        (
            enc_tbl_name,
            'dt_tmp_ver_table',
            array_upper(is_conts, 1),
            verbosity
        ); 

    EXECUTE 'DROP TABLE IF EXISTS dt_tmp_ver_table';
```
okay, sounds reasonable.
When we add streaming to this I suspect we will want to have a HttpServer type singleton, as there won't be a clear way to know if the custom gstreamer output element that wraps a multifd sink or this frontend starts this first. I.e. we will need to restructure this when that time comes. But for now I see no point in making this harder for such a future feature.
ENV.make_jobs still works the same as before, so unless I'm missing something, nothing has changed, as I keep insisting. I guess we can add HOMEBREW_MAKE_JOBS back as supported for the five people who use it.
I don't know if we can omit it nowadays, but otherwise how does it
find the prefix for homebrew?
The old url was versioned. This new one isn't.
Sorry, got confused, my fault :) Ok to merge?
Comment above - not actually clearer.  0 is much cleaner, no side effects.
Hard to tell the frequency this will be run from the code snippet I'm looking at, but should this be debug to not hammer the logs?
Never occurred to me to set up a global gitignore. Thanks for the tip

6359dc9e91d00cc9710d08bdc445cafa4bf0c2c9
Sure.  Done in f8c1b7fd (though I thought I'd still need an explicit scalar(@bright_stars))
rm & mv are probably not needed - why not just mv it?
lol, Node.js your async makes be cry
`}) :` -> `}):`
For me, this was the most simple way to express that toString was going to act as a tiebreaker. But I wonder, does the code communicate the intent well enough ?
Why `< 4`? If all we need to check is that it's not to the `/multi` endpoint (ie, doesn't start with `/multi`), can that just be `!== 0`?
Let's kill commented/debug lines
Absolutely. I think this resulted from a copy/paste from another project.
line note test:
separate this out into two lines as well.
This function needs a header comment
Based on your next comment, fileName is not needed this soon, so I moved it back to where it originally was.

Yeah, it took me a while to figure out what that code was doing too. :) I am not sure how useful this assumption is. Seems like it may be more useful to "do nothing", but I just left it for now.
It's used now. Ignore prior comment.
In the case where nothing is selected in list, I think that hitting a navigation key should always select something. It looks like this happens for down and pageDown, but not up or pageUp. Maybe the first item should be selected in those cases?
Again, an incomplete sentence here :)
I'll have a look and if it's easy to replace I'll grab them. If not I will log a clean up task. Ultimately we probably want the language intelligence stuff factored out as a plugin that both clients can use.
How about "Sort Recent"?
unless we're trying to target python 3, `print` is a statement and thus looks really weird with parens (although is forwards compatible and doesn't break compatibility with python 2.x)
It's a bit late here, so I may be wrong on this, but I think you want this to be in an ensure block, that way if the failure hook raises an exception, they don't get run twice.  I think it could happen if processed as part of the job, then the failure hook raises causing a DirtyExit, which would attempt to run the failure hooks again.
I'm trying to encapsulate it so all you have to do in a form is this: https://github.com/dimagi/core-hq/pull/238/files#L3R66.  I think it's worth it.
I think this should be more like:
```python
function, args = generate_case_export_payload, (domain, include_closed, format, group, user_filter)
return generate_payload(function ,args)
```
where you have something like

```python
def generate_payload(function, args):
    if async:
        ...
        # some callout to the task, etc
        ...
        return download.get_start_response()
    else:
        return function(*args)
```

and then write those two functions
yeah, checked in the console:

In [1]: class A(object):
   ...:     @classmethod
   ...:     def cm(cls):
   ...:         print cls
   ...:         return cls
   ...:     

In [2]: a = A()

In [3]: A.cm()
<class '__main__.A'>
Out[3]: __main__.A

In [4]: a.cm()
<class '__main__.A'>
Out[4]: __main__.A
The only difference between SendTimeoutTask and ReceiveTimeoutTask is which method it's calling on channel. can we de-dupe this code?
IllegalState seems right to me.  The problem is not the arguments, the problem is this object is in a state when the type can not be added.
Bornes -> Bounds/Boundaries. Please try to avoid french words in your code, particularly in method names.
@nvloff — Since we're just creating/deleting a single note per API call (even though, of course, the object can have more than one note) perhaps we'd be better with `create_note` and `remove_note`.
I don't like the -DPACKAGE_TYPE="{DEB}" part there, because it is possible to generate RPM packages too.

* -DPACKAGE_TYPE="DEB" => DEB package will be created
* -DPACKAGE_TYPE="RPM" => RPM package will be created
* -DPACKAGE_TYPE="DEB;RPM" => DEB and RPM package will be created
`endOnTick` is `true` by default. Explicitly set `options.endOnTick = false` to override the `process.nextTick` function call.
comments = fields.ListField(mongoengine.EmbeddedDocumentField(Comment))
AttributeError: 'module' object has no attribute 'ListField

and i gat bunch of errors for other Fields if i use fields.
Just delete this file
also double quotes.
I wonder if 1 is going to potentially be an issue, as it polls really fast.  Should this be 5 or 10?
Remove this PHP block... not required.
sorry about the extra newline, not sure how that snuck in there.
Ok, I'll add some more comments.
fixed all of the formatting things you pointed out
I'm planning on using maven-deploy-plugin to automate deploy of all artifacts. The plugin has a special flag `updateReleaseInfo` which can be used to force release version (strip `-SNAPSHOT` from version strings):

http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html

This means release process would look like: tag, push, deploy with updateReleaseInfo, bump version (leave `-SNAPSHOT` there), commit, push.

However, It might be better to follow a more formal release process: strip `-SNAPSHOT`, commit, push, tag, push, deploy, bump version and append `-SNAPSHOT`, commit, push.
we can fix it in a future review
If we use the hostname like I suggested, would this have any point?
The tag in the repo is called 'v0.1', not '0.1'.
Can we make /tmp/this.class.getName() as the rootDIr? and clean up the rootDir in cleanup method? Seems currently /tmp/streams is not getting cleaned up. Only tmpOut is getting cleaned up.
Which service? :)
Well I expect the latter block to grow, therefore I took this approach, because we would have:

    if defined?(Bundler) and Katello::BootUtil.katello?
      Bundler.require(:candlepin, Rails.env)
      Bundler.require(:pulp, Rails.env)
      Bundler.require(:foreman, Rails.env)
    end
See my comment on line 132.
I propose that we could introduce two classes, MethodInvocatingContext and MethodInvocatedContext, much like the ActionExecutingContext etc., in MVC.
The Processing in the HubDispatcher should then use a MethodInvocationContext class internally to manage data, and update this accordingly.

The MethodInvocatingContext and MethodInvocatedContext could contain the information about the current request such as the HubContext, (and as Damian mentioned in a comment) perhaps HubContext, ClientAgent and GroupManager.

When the method is invoked in the Dispatcher, the result is assigned to the current MethodInvocationContext, which in turn passes it to the OnMethodInvoked method on the filters (if any), and updates it back to the MethodInvocationContext.
Registration could then happen only once and not at every request. I'm not sure, but also instance registration is not necessarily a light operation - that depends on a container implementation used of course.
right, using a console.warn instead.
Re @taldcroft's first comment: yes, your final question gets at the answer - this is a "factory class" in analogy to "factory method"/"factory function", rather than a "class factory".

But I fully agree with @taldcroft's second post - I think it would be better if this were a function that yields any of a number of different objects.   Otherwise, we'll get a lot of people doing ``isinstance(something, Coordinates)``, which will always fail because nothing is actually a subclass of coordinates.

We could also make `Coordinates the superclass of `SphericalCoordinatesBase`, I suppose, but I think that is still rather confusing because it doesn't actually have any functionality.  Instead, I would prefer a factory *function*.  That is just like we have now. 

I know I was outvoted on this earlier, but I think the discussion here (and a few other on-list comments) illustrate the danger of massive confusion here.  How about this as an interim solution: we change `Coordinates` to a function, but leave the name the same. That violates the PEP8 naming conventions, but I'm ok with that if it means this this is allowed to be a function - that will give much more useful errors for something like ``isinstance(obj, Coordinates)`` because it will immediately be apparent that `Coordinates` is not actually a class.

@astrofrog @wkerzendorf @adrn @demitri - do you have any further thoughts on this?  It's a quite easy change code-wise, so it shouldn't be hard to adjust regardless of how its decided.
Yes, I agree - that should be easy to do (I had already done it for the logging implementation).
i wrote the code based on /usr/sbin/rabbitmqctl. /usr/sbin/rabbitmqctl uses su command.
also camelBackStyle here
why defining abstract methods for the method of the interface ? This is useless as the interface already enforces them (making the whole class useless btw)
Can we kill these before merging please.
Although, wrapping each one with `c()` seems to make it work:

```
d> c(if (F) c("a"=1), if (T) c("b"=2))
b 
2 
```
Nice change! I really liked this new implementation :-)
Yup.  That stuff can be changed by whoever forks ipython into a  new project and redoes it from the inside out :)
How about introducing a new `GIT_EUNMERGED` error code and return it here?
Proper naming, please. `git_message__prettify`
Could this be made static?
no QR decomp yet
Why not do it by using the dust.isEmpty ?

dust.isEmpty = function(value) {
if (dust.isArray(value) && !value.length) return true;
if (value === 0) return false;
return (!value);
Haha, I did have it in there before I stashed and lost my changes on
another branch.

Check it now, I added some code.

Thanks for catching it :-)

On Wed, May 16, 2012 at 10:37 PM, Veena Basavaraj <
reply@reply.github.com
> wrote:

> > @@ -459,14 +459,15 @@ var HCHARS = new RegExp(/[&<>\"]/),
>
> we need it in the HCHARS too.
>
> I did the same mistake before; )
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/linkedin/dustjs/pull/34/files#r836841
>



-- 
*Johnathan*
Software Engineer
San Francisco, California
*Follow me on Twitter: @iamleppert <http://twitter.com/#!/iamleppert>*
a bit short, no?
what is it for?
Oh, I just realized this is likely pushing KB results way up over questions now. I think we should have the equivalent for question_title and question_content?
You're right--it should go in static per the Django conventions. I'll change it.
Hmmm, maybe you should just use the `document.id` and be done?
yeah but we cant use it yet because our emails are django templates.
want to fix jingo to handle that? ;)
since that is the end of the test I dont see the value of doing that. If someone doesnt read the code properly it till could be seen as using the same directory even though it changed.
out-of-date copied docstring
ugh, I switched the changes around, fixing
I got it! :relaxed:
Why not just this?

```javascript
this.constant = plane.constant;
```
For a reference type, `default(TData)` will be `null`. For a value type, it will be the zero equivalent.
Some of those are functions not filters. 

On Oct 15, 2012, at 10:35 AM, Owen Coutts <notifications@github.com> wrote:

> In jingo/__init__.py:
> 
> > @@ -104,6 +104,13 @@ def load_helpers():
> >  
> >      from jingo import helpers
> >  
> > +    if hasattr(settings, 'JINJA_FILTERS'):
> > +        for helper in settings.JINJA_FILTERS:
> I don't get why one would call them helpers when its a file of filters
> 
> —
> Reply to this email directly or view it on GitHub.
>
What should I do? Open PR for master branch with removing a class and open separate PR for 2.1 branch with preserving a class?
@everzet is it really needed to clear the stat cache each time ? @fabpot reported a performance impact with these changes, and the only difference when calling ``isFresh`` on resources is that ``clearstatcache`` has now been applied on it.
http://www.vim.org/scripts/script.php?script_id=1849　の注釈を参考にしてます。
comment on what this constant is, or better yet, encode it.
define a constatnt for 200
Good question. My suspicion is yes.
Not a necessary change, but I have a general preference for `sign`, not `log` vocabulary in our apps:

http://robots.thoughtbot.com/post/159805420/sign-up-sign-in-sign-out
Besides the odd formatting here (looks like somehow spaces found their way in) lets refactor this into a new  common init method, and add the following after `wantsLayer`:

    self.layerContentsRedrawPolicy = NSViewLayerContentsRedrawOnSetNeedsDisplay;
You mean assume alpha = 1.0 for all images without alpha channel? No matter how many channels they have?

Hmm, I think we agreed then to handle just those two cases if alpha is not specified. But let me know whatever you want me to change. At this point we handle the case where both input images have alpha channels specified in same positions, and we allow only for images with number of channels 3 and 4 not to have alpha channel.
Please revert this.  We never reformat existing code in the same review or checkin as other modifications.

Also, this code comes from an external source, so although its formatting is less than ideal, I think in this case it may be more helpful to keep it in a state where it's easily diffed against its original form to make it easy to see what we have modified.
I know, all this stuff doesn't really belong here, and looks like a bit of overkill: basically some design decisions needed here.
``self.stdout.write`` is probably safer than ``print``
Tried that before using this bovine approach, and tests whine about settings already configured. Anyway I'll post some code later, as I'm surely missing something
Ember States should not depend on Ember Views. We should definitely fix the code to remove this dependency and then merge this commit without that line.
@everbird 中午忘了问你了，这里我每次给cell一个新的对象，那前面几行是不是就不需要了？
The call to System.getProperty() needs to be wrapped in a PrivilegedAction. We usually do this with a package-protected class called SecurityActions.
shouldn't this be :no_depends? like the deb.erb patch?
Yeah, fixed, although it didn't really matter
Enable the <tt>strict mode</tt> and avoid to pollute global namespace by using a closure.
Let's get ready for CSP, and remove the inline js ;)
This depends on the offline/online state of Firefox. Do you know if the browser was showing you an 'offline' message when you tried yo access web pages or was it a different error?
so this == context?
This is the type of call that concerns me. I think `3` was the only one we had at one point, but we keep going back to the well. Method option hashes are a two edged-sword, but having to remember three parameter default values just to pass a mime type is ugly, too.

Since v2 is shut down and all future versioning will happend via :media_type, I'm thinking we can either combine all of those into a second options hash or combine them with with the actual params hash and cherry pick those reserved keys out internally on the other side. Thoughts?
What about exception handling:
Currently we leak the fact that settings are stored as json, is this what we want?
No self closing ifs, add ```{ }``` please.
It actually works fine for cloning (and random name), but I didn't mean to have it there so I yanked it.
Your current test doesn't actually verify that an exception has been thrown.

For example, you need to increment a counter inside catch (e.g. `throwExceptions++`) and than before calling `test.finish()`, do `assert.equal(throwExceptions, badValues.length`).
Recebi o seguinte [erro](https://gist.github.com/4070170) ao acessar essa página. O que será que eu fiz de errado? ;\
heading 1 は一番上の Frontmatter に書くっぽい！

    1 % Getting Started ←コレ！
    2 % Alex Honor; Greg Schueler
    3 % November 20, 2010

    5 This chapter helps new users getting started with Rundeck. We will begin
    6 by explaining the basics, covering essential Rundeck concepts and
The sent JSON should contain the key 'track' ... How could I be more clear here?
We've had issues in the past sending utf-8 over stdin. I think we did something like

``` python
sys.stdin  = codecs.getreader('UTF-8')(sys.stdin)
```
Is returning None the best thing to do here? It seems like you should throw an Exception here instead.
Please add our standard code header.

Example: https://github.com/Freeseer/freeseer/blob/experimental/src/freeseer-config


Is this just a startup script for the main app?
I wrote `\00a0` because I meant `\00a0`.
`\u00a0` in CSS content won't display a nbsp.
Soft is ignored on anything other than the main thread? I suppose that makes sense since there is no capacity for the end user to actually add anything to a pre-existing secondary thread.

Right?
These features are used in implementing others! Also yes they are super useful one could just provide prototype implementing devtools promise API and they will be good to go.
4 spaces please?
Can we use better naming for exception variables? Also please remove 'you' from the error message and just say 'The selected path is invalid'
Yes that's true, but the content script cannot use this style. You can move the code to inline it in the html markup, but I think that is even messier.

I also tried to use document.body.onload but had no success with it. Do you believe that this form is necessary?
Could be a large array then even when the consumer only needs 2 values from the back of the buffer. A range could probably help here. Would you mind asking some JS devs or Benoit Girard who is working on the internal Profiler which also has a circular buffer. See bug 713227 ff.
to many new lines here
This sounds good to me.  I'll work on that!
why openrutu?
You can't use init_lock_ here directly, since we're after methods that get a gctoken here. That means that the GC might have moved the this pointer. This is also why you see vm->thread-> being used, since that is properly updated when we GC. 

Also, why is it locking and unlocking the same lock here? Not really sure I get why

Hmm, looks like the line numbers confused me. So the first comment isn't true. Still wondering a bit about the second one though
This is copied from the block above. Just keeping it the same
please remove return types unless they are needed by the compiler.
```isset()``` primarily checks if a variable actually exists. Only secondarily it checks if it is no ```null```. Using an implicit ```isset()``` check yields the option that ```$params``` could not have been set in the method.
Shouldn't this be enabled only when `$recurse & self::RECURSE_ARRAY & self::RECURSE_OBJECT`?
You are here acting both as if it was an array and as an object (and just checking `is_object`). Maybe, instead of always returning a value, when none of the conditions is matched you should instead throw an exception.

Also, what about `Traversable`?
Import the subnamespace is better than import the class directly (like the Exceptions subnamespace). Old code was better.
Generally speaking we prefer to never use the @ operator in ZF. I think it's better to check if $rightOperand != 0 before the bcdiv(). In this case the automatic conversion of PHP, from a string to integer, should works as expected that means we don't have to check for zero value using the PCRE.
Mark the test as skipped is enough. Please restore this lines.
This is refactored in a future story/pull request.
The PHPDoc doesn't match with the method signature.
![surprised](http://www.codinghorror.com/blog/images/coding-horror-official-logo-small.png)
This should be `dev` requirements.
I'm not sure I understand your comment. It is the responsibility of the caller of this method to make sure NotifyIndexingService() is called or not and called at the right time. If the caller pass in 'commitChanges = false' then it must call NotifyIndexingService() after that. Otherwise, if commitChanges = true, then this method will call NotifyIndexingService() itself.
don't they have this in any public header?
Is there a problem with the `$name` that is returned from `_defaults()`?
not a fan of lack of max node ver. a lot of packages had been breaking for me in the past just because they used `>= 0.2` in engine req while I had node 0.6.
Ok. 50 is fine for now; just checking to make sure it wasn't an oversight.
Do we need to return anything here? Won't the defaults in the css cover it?
We should use fluid.isArrayable here since isArray is only available in 1.85.
Actually we're adding ; for all proto methods.
AKA `if (!('_id in doc'))`, right? :)