labofsahil/github-event-dataset-2012 huggingface dataset:
Now really, what conventions do you refer to?
We should be sending back a valid JSON string -- `errorString` is invalid JSON because "Invalid Assertion: " is being stuck on the front of it in line 72. The string concatenation should happen in the warning and the `errorString` should be the raw result of `JSON.stringify(err)`.

Also, stylewise, there should be a space between the `,` and `400`.
You don't have to use `.has` -- in js, `undefined` is returned if you access a key that doesn't exist. You can just do

```js
if (totalPerIssuer[issuerName]) { ...
```
pluginFn just handles _natives and defaulting it, then calls addTrackEvent. Just resets references.

Although testing it some more never hurts.
I think I got it with my last commit.  Match up to you?
Disregard this part, it's dead code. Sorry for including it in the pull request.
The indentation and logic here is messed up, looks like?
This clarifying note should go under the input, like the paragraph about valuing input from above. It can be classed with footnote or not.
the :cake: doesn't mean anything, btw
Perhaps leaving out auto_resolve to make the definition a bit simpler?
Can you raise that as an issue separately?

This is a pull request for a new test and your comment is nothing to do with @yurenju 's code. 

The framework was built by james Lal and a-team and is 'branched' directly from the gaia repo so at the moment we're trying to keep them similar.
I think you want square brackets here instead of parens?
Even though your assertHttpStatus metod is useful and nice, I still prefer to read tests with assertThat(something, is(Matcher))
Not yet implemented.
And this will try to read deleted key. 

So it would be an exception.

Even if this is not exception, then if running_jobs == 0 then key was deleted and we have no value here.
No need for the backquotes as you're not using the result. Just `sh "guignol stop ..."`

Plus, after stopping slaves, your should double'check the queue and unlock any jobs locked by the slave.
(Otherwise there's a possible race condition)
I'd probably have went with

```js
Modernizr.prefixed('requestPointerLock', window)
```

But it doesnt seem to matter much. Spec likes both. http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html
Can you remove the `WithoutOptions` because with or without options, the result is the same.
начало чего?
yep. damn autocorrection™
are we sure here that $item is a node and not a property?
Many  developers are certainly encouraging the switch to the new syntax, but I don't agree with it. 
The points for switching that I've seen seem to be centered around:

1. Hash formatting that is consistent with other languages, especially JSON
2. Better code readability, with less whitespace

I disagree with this, as I find switching between Javascript (coffeescript) and Ruby is adequately different that I find that the different hash structure actually makes things much easier when switching between the two. While I would agree that it makes things more readable, I also find that with no particular performance benefits, and the inability to use anything other than a symbol as a hash key using the new syntax, the hashrocket method is much more useful for me.
ok, merging! good bye erb
Our connection-pooling library has functionality to log all queries that go through it, and provisions to only do that for queries that take longer than N millis. That might be a more central spot to put this kind of logging.

Also, we can just disable that logging in the log4j configs if we don't want people to see it by default.

See `make-connection-pool` later in this namespace.
Could be, http://php.net/manual/en/language.namespaces.basics.php I really don't know. I can't try it with a previous PHP Version
Haha. You're fine to merge in. We'll fix it when a fix is available. I haven't been able to test requests-oauth dev branch and requests doesn't have OAuth technically built in all the way. So yeah. Fine for the initial merge. :)

Sent from my iPhone

On Mar 15, 2012, at 7:11 PM, Ryan McGrath<reply@reply.github.com> wrote:

>> @@ -448,10 +439,35 @@ def updateStatusWithMedia(self, file_, version=1, **params):
>>         """
>>         return self._media_update('https://upload.twitter.com/%d/statuses/update_with_media.json' % version, {'media': (file_, open(file_, 'rb'))}, **params)
>> 
>> -    def _media_update(self, url, file_, params={}):
>> +    def _media_update(self, url, file_, params=None):
>> +        params = params or {}
>> +
>> +        '''
>> +        ***
>> +        Techincally, this code will work one day. :P
> 
> Heh, was the goal to have this working for merge-in? Seems like it's fine to me, but this message makes me want to ask to be sure...
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/ryanmcgrath/twython/pull/65/files#r566228
Line 19 checks if there was a row in the Principals CF with the group_id as key. I rather not create a group object from an empty row. Line 24 can be changed as you said.
I thought # was fine because it was performing a different function than the : separator.

: separates a string into different data parts
# is denoting a property of the sectionName, which is in line with how an anchor works on the web, for example

For example, if we needed to structure user profile schema differently for some reason, a column name could look like this:

u:cam:mrvisser#visibility
You can remove this unused require.
Should capitalize the first letter of cassandra here
It's in the comment. I know, it's recursive :)
You need to sanitize this in order to avoid path injections like these:

    /%2Fetc%2Fshadow
    /../example
... except people that want to directly access the segments array.
That's really not what I meant. `microtime(TRUE)` returns a float with the sum of your originally exploded values, it is used like this:

    $time_start = microtime(TRUE);

    // Do stuff

    $time_end = microtime(TRUE);

    $time_total = $time_end - $time_start;
Рад помочь ))
Как я понял ни здесь, ни в randNucleotide не проверяется, была ли произведена замена символа на другой символ. Т.е. возможна ситуация, когда 'A' заменяется на 'A'.
Чтобы не инициализировать переменную x единицей, можно сделать не цикл while(), а цикл do {} while(), который пройдёт как минимум один раз.
@crmaxx и ещё раз - заменяя "А" на "А" в данном алгоритме, взятом из контекста, вы заменяете, да. Но вне контекста, в плане результата - вы не заменили. Всё равно, что вы принесёте вещь на пошив, скажете, чтобы "вот эту рюшечку перешили как-нибудь, ну, на ваш вкус", а вам в результате дадут честно перешитую рюшечку, но только точь-в-точь, как была, вы будете возмущаться, а портной вас не поймёт - он свою работу выполнил, перешил так, как ему понравилось, а ему понравится могло что угодно, как в данном случае - старый пошив. Ну это если образно выражаться, я думаю, суть ясна.
Plus, if I were authed and wanted to DDoS, there are harder things for our severs to do than report a 500.
The mac build script has the same lookups. Ideally, yes, we should be looking inside a "repository" group, but that would add a bunch more complexity, and ideally would be done with a scanner instead of regular expressions.  It should also be done for both mac and win. I guess that is a long-winded way of saying we should keep it agile and fix it if a problem arises. Sound okay?
the default value is also needed here
This clause is failing for me :(  Will check it out...
oh.. i get it
+ 1

On 26.12.2012, at 14:26, Eric89GXL <notifications@github.com> wrote:

> In doc/source/python_reference.rst:
> 
> > +Projections:
> > +
> > +.. currentmodule:: mne
> > +
> > +.. autosummary::
> > +   :toctree: generated/
> > +   :template: function.rst
> > +
> > +   compute_proj_epochs
> > +   compute_proj_evoked
> > +   compute_proj_raw
> > +   read_proj
> > +   transform_coordinates
> > +   write_proj
> > +
> > +:py:mod:`mne.preprocessing`:
> How about updating the module's lackluster docstring to be: Preprocessing with SSP, artifact detection, and ICA. Then you can delete the admittedly somewhat confusing intermediate heading. I don't think they need to be separate anyway...
> 
> —
> Reply to this email directly or view it on GitHub.
>
sorry, copied from terminal... not a good idea :-(


On Thu, Dec 13, 2012 at 9:18 PM, Alexandre Gramfort <
notifications@github.com> wrote:

> In mne/viz.py:
>
> > @@ -51,6 +52,31 @@ def _clean_names(names):
> >      return [n.replace(' ', '') if ' ' in n else n for n in names]
> >
> >
> > +def tight_layout(pad=1.2, h_pad=None, w_pad=None):
> > +    """
> > +    Adjust subplot parameters to give specified padding.
> > +
> > +    Parameters:
> > +
> > +    pad : float
> > +        padding between the figure edge and the edges of subplots, as a fraction of the font-size.
> > +    h_pad, w_pad : float
> > +        padding (height/width) between edges of adjacent subplots.
> > +        Defaults to `pad_inches`.
>
> please be more careful with your docstrings (line too long + missing ----
> below parameters + Adjust ... not on the same line as """)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mne-tools/mne-python/pull/262/files#r2412968>.
>
>
> However, it just occurred to me that we can actually extend the
> functionality of the new raw() to deal with each raw instance having
> different projectors, in which case we wouldn't need this code to maintain
> backward compatibility.

that's my feeling too.

> Specifically, if raw1_fname and raw_2fname have different projectors proj1
> and proj2, in raw=Raw([raw1_fname, raw2_fname]) what we could do is make it
> so that raw.info['projs']=[], and apply proj1 to raw1_fname and proj2 to
> raw2_fname whenever their data are accessed (i.e., on preload or in
> read_raw_segment).

exactly. Now that we can project in Raw it's possible.

>  It's not the most glorious solution, but then again
> including different projectors for different runs isn't that glorious. I
> think this would still function the same way as the C code, since you could
> still specify cov.save(projs=proj1) and epochs.average(projs=proj1)---not
> that this should matter much, since the projectors have already been applied
> to the data themselves.

it's not even clear why we would need this. Epochs with epochs.proj = True will
able the projector in epochs.info['projs']

> We could even throw a warning to the user when (not
> proj1 == proj2) so that they know this is happening, and it's only safe if
> you're really sure you know what you're doing. How do you think on it?

+1

how do you want to play it? close this PR and add the relevant pieces
to the other
PR on multiple raws ?
there is already a page about the HTTP cache in the book so you should avoid duplicating things in the component. IMO it should be moved to the component doc but it should probably be a separate page, and the current doc is far more complete
@richardmiller why a cookbook ? It should go in the component doc IMO
This should be:

    // fetch a user of type Acme\Entity\LegacyUser
    $user = ...;
以毫秒的精度保留服务器的响应时间，（输出）单位是秒。
Use pattern matching like the above examples
This is asynchronous
Don't put code in docs, look at the other Akka docs for how to include compiled&tested code into the docs.
read the package names :)
No but seriously I was learning package visibility rules for scala when I moved it there and I didn't realise hierarchies apply so we could do private[camel]
use for-comprehension
It is, as the loop is mutating an object from line 122. If the module is not found, I delete it, warn and continue.
@ninfaj same here
Como estaba antes, si había un error daba acceso.

También podría hacer que si hay un error no se de acceso, pero prefiero que salte un error a que ocurra sin que nadie se entere.
Yeah they make us 9-5 suckers look bad too. Weblibrity brogrammers. Pffft.
C habits die hard :)
Check it: http://rubyfiddle.com/riddles/98466
Instead of using strings to indicate True/False, you should use pythons representation. Here you would write found=False so that later on your conditional would be 'if found:'
Yay ternary!
Limechat is popular too http://limechat.net/mac/
I do not see the copy_uploaded_to_lazaret method anywhere ... missing in commit ?
Please remove this outdated class header
Please don't use any of the regex-based methods of the String class. Many developers are not aware of those regex parameters, leading to confusion and bugs (besides the fact, that String.split() also has some very surprising corner cases). You want to use StringUtils instead: http://commons.apache.org/lang/api-2.5/org/apache/commons/lang/StringUtils.html#split(java.lang.String)
We will bump the version in master once this is merged, could you please rollback the version changes?
No, you're very much correct. The problem's with the persisted_models function thrown to the mappers above; with the management API framework in place and a little discussion, I'd love to excise this and put it where it belongs.
I can see the point of what you're doing, but given that this test is functional (not stress), it could potentially fail with the paralell testsuite, and I'm not sure your console printouts will appear... The right approach here is probably to print both to console and the log, that way you have both bases covered. I'm not hugely fuzzed about this, but just pointing out that when the test fails in  a random testsuite run, having all log information logged using our logging infrastructure helps debugging.

I'll handle the pull request as is, but bear this in mind.
20 is reused through in 3 places, would be nicer to have it as a constant, e.g. CANCELATION_CHECK_FREQUENCY
Hey, I just discovered MurmurHash3 is externalizable!
Instead of the `display: none`, you can use the `hide` CSS class
Yeah dude, super annoying on your side. It's just a suggestion. For me I just try to avoid pushing workaround code to the repo. If everyone pushed workaround code, the repo would have all this random stuff commented out. I've seen it happen, and it leads to subtle bugs and unexpected behavior. I may or may not be guilty of doing that myself. :)
The main critique is that it's just text, it's not actually executable.
Could you specify why this or what could go wrong?
I'd rather not pollute the index.css with noscript
@arnodeclercq 

* space between `if` and `(`
* use 3 `=` instead of 2
Same note as above:

`<Import-Package>*</Import-Package>` is the default behavior, so you can remove this line completely.
It seems more idiomatic, given the precedent of conventions like [Backbone.View.$el](http://documentcloud.github.com/backbone/#View-$el), to call this `$lastToggle` instead of `jToggle`.
That's not left on purpose right ? :)
I think we should use the multiline lua comment. thoughts?
It has to treat each format slightly differently, since different commands are used to uncompress each format, and each format does so slightly differently.
Should the type for parameter ``$cookie`` not be "CHttpCookie|null" instead of "CHttpCookie"?
I am thinking that fit_path should be False in LassoLars as you only want one value of alpha. Maybe fit_path is not necessary at all for LassoLars and Lars

wdyt?
The `if` statement is no longer needed here since we're not actually using `$`.  Also, there is a missing semicolon after the function declaration.
Removed, wasn't sure if it was more efficient to store the context alongside the callback so it was only present in the inner function.
Yes, utilizing java.util.logging instead, which claims "All methods on Logger are multi-thread safe."
I think we should use foreach($attachment $key => $file) instead of the for loop and document that $attachment and $name have to have the same keys. This way the keys don't have to be numerical and without gaps.
"The defer and async attributes must not be specified if the src attribute is not present." (http://www.w3.org/TR/html5/the-script-element.html#the-script-element)
`rebar_utils:is_arch/1` will return `true` or `false` instead of `match` or `nomatch`.
I guess we're not actually using it so any updates should be fine :)
The size should probably be an attribute somewhere, rather than hard-coded like this (and that was true of the old code as well).  Also, you've changed the size (375x295 -> 375x395).  Was that intentional?
Okay.  I'll look for/write a template tag which fixes the URL so it's always absolute.
To be honest, I only included it because I remembered it from Paul Graham's Lisp book. I agree it's a less "useful" exercise than the others, so I wouldn't be opposed to just removing it. :-)
Please add a comment indicating that class is only non-abstract to make Ant's JUnit test runner happy.
You shouldn't need this, since you have the `<=>` method below.
This code is quite similar. Can you somehow de-duplicate it?
No, iterate over `number` values. There might me some number missing.
yes i did it in virtualenv.

here are some logs when i run install..
pip install -r requirements.txt  -->  http://pastebin.com/Tf2qdMrV
pip install --upgrade -r requirements.txt --> http://www.sendspace.com/file/ghii7i

python = 2.7.3

as i talked to others, it also doesn't work for them
Rename to `location`.
So `number` values from fetched data.
Yeah, I told igypigi to fix it(since he wrote most of it, he should fix it).
You are doing only `GET` on this resource. Maybe you should limit only that GET should be allowed?
It is only shown if they created it. However, it's a link to a standard GET request. Any user could manually type in /dashboard/announcement/edit/?id=ANY_ID_FOR_ANYONE and go there. I'm adding security so that if someone gets a malformed URL or maliciously tries to edit it they can't.
Is there no way to case this for 2.2 and 4.0 as well?
Kann man auch Abbrechen?
I agree that it's probably not the best test. I wanted to make sure I covered the changes I made. I don't any experience with cucumber or I would add to the feature.
could you close the method at newline, and add a comment like //Nothing to do
?
That better highlights this is intentional.
remove the connect write block, we already know we could write
It's a nitpick, but please insert a newline above the start of the list to be consistent (and the same for the "Features" bit below)
Whoops...move this up a few lines so that it can be used to build up to the concept of delegation instead of explaining it after.
wrong description, also the variables below

kmenta not munnel
which kind of new methods?   from the docstring it's not clear what these extra_fit_funcs should do. Some information in the Notes section will be helpful if the docstring cannot explain it well enough
a possible complication: df_model is an int or float, so when df_model is assigned in the results instance it will be a copy of the one in the model instance.
then we need to set df_model both in the model and the results instance.
Interesting parallelization results. I don't know if you want to play around with this that much, but you don't start seeing gains for using all cores until nobs > 1500 or so, and even then it's modest (ie., barely worth it). I guess the overhead of joblib is still costlier than the computations, but I would've expected it to be a bit faster earlier. There may be other hotspots that this benefits from, you can use this

```
        var_type = self.var_type
        tdat = self.tdat
        LOO = tools.LeaveOneOut(tdat)
        from statsmodels.tools.parallel import parallel_func
        parallel, p_func, n_jobs = parallel_func(tools.gpke, n_jobs=-1,
                                                 verbose=0)
        L = sum(map(func, parallel(p_func(bw, tdat=-X_j, edat=-tdat[i, :],
                            var_type=var_type) for i, X_j in enumerate(LOO))))
```

Alternatively we're going to have look elsewhere for speed gains.
Can you, please, explain what is this change about? I'm going to extract this method in the nearest future, because we have it duplicated in several places, so I'd like to know all use cases.
Do you have some options for this method, other than the normalization form, in mind? If not, I think it'd be better to have a single argument named `form` with a default value `:NFD` instead of this uncertain options hash. 

Another question is about returning `nil`. For this method we can clearly specify a list of valid options (that are just `:NFD` and `:NFKD` at the moment), so wouldn't it be appropriate to throw an `ArgumentError` if some invalid normalization form name is passed?
Well, there's no distanceSquared yet :/
Note unqualified exception, but always re-raises.  Really this just does some logging.
I didn't test the chef stuff; I was sort of madly hacking away and was like, "oh that part's not needed any more, it can go". 

I'll revise the branch to return chef/cookbooks/class2go-python and be more selective in the removal. In particular I'll add a package recipe for python-gdata, make sure other recipes remain untouched, and only remove the patching-of-gdata recipe. Later this morning we can test that I didn't break chef on stage.
So, the first question for networking would be <div id="Survey-Checkbox-networking--Fall2012-01">   is that right?

Which parts are required?
inline styles strictly prohibitted!
It might be worth introducing the term *datalock*, which is distinct from *deadlock*. Deadlock is not possible in single-threaded JavaScript. Datalock is the occurrence where a program cannot make progress, but the event loop is free. This happens when there are cyclic dependencies among scheduled work. I was introduced to the term by Mark Miller and can ask him for a citation reference.
Again, this val has to be configurable
For now, only the Google+ one is really relevant. If you link back to automaton2000.com from your Google+ profile, your avatar will show up in Google search results next to your page.
Good deal. I'll merge in the pull req and change generate() to use Date(long) on a subsequent commit.
A separate results management file/module/something. Brad probably has some ideas here.
Точно, мы же после to_f получим с точкой.
Тогда надо дописать метод, который просто запятую на точку будет менять.
The specification on return type should appear in documentation for the method.
Making the date formatters vars makes sense, although I wonder if maybe the regular expressions should get the same treatment.
Seems I forgot to add this file to the commit; fixed
Nu era mai okay sa folosim <code>switch</code> aici?
probably meant '$reset'
Maybe we have some plans for it, but even on unit tests the constructor below is never used
I need to fetch the template data to log it later (see FormMails.php https://github.com/qzminski/contao-formmails/commit/a342f73a69badf18bd386dc8b8baef2569ef1b73#L0R62).
This won't resize the list up if the window is resized, e.g.

$.viewportHeight = 600;
menuHeight = 480;
// resize window

$.viewportHeight = 1000;
menuHeight = 480;

It does work when resizing the window down though.
In jedem Fall ist das eine Fehlerquelle, bitte beheben.
Почему он называется calendarExample?
https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/StyleGuide
Should check that the app is available for purchase before we click on it. On line 29 do something like `click_first_app_for_purchase()` to be sure the test can continue.
or maybe better intercept_hidden_ and intercept_visible_
pep 257 here too
the active set warm restart should be given by the non-zeros of the coef_init passed don't you think?
You should never use ``is`` unless comparing to ``None``
It was me, thanks!
you don't need the parenthesis
There clearly is a n indentation issue around there
So _settings and settings are identical now. See comment below
This loop could be simplified (inlining of initialization) as:

    do {
        T result = condition.tryToFullfil();
        if ( result != null ) return result;
        sleepWithoutInterruption( 1, "Failed waiting for " + condition + " to be fulfilled" );
    } while ( System.currentTimeMillis() < endTime );
If it's a change you made, please revert as i don't think we should be touching mobileweb specific code.  Otherwise if this is some external change that somehow got picked up in the diff then don't worry about this comment.
Why wouldn't the ndk path just be specified using --ndk even when -t is specified?  Seems like that would be more consistent.  Having `[--ndk ndk] [-t [ndk_location]]` in the usage is confusing
Also make that change in docgen.py in pretty_platform_name function
Hardcoded ip address
no need for ``else`` when the if returns
```if get_link(linkage):``` should suffice as the result is a list.
Because of some previous ABI incompatibility, the scala convention is to happend the version of scala to the name of the jar. Sbt push this concept a little bit further by adding the version of sbt.
The people that developed those plugins have stopped maintaining them (maybe because there were tired of releasing a new version of the plugin for each new version of sbt). For those plugins the latest build available is for sbt 0.11.2, if you use another version of sbt this code won't compile.

A pragmatic way of avoiding this version number nightmare would be to provide your own sbt script like in finagle (See https://github.com/twitter/finagle/blob/master/sbt)
A glue of , is standard.
@raydavis Right - see my comment to @christianv above re: Setting fake properties on real data for demo purposes.
can this become a const ref to save the ref/deref on the return?
This would be better as a case/when block instead of repeated ifs.
You should avoid ```process.execute``` when ```cmd_exec``` will do (i.e., unless you need to use a token). Using ```process.execute``` means this can't run on a shell session.
To be honest, I don't fully understand why we have to do this these days to avoid problems.  I think we have modules that use mixins from msf/core/exploit that don't need to this, and still work fine.  Any idea?
`a3 -> a2` and `b3 -> b2` to match matrix below.
It looks like `:attribute_name` is set to the attribute and `:attribute` is set to the attribute name, which looks backwards to me. Maybe I'm missing something?
@shunter think you can add some doc to this?  I only barely understand what it does.
Moved into Source.  Hopefully a file called `copyrightHeader.js` should be clear to newcomers.
No generated doc.
sure, I will.
这各种空格是？
Some nodes have predefined values

        case XML_TEXT_NODE:
            return @"#text";
        case XML_COMMENT_NODE:
            return @"#comment";
        case XML_CDATA_SECTION_NODE:
            return @"#cdata-section";
        case XML_DOCUMENT_NODE:
            return @"#document";
        case XML_DOCUMENT_FRAG_NODE:
            return @"#document-fragment";
This statement will almost definitely cause a compile error. There is no LCAT in TiUIText (Replaced by TAG). Also no need to log this at an error level. info or warn will be fine. The statement should read something like 

`Log.i(TAG, "Invalid range for text selection. Ignoring.",Log.DEBUG_MODE);`
Missing period. 
Also for a boolean value, I think it's clearer to either describe the positive case:

"Specifies whether the tabs should be at the top of the screen."

Or clarify each case:

summary: Specifies whether the tabs should be at the top of the screen (true) or the bottom (false).

summary: Specifies whether the tabs should be at the top of the screen.
description: If `true`, tabs are displayed at the top of the screen; if `false`, tabs are displayed at the bottom of the screen.

I think in this case I'd lean towards clarifying each case, because the negative case for "tabsAtTop" is not quite as clear as the 
alternative to, say, "enableFoo".
window.alert is less than ideal. could you instead update an <output> element with the error?
Can you write ".add((e)=>errorHandler(e))" as ".add(errorHandler)"? If not, you should at least add spaces around "=>".
just a remark on this one.

if Metlog wants to mimic the logging api --which I think would be a good idea-- logger.exception() should automatically add the traceback, so this line is not needed when we do calls on exception()

see  http://docs.python.org/library/logging.html#logging.exception

cc @crankycoder @rafrombrc
Then I don't see the point of the blocktrans block. There don't seem to be any strings in there.
ill change it to that then
we should also check that the the featured sort filter is selected and
Why the explicit `Tuple!(S, S[])`? Normally, `tuple` works just fine and is cleaner. Is there a reason why it doesn't work here?
This breaks existing behavior. If source is just a input range, and the leading sequence is accidentally matches with "0x":

```d
struct InputRangeSource
{
    string source;
    @property empty() { return source.empty; }
    @property front() { return source.front; }
    void popFront() { return source.popFront(); }
}

auto irs = InputRangeSource("0xyz");
assert(parse!uint(irs, 16) == 0);  // parse just only "0"
assert(irs.source == "xyz");
```
Okay. It should be fixed now.
Good point.

I believe that using [U]LARGE_INTEGER is the proper way to manipulate High/Low pairs when working with the Windows API. However, it has never been used in Phobos until recently.
Function, function pointer, and delegate types are not distinguished?
Why are the ControllerActions removed, is there another possibility to do this? ... These are very basic entities which are actually just nodes with a slug etc. which forward to a certain controller action.

We want to be able to put these controller actions in the node tree so that we can change the url of the controller actions.
What has changed in this section? Is this some xml formatting?
Normally, we place build below dependencies and dependencyManagement
Aha, I cunningly already provide the payload string. Err…

I think you mean "`jsonContents`" or something.
The username/password is encrypted in the DB, and in the repoSession, we don't have access to the encryption keys. So the only way is to filter through the records returned by a more general query.

I'll add a comment.
Separate manifest files, plz!  Announcements have nothing to do with Sync.
this class is harder to read than required, think about capsulating some parts into private sub methods
These names were borrowed from Qt's similar enum.
Pensando melhor agora, acho que turma deve ter outros atributos...

Talvez um código, além do id.
Porque pode ter duas turmas que sejam da mesma disciplina no mesmo período.
Digamos, que tenham duas turmas de calculo 1 para o curso de LCC no período 2011.2. Entenderam?
Oops, let me rectify that.
I think it is currently trivial and bizarre. Logic says if I want to seperate by "-" then I should type "-", not "dash". 

There is no performance difference, no worry about "correct usage" and there is no need for us to hold a developers hand in this way. If the developer wants to separate with `'[chickens]'` then let them, its nothing to do with us.
Not sure which step you are referring to.

I considered setting up a table, but since the actual content of the registrations doesn't matter too much, I did it this way.  I can set up a table.  Transparency in that respect seems like a good idea.

Not quite clear on why the switching day scenario should be a different feature file.  I wanted to make sure that, even if there were registrations yesterday, if we stub the time to be the next day, there shouldn't be any registrations.
Why are you usign a different title than the page itself ? This is not a good idea IMO (btw, there is nothing specific to passwords in the document)
good call...I'm not very familiar with ruby. I'll update the code and modify the PR
Sure !
Ja ich weiss und du hast vollkommen Recht - versuche darauf zu achten. Dies hier hats mir im Eclipse gar nicht angezeigt -> waren versteckte Leerschläge oder so ?!?
a method sounds right. btw, why preg_match and not simply == or maybe str(n)cmp?
These should use the `PhaseStarted` field outlined in the class diagram. If the phase is manually bumped, these dates should slide along with it. I'll file an issue for this.
@croby: Yes, and that's fair. I agree that as a best practice we should avoid these where possible.
Please use the Process component instead of doing the work by hand. The process component adds many things to ensure it works on all platforms (at least it tries). your code is likely to be broken on some platforms
Hmm, to me it seems like calling `import_data` twice obscures the intent of the test, compared to just creating the Case and then calling `import_data`, since the test isn't specifically related to `import_data` being called twice in succession. But I don't feel strongly about it.
space after comma :o)
Declare as const?
Got a little excited ... Or kidding ;-)
So, we don't get the performance benefit of avoiding the copy for a unicasting dispatcher (which is probably the most common) ???

This is __more__ expensive than the previous implementation

````java

    public ArrayList(Collection<? extends E> c) {
	elementData = c.toArray();
	size = elementData.length;
	// c.toArray might (incorrectly) not return Object[] (see 6260652)
	if (elementData.getClass() != Object[].class)
	    elementData = Arrays.copyOf(elementData, size, Object[].class);
    }
````

This looks like it's __more__ expensive than the original implementation. Looks like we need to extend LoadBalancingStrategy to take a collection instead of a list. The LBS makes yet __another__ copy too.
Needed for JavaDocs
It is using @citizen now ;) and I plan to use @profile in the future.
not a username
I would change the key to `verify` (reverse it) otherwise LGTM, +1
Let's be consistent and use "URL" with all caps.
Zend\Debug has been moved to Zend\Debug\Debug
@apex13 Can we add `?vq=hd720` to this URL so we see it in HD by default? (The sound is also way better)
also you can remove the 200 value (default)
Could they just not be included since they're ignored?
because it is used in `History.handleInitialState.js`, is there a better way to do this?
Dave: change to "Upload or Link to File"
I still don't like the idea of doing a sudo in a script, we should just tell them to run these commands automatically or at least show a message why they are being prompted for credentials.
像$hotquestion、$cm、$course这类的变量可以设计为类的成员变量。构造对象时把值传入一次，以后就直接使用，不用每次调用函数都传一遍了。
cmd_wipe_queues here?
did you check if this still works with the updated test suite? i am not sure if this does not only match on class name.
No dot at the end. (Sorry, I just cannot help myself noticing such things.)
You can just import this from horizons.util.python, __init__ is special python magic.
Ben non. Toute la puissance du pattern, c'est que le visitor est une interface, qui peut avoir toute une série d'implémentations différentes. On pourrait donc utiliser la même méthode accept() pour passer un visitor qui enverrait le message, ou qui le validerait, ou qui le clonerait, ou qui l'imprimerait, ou quoi que ce soit d'autre. Et effectivement, accept() est le nom consacré.
Done. Added method in utils and moved the URL to constants.
That might mean that we will need to keep around the `usingContext()` customizations done on a` Validator`
The thing is that sets are not loaded by default. Unless you require it.
But given active model serializers is a rails dependency and rails surely requires it, let's merge this.
Yes, it would be more clear to define in android_modem.h. I think we should do that.

As for emulating other causes, IMHO, I'll say no, we don't.
Labels of samples to ...
typo exactly
bara project hat 2 ta folder mojaza 2ros kon ke hala mitooni ye folder be esme khodet bashe va ina har kodom to ye folder dg be soorate mojaza
Refactor this to have isinstance(value, self.python_instances), etc. so we can define the method once in the _NetAddressField?
consider naming the exception variable `xmlException `
extra newlines around here
I would find it more readable to use a string concatenation here
лучше swap
может быстрое сделать?
Per our discussion, I think we also can't do separate start and end points for radial gradients?

Do we have any limitations on start/end point for linear gradients?
you can remove the "with TYPE_IMAGE id"
better use sync instead of list?
Library name to load differs from gem name, so it needs to be specified.
This prevents from having to put a require statement in app and issues like #3
It seems to be working both ways, but I don't think it's obvious what the difference between the two is. Maybe there is just more/unnecessary server-side processing if we put to the collection?
On most of them, yes. Fixing.
`}).mouseenter(function(){$(this).addClass('sn-mouseenter')}).mouseleave(function(){$(this).removeClass('sn-mouseenter')});`
Не слишком ли ресурсоемкое енто црц32 преобразование? Какой цимес в применении таблицы?
Зойчем нам избыточность?
Add it where exactly?  Before I set it to:
        data["rim:permissions"] = {
            "rim:permit" : [ 'read_geolocation', 'run_when_backgrounded', 'access_internet' ]
        };
you mean?
is there a way to improve the testing a little here?
Seems like we are not testing the invoke data at all
@jkeshavarzi - any ideas to add better tests here?
- pull out $user variable (is globally available)
I don't know whether current D1 documentation (digitalmars.d/d/1.0) is really generated from this repository. But Walter sometimes mentioned about it for past pull requests. So, considering about it is not bad.

> Well, at least we'll be able to ditch macros like that come the first of next year.

Yes. I'm looking forward to it.
The problem is that there are two elemnts inside <label> element. So if you click on the text (label) nothing happends. Correct thing would be that checkbox change status. So for is necessary that this works correctly.