labofsahil/github-event-dataset-2012 huggingface dataset:
ok I've tried calling this 3 different ways why won't it allow me to run startActivity(Intent)

its in the apis http://developer.android.com/reference/android/content/Context.html#startActivity(android.content.Intent)

but causes build to error complaining about:

frameworks/base/policy/src/com/android/internal/policy/impl/GlobalActions.java:291: non-static method startActivity(android.content.Intent) cannot be referenced from a static context
                        Context.startActivity(new Intent(Intent.ACTION_MAIN).setFlags(Intent.FLAG_ACTIVITY_NEW_TASK

then if I remove Context I get:
frameworks/base/policy/src/com/android/internal/policy/impl/GlobalActions.java:291: cannot find symbol
symbol: method startActivity(android.content.Intent)
                        startActivity(new Intent(Intent.ACTION_MAIN).setFlags(Intent.FLAG_ACTIVITY_NEW_TASK

we are importing android.content.Context WTF?

any ideas on how I can call startActivity(android.content.Intent)? I understand that Context is static but how to get nonstatic Context to call startActivity on?
nope, after remoing it usb.apk works wine and all works wine.
bt gps? error with it? if so just update framework base... also get that problem some hours ago.
this is not the scope of this pull request 8)
Right, you're using `call()` nevermind.
Okay, I'll go ahead and remove `shallow` for now, and we can add it back, probably as a Number, like you mentioned.

On Aug 7, 2012, at 2:05 PM, Satyen Desai <notifications@github.com<mailto:notifications@github.com>> wrote:


In src/collection/js/array-extras.js:

> @@ -360,3 +360,36 @@ A.zip = function(a, a2) {
>      });
>      return results;
>  };
> +
> +/**
> +Flattens nested arrays at any abitrary depth into a single, flat array.
> +Specifying a truthy value for `shallow` will not recurse to all depths.
> +
> +@method flatten
> +@param {Array} a Array with nested arrays to flatten.
> +@param {Boolean} [shallow] Whether flattening should _only_ happen at the first
> +  depth.
> +@return {Array} An array whose nested arrays have been flattened.
> +@static
> +@since 3.6.1
> +**/
> +A.flatten = function(a, shallow) {


If we're unsure that there's a use case, my vote would be to leave it out for now. We can add it later, and which point we may want to consider whether it's a number (depth/level) instead of a boolean for more flexibility.

—
Reply to this email directly or view it on GitHub<https://github.com/yui/yui3/pull/214/files#r1324345>.
This is my attempt at identifying the constant here and extracting out the column identifier.
They are new constants, but before you had to enter the string in the parameters, so this is just a step towards making them integers, and also makes auto complete possible
Evernote was unable to submit your note for the following reason:
The storage limit for this account has been reached.

Original message information:
From: =?UTF-8?B?VmlrdG9yIEtsYW5nICjiiJop?= <notifications@github.com>
Delivered to: thanhbv.fa84f@m.evernote.com
All recipients: akka/akka <akka@noreply.github.com>; giabao <giabao@sandinh.net>; 
Subject: Re: [akka] Moderate restructuring of NettyTransport (#982)
Sent: Fri Dec 21 11:54:31 PST 2012

To prevent excessive emails, you may not receive another error reply
for the next 360 minutes.
trait SupervisorStrategyConfigurator extends Creator[SuvervisorStrategy] ?
references stuff from the renderer moved to a model module (references).
I don't think "Card.as" makes intuitive sense.  Could we extend the Session class and do Session.as ?
I think this should be:

    this_eval, this_evec = decompose_tensor(from_lower_triangular(this_tensor))
    dti_params[vox, :3] = this_eval
    dti_params[vox, 3:] = this_evec.ravel()
No additional copy required
Whatever you decide on the optional suggestion above be sure to apply here as well.
They could. I can't really describe why this feels better, maybe it's as superficial as the coloring in PyCharm feels right. If the performance increase was noticable enough I'd override that gut feeling, but in this case I'm going to acknowledge it's less than the perfect ideal and appease my OCD.
This is part of fix_tests, your merge must have went wrong somehow.
Why do you need these variables? m_Subtile structure is perfectly valid in GetOverlay. So you calculate this there instead.
I know this is a real sucker as I tried to abstract it as well back when I worked on EGL for android. Maybe someone else has an idea on how to properly abstract this into something platform-agnostic.
Probably yes. They mainly differ in the WHERE and GROUP clause (which is easily handled with the Filter class) and in the field read from the database and used for the label and path.
here and on the for loop below using *setattr* is required because you don't know the attribute name.
```python
if key and mins_to_expiration is not None:
```
Why `create-emr-job-flow` but `terminate-job-flow` (no `emr-`)?

I think the only sub-command that needs "emr" is `audit-emr-usage`. For all the others, EMR is either implied by something else in the name (e.g. "job flow") or the script could conceivably be made to work on other platforms too (e.g. `fetch-logs`).
Can you please catch specific exceptions here?

What happens if the job flow is already going down (e.g. due to failure) and we hit this code block?

(Sorry for the delay in re-reviewing this change.)
Put this before `JOB` so if you specify both it terminates faster.
OK removed
Ops! Falha nossa!  Valeu!
why the change here ?
I believe the previous version was more cleaner and readable
putting this in an `else` below would be slightly better
I know this was not originally your code, but since you're updating the formatting it is a good time. These braces should not be on a new line.
використовуй jQuery а не чистий JS
I'd rather use full name - `initialize`, same for the event - `$onInitialize`.
i don't think os.getcwd() is necessary here or elsewhere
I think we should be able to just delete these special cases for 0- and 1-d arrays, since it's simpler to just handle them as part of the general case?
That doesn't make sense, since both `alert` and `document` are also properties of the window object and by your reasoning should also be accessed via the `window` variable.

However, `window` is nothing more than a reference to the global object, so it is redundant.
A whitespace is needed after comma.
If think it is green because it will return `nil` instead to raise an `NoMethodError` and I think we are expecting `nil`
Just to be absolute sure, can you verify this works just importing the search implicit rather than all of them?
Hm, this is a PEP8 "whitespace around operators" violation. Should I close and send another pull request?
The test should check with [[[1,0]]]
Why don't you just add a property `.unimodular`? No complicated checks would be necessary.
I feel my concentration fading. I will pick up from here tomorrow.
Why was this changed? Is this change necessary for the tests to pass?
What is the purpose of using ``.as_coeff_Add``?
If inputs are ImmutableMatrix objects maybe we should return Immutables as well.

`return b.__class__(vect)` will work for Mutable or Immutable matrices

`return b._class__._new(vect)` will also work for objects that inherit from MatrixBase like the optics stuff

`return classof(self, b)._new(vect)` will use both self and b to determine if vect should be Immutable (or whatever other class is used).
Cool that this is so simple.
I would just remove this confusing parenthetical.
I agree with Tom: `det_LU` is probably ok unless there are lots of different things that might have the LU prefix. But even still, the keyword to det could be `det_LU` and it could call the `det_LU_decomposition` method.
Word. I'll delete it.
Are you sure about sequence for a table will be always named like that?
Here is the issue this has been discussed in: http://code.google.com/p/yii/issues/detail?id=3022
@samdark please see my last comment on the google code issue, you should add a note on this to the errata page of your book.
Wrong code style. Check https://github.com/yiisoft/yii/wiki/Core-framework-code-style
@samdark 
Indeed.
Removed them --> Travis result: http://travis-ci.org/#!/suralc/yii/builds/2134571
Sounds good.  I'll go with those.
Not always the exceptionsDirectory. Could be any of the others. Rename please.
Could you add a line return so it doesn't go over 120 characters. :)
```js
delete this._changeToSync[key]
```
this looks weird to me. ``array($id, $method)`` is *not* callable. So it does not make sense to pass it this way. You should have 2 different arguments
see 614571a84b403c6b381c21a73b25fafc78eef034
Bitte "[%s]-Tags". Ich glaube, das wäre korrekter (und außerdem konsistenter, siehe Zeile darüber).
It adds no value, please remove it.
Whats the problem with something like??
Hehe, that's why I never build in N-Triples support :-) - RDF Triples don't have any ordering. `rdf:list` is a way to compensate that. Mainly it consists of head, tail decompositions with tons of blank nodes.

The XML-Serialization is a little more clear which triples this actually induces: https://github.com/innoq/iq_rdf/blob/master/test/xml_test.rb#L104-116
This file should not be committed.

Feel free to add it to .gitignore in your next pull request.  :-)
Убери это. Загрузку иконки для places будем делать в отдельной форме.
Далее можно в UrlManager "управлять" с помощью CUrlRule видом ссылки
A good rule of thumb is "fat models, skinny controllers", i.e. put as much logic as possible into the models, and make the controllers simple.

All of this credit logic needs to go into AnswerChoice, probably using a ````before_save```` callback, e.g. ````before_save :initialize_credit````.

In general, I also recommend taking a hard look at any code that uses a temp variable.  Here you are using temp variables because these variables don't make a ton of sense in this context (weird to be messing with the guts of an answer choice in the high-level questions controller).  Putting this logic into answer choice will result in code that looks a lot simpler and that is more encapsulated.

Also, we want to avoid having a separate ````save```` call in the controller.  What happens if the update_attributes below fails and gets rolled back?  The answer choice will have been irreversibly modified.
Why are we importing org.apache.commons.logging?
These seem to be providing the exact same information.  Does something else use the movedCounts registered with the params?
We've implemented this same method 3 times now in the exact same way, is there no better option?
I feel like we've said this a number of times, and I think we should try and avoid the redundancy.
if you move it to django forms, you could just do it like 

``q = forms.CharField(label='search', widget=forms.TextInput(attrs={'placeholder': 'Search'}))``

and break like this https://github.com/ednapiranha/webtools-workermgmt/blob/python/apps/webtools/forms.py#L122
Should explain or link to an explanation of "tidied".
Hmm, I didn't realise 2^32 was so easy to brute force. Will gmp_random() solve the issue at all?
Rather than indent further description you should insert an empty line (with a *) and then add the next paragraph at the same indentation level.
`Boolean` should be lowercased, like the rest of the project.
It should be clear what this does without having to dig through language entries or so.
Make sure to keep the newline at the end of the file
btw username is not using an underscore in the phpbbs variables and database fields, maybe remove that one here aswell for consistence.
Why go through the trouble of making the list comma separated above just to split it again below?
It's not the Top History, but the scoring History. I think this could use a rename.
Ok, I’ve changed it: Messages with a category will only invoke namespaced listeners.

The event emitter itself has no special support for namespaces
I thought we agreed on using `tools.forEach` in "non-critical" code?
Another nice reusable mocking function. Can we migrate to the test harness?
FYI: recommend that constants (like timeoutLimit) are written in all uppercase (TIMEOUT_LIMIT)
Should use REGISTRATION rather than ADULT_RETURN encountertType
copied from a comment to Karan in https://github.com/Raxa/Raxa-JSS/pull/70 (#70):

"I think it might be helpful to create an enum for the different pages you can navigate to. in case the order of the pages is ever updated, then you just have to update the enum, rather than finding every instance of "setActiveItem" in the code.

CONFIRMATION_PAGE = 0;
..
BMI_PAGE = 4;

See: http://stackoverflow.com/questions/287903/enums-in-javascript . I also like the idea of capturing pages within a values object (as shown in example two), which allows you to associate a number with each page and also be able to output a string."
using a "combo" (as below with caste and occupation) seems like a more elegant way than "radiofield"
change this to 'seen'
Can you add a small docstring that tell it return True if a depend on b?
I'd strike this comment since it's a very shallow copy (isn't it?) and so, not all that unfortunate.
Also, would you look into whether insertTuple SHOULD logically accept a "const TableTuple&"? It seems like that just may be a minor mistake in the function signature?
Missing ``__future__`` imports and encoding. Use a template from another source file.
DC2, seriously?
Please leave the match in, see also basoh/riak_api#4 and #354.
Yup.

Yes, It's just not possible at this point.

Thats why most of croogo core mostly prefixed class names with the plugin name:
Extensions -> ExtensionsPluginsController (instead of just PluginsController)

Hopefully, this limitation would be resolved with croogo 2.x with cake 3.x.
This is really tricky to introduce clearly here - not sure if I have an improvement - maybe something a bit handwavy like:

Naming your URL lets you refer to it unambiguously from elsewhere in Django especially templates
Almost feels like a `Method not allowed` but I guess it isn't, more of a `Bad Request`. Problem (as usual) is returning anything other than a 404 or a 500 from deep in a Mixin - throw an error and catch it, somewhere? To be honest, I'm not that bothered about just cutting out this method all together. It would only happen on a `get` with AJAX, which you're unlikely to write and would be pretty obvious.
Those 3 lines about composer should be reduced to: `composer install --dev` because:

1. Composer is downloaded always up-to-date
2. Composer was added globally to travis-ci php instances.
Missing declarations for actual and expected?
It's an inference based on our understanding of how regular expressions are implemented. If \s matches \xA0 then \s picks up unicode characters, if not then it doesn't. It's not a check for the specific characters that we want to trim as whitespace, it's feature detection.

"Does your \s match unicode characters?"
"Yes, awesome we'll use \s"
"No, too bad, we'll enumerate the unicode characters we want to trim one at a time."
Well, prioritizing correctness over performance, I wanted to be sure not to miss any cases where the fallback is necessary. I do already know that it's not necessary for the element itself to have the negative margin http://jsfiddle.net/cEUun/2/; are you **sure** the element has to be `inline` to trigger the bug?

Checking `box.top === 0 && box.left === 0` is already an optimization, it's as far as I was sure I could go and still be guaranteed correctness.
You could call the constructor through RDF::Trine::Parser->new, yeah. We've generally been accepting of either way, though, because in some cases you don't know exactly what you'll get back from ::Parser->new, and you might need a specific implementation.

Does the part of the patch I did apply fix your problem? For more discussion (and bringing in @tobyink), I'd suggest taking this to the perlrdf mailing list (<dev@lists.perlrdf.org>).
Made some experiments, we may pay some attention to the performance issue. Please view the email for details.
yes, It is a bug. I already removed the if statement.

On May 1, 2012, at 7:06 PM, Hitoshi Harada wrote:

>> +	                SELECT segment_hashtbl.seg_text, features.label_id, features.weight 
>> +	                FROM   segment_hashtbl AS segment_hashtbl, 
>> +	                 """ + featuretbl + """ AS features,
>> +	                 """ + regextbl + """ AS regex
>> +	                WHERE  segment_hashtbl.seg_text ~ regex.pattern 
>> +	                       AND features.name||'%' ='R_' || regex.name;""")
>> +
>> +	# UnknownFeature
>> +	plpy.execute("""INSERT INTO rtbl(seg_text, label, value) 
>> +	                SELECT segment_hashtbl.seg_text, features.label_id, features.weight 
>> +	                FROM   unknown_segment_hashtbl AS segment_hashtbl, 
>> +	                 """ + featuretbl + """ AS features 
>> +	                WHERE  features.name = 'U';""")
>> +
>> +	# Wordfeature
>> +        if document_id == -1:
> 
> Why don't we want word feature in case of interactive mode?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/madlib/madlib/pull/103/files#r759164
>
I think this should probably be checked within the function getAs(), although I am not super clear whether it is or not now...
Currently I think that I'm just going to use the WS for events from the server and REST for the rest (pun intended). The comment is mostly targeted at other people considering to extend this code.
The base playback provider has been updated with sane …
Patches go at the top under the url and checksum lines so that it is easy to review them when updating to a new version. Also, the patches need a couple lines of commentary so we know what problem they fix and if that problem has been reported upstream. This helps other maintainers figure out when the patch can be removed.
Thnaks, I'll have to apply this to the python formula, too.
Seems like we are duplicating `State` here in the return value for this error case. Was that intentional? I think this clause could just return `{error, Error}` and then well add state after this clause.
I'll add some more commentary. There isn't actually a way to index `None`, so we need to stop trying to search on it. The main place we do this is the conversation listing, and fixing that requires the data migration work that hasn't been finished yet.
^Return all comments as a list.

It is not just top-level.
Já tu Dejvovu strukturu teda původně pochopil tak, že v courses budou nějaká data popisující postup pro jednotlivé kurzy (tudíž včetně toho, jak řešil jejich jednotlivé lekce) a i věci, které se do dat o jedné lekci nehodí, např. kterou lekci měl v tomto kurzu naposledy otevřenou apod.  Nemám zkušenosti s tím, jestli by placatější model nebyl výhodnější než tenhle hierarchický, což by třeba dávalo smysl (v databázi bys mohl chtít mít kolekci fakt, který nejsou nějak rigidně strukturálně propletený).

Slovníková podoba pro courses, a jejich příp. vnořené lectures, by asi víc odpovídala tomu, že se často budeme chtít podívat na data o jednom konkrétním kurzu nebo lekci. Uspořádanost toho pole asi nebudeme využívat a když už bychom chtěli kurzy nějak řadit, tak by bylo asi lepší k nim to pořadí, např. timestamp, kdy do toho kurzu vstoupili, zapsat explicitně. Unikátní klíče pro kurzy a lekce v nich budeme mít taky, jelikož je stejně budem potřebovat na jinejch místech pro naše vlastní účely.
Ah, I see. Didn't know about that feature.
How would I go about checking? I checked Requests' requirements, and they're not on this list.
Will we ever rediscover this class when we call getInjectedClasses?
Good call.  Better option.
Is maven capitalized?
code-generation --> dagger-compiler
No, the problem has nothing to do with Cookie authentication.
Here a cookie is stored on connect, then it is sent with other headers on each request.
On 12 Apr 2012, at 21:56, David Saff wrote:
>> @@ -143,7 +143,10 @@ public void testTestAndTeardownFailure() throws Exception {
>> 		Result runner= core.run(TestAndTeardownFailureTest.class);
>> 		assertEquals(1, runner.getRunCount());
>> 		assertEquals(2, runner.getFailureCount());
>> -		assertThat(runner.getFailures().toString(), both(containsString("hereAfter")).and(containsString("inTest")));
>> +		assertThat(
>> +				runner.getFailures().toString(),
>> +				CoreMatchers.<String> both(containsString("hereAfter")).and(
> 
> Ugh.  All of these explicit type parameters still make me think that the typing in hamcrest is more trouble than its worth.  What do you think?

my point exactly. That's why I use allof() instead of both()

In real life, it works most of the time and I find myself writing little helper methods that often end up improving the code. Anything with typed collections, though, is unpleasant.

S.

Steve Freeman

Winner of the Agile Alliance Gordon Pask award 2006
Book: http://www.growing-object-oriented-software.com

+44 797 179 4105
Twitter: @sf105
Higher Order Logic Limited
Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. 
Company registered in England & Wales. Number 7522677
s/rather then/rather than/
Based on your usage I'm sure you had good reason but I'm wondering if it is possible to remove this, in order to keep the interface as small as possible. i.e. you'd use `addJsonSchema` to add referenced schemas ans `validateJson` for the actual validation.

Alternative, `validateJson` could take an array of schemas as dependencies.
Of note, it's currently failing TravisCI due to the fact that the default backend is S3 and it tries to initialize without any config. We could change the default to be memory, but we'd need to make sure any deployment configuration explicitly specify the backend. 

Thoughts?
You're right—still not used to dojo magic.
This comment should probably be in the param's JSDoc instead of down here.
I still see this typo.
Looks like Raymond already verified that this fails and logged #1953.
I agree - but: 1- `complete_util` isn't actually a public API & 2- we don't have third party plugins using it yet.
So, take the chances & do one of 2 things:
1- Just remove it (plzzz do it)
2- Make it deprecated in behaviour
```javascript
exports.retrievePreceedingIdentifier = function() {
    console.error("Deprecated: 'retrievePreceedingIdentifier' - use 'retrievePrecedingIdentifier' instead"); 
    retrievePrecedingIdentifier.apply(this, arguments);
};
```
- tabEditors.getPage() always returns the active page
- $model.data is better than $doc.getNode()
I think you reverted my recent formatting changes to this comment here.
you might be able to use dimagi.utils.dates.months_between here
is this just trying to tell if any of these vars are set to a value? it's confusing in current form because you think their numerical sum matters. do ```return any(getattr(self, field) for field in ('startdate_shift', 'enddate_shift', 'fixed_datespan_days', 'fixed_datespan_months'))```
Not same.
!string.IsNullOrEmpty(loginResponse) is preferred here
Rename A to A1
Ok I removed them for now.
What arrays?
Make sure these other var declarations line up with the first variable (not at the beginning of the line).
else should be on the line above `} else {`
Personally, I'd prefer to have a single set of warnings that we follow, rather than being able to override it somehow. so this would just be `var warnings = [`, and the checkCSS function signature above would change.
This breaks the future chaining. If converting to `Future[Void]`, prefer `myFuture.voided`
Fair enough =).  Fixed on 93b2c3a.
Yes! Page size by default is set to 25 but 26 results were always showing as first page. I have always been annoyed by that and decided to sneak in a fix. :)
Incorporated! THanks.
Nope :( because of important - apparently this is a SASS issue - can't do `include thing() !important`
I enabled spelling in vim and catched another one, thanks!
In my opinion, these two make it easier to work with big integers.
Eventually, you're the boss, thus, it's your call.
that should be http://homescreen.gaiamobile.org/
I guess I do, but I never write any software that doesn't meet those criteria...
This can also be of type `repair`
Same as above. The majority of the code in this function `handle_check_return({down, Check}, ...)` was copy/pasted from `handle_call({service_down, Id}, ...)`. Would be better to refactor out the common logic in both functions into a new internal function and reuse in both places.
Seems better suited, yes.
Why? It's a new file, so let's use a new object. There's no need to be conservative with variable usage, better be explicit, for example `info_gpg` and `info_gitian`.
@jgarzik I'm only replying to Luke's suggestion to have the locking functionality inside COutPoint. That would be a bad idea.

No objection to having a method on a wallet to lock a certain output.
Yes a cmake or autotools build system would be great. Feel free to contribute that instead :)
hmm, shouldn't that be `mul`?
not really, before commas there are also no spaces.
Should the handler be renamed to applyStateOnChangebaselayer?
Yes let's do that.
please move logic out of the constructor into another method. Constructors are only about assignments.
maybe `dismiss_help_text_path`
I'm not sure if this will be sufficient, but I was thinking about making type an array. So in the xml driver, it would probably be something like

<types>
<type name="my_article_class" />
<type name="my_other_article_class" />
</types>

but that depends a bit on how much configuration the child types need (e.g. I think you can define a minimum and maximum number of children, but I don't know if that's per type or for the entire collection)


On a non-related note, could we shorten this particular code to look like this:

```php
            if ($c instanceof CollectionDefinitionInterface) {
                if (!isset($child['type'])) {
                    throw new RuntimeException('Type attribute must be set in the definition type XML file');
                }
                $c->setTypeName((string) $child['type']);
            }
```

Purely aesthetical, I know, but still :-)
Use IdList and special method join.
Let's remove the console.log before merging.
Any particular reason to not follow the naming pattern for test files of having them all be called `test_*`?  I know nose will recognize this as well, but since we already have a pattern for those filenames, I think it would be best to follow it.  That makes it easier to know that all files *not* named `test_X.py` are simply auxiliary tools for the test suite.
Yes, I will change that one to match.

-MinRK

On Jul 27, 2012, at 17:28, "Brian E. Granger"<reply@reply.github.com> wrote:

>> @@ -360,7 +360,19 @@ var IPython = (function (IPython) {
>>         container.hide();
>>         // If the Javascript appends content to `element` that should be drawn, then
>>         // it must also call `container.show()`.
>> -        eval(js);
>> +        try {
>> +            eval(js);
>> +        } catch(err) {
>> +            console.log('Error in Javascript!');
>> +            console.log(err);
>> +            container.show();
>> +            element.append($('<div/>')
>> +                .html("Error in Javascript !<br/>"+
>> +                    err.toString()+
>> +                    '<br/>See your browser Javascript console for more details.')
>> +                .attr('style','color:darkred')
> 
> Seems like `render-error` in the other branch should be called `js-error`.  Aren't they really the same thing?  
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/ipython/ipython/pull/2199/files#r1257667
Fixed with #924.
Sorry - I forgot about that comment as well. Of course, ignore it.

I was thinking about how to incorporate some of Fox and Weiner's astophysics-independent parameterization into pyWIMP: http://mnd.ly/ziShed

yes, maybe create a halo class that just gets plugged in directly. 

On 14 Mar 2012 (11) [74], at 10:07, Michael Marino wrote:

>>         self.v_sub_esc = ROOT.RooRealVar("v_sub_esc", \
>> -                  "Escape Velocity", 600, "km s^-1") 
>> +                  "Escape Velocity", 544, "km s^-1") 
> 
> There should be an interface added to change these values, since experiments tend to use difference values (even though they shouldn't)
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/mgmarino/pyWIMP/pull/1/files#r556228
The "#main-content .intro" element has a margin-left of 0 that is pulling the rest of the page off of the grid in the full desktop size.
Could we do this in the js/global.js?
typo: permanent not perminant
I have it returning so that the `invoke` method inside `RestAdapter` sees that all paths either return or throw. If we switch these convenience methods to throw there will have to be a `throw new AssertionError();` or something at the end of that method.
@stof It was odd to write something like `'/([^\\'.self::LG_CHAR_ESCAPING.']?)</is'`.
@fabop Okay, I just remove it.
The phpdoc is missing
No this fails under 5.3 And works as expected under 5.4. I'm running on 5.4 and thus didn't catch it. I've seen the reports from travis a couple of hours ago and I plan to extract this into helper method... But I really can't find the proper name for it.
... will use os.path.join()
Can you add a patch_minor: here, that's breaking the build.
Why do we have two identical nav templates?
Wow - weird. @kaishin - is this convention? I would guess consistency would be preferred but curious to hear designer's perspective.
Bang method here? I would want an exception if I couldn't find the event.
We had trouble with this before -- the normalization is done very carefully with a divide and not multiplying by the inverse to guarantee that the returned values are within the range that they had in the texture. Without that they could become slightly above or below 1.0 (which is problematic for alpha channels).

I would keep this one and nuke the other.
This sentence doesn't parse, but I've fixed it in PR126 which changes the caching.
This makes me uncomfortable. I can see why you've done it, but is definitely not the "correct" long term solution. Maybe make that clear and link to a ticket which should remove this?
Hahaha, awesome :). Not necessary, you're probably right!
Oh, you put them there. Duh. I checked the existing source, and saw they weren't there. ;)

Really, I'd prefer that `draper.rb` just require all the other files, and we put everything else in other files. Not sure what that one should be named, though.
I also tried :-1:
I would be more comfortable if this was done with one SQL query instead of updating each and every tag, as potentially, the tree to hide/unhide can be huge.
I'd use `click_link` etc instead of `visit` here. It is in a `Given`, but visiting anything besides `root_path` indicates that users might be unable to use your site the way they should.
Even though you might find this style of keyword passing more readable, it's not in accordance with PEP8 (http://www.python.org/dev/peps/pep-0008/):

    Don't use spaces around the = sign when used to indicate a keyword argument or a default parameter value.
    
    Yes:
    
    def complex(real, imag=0.0):
        return magic(r=real, i=imag)

    No:

    def complex(real, imag = 0.0):
        return magic(r = real, i = imag)
I won't hold up merging for this, but I think we shouldn't make this method abstract. I'm thinking it should have a default implementation that throws an UnsupportedOperationException.

That's ugly, but the large number of subclasses you had to modify tells me this change will likely break subclasses in subsystems outside the AS code base.

Any such subclass must have implemented the old marshallAsElement variant that is no longer abstract, and their implementation will still execute. So my proposed default impl of this method won't be executed.
This looks like something that should be done using the StartContext.asynchronous() API.
OK.  Noted
It should, but even before that, we need to stop using `.disableSelection()` inside dialog.
Nevermind, you're right. It just seemed like this test was redundant given the other test, but it can't hurt. Have you also considered one test with reversing the calls to draggable() and sortable()?
I get the same when I return ``response.children`` directly.

zkCli:

```
[zk: localhost:2181(CONNECTED) 60] ls /a/b/c/d
[f, g, e]
[zk: localhost:2181(CONNECTED) 61] ls /a/b/c/d/f
[h, i]
```

Get children method:

```python
    def get_children(self, path, watch=False):
        request = GetChildren2Request(_prefix_root(self.chroot, path), watch)
        response = GetChildren2Response(None, None)
        self._call(request, response)
        return response.children, response.stat
```

Test:

```python
    for chroot, paths in [
            ("/", ("/a/b/c/d", "/a/b/c/d/f")),
            ("/a/b/c/d", ("/", "/f")),
            ]:
        z = zookeeper.allocate("localhost" + chroot)
        for path in paths:
            children, stat = z.get_children(path)
            pprint.pprint({
                "chroot": chroot,
                "path": path,
                "children": children,
                })
        z.close()
```

Test output:
```python
{'children': ['f', 'g', 'e'], 'chroot': '/', 'path': '/a/b/c/d'}
{'children': ['h', 'i'], 'chroot': '/', 'path': '/a/b/c/d/f'}
{'children': ['f', 'g', 'e'], 'chroot': '/a/b/c/d', 'path': '/'}
{'children': ['h', 'i'], 'chroot': '/a/b/c/d', 'path': '/f'}
```
Can you use a data-l10n-id here in order to convert Browser OS t o Firefox OS when this is an official build ?
Sorry, this should remain `typeToHandle`
`md_alert`
Thanks for your reminding. It will be ready tomorrow along side a simple dictionary without license issue.
Ok, I prefer to ensure this write `thing === undefined` instead of `typeof thing === 'undefined'`
can we simplify here the logic for returning the boolean value?
Let's ask Alive if that's fine then.
We use `id-like-this` in `system/index.html`
Should this be select or radio buttons? Is there a spec for reference?
Just to be safe, I think this function itself should implement the `or` check. It will need to create another scope and ugly (I know!) but I want to be future-proof.
Hawkeye!
1) Enter in home (English for example)
2) Settings -> Spanish

navigator.language -> en_US
document.documentElement.lang -> es

3) Settings -> English

navigator.language -> es
document.documentElement.lang -> en_US

It's look like a step behind :)
Please note that MB, GB would also need to be localized here.
Yep I think it's too heavy. Lets move it to the FunctionalTests project.
And now that you mention it, I'm not sure what the right pending policy is here. These are features that are nice to have but may never be implemented. Do we want to clutter the test output with permanent pendings?
I don't think `profile` would solve the "doesn't sound like a number" problem. Also, it already exists as `profile_examples`, so it would have to be deprecated.
I still don't see justification to do this in the current change set. `ProcTypes` are still bound to `Apps`.
装飾ずれ **
`didPersistRecord` instead of `didDefineId` ?
Like this change.
doc string ? </joke>
I want to leave it not set so that I could add automatic setting of zIndex for layers that don't have it explicitly set in future (maybe in order they're added to the map).
We probably can by declaring a variable as QMessageBox() in the talkeditor and then using that to setup the dialog box. Haven't tried it though so I don't know for sure.
I think we'd better use KunenaForumCategoryUser object than direct query (better caching). See KunenaForumCategory::subscribe()

I would also rename function to getSubsribed() because of we're not in user object.
So, the equation in line 382 includes contributions #2 and #3 from Reach et al. (2005). It doesn't include #1 which is the uncertainty in the background level. This is because background subtraction is not part of `aperture_photometry()`, and the uncertainty in the background will of course depend on how you calculate it (globally vs locally, and if local, depends on size of annulus you use). It's a complicated business because depending on how you do it, the statistical uncertainty in the background might be negligible, but there might be significant systematic uncertainty. (For example, a constant global background would have negligible statistical uncertainty but significant systematic uncertainty from the fact that you're not capturing positional dependence in the background.

Not sure in this context what you mean by uncertainty on the pixel values (as I mentioned above). can you try to explain?
Python does not accept yield d, as it comes with the message:
     Failure: exceptions.TypeError: Yield waitForDeferred(d), not d
The commented-out version is closer to correct, though - this needs to fetch the version from the properties.  The test on line 93 needs to be updated, too, right?
@Baachi there is simply no other source type supported in composer currently anyway (and the installation is forced from source)
This line here cancels the activations of rule2-modify and rule3-modify
en effet, merci, je dormirai moins con (un peu) ce soir
Idiomatic ruby would probably look like:
```ruby
case provider['args']
when Array
  # ...
when Hash
  # ...
default
 # ...
end
```
The same comments as for `tun_recver.c` above apply, except when they were specific to `tun`.  I don't think you're measuring what you think you're measuring (what do you think you're measuring???).  `rlimit` stuff needs to be added (as in `cos_loader.c`).  ...etc...
Please do not change code indentation, the diff is completely f*cked after that and so hard to review. Thanks!
Watch are our chances of getting this incorporated directly into the `Front` object without looking too messy?
It seems that casting should work but I had notices because of that. Not sure why
You are right... I was experimenting... so I take the css from 
html-blogger to get if I can read well the css from reveal.
My plans are to change the code and get it from IPython dir, as you 
mention before.
I will do the changes soon.
I don't really object to using `nsICommandLineHandler` it was just unclear why, maybe you could put your comment above as a comment somewhere so it's clear for people wondering.
Warning, override overflow! What is the point of `override({}, globals)`?
Can't we replace it with just `globals`?
It's reliable for desktop as the linkedPanel property always returns a string 'panel1234567' for example. There would need to be a test written to ensure that the platform continues to produce that string format as the property.

I do this string manipulation out for aesthetic reasons, it looks wrong for something like 'tab.id' to have a value 'panel1234' - panels are something completely different in the SDK and we don't want to confuse people.

I think I have three action items here:

1. write a test that will fail if the value of tab.linkedPanel changes
2. investigate a cleaner way to re-format the linkedPanel value
3. do some tests on fennec to see what their tab.id looks like
the route `/signup` was removed with your other PR.
Here's where I often make numdays optional, but days_ago required.  If numdays is omitted, the get_day_range method will just return from days_ago to present (ditto from other comment for the pushlog model).  But if you require numdays, you may want to require days_ago, too.
I was able to remove all this junk. Not sure why I had to add them before.
Oops, you're right. I had intended to change this along with the this.lengths but it slipped my mind. Thanks
closing parenthesis missing
as what I trying yesterday, it may not run using DOCUMENT_ROOT. So I just remove that and it running well
You may find the [FakeFS](http://rubygems.org/gems/fakefs) gem useful for some of these kinds of things.
@Evan-Pierce This line can change to
```
 ... = [ "/test1", "/test2"].join File::PATH_SEPARATOR
```

That should help get you started.
All you require is `WRITE_DAC` on the target file, which I understand that full control provides.  (I infer this from the examples of how to ignore the missing capability for setting ACLs. :)

Unless one of the "ignore merge errors" or "ignore ACL errors" options is given, being unable to effect that change should result in a failure anyhow, which should abort the replacement entirely.

I think that is the most correct platform behaviour - delay until reboot isn't sustainable, and ignoring a failure like that feels wrong to me.  I would rather abort because of a missing `WRITE_DAC` capability than carry on.
@zaphod42 btw, the cert signing code was recently updated to set the `not_before` to be 24 hours from "now":

<pre>
cert.not_before = Time.now - (60*60*24)
</pre>

Along the same lines, should the crl revoked time be one second in the past?
Thanks for the feedback. I think it was pretty confusing that this first overview didn't mention INSTALLED_BACKENDS and wasn't always explicit about using HTTP.

I'm open to any other ideas that might help (or anything that is just incorrect).
Even though it doesn't look too pretty, this is possible a better way to do it:

```ruby
def check_main_page
  Page.where( :main_page => true ).find_each( :batch_size => 100 ) do |page|
    page.update_attributes :main_page => false
  end

  self.main_page = true
end
```

I'd like to not assume that only one `main_page` exists.
This last check is unnecessary: un-rescued exceptions will be propogated anyway.
CS dictates moving the closing paren to the same line as the opening brace in these situations, and only one level of indentation for the arguments:
```php
public function __invoke(
    array $matchAgainst = null,
    $returnDefault = true,
    & $resultReference = null
) {
```
I'm againts of set a specific schema by default
:-)  It is....  I couldn't think of another way to detect if the $value was already encoded or not.  Doing this will make it so the $value isn't encoded twice.
So what do we do about that bug?
No, its not fixed. The problem are the <para> tags inside of <example> tag
and why not simply using ``title``, which works for tipsy out of the box (without the need to pass a special option for this) and fallbacks to native tooltips when JS is disabled ?
Remove the value attribute
does that trim of tabs etc?
I found such due date functionality in the canjs/*-widget examples,
appatently to demonstrate canjs's widget binding functionalities.

I know that these don't exactly match the TodoMVC specs. As such all of the
CanJS widget samples should be removed. But since in this pull request I
simply upgradet the style I didn't do that (also 'cause I've not written
those sample implementations)
On Oct 29, 2012 11:35 PM, "Sindre Sorhus" <notifications@github.com> wrote:

> In labs/architecture-examples/canjs/dojo-widget/todo.css:
>
> > +#todo-list li .due-date {
> > +  display: none;
> > +  position: absolute;
> > +  top: 0;
> > +  right: 10px;
> > +  bottom: 0;
> > +  width: 40px;
> > +  height: 40px;
> > +  margin: auto 0;
> > +  font-size: 22px;
> > +  color: #a88a8a;
> > +  -webkit-transition: all 0.2s;
> > +  -moz-transition: all 0.2s;
> > +  -ms-transition: all 0.2s;
> > +  -o-transition: all 0.2s;
> > +  transition: all 0.2s;
> >  }
>
> Where is this used? We don't have any due date in our app spec.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/addyosmani/todomvc/pull/312/files#r1973027>.
>
>
I am a little confused by this comment. Consider expanding it or dropping and adding a more details explanation to the Search class definition.
this shouldn't exist. Either I propose to rework the StaticDocument object and having a View object able to raise an exception and/or accept/ignore unknown property of an object. So the Static Document would become something like:

    class StaticDocument(Document):

        def view(self, ..):
             return View(db, dynamic_property=True)


Same for other methods. And we remove everywehere this ugly class parameter. Thoughts?
i like to write this type of thing as 365 * 5 so it's more clear what it's representing
docstring doesn't make sense, should use `pass` with empty configure
Well, seems like only Firefox has that bug.  The movement is 0 for non-mousemove events in Chrome at least (which is the only other one implementing pointer lock.)

Note that this is a work-around for a Firefox bug, which I hope to take out once the Firefox bug is fixed.
Same as above: 
Add a space between the first '>' and '.row' for readability
What's with all the safe filters? We patch our form libraries to do that I thought? Having to `|safe` a bunch of stuff is pretty annoying too.
Pep8 says yes to the number of newlines.
Spaces between the fonts would be prettier.
Is this meant only to be used on registration? Notice that the widget is being overridden here: https://github.com/davidw93/mozillians/blob/be352e8d95a03244c5fab32767891349f4c4b5a3/apps/phonebook/forms.py#L123
Instead of doing this you should create the user you are going to search for in this test using the method you created.
Here ^
value origin is the used matcher, we can rename the method if you think used_matcher  is better.
Should be ```if (metadata.length) {```, no?
Double position declarations - relative and then absolute.
question should usually be a `<p>` so it gets bolded
Use color in the formula.  Also, I'd be tempted to have 1/2 bh instead of bh/2, but either should work
Missing phpdoc (all new or changed function signatures should add phpdoc)
Why do we need to override the method?
asdfasdfadsfasdfasdf
"icons" Also, write what I am allowed to put in there.
We can probably use a more descriptive name for `keys`
I keep track of the original value to avoid having to render the template again.
Oh, right, I got confused. Sorry for the noise.
can we do this in a more generic way? e.g. make sure of templates - it would be good to allow easy changes to this
just `$this->kernel->getContainer()->get...`
понял, спасибо
Про метод initialize класса NSObject:
https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSObject_Class/Reference/Reference.html#//apple_ref/occ/clm/NSObject/initialize

Про static (и extern):
http://www.rsdn.ru/forum/cpp/2706624.1

Общий смысл таков:
1) + (void) initialize - это метод класса, а не объекта класса, и он будет вызван только однажды (до того, как вы пошлете классу Cell первое сообщение).
2) Статическая переменная создается в только однажды.
@slebedev 
Да и тут кстати помогла бы парадигма TDD 
сначала тесты потом реализация
If you check out what transmission does, they in fact, do set it to use beta updates as the default on beta builds.

This sort of thing is too specific to be a good candidate to go into autorevision its self; this is exactly the sort of thing that scripts driving autorevision should be doing, though it may be a good idea to add a number of examples of such scripts for people to work off of.
This is mostly pedantic, but %whitebox already includes clearfix, so you can kill this line if you want
I'm using backticks for parameter names. I'm not using them for anything our hypothetical TomDoc parser would recognize as a class (`RACDisposable`) or method name.
> Just to make sure we're both on the same page, `-repeat` has two issues:
>
> 1. The disposable isn't returned before the repeat happens.
> 2. The potential for stack overflow.
>
> `+iterativeScheduler` was meant to solve (2), while `+deferredScheduler` was meant to solve (1). It's totally possible that doesn't solve the problem but I'd be curious to hear why.

`+deferredScheduler` suffers from the same "current scheduler" problem I described above, and (as mentioned in my commit message) can allow code to execute _concurrently_ instead of deferred, which means You're Gonna Have a Bad Time.

But, in addition to that, I guess I just assumed we would want the first subscription to happen as soon as possible, instead of waiting a run loop (a la `+subscriptionScheduler`). If that's not the case, then I can refactor this to use more deferred-like semantics. I would question when you would want `+iterativeScheduler` and _not_ a deferred scheduling, though.
He did mention he still had to move some methods from `RACSequence` and `RACSubscribable` to `RACStream`.
`mod`跟`rem`的实现反了吧？
BTW, thanks to @ethomson, we may have a `GIT_EUNMERGED` error code [in the pipe](https://github.com/libgit2/libgit2/pull/1013).
nope, for once atleast_2d does the right thing :)