@veasna-t,
- automation_helper.rb is just a place_holder for the common library functions that will be used in this automation.
- The empty it blocks are just a demonstration on what could be done on the positive and negative testcases for evaluating the login. (valid username/password, invalid username, invalid password etc)
- That  'should be able to access the Forgot password page' is just a demonstration on the user navigating to forgot password page and submitting an email address on that page.  (I did not put much validation at the end though)


Это можно не пистаь если явно прописываем rebuildCache(); в createGroup методе.


code have any problem and dont have examplemay be send all codel with example, pleaseFernando
 Fernando Valdes C.

     El Viernes, 2 de octubre, 2015 15:18:05, Abhishek Kandoi <notifications@github.com> escribió:

 @fvaldesc the code is present here just like any other GitHub repository—
Reply to this email directly or view it on GitHub.


сразу пишем return (driver.getCurrentUrl().contains("/groups.php") && driver.findElements(By.name("new")).size() > 0)


This makes the codebase dependent upon a ruby gem? This seems not awesome. Can we make this more awesome?


Enable it in device config telephony folder got mine showing now


@smilli What do you think of this?


any concerns with this approach?


Wouldn't multiple, smaller commits be more suitable for all these changes?


I tried. Did you set it to true?


The default action on a hyperlink is to navigate.  When the `href` is set to `#` this means the beginning of the document.  This is why you get the jumping behaviour to the top of the page when the link is clicked.

You can address this by using the event that is sent as an argument to the click handler function as follows

    $('.readmore a').click(function (e) {
        e.preventDefault();
        /* You could keep your code as before */
    });


@lehni Here comes the first result of my new quantification tool. The last two commits causes a drop in error messages by almost 40%. Very nice.


For layout challenge (day 4): 13/16 (missing magazine layout). Great work on the rest of the layouts!


4/16 - only one layout submitted. It looks great, and I know you're pretty comfortable with floats and positioning, so let me know if you want to submit the other four layouts! :)


That's a good point @jtsternberg. considering there haven't been too many commits or stars, I'd say just start over. :+1:


16/16 - great work!


You do not need to return this. Changing matrix[][] works.


grade of 16/16 - fantastic job!


Miss follow up question.


grade for day 4: 16/16. Really great work!


grade for day 4: 16/16. Great work!


Make it more detailed.


Misunderstand the question.


Not calling a super method will result in unexpected behavior so make sure to call it.


Please read the problem again...


grade for day 3: 16/16. Fantastic work, and really nice job with the animation and javascript!


Indeed, that is what I meant to check for. Thanks for catching this.


^ The flattening happens inside this constructor, so lets move it out of the way of the regular camera case:
```js
  case dom::MediaSourceEnum::Application: {
    FlattenedConstraints c(aConstraints);
    ...
    break;
  }
```


unused


I tried to define the symbol `HAVE_GL_OSMESA` but that only lead to other errors. A simple driver that `#include "GL/osmesa.h"` clearly has `GLAPI` defined:
```
#include <stdio.h>
#include "GL/osmesa.h"

int main(void) {
#if defined(GLAPI)
  printf("GLAPI is defined\n");
#endif
  return 0;
}
```


@kemitchell, I think this pretty much works. I haven't yet done significant testing (https://github.com/anseljh/passive-aggressor/issues/4), so we may want to hold off before merging.

I also don't have it recursing through forms yet, which is kind of important. I couldn't quite wrap my brain around how you were doing that in other annotators. Any tips?


@sjoelund: unfortunately getline is NOT portable! It is a GNU extension which is not working on MinGW or MSVC. I guess we should either use fgets or go back to std::getline.


Getting started should be hyperlinked - incorrect markdown


Grade for day 3: 15/16. Great work! Watch how you target your classes vs ids in CSS. Good job with the vendor prefixes!


Actually, this is a simpler approach, since `GetResult()` is `void` for `TaskAwaiter`:
```c#
return task.ContinueWith(
    antecedent =>
    {
        antecedent.GetAwaiter().GetResult();
        return default(object);
    });
```


Incorrect markdown - TechnicSolder should be hyperlinked


Bingo! : )


Could you check the difference in drops between the two commits also? I think the previous one should probably have fixed more than this one here.


Grade for day 3: 12/16. Missed using pseudo-classes to make every other line item in the Benefits list bold (see assignment), but the rest of it looks great! One note: if you want all the text on the page to be one font, you can simply apply it to the body in your CSS. This will save you from having to put it on H1, H2, p, &c. Nice work!


UITableViewControllerを使っているのになぜassignしているのか


@BREANAL very good! :bowtie:


Temporary fix


I like how you used `sum` as your variable name!


It's no longer functional


Grade for day 3: 16/16. Great work! You might want to try centering the whole thing on the page, especially the top image. Nice job with the box shadow and including a link in the button!


boolean 변수의 이름이 count라는건 좀 이상해 보입니다


`mIdeal` can be outside the min-max range, and must be clamped. Max is an upper bound and shouldn't be used directly, as it can be any obscenely large value, not just the one you're testing for.

I recommend using the `Clamp` function as shown here http://mxr.mozilla.org/mozilla-central/source/dom/media/webrtc/MediaEngineTabVideoSource.cpp?rev=7e6cf02b174c&mark=136-142#121. It should do the right thing.


Grade for day 3: 12/16. Great work - just missed using pseudo classes on the Benefits list to make every other list item bold. Nice job with this!


I did not know how to add this files to the images folder...


Hi Leron,

There's a few things we need to correct here:
* The name of the file should have a file extension of `.rb`
* The `puts` method or `print` method must be used to output those questions in the terminal when the program is run. If you don't have this code on Cloud9 yet, just try running the code on repl.it so you can see the output.


break is redundant with return


Grade for day 3: 16/16. Great work! I like how you chained classes together, using the class "button" twice and then adding the class "top" or "bottom" to it, depending on your need.


Should be in place.


Wrong method.


Heh oops. I ran a bundle install, and that happened.


@WebSpider @miigotu wants this changed to use the db function only once and I don't know enough about Python to do that.


@msledge we have to get this finished!

6/10


I see the updated version. Ignore this comment.


Grade for day 3: 8/16. Nice start to this! You used the suggested colors and fonts, and you're getting there with the background image. Good work!


Miss follow up problem.


grade for day 3: 16/16. Nice job! If you're interested, play around with adding margins to the body of the page, or padding to some of your text!


This breaks levelization, translation units inside the ripple/resource directory are not supposed to include higher level business logic components like ripple/server.


This terminates the whole JVM. You don't want this.
Just return false.


I tried to make it pass a tuple and split the tuple in the def, but I get undefined errors about meta var in mako -.-

Will look at it again sometime soon


This logic should be at the call site of `newInboundEndpoint`, not integrated into the `Resource` manager logic. Consider making this a free function in `ripple/server/Role.h`, like this:
```
/** Create a Consumer with access credentials based on port */
Consumer
newInboundConsumer (beast::IP::Endpoint const& remote_address,
    HTTP::Port const& port);
```


Which SDKs & Visual Studio version is being used that supports inttypes.h ?  Were you able to build the entire solution after this commit?  I'm trying to determine what mixture of toolsets is needed.


How can an outbound endpoint be permissioned? I believe these are only for peer connections, which don't use the `HTTP::Port` privileges.


This could read
```
     boost::asio::io_service& io_service)
         : InfoSub (source, // usage
                   newInboundConsumer(remoteAddress, handler.port()))
```


Remove those backslashes, it's more readable on one line


Can you change these imports to remove the backslashes and use parentheses instead


This URL returns 404 here.

The current URL for claws-mail releases according to their website is: `http://www.claws-mail.org/releases/claws-mail-${version}.tar.xz`


Kev,

Make sure you add an extension on your file name so that when the computer runs the program it knows to use the Ruby Interpreter.

Mr. Moose :bowtie:


Please add problem number to your source file name!


It should still be on Transifex. I'll check it tomorrow


Yeah, I probably used an old commit when pushing to Github.  Fixed in the PR now.  Thanks!


@FauziAkram: you can always compile them by yourself and use them if you
want.
The procedure of accepting patches takes time, and some of them won't maybe
be accepted.

On Sat, Oct 3, 2015 at 11:48 AM, FauziAkram <notifications@github.com>
wrote:

> Now we have 3 successful patches that passes both STC and LTC tests, and
> still not being purged:
> 1) This one
> 2) http://tests.stockfishchess.org/tests/view/56070cff0ebc597e4f23e29a
> 3) http://tests.stockfishchess.org/tests/view/5606e15b0ebc597e4f23e291
>
> What's gonna happen?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/snicolet/Stockfish/commit/61a3b88be2a1b14e4a7c71926940a14d9e410c3f#commitcomment-13575067>
> .
>

--
IQ World <http://www.ultimaiq.net/>


i think you have mispelled canola to canol


this is not a valid syntax with 4.01


Avoid variables with short names like $db. Configured minimum length is 3.


Avoid unused local variables such as '$required_functions'.


Avoid unused local variables such as '$requiredFunctions'.


Method Install::writeEnvFile does not have a Docblock comment.


Method Install::generateKey does not have a Docblock comment.


Method Install::migrate does not have a Docblock comment.


Method Install::getEmailInformation does not have a Docblock comment.


Method Install::verifyDatabaseDetails does not have a Docblock comment.


Method Install::checkRequirements does not have a Docblock comment.


Method Install::getDatabaseDrivers does not have a Docblock comment.


Method Install::block does not have a Docblock comment.


Method Install::header does not have a Docblock comment.


// TODO: Add options so they can be passed in via the command line?


// FIXME: Handle error!


@daid
Why so halfhearted? There are several `Configuration_adv.h`'s alone in this branch.


In systemd, functions should either log all their errors, or none of there errors (in which case the caller should). This function will log in case of OOM, via log_oom(), but not in this case here. Please decide whether it should be this function that logs, or the caller, but stick to one. See CODING_STYLE for details.


On windows 7 (oracle jdk 7.x) system classloader throws classnotfoundexceptio.


нельзя так в сервисах писать
надо через массив делать


It was late and I was tired - forgot to change it - my bad! :disappointed:


does this fixes your systemui force closes???


fixed


fixed.


Maybe it just needs fixed


.factory('dataService', ['$http', 'ENV', function($http, ENV) {

}])
так надо


removed setOutputMarkupId


wow!


ресурсы должны быть в сервисах


nitpick: when concatenating strings, please use strjoin(), rather than heavy-weight asprintf().


Avoid variables with short names like $db. Configured minimum length is 3.


Avoid unused local variables such as '$required_functions'.


Avoid unused local variables such as '$requiredFunctions'.


if you don't hit feature requirement `r18` often enough here, you can generate valid and invalid fuses directly by looking at what is in the state and then using that as a base, see e.g., https://github.com/jlouis/maps_eqc/blob/master/src/maps_eqc.erl#L693-L696 in which you either genrate a fuse which is there, or a fuse which is not there. The precondition of having installed fuses then also disappears.


done.


This resolves [#21671](https://community.openproject.org/work_packages/21671/activity) and related.


Method Install::writeEnvFile does not have a Docblock comment.


Method Install::generateKey does not have a Docblock comment.


Method Install::migrate does not have a Docblock comment.


Method Install::getEmailInformation does not have a Docblock comment.


Method Install::verifyDatabaseDetails does not have a Docblock comment.


Method Install::checkRequirements does not have a Docblock comment.


Method Install::getDatabaseDrivers does not have a Docblock comment.


Method Install::block does not have a Docblock comment.


Method Install::header does not have a Docblock comment.


  .factory('Job', ['$resource', 'ENV', function($resource, ENV) {
    return $resource(ENV.apiEndpoint + '/model/jobs/:id', {
      id: '@id'
    }, {
      update: {
        method: 'PATCH'
      }
    });
  }])
пример сервиса


// TODO: Add options so they can be passed in via the command line?


// FIXME: Handle error!


Yep I'll do my best to implement the load functionality, soon.


Happy to take pull requests

---------
Ben Rometsch - Director
Tel: +44 (0)20 7613 7223

On 2 October 2015 at 22:44:04, Teddy Bradford (notifications@github.com) wrote:

Do you mind updating this again for OS X El Capitan? Terminal is now Version 2.6 (361).

—
Reply to this email directly or view it on GitHub.


I think this is a typo.
The correct one is Request :bow:


I'd prefer if we just compiled in the path, using macros. We do that in most other cases too, see the top of Makefile.am for various definitions like this.


Mh, maybe we can change this if all is finished.


Will turn on by default.


Will also credit Giorgos Vasilakos in the commit comments.


I wonder if we couldn't drastically simplify the forking logic: just fork off all the children, and wait for the first child to die, then exit. Now, relying on PR_SET_DEATHSIG as well as systemd's own killing logic as safe-guard we would not have to kill the other children explicitly. This would basically allow us to get rid entirely of any explicit tracking of the children we fork off, and the patch would be much much shorter.


Nitpick: whenver I see wait() I wonder if it wouldn't better be waitid() that we use...


Avoid variables with short names like $db. Configured minimum length is 3.


Avoid unused local variables such as '$socket'.


Avoid unused local variables such as '$required_functions'.


Avoid unused local variables such as '$requiredFunctions'.


Class UpdateApp does not have a Docblock comment.


Method UpdateApp::verifyInstalled does not have a Docblock comment.


Class ResetApp does not have a Docblock comment.


Method InstallApp::writeEnvFile does not have a Docblock comment.


Method InstallApp::generateKey does not have a Docblock comment.


Method InstallApp::migrate does not have a Docblock comment.


Method InstallApp::getDatabaseInformation does not have a Docblock comment.


Method InstallApp::getInstallInformation does not have a Docblock comment.


Method InstallApp::getEmailInformation does not have a Docblock comment.


Method InstallApp::verifyDatabaseDetails does not have a Docblock comment.


Method InstallApp::verifyNotInstalled does not have a Docblock comment.


Method InstallApp::checkRequirements does not have a Docblock comment.


Method InstallApp::getDatabaseDrivers does not have a Docblock comment.


Method InstallApp::block does not have a Docblock comment.


Method InstallApp::header does not have a Docblock comment.


// TODO: Add options so they can be passed in via the command line?


fix spacing


// FIXME: Handle error!


fix spacing in below while block


put this if in a bracket to clarify it


ohuenno ti zapushil ropeproject


-# Miyabipoker.com-Agen-Poker-dan-Domino-Online-Terbaik-di-Indonesia


Avoid variables with short names like $db. Configured minimum length is 3.


Avoid unused local variables such as '$socket'.


Avoid unused local variables such as '$required_functions'.


Avoid unused local variables such as '$requiredFunctions'.


strip out the else here


Now I figure I introduced that "bug" into the code a couple of days ago when I merged in the changes for the options page.  It is my bad!  You have been extremely polite.  Again, sorry!


prepend with $tmp


Class UpdateApp does not have a Docblock comment.


Method UpdateApp::verifyInstalled does not have a Docblock comment.


Class ResetApp does not have a Docblock comment.


Method InstallApp::writeEnvFile does not have a Docblock comment.


Method InstallApp::generateKey does not have a Docblock comment.


Method InstallApp::migrate does not have a Docblock comment.


Method InstallApp::getDatabaseInformation does not have a Docblock comment.


Method InstallApp::getInstallInformation does not have a Docblock comment.


Method InstallApp::getEmailInformation does not have a Docblock comment.


Method InstallApp::verifyDatabaseDetails does not have a Docblock comment.


Method InstallApp::verifyNotInstalled does not have a Docblock comment.


Method InstallApp::checkRequirements does not have a Docblock comment.


Method InstallApp::getDatabaseDrivers does not have a Docblock comment.


Method InstallApp::block does not have a Docblock comment.


Method InstallApp::header does not have a Docblock comment.


// TODO: Add options so they can be passed in via the command line?


// FIXME: Handle error!


i don't understand why you rename $societe to $object


Thanks, this is really a nice fix. I didn't know you could specify the connection per task. That would be really handy for using/abusing Ansible to do other things ... like configuring switches for example.


The information is interesting. I personnaly don't use IDE so I won't use it for myself, but the day I use an IDE I hope I will remember it ;-)

I just say that it is simpler to use .gitignore. Maybe there is a more efficient way to do it on a given environment, but using .gitignore will avoid problems on environment not correctly configured (which is the majority I guess).


This changed already. See later commits. There are two ways the selectize can be used - as textfield and as select. if textfield is used the value of the model is set as value. if select is used. the arguments are going to be past into the javascript and applied as options and optgroups. See: https://github.com/klopfdreh/core/commit/5bd618f81a3d9c8b382a2af31a6ef72dae35dae7


Likely need to add this back.


Lateron the SelectizeOption and SelectizeOptionGroup can be used to apply other values which can be used in the render function.


Oh man, this brings me back! Do you remember [this](https://github.com/rails/rails/commit/3756a3fdfe8d339a53bf347487342f93fd9e1edb)?


hmm, I have no idea what this tag is??


Good point - I'm going to change this when I implement the ajax functionality.


In the interest of avoiding that threadnaught, perhaps we should conclude like they did – _but what was that_?


done


Please, leave redux, let us settle already! :D


Should be "bananen".


Odd, this doesn't work on Travis, despite being wrong. Most likely we will need to update either Travis or Qt to get it to work.


It appears that it [stayed reverted](https://github.com/rails/rails/blob/add46482a540b33184f3011c5c307f4b8e90c9cc/actionpack/lib/action_dispatch/http/request.rb#L244)! It's funny how the comment above it says that it returns true, though – it should really say returns _truthy_ (the actual return value being either `0` or `nil`).


Fixes #2


I just love how a little thing like this could cause so much controversy. So what do you think, @hyperoslo?


Only collaborator's can do this.


Method InstallApp::generateKey does not have a Docblock comment.


Method InstallApp::clearCaches does not have a Docblock comment.


Method InstallApp::optimize does not have a Docblock comment.


Method InstallApp::getDatabaseInformation does not have a Docblock comment.


Method InstallApp::block does not have a Docblock comment.


Nice.


:metal:


@jgorset right, I remember that epic thread :)

Yeah, it stayed reverted but If we really want to keep it boolean I'd at least change it to something like

```ruby
define_method "#{name}?" do
  !!send("#{name}_id")
end
```

maybe it's just me but `? true : false` looks strange. :)


Included in 41ed6338a, thanks!


done


Does this clear td_client_id, once users update td-js-sdk version? If yes, let's revert this. If no, that's totally fine.


Indeed this is exactly how I would of have refactord the get_found_rows.


Maybe with this commit we do not need https://github.com/MinetestForFun/server-minetestforfun-skyblock/commit/38014580ac222de9593738734a9e8f1ddfc40b9d anymore.


Hmm, it works without this... Or I missing something?


Yes obviously, sorry for that.

Can you fix it when applying ?

Best regards,
Romain


@looselycoupled better now?


Create new photo Gallery effect


I see you have a `Mathematics.md` files, maybe it's a more appropriate place?


What about just comitting an extra commit on top of the original rather than recommitting with the edit inline to avoid lowering the accuracy of BLAME since now it will should you as the author not me and it's not clear which edits were added by you compared to what I originally committed in the history in your repo.

Not a big deal, just a thought to ponder on...


\documentclass{report}
\title{Premier rendu }
\author{Ilhem BADREDDINE,\\ Latifa BOUCHOUAF, \\ Xiaofan XU, \\ Rok IVANSEK.}
\date{21/07/2015}

\usepackage[utf8]{inputenc}
\usepackage[french]{babel}
\usepackage[left=2cm,right=2cm,top=2cm,bottom=2cm]{geometry}
\geometry{scale=1.0, nohead}
\usepackage{graphicx}
\graphicspath{ {figures/} }
\usepackage{array,multirow,makecell}
\setcellgapes{1pt}
\makegapedcells
\newcolumntype{R}[1]{>{\raggedleft\arraybackslash }b{#1}}
\newcolumntype{L}[1]{>{\raggedright\arraybackslash }b{#1}}
\newcolumntype{C}[1]{>{\centering\arraybackslash }b{#1}}
\renewcommand{\baselinestretch}{1.5}

\begin{document}

\begin{table}[htbp]
\begin{center}
\begin{tabular}{|L{4cm}||L{10cm}|}
\hline Nom du scénario & L'enregistrement à une séance par l'application    \\
\hline  Acteurs &  membre du club \\
\hline  Flot d'événements &  \begin{enumerate}
\item Se connecter sur son compte.
\item Aller dans section planning.
\item Choisir un horaire qui convient.
\item Validation si il reste des places.
\item Envoi d'une validation
\end{enumerate} \\
\hline
\end{tabular}
\caption{enregistrement membre.\label{engmembre}}
\end{center}
\end{table}

\begin{table}[htbp]
\begin{center}
\begin{tabular}{|L{4cm}||L{10cm}|}
\hline Nom du scénario & L'enregistrement à une séance par l'appli    \\
\hline  Acteurs &  Animateur \\
\hline  Flot d'événements &  \begin{enumerate}
\item Se connecter sur un compte visiteur.
\item Aller dans section planning.
\item Choisir un horaire qui convient.
\item Validation si il reste des places.
\end{enumerate}\\
\hline
\end{tabular}
\caption{enregistrement visiteur.\label{engvisit}}
\end{center}
\end{table}

\begin{table}[htbp]
\begin{center}
\begin{tabular}{|L{4cm}||L{10cm}|}
\hline Nom du scénario &  Création de planning \\
\hline  Acteurs &  Administrateur \\
\hline  Flot d'événements &  \begin{enumerate}
\item Se connecter sur son compte.
\item Aller dans section planning.
\item Choisir les horaires et les créneaux.
\item Choisir les deux animateurs pour chaque séance.
\item Validation du planning.
\item Envoie du planning aux animateurs.
\end{enumerate}\\
\hline
\end{tabular}
\caption{Création de planning.\label{creatplan}}
\end{center}
\end{table}

\begin{table}[htbp]
\begin{center}
\begin{tabular}{|L{4cm}||L{10cm}|}
\hline Nom du scénario &  Modification du planning \\
\hline  Acteurs &  Administrateur \\
\hline  Flot d'événements &  \begin{enumerate}
\item Se connecter sur son compte.
\item Aller dans section planning.
\item Choisir les horaires et les créneaux à changer.
\item Choisir les deux animateurs pour chaque séance.
\item Validation du planning.
\item Envoie des nouveaux planning au animateur.
\item Envoie des modification des séances au participant des séance modifier
\end{enumerate}\\
\hline
\end{tabular}
\caption{Modification du planning.\label{modifplan}}
\end{center}
\end{table}

\begin{table}[htbp]
\begin{center}
\begin{tabular}{|L{4cm}||L{10cm}|}
\hline Nom du scénario &  Validation des séance du planning \\
\hline  Acteurs &  Animateur \\
\hline  Flot d'événements &  \begin{enumerate}
\item Se connecter sur son compte.
\item Aller dans section planning.
\item Valider les séances à animer.
\end{enumerate}\\
\hline
\end{tabular}
\caption{Modification du planning.\label{creatplan}}
\end{center}
\end{table}

\end{document}


:grinning:


J'ai fait les scénario pour planning.
github ne supporte pas le fichier .tex


github 居然过滤了下划线


Yeah, I'm struggling to understand the same? It looks like it adds 9 for API Level 20+ or 8 for API Level 14+. What's the purpose of this?


Presumably we want <OtherFlags>--mlcompatibility</OtherFlags> here as well


If `rx_setDelegate` is not called, the following delegates is not used.

```swift
     // MARK: Table view delegate

     func tableView(tableView: UITableView, viewForHeaderInSection section: Int) -> UIView? {
         let title = dataSource.sectionAtIndex(section)

         let label = UILabel(frame: CGRect.zero)
         label.text = "  \(title)"
         label.textColor = UIColor.whiteColor()
         label.backgroundColor = UIColor.darkGrayColor()
         label.alpha = 0.9

         return label
     }

     func tableView(tableView: UITableView, heightForHeaderInSection section: Int) -> CGFloat {
         return 40
     }
```


@Matthewacon Lol k.


Reverted this


The bower.json `version` field is optional. Imo, we should just drop the reference to it here.


:metal:


Reverted to Welcome


So this commit only adds `--mlcompatibility` flags in some projects. All other line-ending/spacing changes should be discarded.
I guess we want that flag in all projects to avoid similar issues in the future.


Oh, yes. You are right. I was doing demo (docker hub search app) and I didn't need custom header.


adoooo mekane?


Thanks, fixed : c7f1f92b9237793191e3a36e28fbebe368246ab1


It would be useful to add a few quick sentences to the readme so it's clear why there are multiple elements.* artefacts around.


Conditional polyfill loading changes lgtm.


Najverojatno problemot e so return typot.
Probaj:
```
prod :: Num a => [a] -> a
```


Nemora (++) moze (:)   :-)


This should be `<Private>true</Private>` as suggested in [Notes and Guidance on FSharp.Core](https://fsharp.github.io/2015/04/18/fsharp-core-notes.html), otherwise `FSharp.Core.dll` won't be copied to the `bin` directory.


well, this is neither secret, nor 16 bytes long... I mean, it doesn't really matter what key we pick here, but so far we always generated one with "journalctl --new-id128" and then simply used that. I think we should follow the same logic here. Also, you want this to be static as well as const.


Sorry for late reply. I've been thinking whether to apply this as-is or not. The only thing I don't like is that 'static' is removed from the functions.


we generally return negative errno-style errors, and should do so here, too. `asprintf()` returns -1 however on failure.  Also, please use PRIx64 here.


No point in redirecting 4.4.0.0 to 4.4.0.0


I think it would make sense to turn this into a proper #define macro, i.e.

```
#define HASH_URL_THRESHOLD_LENGTH (_POSIX_PATH_MAX-16)
```

or so, which we then use here.


We want these to be set to `true`. Is there any issue with that?


looks like it should be a </div>


Remove this


Again, we want this to be set to `true`


Again, we want this to be set to true


:+1: switching these to computed bindings. Good call.


Not something to change here, but aren't toplevel-keys really image-names?


Seems like you're not using the `should` syntax in your specs, so that setup line could be removed.


Few too many f's here - followinf froupds


element


@dalinaum no parameters named `configuration`.


If it is added, `./gradlew realm:javadocRelease` fails. An error message said that realm:javadocRelease/home/jenkins/jenkins/workspace/java_pr/realm/src/main/java/io/realm/RealmObject.java:20: error: package io.realm.internal does not exist
import io.realm.internal.Row;


**react/jsx-sort-props**: Props should be sorted alphabetically


**semi**: Missing semicolon.


Tack tom :+1:


This is very good!


Calling `chai.should()` has the side effect of [extending each object (through the `Object` prototype) with a `should` method](http://chaijs.com/guide/styles/), so it's best not to call it if you don't use it.


Ich fürchte das funktioniert so nicht in Ansible. Man müsste die freizugebenden Ports dann über host_vars einstellen.


That's the idea!


Not sure what you mean. These’re scoped to ‘infra’, so the namespace of AWS resources.


Hi,

Got it working nicely(I also tested the file incrementer mechanism which works). Here's the things I changed from your code:
https://github.com/bradymiller/openemr/commit/d2708b9c13e53334507e5e6490fe15862d1b4ad6

And here's a rebase of everything in 1 commit, which is what I'll bring into the codebase:
https://github.com/bradymiller/openemr/commit/7a14c8517b34dfc49ade1a42c9a6c8bf6989921e

thanks for the contribution!!!
-brady


Sorry & never mind, had something unrelated in mind -.-


please see for this up. Im confused here.
http://www.formget.com/how-to-create-pop-up-contact-form-using-javascript/


Yeah, usually that's the preferred way for me as well. In this particular case it seemed to me more straightforward to just pick those hunks which were relevant to `argparse` instead of applying the whole patch and then reverting back the exception handling modifications and test suite adjustments.

Perhaps just one little cosmetic request: I'm used to put most of the important changes directly from the git log to change log. Could you please start the commit messages with capital letter and formulate sentences as they were for the change log so that I can paste them directly? Thanks.

http://did.readthedocs.org/en/latest/contribute/#commits


You may need to create such dummy actions in numerous places. If you want to avoid redundancy and also allow for easy customization, you may use [a factory](http://chaijs.com/plugins) plugin to keep all your "seed" data in one place, exposing them through generator functions.


Would be nice if `@reflectable` on the class would expose all public members, for classes that are only used as model classes for Polymer.


If a particular version of LLVM is hard-coded here, won't that make the build fail with all versions of GHC that don't support that version of LLVM? In other words, does that patch really belong into `configuration-common.nix`?


does autoconf support the creation of functions or macros?
seems like unnecessary code repetition, a function that takes the lua version would do better for future maintenance.

(I'm just a curious reader)


Congratulations!
I am happy that this idea finally succeeded.


I need to look into how thermal expansion dose this as I think they have it automatic for all woods


Change to port 80, since there is no problem, after all, with ~okeanos. (virtualhosts as well)


Closed in favour of #199


По моему мнению они не стали сильно логичнее. Они все еще зависят от структуры страницы (table) и контекста (title). Чтобы будет когда текст Error ты будешь выводить не в заголовке? Или Total persons тебе понадобится не внутри таблицы?


btw, I just committed the feature to the official codebase.


Уже лучше.


@arossiko. I think we should extract the notejs installation to another role.


Если у тебя такой одинаковый код на двух страницах, то может его вынести в отдельный JS-файл? И подключать в оба файла? А т.к. тебе понадобится подстановка значений из Thymeleaf-а, то тебе также придется извлечь функцию и необходимые значения передавать при вызове на самой странице.


Такое было только в версии, где использовался JavaScript?


Method UpdateApp::verifyInstalled does not have a Docblock comment.


FemTools removed? Is that correct?


No CPU time needed for thumbnail generation, file saving should be faster.


А зачем тебе передавать id внутри поля, если он уже содержится в URL-е страницы?


in what way are they incomplete?  were u going to share that info or just leave it?


I think that core developers like to see header here


Please add header


Well, is not available on either MSVC and MinGW. Nevermind, I made an implementation hack based on fgets.


Если это нужно только для тестов, так может добавить `<scope>test</scope>`? Или я не так понял?


I don't think debug prints should be included in "production" code. Minimum messages until there is an error.


Please update with your details here


Я бы написал немного иначе: `and following fields` -> `with the following fields`


Нету его уже.


JDBC ты тоже уже не используешь. В смысле, явно не используешь.


Also commented, but...


Lean или Learn?


Method InstallApp::generateKey does not have a Docblock comment.


Method InstallApp::clearCaches does not have a Docblock comment.


Method InstallApp::optimize does not have a Docblock comment.


Method InstallApp::getDatabaseInformation does not have a Docblock comment.


Original test code


new code for message only


Message only


Cool


Напомни, оно само вызывает mvn test? Или какая там команда по умолчанию? Может ее явно прописать?


You can still use it the old way if you wish.
From the docstring:
```
from packagekit.progress import PackagekitProgress

steps = [10, 30, 50, 70]
progress = PackagekitProgress()
progress.set_steps(steps)

for milestone in range(len(steps)):
    # do the action is this step
    print "progress : %s " % progress.percent
    progress.step() # step to next milestone
```
and
```
from packagekit.progress import PackagekitProgress

steps = [10, 30, 50, 70]
progress = PackagekitProgress()
progress.set_steps(steps)

for percent, milestone in zip(progress, range(len(steps))):
    # do the action is this step
    print "progress : %s " % percent
```
produce the same output which is:
```
progress : 0
progress : 30
progress : 50
progress : 70
```

This could also be done the way ```click.progressbar``` is done with a ```with``` context http://click.pocoo.org/5/api/#click.progressbar but I felt it was ok for this case.


@peti it uses it not for `-fllvm` but for linking -- this should not affect `-fllvm` in other packages in any way (however just to be sure I'll check this later today).


I think `n` and `--network-veth` should be seperated. The former should not take any arguments, as before, the latter should take an optional argument now. This is useful, since "systemd-nspawn -nb" previously meant: "set up veth + boot it up", but if we just make "-n" mean optional then "b" would be considered the optional argument for "-n" suddenly, and the line would hence now mean "set up a veth called 'b'" if you follow what i mean.


@arossiko, Installing the passenger inside the ruby role introduces a dependency problem.
To be more specific:
1. Playbook installs ruby
2. Playbook installs ruby gems
3. Playbook installs passenger gem
4. **[problem]**: no apache installation is found.

Inside **ansible/playbooks/access.yml** the **httpd** role should be before **ruby** role.


optarg is optional here, hence, make make sure to handle that it can be NULL! The way it is right now this will explode...


We log with "log_error()", and specifically "log_error_errno()" in cases lwhere we have an errno-like error.


Same here.


"-1" is not a valid error. Please see CODING_STYLE. Use "return -EINVAL" here, or something like that.


Can you explain a little bit? Thank you!


Also, I don't think we should use strv_split_extract() here really, that's only a good choice if we expect an arbitary number of parameters here. Instead, just use extract_first_word().


The aforementioned factories could also help you reduce the length of that code. Consider the following:

``` js
it('should handle TOGGLE_GROUP', () => {
  let dummyAction = chai.create('action_toggle_group');
  let expectedResult = chai.create('state_ward_all_on');
  let resultState = reducer(undefined, dummyAction);
  expect(resultState.ward).to.eql(expectedResult);
})
```

True the test itself is less explicit because the actual objects you can't see anymore, but in the long run, as you keep adding tests, you may prefer conciseness over explicitness. The reason why I usually prefer the shorter version is because, once I added a test, I don't come read that test that often: only if it breaks. Meanwhile, the shorter the code I need to browse through, the better. When a specific test breaks, I can easily [add breakpoints](http://blog.andrewray.me/how-to-debug-mocha-tests-with-chrome/) using mocha's `debug-brk` option and/or `console.log` statements.

It also let me easily test the factory functions themselves, just to make sure my seeding is always what I need:

``` js
// Say, test/factories.js
const camp_all_on = {
  box: true,
  pull: true,
  stack: true
};
const truesight_all_on = {
  sentry: true,
  tower: true
};
const ward_all_on = {
  runes: true,
  offense: true,
  defense: true,
  push: true,
  utility: true
};

const all_on = Object.assign({is_radiant: true}, {camp: camp_all_on}, {truesight: truesight_all_on}, {ward: ward_all_on});

chai.factory('state_camp_all_on', camp_all_on);
chai.factory('state_truesight_all_on', truesight_all_on);
chai.factory('state_ward_all_on', ward_all_on);
chai.factory('state_all_on', all_on);
```

``` js
// Say, test/factories/actions.js
describe('state factories', {
  describe('ward_all_on', {
    it('turns all ward-related flags on', {
      // Below, will be the only place I need to be explicit about the hash within my tests suite.
      let expectedResult = {
        runes: true,
        offense: true,
        defense: true,
        push: true,
        utility: true
      }
      expect(chai.create('state_ward_all_on')).to.eql(expectedResult);
    });
  });
});
```


There is no need to splice here, just build a new array out of the required schemas.


Oh, and also improve plank removing code


Thanks.
I have a request from a customer to be able to turn off the other items on the portal screen. In the next revision I will add more globals to do this with (if that is ok)
Thanks
Terry
      From: Brady Miller <notifications@github.com>
 To: teryhill/openemr <openemr@noreply.github.com>
Cc: teryhill <teryhill@yahoo.com>
 Sent: Saturday, October 3, 2015 7:53 AM
 Subject: Re: [openemr] Changes requested by Brady (678de63)

btw, I just committed the feature to the official codebase.—
Reply to this email directly or view it on GitHub.


Also, about debugging mocha tests: if you want to use breakpoints, besides using the `debug-brk` option, there is also [the `debug` command](http://stackoverflow.com/questions/14352608/whats-the-right-way-to-enable-the-node-debugger-with-mochas-debug-brk-switch), that's even easier.


This is probably involuntary line end change - please make sure your editor don't mess with existing line endings.


Modify podspec to support Alamofire 3.0.0-beta.3


Could this case be put in a separate function, so that both branches of the preprocessing conditional are short?


Where is the documentation of this value? Would it make sense to allow users to tweak it?


Wtf is that commit?
Did you take a look at the code just slightly above?
The variable is already checked against null and also final.


That would be a good thing to have.
-brady

On 10/03/2015 05:14 AM, teryhill wrote:
> Thanks.
> I have a request from a customer to be able to turn off the other
> items on the portal screen. In the next revision I will add more
> globals to do this with (if that is ok)
> Thanks
> Terry
> From: Brady Miller <notifications@github.com>
> To: teryhill/openemr <openemr@noreply.github.com>
> Cc: teryhill <teryhill@yahoo.com>
> Sent: Saturday, October 3, 2015 7:53 AM
> Subject: Re: [openemr] Changes requested by Brady (678de63)
>
> btw, I just committed the feature to the official codebase.—
> Reply to this email directly or view it on GitHub.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/teryhill/openemr/commit/678de630406d6e656fc6e4c7004a78bb98445779#commitcomment-13575559>.
>


Avoid variables with short names like $db. Configured minimum length is 3.


@phil65: this branch will interesting for you (maybe), because it change the homescreen preview to playlist (and you can override the onclick actions, which was your problem, too)

But i have actual a problem with the musicdb://recentlyaddedalbums/ there is "all albums" included.
This problem should solved, before i make a squashed PR.


@taconaut I think you're explaining the separate duplication issue (which is over my head :-), but the endless loop is because ```getChildren()``` is being called in every cycle of the ```while()```, so the ```next()``` child is always the first child and we never get to the second child.

I guess as a random user I'd expect to find my plugin folders initially added to root as usual, and then move them around in the tree if I like, but maybe this doesn't fit with your philosophy here?


cc @fredemmott


he is referring to GOOD BAD UGLY, but iirc those have been added to bb now


This is just what I was looking for, thanks! Up untill now I was using `App::make('twig')->...`, but no longer :+1:


@pweil- Yeah, a little late, but this needs to be `GetResource`.  We want to allow the resource through since that's a particular intent, but the `Kind` shouldn't be used as a determiner intent.


ok, I'll repost fixed version a few hours later (I'm away from laptop ATM and have no compiler on the cell).


Now it seems that this kernel has a lot of commits that makes it even worse.
Now I must clean it up and try to make the drivers compatible with the new HALs, and make it fully stable on kitkat.


Muito bom!


Shouldn't the FIXMEs in MFTUnregister and MFTEnum be turned into TRACEs?


Aqui depois precisamos rever algumas coisas....

https://www.python.org/dev/peps/pep-0008/#imports

Se quiser pode abrir um Pr novo... a solução é simples.


後面多了 r，麻煩推上來之前先檢查一下，這次我就先合併了


Remove


Redundant comment. A good function name gives the same info


Whar does '-2' mean ?


I used FIXMEs on purpose since most other functions in this library are stubs and the implemented functions haven't been tested a lot. If an applications crashed due to mfplat I would like to know if my functions are involved in the crash. I also didn't sign off the patch as I consider it experimental.


Do we really `phpexcel` to generate CSV files? `fputcsv` can't do the job?


Click here to deploy . After this a new window opens with command NONE . Not working . I reinstalled python still the same problem .


This change should not be necessary.
If a player is found (playerIdent != null) then it should return this one.
Otherwise it should fallback to basically the same code you wrote which has been in line 378 before.
Maybe it was just the isComplete which was missing.


merge


@stfx No, I have to correct you. Your first thought was actually correct (but there's a catch).

Assuming functions with no side effects for a second, your first thought was correct:
```
(itr++)->second->AuctionBidWinning();
```
is the same as
```
itr->second->AuctionBidWinning();
++itr;
```
because the post increment operator returns *the original, not incremented* value. But there's a catch of course. Where the post increment operator works just fine on valid iterators, the pre-increment in the second version will only work correctly if itr is still a valid iterator, and that's exactly what the problem was here: the AuctionBidWinning function invalidates itr indirectly! It's like sitting on a branch in the top of a tree, then asking someone else below you to saw off the tree trunk there...

Note the difference with your "apparently" version: in your version, itr itself will *also* be incremented and newItr will be the new incremented value, making you call AuctionBidWinning on the wrong value.

So, the original code was
```
itr->second->AuctionBidWinning();
++itr
```
which did not work because AuctionBidWinning invalidates itr indirectly, so using it later on fails. In this case later use is incrementing it, but it could as well have been any other use of the invalidated iterator really - it would have failed.
The new code is
```
(itr++)->second->AuctionBidWinning();
```
which starts with incrementing itr while it is valid, and returns the *old* value (post-increment) so that AuctionBidWinning is still called on the correct value. Note that itr is already successfully incremented when the post-increment returns, so it remains valid and it's not a problem that the old value is invalidated (we're not using it any more).


... an ASCII ..


Yeah, should be good -- `llvm` doesn't get propagated to any other packages and `ghc` invokes it as a separate process, not as a library.


IDK how the JVM works, but it seems that the null variable is being passed on to TaskRegistry. Wouldn't hurt to check again.


Seems our msys2/git isn't doing git send-email, which I wanted to use. Perhaps I didn't set it up correctly? Hopefully I won't have this problem with your mingw-w64 git :-)

I'll just send the email from gmail in my browser instead. Hopefully it won't reflow it; if it does I'll have to send as an attachment. Urgh.


Here you go: https://github.com/este/este/tree/75186529e4d484c411f196bfa8e45f12e14a8700
```
git checkout -b "feature/universal" // let's make a copy of current master
git checkout master // go back
git checkout 75186529e4d484c411f196bfa8e45f12e14a8700 // rollback
git push -f
```


Somehow or rather something was null - which is what caused #1763 in the first place. GameProfile.isComplete just checks that the username is not empty and that the UUID is not null - which you were already doing.


OK, cool. Thanks!


maybe it should rather depend on whether the borg_cache_dir already existed or we created it empty.


Yeah, we should probably look into the other known failures if they can be fixed or if they are unsupported.


Can we please speak English when we explain what a commit did


Fixed. So, I can rebase?


Maybe he just used a version where I didn't add the first check yet.
Anyway the second check is totally useless - final variables are there to prevent exactly such things.


Why is this commit undoing all of my work


wdf


maybe rather don't add 'config' here. it would run header_replace on it.
even if that does not do harm because it checks for the attic magic, it seems dirty.

just copy the file separately.


この修正はherokuにapi keyの環境変数を設定する目的でしょうか。


I thought a full example would be better here.

Let's say I have a problem with the first test for the actions. Let me add a `debugger` statement there:

``` js
// test/actions/MapActions.spec.js
describe('MapActions', () => {
  it('should create an action to switch the faction', () => {
    let expectedResult = {
      type: SWITCH_FACTION
    }
    debugger;
    expect(switchFaction()).to.eql(expectedResult);
  })

// …
```

I then run the following command:

```
mocha debug --opts ./test/mocha.opts --compilers js:babel/register --recursive test/actions/MapActions.spec.js
```

It *is* cumbersome to write, but you may actually tweak the `test` entry from `package.json` to allow for dynamic arguments, I believe, so as to handle the `debug` command and the custom path.

Anyway, here's the result, in the terminal:

```
$ mocha debug --opts ./test/mocha.opts --compilers js:babel/register --recursive test/actions/MapActions.spec.js
< debugger listening on port 5858
connecting... ok
break in /usr/local/lib/node_modules/mocha/bin/_mocha:7
  5  */
  6
  7 var program = require('commander'),
  8   path = require('path'),
  9   fs = require('fs'),
debug>
```

This is [Node's debugger](https://nodejs.org/api/debugger.html). Check the documentation for all available commands, and/or [this tutorial](https://devcentral.f5.com/articles/nodejs-abcs-d-is-for-debugger) for additional insights.

Here's an example debugging session:

```
$ mocha debug --opts ./test/mocha.opts --compilers js:babel/register --recursive test/actions/MapActions.spec.js
< debugger listening on port 5858
connecting... ok
break in /usr/local/lib/node_modules/mocha/bin/_mocha:7
  5  */
  6
  7 var program = require('commander'),
  8   path = require('path'),
  9   fs = require('fs'),

// Node paused by default on the first line of the executed script. I type c (continue) to move
// from the default breakpoint to the next in sequence, mine.

debug> c
<   MapActions
break in test/actions/MapActions.spec.js:14
 12       type: _srcJsConstantsMapConstants.SWITCH_FACTION
 13     };
 14     debugger;
 15     (0, _test_exports.expect)((0, _srcJsActionsMapActions.switchFaction)()).to.eql(expectedResult);
 16   });

// I am paused within my test. The code looks a bit different from the file, because of
// the JavaScript engine (node). It's still pretty clear what's going on though.
// I'd like to inspect variables at this point. In order to do so, I must enter a sub-mode,
// named repl (Read-Eval-Print Loop).

debug> repl
Press Ctrl + C to leave debug repl

// There is built-in auto-completion: I type "_sr" and then pressed [Tab]

> _sr
_srcJsActionsMapActions      _srcJsConstantsMapConstants

> _srcJsActionsMapActions
{ __esModule: true,
  switchFaction: [Function],
  toggleFilter: [Function],
  toggleGroup: [Function] }
> _srcJsActionsMapActions.switchFaction()
{ type: 'SWITCH_FACTION' }
> expectedResult
{ type: 'SWITCH_FACTION' }

// Fair enough. Let's see if those are actually equal…

> _srcJsActionsMapActions.switchFaction() === expectedResult
false
> _srcJsActionsMapActions.switchFaction() == expectedResult
false

// Seems weird, but that's the way it works within Mocha. The output above is not the
// actual "nature" of the inspected objects, only their representation. In order for me
// to trully test the equality of those objects, I need to rely on mocha's expect function.

> expect
ReferenceError: expect is not defined

// In the repl, expect is available on a _test_exports object. Let's use it.

> _test_exports.expect(_srcJsActionsMapActions.switchFaction()).to.eql(expectedResult)
{ __flags:
   { ssfi: [Function],
     object: { type: 'SWITCH_FACTION' },
     message: undefined } }

// When you get such a message, it means the test has passed. A failing one raises:

> _test_exports.expect(_srcJsActionsMapActions.switchFaction()).to.eql({})
AssertionError: expected { type: 'SWITCH_FACTION' } to deeply equal {}

// Here I typed Ctrl+C to exit from the repl, back to the debugger.

debug>
(^C again to quit)

// Ctrl+C twice to exit the debugger.

debug>
```


TibEd says 120 for me :?


not sure I can follow here, why does it trigger a cache resync precisely?


Sure why not


I added a case to admin flags, checking for "flag" as well, the derp part was because of crafting, he forgot the 's' and made me think the whole system was broken.


I forgot to update my local copy before making a commit, and git freaked out. Had to backtrack main branch, then reupdate in this commit.


StrStarts(szStr, "flag", true)


how much does encoding a small thumbnail affect CPU?


`Stopping PostgreSQL 9.3 database server       * Error: You must run this program as the cluster owner (postgres) or root`
I think it's better to keep these sudos for now. We wouldn't need them in container builds anyway.


What was your issue with the parralax mapping? As I've implemented it and it appears to work if you put in a negative scale factor.


confirmed working where it didn't work before on custom snapshot build.


I tried it at first to compare (especially in term of generation speed). The only advantage of phpexcel seems to be the getProperties() methods, but these properties don't seem to show up in LibreOffice anyway. I'll change it back.

I also thought maybe we would use it also in graby to parse xls/csv files ? But that's far ahead.


And I just learned something super useful: you [may pass options to npm `scripts` commands](https://docs.npmjs.com/cli/run-script), so all you need to debug a test is:

1. Add a `debugger` statement somewhere
2. Run the `test` command like so: `$ npm test -- debug`

Can't get any simpler than that!


But the current code causes problems if actually a player was referenced.
This definitely needs some checking again.
Could you maybe try it with the code in the braces still enabled?
...
Oh... just now I noticed the problem.
`playerIdent` is never checked for a valid game profile.


Also try adding `requests[security]` to pip install list, might fix SSL issue.


And why is withCanoncalizedTempDirectory not useful?


Thank you, I was just wanting this!


Sorry, I meant that the message should be as specific as possible.  If I had
```
self.assertTrue(500 != 501)
```
I would want the message to say, "use assertNotEqual", or at least, "use assertEqual or assertNotEqual".


嘖嘖ww.......
不愧是傻逼才會幹這種事


I liked your first patch, because  it was not playing tricks to add the fake mechanism, and did not rely on the register_mechanism to OR the flags bits.

This may not be the last card that has issues like this.

register_mechanism has comments like:

4639 /*
4640  * Mechanism handling
4641  * FIXME: We should consult the card's algorithm list to
4642  * find out what operations it supports
4643  */

4670         /* For now, we just OR all the algorithm specific
4671          * flags, based on the assumption that cards don't
4672          * support different modes for different key *sizes*. */

The GenSafe V3 with SHA256 does not meet the assumption, although the comment is talking abount key sizes, rather then hash sizes.

Would a more general fix be to look at the cards algroithm list and have the list define different flags
for the sha256?

Or do we need a seperate flag to indicate that the hash header should not be sent to the card?
#define SC_ALGORITHM_RSA_NO_HASH_HEADER         0x20000000
This would only be set for SHA256 for the GemSafe cards.

Just proposing to make the core code handle this type of situation.

The SC_ALGORITHM_RSA_HASH_* flags can be misleading because they do not say if the hash is done on the card or in software via OpenSSL. This also needs some work.


Joe Zawinul


@danilaml But do we need them even anymore? We aren't failing builds anymore due to filling up the ram and thus failing.


Tuka ustvari namesto filter moze takeWhile, malku poefikasno :-)


not sure about this, in other softwares and in the TIFF format, 32 bits per channel use floating point numbers


あざます


Ca c'était un gros morceau ...


TeamCity ChameleonForms :: Continuous Integration [Build 260](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=5634&buildTypeId=bt20) is now running


TeamCity ChameleonForms :: Continuous Integration [Build 260](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=5634&buildTypeId=bt20) outcome was **FAILURE**
Summary: Error while applying patch Build time: 0:0:0


TeamCity ChameleonForms :: Continuous Integration [Build 261](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=5635&buildTypeId=bt20) is now running


TeamCity ChameleonForms :: Continuous Integration [Build 261](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=5635&buildTypeId=bt20) outcome was **FAILURE**
Summary: Error while applying patch Build time: 0:0:0


TeamCity ChameleonForms :: Continuous Integration [Build 260](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3663&buildTypeId=bt20) is now running


С сортировкой по дате, кстати, тоже можно так же поступать, как и с сортировкой по значениям - вычитать)


Nice :+1:


чем split из stdlib не устроил?


looks good, can you make a pull request?


Tack för stödet kamrat :+1:


For this kind of assertions, where you expected a value from a hash to have been changed, you may use something like [a change plugin](http://chaijs.com/plugins/chai-change) for mocha. Not that useful for this very test, but may come in handy for more complex assertions.


@danilaml Since do I don't know how pip exactly works, could you care how I add it to the install list?


What's this doing?


This revision is clean.


Just look at the file history few revisions back: 6fd277c08c2580c0206aa3034b9a284e292a9f18 – `tags` was previously referenced after the block.


TeamCity ChameleonForms :: Continuous Integration [Build 1.2.1+026](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3663&buildTypeId=bt20) outcome was **FAILURE**
Summary: Tests failed: 2 (2 new), passed: 3007 Build time: 0:0:0
### Failed tests
```
ChameleonForms.Tests.dll: ChameleonForms.AcceptanceTests.ModelBinding.ModelBindingShould.Function_correctly_with_checkbox_and_radio_lists: Test(s) failed. System.TypeInitializationException : The type initializer for 'ChameleonForms.AcceptanceTests.Host' threw an exception.
  ----> System.ComponentModel.Win32Exception : The paging file is too small for this operation to complete
   at ChameleonForms.AcceptanceTests.ModelBinding.ModelBindingShould.Function_correctly_with_checkbox_and_radio_lists() in c:\TeamCity\buildAgent\work\81e762d276ae250c\ChameleonForms.AcceptanceTests\ModelBinding\ModelBindingTests.cs:line 29

ChameleonForms.Tests.dll: ChameleonForms.AcceptanceTests.ModelBinding.ModelBindingShould.Function_correctly_with_default_form: Test(s) failed. System.TypeInitializationException : The type initializer for 'ChameleonForms.AcceptanceTests.Host' threw an exception.
  ----> System.ComponentModel.Win32Exception : The paging file is too small for this operation to complete
   at ChameleonForms.AcceptanceTests.ModelBinding.ModelBindingShould.Function_correctly_with_default_form() in c:\TeamCity\buildAgent\work\81e762d276ae250c\ChameleonForms.AcceptanceTests\ModelBinding\ModelBindingTests.cs:line 16

```


So we are switching to 4 spaces?


This one -> https://github.com/INTproject2015/project-webtech


TeamCity ChameleonForms :: Continuous Integration [Build 261](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3664&buildTypeId=bt20) is now running


changed fadeTime  from 500 to 300, to make it looks more synced with old toptimes fading


Yes please.


test


No.


xD


wew didn't need this lulz needed -- > https://github.com/akhilnarang/scripts/commit/9101fc17d81e5e4531b67b103a575c0f5059529a :P


Not really, I think (though I'm not too sure about gcc). But if we are to delete them - after_failure should be removed too.


I need a pair, not a collection that I will need to join back again


@tambry just changing `sudo pip install cpp-coveralls;` to `sudo pip install cpp-coveralls requests[security];` should be fine if I'm not mistaken.


yo


Great٩( 'ω' )و


Join back? Why? May be you are not familiar with `limit` argument?


TeamCity ChameleonForms :: Continuous Integration [Build 1.2.1-PullRequest91+027](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3664&buildTypeId=bt20) outcome was **FAILURE**
Summary: Tests passed: 2590; NUnit runner failure (new) Build time: 0:0:0


Didn't work - happened again


But okay, this should be improved anyway later.


On which line did it return the incorrect game profile?
From what I can see all possible branches can only return valid game profiles...


Much appreciated!


Will the last element of result collection contain the whole string's tail?


// TODO: Add options so they can be passed in via the command line?


Ah ok.


@ZucchiniZe this has the potential to be ran multiple times. It is called by the DOM Mutation Observer whenever a change to the DOM is made. This means, there would be a ":wq" appended to the page every mutation. I would suggest moving this into the `window.ZRLIFY` block; It is guaranteed to only run once.


環境変数設定の行の先頭にハイフンが必要と思います。
    - secure: <long encrypted string here>


looks like

```javascript
      if (!tag) {
        // mount new
        tag = tags[i] = new Tag(impl, { // this created a reference in the old code
```

I have been trying to duplicate this with the new code by splicing a null in place, then setting `tag = tags[i] = new Tag` and if fixes the final test, but causes 3 server side tests to fail.  Any ideas on preserving the reference in a different way?


Leoasdsadg


I know @sindrenm is just aching to get in on this action, but he was on his phone and for some reason he can't GitHub on that.

He had this to say on Slack, though:

> I actually prefer predicate methods (methods ending with a question mark) to explicitly return `true` or `false`, but that might just be me. Not that I'm checking for `== true` or anything, it just “feels more correct” since it's a yes/no-question. Also Johannes is awesome.

I'm inclined to agree with him (in part because he's bigger than me and could beat me up with his index finger, but mostly because what he thinks makes sense).


Oops I missed the quotes. Good catch. I didn't test 64-bit python yet. Did you test on 64-bit yet @jherico ?


Is "format" causing a warning somewhere? Is it a reserved symbol in python? @jherico


On a related note, [Rubocop hates `!!`](http://www.rubydoc.info/github/bbatsov/rubocop/Rubocop/Cop/Style/DoubleNegation) and I completely disagree with it on this point.

```ruby
# bad
!!something

# good
!something.nil?
```

Really, Rubocop? `!something.nil?` is _terrible!_


can I pull it? I will have a look at it


TeamCity ChameleonForms :: Continuous Integration [Build 262](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3665&buildTypeId=bt20) is now running


`addEventListener` 使おう


I'd like to make Matrix4f a proper python container. But I'm torn between A) making it a container of 4 sets of 4 elements, just like in C/C++, or B) making it a container of 16 elements, like we actually want to use it... I'm inclined to make it a 4x4 container, but also keep this method, but with a better name like "toList16()" or something, to clarify its effect. @jherico


みた！


This should still be `CaptureTypes: building, husk`.    :?


 #[zstack Test Bot Report] P A S S
 Integration Test Result:
Test Summary:

 TestSuite|TestCase | Pass | Fail | Timeout | Skip
 ---------|---------| ---- | ---- | ------- | ----
 basic_test|__suite_setup__|0|1|0|0
basic_test|_basic/test_create_vm_|0|0|0|1
basic_test|_basic/test_stop_vm_|0|0|0|1
basic_test|_basic/test_start_vm_|0|0|0|1
basic_test|_basic/test_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_volume_|0|0|0|1
basic_test|_basic/test_add_vol_to_stopvm_|0|0|0|1
basic_test|_basic/test_add_volume_reboot_vm_|0|0|0|1
basic_test|_basic/test_add_multi_volumes_|0|0|0|1
basic_test|_basic/test_add_volume_negative_|0|0|0|1
basic_test|_basic/test_crt_temp_from_volume_|0|0|0|1
basic_test|_basic/test_crt_vm_with_volume_|0|0|0|1
basic_test|_basic/test_vm_securitygroup_|0|0|0|1
basic_test|_basic/test_create_iso_vm_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account_|0|0|0|1
basic_test|_account/test_crt_vm_by_normal_account2_|0|0|0|1
basic_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
basic_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
basic_test|_suite_teardown_|0|0|0|1
virtual_router_test|__suite_setup__|0|1|0|0
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
virtual_router_test|_novlan/test_create_vm_|0|0|0|1
virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_vlan/test_create_vm_|0|0|0|1
virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_snat_create_|0|0|0|1
virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
virtual_router_test|_vlan/test_start_vm_|0|0|0|1
virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
virtual_router_test|_volume/test_add_volume_|0|0|0|1
virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
virtual_router_test|_sg/test_ingress_|0|0|0|1
virtual_router_test|_sg/test_egress_|0|0|0|1
virtual_router_test|_sg/test_icmp_|0|0|0|1
virtual_router_test|_sg/test_udp_|0|0|0|1
virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
virtual_router_test|_sg/test_vm_ops_|0|0|0|1
virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
virtual_router_test|_sg/test_detach_l3_|0|0|0|1
virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
virtual_router_test|_pf/test_attach_pf_|0|0|0|1
virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_multi_rules_|0|0|0|1
virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
virtual_router_test|_pf/test_tcp_|0|0|0|1
virtual_router_test|_pf/test_udp_|0|0|0|1
virtual_router_test|_pf/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_2_eips_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
virtual_router_test|_eip/test_attach_eip_|0|0|0|1
virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
virtual_router_test|_eip/test_vm_ops_|0|0|0|1
virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
virtual_router_test|_lb/test_create_lb_|0|0|0|1
virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
virtual_router_test|_host/test_reconnect_host_|0|0|0|1
virtual_router_test|_suite_teardown_|0|0|0|1
local_ps_virtual_router_test|__suite_setup__|0|1|0|0
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_ps_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_ps_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_ps_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_ps_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_ps_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_ps_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_udp_|0|0|0|1
local_ps_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_ps_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_ps_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_ps_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_ps_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_ps_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_ps_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_ps_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_udp_|0|0|0|1
local_ps_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_ps_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_ps_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_ps_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_ps_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_ps_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_ps_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_ps_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_ps_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_ps_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_ps_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_ps_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_ps_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_ps_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_ps_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_ps_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_ps_virtual_router_test|_suite_teardown_|0|0|0|1
local_nfs_virtual_router_test|__suite_setup__|0|1|0|0
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_account/test_vm_ops_by_normal_account_|0|0|0|1
local_nfs_virtual_router_test|_account/test_multi_accounts_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_novlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_snat_create_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_dnat_reboot_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_ping_vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_create_3vms_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_3l3s_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_remove_dhcp_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_2l3_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.0_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vms_with_limited_ips2.1_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_start_vms_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_crt_vm_with_hostname_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_reboot_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_chg_static_ip_vm_|0|0|0|1
local_nfs_virtual_router_test|_vlan/test_attach_nic_with_static_ip_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_m_vols_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_add_volume_vr_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_volume_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_2_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_24_volumes_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_volume_ops_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_volume/test_crt_vm_from_dvt_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_crt_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_template_image/test_del_temp_image_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_icmp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_egress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_2vm_ingress_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_4vm_complx_|0|0|0|1
local_nfs_virtual_router_test|_sg/test_detach_l3_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_2l3s_pfs_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_attach_pf_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_delete_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_del_vip_before_add_pf_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_pfs_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_multi_rules_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_after_destroy_vm_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pf_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_udp_same_vip_ports_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_pfs_tcp_with_same_vip_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_tcp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_udp_|0|0|0|1
local_nfs_virtual_router_test|_pf/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eip_pf_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_2l3s_eips_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_attach_eip_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_create_eip_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_del_vip_before_add_eip_to_vm_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_eip_sg_tcp_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_pf_eip_attach_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops_|0|0|0|1
local_nfs_virtual_router_test|_eip/test_vm_ops2_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_alone_vr_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_source_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_create_lb_|0|0|0|1
local_nfs_virtual_router_test|_lb/test_lb_health_check_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_sp_after_delete_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_create_image_by_snapshot_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_for_both_root_..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm2_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm3_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_delete_snapshot_on_ru..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_in_live_vm_|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_crt_sp_from_vol_crt_f..._|0|0|0|1
local_nfs_virtual_router_test|_snapshot/test_change_max_sp_depth_l..._|0|0|0|1
local_nfs_virtual_router_test|_regression/delete_sg_with_2_attache..._|0|0|0|1
local_nfs_virtual_router_test|_regression/rm_nic_sg_on_stopped_vm_|0|0|0|1
local_nfs_virtual_router_test|_regression/test_data_volume_with_vm..._|0|0|0|1
local_nfs_virtual_router_test|_vr/test_ping_vms_reboot_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_reconnect_vr_|0|0|0|1
local_nfs_virtual_router_test|_vr/test_start_vrs_simultaneously_|0|0|0|1
local_nfs_virtual_router_test|_host/test_reconnect_host_|0|0|0|1
local_nfs_virtual_router_test|_suite_teardown_|0|0|0|1
Total|304|0|4|0|300


@jherico There is a lot of custom string code here! Can you describe to me the problem it solves? I recently noticed that ctypes has a special "c_char_p" type that might be a bit more string friendly than POINTER(c_char). I would prefer to use c_char_p if possible. If not, I'd like to create a unit test to prove that the custom string is needed.


I see. Yeah, I think I agree with predicate methods should return `true` or `false`. Probably I should just revert that commit and keep this pull request about AS stuff only. Wdyt?

PS. @jgorset something is wrong with your Slack's copy/paste technique. Looks like it randomly adds something about  Johannes being awesome. Weird.


coreでは

```javascript
return  fetch(url)
  .then(function(res){
    return res.json();
  });
```

てな感じにしといて、呼び出し側で

```javascript
core('image/search', query, "GET")
  .then(function(images) {
    //正常時の処理
  })
  .catch(function(err){
    //エラー時の処理
  });
```

としたほうがスマート


TeamCity ChameleonForms :: Continuous Integration [Build 1.2.1-PullRequest129+032](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3665&buildTypeId=bt20) outcome was **FAILURE**
Summary: Tests passed: 2559; compilation error: ChameleonForms\ChameleonForms.csproj (new); compilation error: ChameleonForms.Tests\ChameleonForms.Tests.csproj (new); compilation error: ChameleonForms.AcceptanceTests\ChameleonForms.AcceptanceTests.csproj (new) Build time: 0:0:0


というか、なるべく `callback` をなくすのが重要

```javascript
methodA(hoge, function(res, err){
  methodB(hoge, function(res, err){
    methodC(hoge, function(res, err){
      methodD(hoge, function(res, err){
      });
    });
  });
});
```

みたいに、ネストがどんどん深くなっちゃうから、thenでつなぐように意識！


I think your suggestion to replace `? true : false` with `!!` is great, actually. In your face, Rubocop!

PS: Hø hø hø.


What happened to v1.3? Also, does this add interfaces (if not, would be v1.2a not v1.3 anyway)?


Add it to index.htm


TeamCity ChameleonForms :: Continuous Integration [Build 263](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3666&buildTypeId=bt20) is now running


Please write backwards compat like `Gundo = gundo-vim;`


sure


TeamCity Colore :: Main Build [Build 151](http://tc.sharpblade.net/viewLog.html?buildId=694&buildTypeId=colore_mainbuild) is now running


cool. Would be nice to separate your stuff and put up different PR´s for each of those. Please dont make a squashed PR.


`console.error(err)` を使えば、エラーは赤い背景で表示できる！


TeamCity ChameleonForms :: Continuous Integration [Build 1.2.1+032](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3666&buildTypeId=bt20) outcome was **FAILURE**
Summary: Tests passed: 2559; NUnit runner failure (new) Build time: 0:0:0


On 3 October 2015 at 14:39, Joseph Wright <notifications@github.com> wrote:

> What happened to v1.3? Also, does this add interfaces (if not, would be
> v1.2a not v1.3 anyway)?
>

oh sorry I incremented it at the start, and then again at the end of the
coding session....

"add interface" depends how you define add, since it wasn't usable
previously. but 1.2a would be Ok too if you prefer.


Why `addInsidePolygon` instead of `searchInsidePolygon`?


Did it.


Don't get the difference


I've tended toward using `<rewrite>.<added-features><fixed-bugs>`, so to me 'it didn't work' isn't an API change so is a letter on the end :-)


TeamCity Colore :: Main Build [Build 151](http://tc.sharpblade.net/viewLog.html?buildId=694&buildTypeId=colore_mainbuild) outcome was **SUCCESS**
Summary: Tests passed: 111 Build time: 0:5:47


We are gonna put phone number and stuff.


Eh maybe I was just dumb when I did that. I thought I had a reason.
On Oct 3, 2015 4:43 AM, "Dario" <notifications@github.com> wrote:

> Does it change the behavior from the old code? From my understanding it
> would do the break outside the 'if latch_target == nil' so I moved it inside
>
> Also if it prefers units further away then line 38 needs to be changed
> from FIND_ANY_ORDER to FIND_FARTHEST so that the first unit in the table is
> the farthest one
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Pizzalol/SpellLibrary/commit/80edc821527fd5f129e7def90d51b5d8dd0ff48a#commitcomment-13575057>
> .
>


i planed to squash to two commits: guilib and confluence.


Thanks to @stevengj


that sounds fine. Please do two separate PR´s for those. (first we try to get core changes in, next step would be confluence changes then)


I think you want to do this instead:

```
self.currentMatch.names[0] = self.currentMatch.names[0].replace(',','');
```

([Reference](http://www.w3schools.com/jsref/jsref_replace.asp))

Also, it's probably better to do it in the Strategy constructor, [here](https://github.com/synkarius/saltbot/blob/master/src/strategy.js#L6). If you do it in the Strategy constructor, I don't foresee there being any betting problems created.


Hi, I'm the creator of SaltBot. I just wanted to stop in and say, I tried out your branch, and I really like what you're doing with the UI.


i will make some test, and PR tomorrow.


TeamCity ChameleonForms :: Continuous Integration [Build 264](http://ci.robdmoore.id.au:8010/viewLog.html?buildId=3667&buildTypeId=bt20) is now running


I think the problem with the errors is we are doing a redirect here instead of a render.


Ahhh. Now i sea


Because we are using Checklist.new here, it's always carrying that to the form rather than using the one that errored out.


We'll need to change this form to use @checklist, and set @checklist to Checklist.new in the controller's index method. Then when we do a render instead of a redirect in the create when it fails, it will use the @checklist that has the errors associated with it and render the validation messages.


tu peux simplifier ça en mettant `return {kernel, kWidth, kHeight};`


have you pushed all your stuff?


I just want to point out that this is a breaking change from 2.0 to 2.1. It broke the acceptance test project for xbehave when I upgraded, see https://github.com/xbehave/xbehave.net/blob/b43e466983df54d17a6de4d04626f66a9ce04077/src/test/Xbehave.Test.Acceptance.Net40/Infrastructure/Feature.cs#L108

Having said that, my direct usage of this is probably an edge case. I guess it could be fixed it by releasing a patch with a defaulting overload but I'll leave it to others to judge the ROI on that :wink:


Oooh! Thanks! Learned something new. :heart:


do you want the fix to the one test that breaks the other 3?


TeamCity Colore :: Main Build [Build 152](http://tc.sharpblade.net/viewLog.html?buildId=695&buildTypeId=colore_mainbuild) is now running


Ok let me check if I could fix the current release first thanks


TeamCity Colore :: Main Build [Build 152](http://tc.sharpblade.net/viewLog.html?buildId=695&buildTypeId=colore_mainbuild) outcome was **FAILURE**
Summary: NUnit error running tests in 'C:\TeamCity\buildAgent\work\be266160709880ba\Corale.Colore.Tests\bin\x86\Debug\Corale.Colore.Tests.dll' assembly
Loading assembly is compiled for v4.0.30319, x86
NUnit runner runtime is v4.0.30319, x64
System.BadImageFor... Build time: 0:0:31


@foolip do you remember why we added `required` here? It seems unusual for event init dicts.


Merged here, right now.


* TODO: Refactor the validator to reduce duplication, maybe move the askWithValidation to a generic class


Текст оставим всё-таки


@j-martyn Кнопка cancel не работает в диалогах, тенька стала некрасивая (сзвиг справо вниз), не такая, как с старых версиях IAS


Haven't tried running this yet; Is the double `nvm nvm` a typo?


Thanks for catching this. We landed a fix for it over in https://github.com/addyosmani/es6-equivalents-in-es5/pull/28.


Символ кружка


Can we wrap arguments, NodeList etc. in backticks? i.e `arguments`


TeamCity Colore :: Main Build [Build 153](http://tc.sharpblade.net/viewLog.html?buildId=696&buildTypeId=colore_mainbuild) is now running


so its this?
AuctionEntryMap::iterator newItr = itr;
newItr++;
itr->second->AuctionBidWinning();
itr = newItr;
?


TeamCity Colore :: Main Build [Build 153](http://tc.sharpblade.net/viewLog.html?buildId=696&buildTypeId=colore_mainbuild) outcome was **FAILURE**
Summary: Tests passed: 111; cannot start build runner; NUnit runner failure (new) Build time: 0:0:31


Arrow functions weren't present in ES5. Ideally, you will want to show the non-arrows idiom here.


Thanks a lot for your awesome work!
But currently I'm too busy to hack on the device, I'll try ASAP

2015年9月27日星期日，Rudolf Tammekivi <notifications@github.com> 写道：

> Tagging @dianlujitao <https://github.com/dianlujitao>
> I was able to get NFC running with this (writing/reading NFC tags works),
> check https://github.com/Blefish/NfcDNci for the source of the changes to
> the app. I think resources should be updated and we could use the NfcNci
> resources for this.
>
> I cleaned com.android.nfc.helper.jar and removed all stuff that was not
> used by the NfcDNci. Possibly this can be open sourced but I have no time
> right now.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Blefish/android_device_huawei_g620s/commit/76e578b8ac6ff922316d2e4ef0464fa1636d141d#commitcomment-13455478>
> .
>


`var divsArray = [].slice.call(document.querySelectorAll("div"));`?


same ES6 arrow function comment as earlier. Drop in favor of the more verbose ES5 pattern.


The invalid-email-address can be attributed to the git profile on the vm instance of this build not having the same details. this has now been corrected.


TeamCity Colore :: Main Build [Build 154](http://tc.sharpblade.net/viewLog.html?buildId=697&buildTypeId=colore_mainbuild) is now running


TeamCity Colore :: Main Build [Build 154](http://tc.sharpblade.net/viewLog.html?buildId=697&buildTypeId=colore_mainbuild) outcome was **SUCCESS**
Summary: Tests passed: 111 Build time: 0:0:46


@alwey Ok, thank you. Yesterday I misunderstood everything you wrote.


@aquette In the future, we might want to have DDL entries for pre-release driver versions exist on a separate branch. That way, we can update the NUT website with the DDL for the latest release, but not confuse people who are looking for currently-supported devices. Or maybe a `stable` branch for the production website, since we apply source code changes to `master`?

Also, the DDL convention is to add "@ version" to the first line of the commit message, which doesn't help much in this situation.


Well is a habit of mins to put "eXtended" object in xobjects and xdwidgets etc..

But where should they go..?? I dont know, what to you suggest ?


That would be too easy.  There is no python3.exe on Windows.

But you can cheat: the `py.exe` launcher is included since Python 3.3, and it’s also guaranteed to be in %PATH%.  Which is exactly what we need.


okay~~


the message should appear in both cases IMO


Ok..  but sorry to mess things up..
Maybe you should merge to develop, and I'll put in PR requests..


@devhell sorry, you're right, I added those flags to wrong place. Fixed with: 4e9f5328a5a08e6f0c3c20f54ced49aad5d10635


this is Θ(n^2).


All tests were quite neutral, but promising because different functions give similar results. That's why I'm starting tuning 6 by 6 moves, and then 6 by 6 depths, starting from default values, until some progress will be noticeable. This will be a long struggle, and I'll try to find a compromise between not giving up and not to run my tests too frequently. I suppose that SPSA won't give me a global maximum, but will indicate some directions for improvements.

Thank you for any comment or advice, anything can be helpful.

There is no significant progress any more for moves 1-6, and I'm now going to tune moves 7-12.


Why $cityEntity?


Update Butterknife


Well, I would rather not do that, which may feel a bit aggressive, when the user doesn't have py3 installed and may be in trouble upgrading.


index out of range. what result are you expecting?


Dear Benedikt,

that change isn't doing well, given that 8 lines below, the call to get_relval() is doing something similar (dividing by 256), hence resulting in strange behaviour, since handle_sync_error cannot work as expected anymore.


Oh, I had already fixed this in #366. I'll tag that instead.


base on your function, user expect to get true or false

Date: Sat, 3 Oct 2015 07:28:25 -0700
From: notifications@github.com
To: DailyPractice@noreply.github.com
CC: jackhwl@hotmail.com
Subject: Re: [DailyPractice] # did you try is_friend('') ? (6c6988c)

index out of range. what result are you expecting?

—
Reply to this email directly or view it on GitHub.


@aycanirican No problem. The build is successful now. Thank you!


You can check thumbnail generation process in source. Just revert for yourself if you thing this is useless.


* TODO: Refactor the validator to reduce duplication, maybe move the askWithValidation to a generic class


Good! But I realized that I have to move the new module 'camunda-typed-value' to another git repository to use it inside the dmn engine. So I will move it first and then fix the configs for wildfly, tomcat etc.


Pow cara pq vc colocou em ingles?


TeamCity Colore :: Main Build [Build 155](http://tc.sharpblade.net/viewLog.html?buildId=698&buildTypeId=colore_mainbuild) is now running


TeamCity Colore :: Main Build [Build 155](http://tc.sharpblade.net/viewLog.html?buildId=698&buildTypeId=colore_mainbuild) outcome was **SUCCESS**
Summary: Tests passed: 111 Build time: 0:1:45


Nice one :+1:


:pray


Perdone profesor, durante este fin de semana lo haré, un cordial saludo,

Lorenzo Manuel Rosas Rodríguez.
El 3/10/2015 10:50, "Juan Julián Merelo Guervós" <notifications@github.com>
escribió:

> Pon ciudad y uni en el perfil y actualiza el avatar, por favor.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/JJ/IV-2015-16/commit/d2ba7630817634e8f1b2e290868dc287899dd2ec#commitcomment-13574909>
> .
>


Too complicated here!


I had the button because the exit button is disabled, and you need an option for the menu to even display. So I made the exit button a button.


What?


And also, you can close it


Typo in the ingredients list!


To express with more clarity, as words are imprecise, something like this: https://github.com/aspnet/KestrelHttpServer/pull/239


yeah, i got lazy.


@mbootsector : my logic is that the author of the patch work on it, and that we all give suggestions. I'll always do so, unless asked otherwise, and I think this is good for the development of Stockfish.


MenuAction_End is only called when you hit the exit button that is off, afaik


Tabs instead of spaces :(


you tell me - i don't know why that happened: i had copied the cache file from attic and borg ignored that and went on to create the monstruous `chunks.archive.d` i described in #235....

the point of this patch is to make people just aware that the first backup may take longer. furthermore, `borg check --repair` is *not* necessary after the conversion.


TeamCity Colore :: Main Build [Build 156](http://tc.sharpblade.net/viewLog.html?buildId=699&buildTypeId=colore_mainbuild) is now running


then that wouldn't work if we're trying to resume a failed conversion...


I'm getting gtk-doc in there, but it's atop a different set of commits...


Yeah. But the homework numberd 001, 002......, I only pasted whatever I did
on Udacity for future review if needed, and the assignment has the
limitation so that I don't need to count in all the exceptions. ;)

On Sat, Oct 3, 2015 at 10:31 AM, Jack Huang <notifications@github.com>
wrote:

> base on your function, user expect to get true or false
>
> Date: Sat, 3 Oct 2015 07:28:25 -0700
> From: notifications@github.com
> To: DailyPractice@noreply.github.com
> CC: jackhwl@hotmail.com
> Subject: Re: [DailyPractice] # did you try is_friend('') ? (6c6988c)
>
> index out of range. what result are you expecting?
>
>
> —
> Reply to this email directly or view it on GitHub.
>
>
>
>
>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/LizzyYao/DailyPractice/commit/6c6988c1fc47df795148a50f1ec5b6af5a9e9a5a#commitcomment-13575974>
> .
>


go!


TeamCity Colore :: Main Build [Build 156](http://tc.sharpblade.net/viewLog.html?buildId=699&buildTypeId=colore_mainbuild) outcome was **SUCCESS**
Summary: Tests passed: 111 Build time: 0:1:49


I'm thinking I won't accept your pull request as is, but rather keep it for reference, because I have a few adjustments I want to make to the suggested API. In other words, you don't have to keep adding changes.

Thanks for this one, though.


No way! :+1:


GH


Hi. I didnt found your email, so if you dont mind I'll ask here.
Is it you who found a way to unlock the bootloader for mx4/m1 note?
I have m2 note and some experience in cyanogenmod building from sources (previously i developed cm9/10/10.1/11,, roms for huawei mediapad from scratch), The only problem now in closed bootloader..
I will be glad for any help regarding this problem, thx in advance.


If you don't merge other commits related to "toolbar button", the minimize button,maximize button and close button will not show the same color as titlebar.


We'll keep it this way for the moment.

Actually the current namespace is not optimized at all (have circular references all the time (between position, route and trackitem for instance), long doted path to single class, etc.) and we'll need to change it all to something simpler. The current namespace is just the copy of the file organisation that existed at the beginning of ts2 when it was coded in C++ (yes, it was, up to v0.2 !) but is not appropriate for python.

Any ideas/recommendations are welcomed !


Ok, it was probably interaction with https://github.com/dezgeg/nixpkgs/commit/67c9bc422c361acb38aa5815a23cf52112c34b21 then.


Oh yeah. whoops. B-)


我这里是用的react 1.4 rc


You must resync again. Your are deleting newly added code (e.g. the explanation of the use of Docker).