Wow! Knocked it out of the park - the cite looks great! I left some comments above, let me know if you have any additional questions!

#FEWD Week #2 Project: Styling with CSS

---

###Description

A hot, new NY Tech Startup, Relaxr, has approached you to help them develop a new landing page for their company. They've handed you the design file for the site, along with the copy and assets. You need to take these files and turn it into a landing page.

Student: Nathan Keeys

|                                                                                |                                |                        |                          |
|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------|--------------------------|
| Technical Requirements                                                                                | Does Not Meet Expectations (0) | Meets Expectations (1) | Exceeds Expectations (2) |
| Use HTML5 structural elements (nav, header, footer)                                                                           |                                |                        |            X              |
| Use a CSS Reset file in addition to your style.css file to style the page                                                     |                                |                        |            X              |
| Use IDs and Classes to to select and style elements on the page                                                               |                                |                        |            X              |
| Style your text with the Google Fonts provided by your style guide                                                            |                                |                        |            X              |
| Follow naming conventions, maintain consistency across .html and .css files and use best practices for naming IDs and Classes |                                |                        |             X             |
| Indent nested elements to increase your code's readability                                                                    |                                |           X             |                          |
| Use width, padding and margin on at least two block elements on your page                                             |                                |                        |              X            |
| TOTAL: *13*/14                                                                                |                                |                        |                          |


Here is a suggested reading： http://www.pearsonhighered.com/samplechapter/032126889X.pdf


I have a few more changes that I may not have pushed yet. When I'm in my
office in Monday I will make sure everything is up to date and I will look
at the min width
On Sat, Oct 10, 2015 at 6:25 PM Rahul Gupta <notifications@github.com>
wrote:

> @ben0910 <https://github.com/ben0910> , Thanks for your support, i am
> using your code for aspect ratio, but i have a issue can you please tell me
> how to set _minSize to image actual with, by default _minSize = 80 in
> crop.factory('cropArea', ['cropCanvas', function(CropCanvas) {}
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/ben0910/ngImgCrop/commit/2d5952d5e34c4c1831407b4c0847fab365ba2b4f#commitcomment-13702669>
> .
>
--
Ben Rubin
215.776.2706


oh, now i got it.


nit: line 132 is now unreachable


This doesn't block it properly
https://www.owasp.org/index.php/XSS_Filter_Evasion_Cheat_Sheet#Non-alpha-non-digit_XSS


this is presumably also present on release-0.4? cc @juliabackports

could use a test that hits these branches


this code is fine.


Thanks for the advice, will fix this soon!


I have no problem with copying gaff's strategy. I'm assuming you have a fix in mind to train on every tick. If it's something I can implement on my own, let me know and I'll work on it.


Fixing all the database and model to match the planned schema


just understood this one too. code is fine.


I'd consider this a "base style". I usually think of styles on a single html tag as "base styles".


TeamCity ReOpenLDAP :: devel-2.4 [Build 199](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=926&buildTypeId=ReOpenLDAP_Devel24&guest=1) is now running


Hi Kyle, I dont know whats going on, but I have multiple errors(Raspbian Wheezy) while trying to operate with notes functions.
Here is part of Apache error.log
```
/var/log/apache2/error.log                                                                                2870/2870              100%
[Sun Oct 11 02:04:21 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/mycodo.php on line 3485, referer: https://192.168.0.10/mycodo/
[Sun Oct 11 02:04:21 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/mycodo.php o
n line 3487, referer: https://192.168.0.10/mycodo/
[Sun Oct 11 02:04:23 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/mycodo.php on line 3485, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:04:23 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/mycodo.php o
n line 3487, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:04:54 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/mycodo.php on line 3485, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:04:54 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/mycodo.php o
n line 3487, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:04:55 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/mycodo.php on line 3485, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:04:55 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/mycodo.php o
n line 3487, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:05:01 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/mycodo.php on line 3587, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:05:01 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/mycodo.php o
n line 3589, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:05:02 2015] [error] [client 192.168.0.2] PHP Warning:  SQLite3::query(): Unable to prepare statement: 1, no such table: Uploads in /home/pi/Mycodo/3.5/include
s/restricted.php on line 2671, referer: https://192.168.0.10/mycodo/?tab=data
[Sun Oct 11 02:05:02 2015] [error] [client 192.168.0.2] PHP Fatal error:  Call to a member function fetchArray() on a non-object in /home/pi/Mycodo/3.5/includes/restricted.p
hp on line 2673, referer: https://192.168.0.10/mycodo/?tab=data
```


@ezakto de nada, gracias a ti por compartir compañero 👍


This is good. You could also use a `<button>` tag.


Looks like you have a misplaced `</span>`


Nice use of the `<small>` tag!


Ok, Im stupid, I forgot to update from Mycodo software...


The Dev-1.0 branch doesn't output it anymore. That was fixed like a week or 2 ago.


Yes, I think you should elaborate a bit more on the difference in terms of software specification between the two.


Working great now!


Really awesome work. Site is pretty much exactly to spec! I left some comments up above, but other than that, I don't have a lot to add. Let me know if you have any other questions!

#FEWD Week #2 Project: Styling with CSS

---

###Description

A hot, new NY Tech Startup, Relaxr, has approached you to help them develop a new landing page for their company. They've handed you the design file for the site, along with the copy and assets. You need to take these files and turn it into a landing page.

Student: Saline Jiang

|                                                                                |                                |                        |                          |
|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------|--------------------------|
| Technical Requirements                                                                                | Does Not Meet Expectations (0) | Meets Expectations (1) | Exceeds Expectations (2) |
| Use HTML5 structural elements (nav, header, footer)                                                                           |                                |                        |            X              |
| Use a CSS Reset file in addition to your style.css file to style the page                                                     |                                |                        |             X             |
| Use IDs and Classes to to select and style elements on the page                                                               |                                |                        |              X            |
| Style your text with the Google Fonts provided by your style guide                                                            |                                |                        |              X            |
| Follow naming conventions, maintain consistency across .html and .css files and use best practices for naming IDs and Classes |                                |                        |             X             |
| Indent nested elements to increase your code's readability                                                                    |                                |                        |          X                |
| Use width, padding and margin on at least two block elements on your page                                             |                                |                        |         X                 |
| TOTAL: *14*/14                                                                                |                                |                        |                          |


@boomstick8x Good to hear! :)

Why update another way?


@frol sorry, I should have saved you the trouble and made a pull request may be. It is much simpler to switch back to using your image ;)


Try to use consistent indentation throughout your CSS files


@sventschui Watch out, you committed this with pretty weird author information.


Well done centering an inline element!


I have finished my part --- Dataset  [Dataset part.pptx](https://github.com/GiannisPapadopoulos/DiscriminativePatches/files/11344/Dataset.part.pptx)


You could use the `background` shorthand to do this all in a single line


afais `vcs-snapshot` is obsolete here, since we get the pypi tarball


wops, this was not supposed to go to this repository. Can this be reverted?


remove this


For whatever reason, we don't usually capitalize the first letter of classes, so `amandaQuote` may be a better choice for this class name


Because I have a copy of your repo and my working Mycodo cloned from my repo, and when newer version available I get it by: 'git fetch --all' and then `git pull upstream master` for me is faster then clicking tabs. But now I will remember :)


you can't use shorthand on `font-weight`, but you can using `font`


Вопрос тот же. Вылетает исключение о неизвестном хосте: UnknownHostException где-то через 50-200 запросов. Всегда по-разному.


No you shouldn't need to also put bold. In fact that would probably cause your font to look less "good". The difference from the mock might be a mistake


In that case, just make sure you update the databases with `./update-database.py -i update`
There may also be commands in update-post.sh that may need to be executed after updating. There might be more going on but I can't think of anything off the top of my head.


oh? hmm wierd i was using /help test 1 2 3 to fire it.
Probably dont need it now anyway, your epic commit pretty much replaces it.


Why? "br" is the abbreviation for Brazil. This is just confusing. I can't think of any collision or ambiguity for "bro". Please explain.


cool, I think this is a totally valid use of the `footer` tag. You could also use the `<cite>` tag.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.653](http://teamcity.monogame.net/viewLog.html?buildId=10519&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


You are all spies


I'd probably use CSS `margin` instead of `<br/>` tag here


Impressive. Do you have something that generates this?


Really great work! You've knocked this out of the park. I don't really have anything to add other than the things I mentioned in the comments above. Let me know if you have any questions!

#FEWD Week #2 Project: Styling with CSS

---

###Description

A hot, new NY Tech Startup, Relaxr, has approached you to help them develop a new landing page for their company. They've handed you the design file for the site, along with the copy and assets. You need to take these files and turn it into a landing page.

Student: Savanna Rovira

|                                                                                |                                |                        |                          |
|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------|--------------------------|
| Technical Requirements                                                                                | Does Not Meet Expectations (0) | Meets Expectations (1) | Exceeds Expectations (2) |
| Use HTML5 structural elements (nav, header, footer)                                                                           |                                |                        |         X                 |
| Use a CSS Reset file in addition to your style.css file to style the page                                                     |                                |                        |         X                 |
| Use IDs and Classes to to select and style elements on the page                                                               |                                |                        |         X                 |
| Style your text with the Google Fonts provided by your style guide                                                            |                                |                        |          X                |
| Follow naming conventions, maintain consistency across .html and .css files and use best practices for naming IDs and Classes |                                |                        |            X              |
| Indent nested elements to increase your code's readability                                                                    |                                |                        |            X              |
| Use width, padding and margin on at least two block elements on your page                                             |                                |                        |            X              |
| TOTAL: *14*/14                                                                                |                                |                        |                          |


Now I will always make updates with Update button, also because of creating Backups!
p.s. Kyle, thank you million times for your project and working out on it! :)


It should be version 0.1.7


This one was a bad idea


This was simply wrong: ```Content-Type: text/Calendar, charset=UTF-8``` instead of ```Content-Type: text/Calendar; charset=UTF-8```


i see you are fixing things. i like to fix things too!


Plot 2


I realized that I shouldn't delete User Queue as we use it for "Your Queues". Will restore them now.


Oops thanks


hahaha


some line note


You are assuming a Player here. Do first(blah).orElse(null) and check it.


plots


That's plain stupid. People who are offended by a HTTP header accidentally named like a slang word for a (male) friend have serious mind issues and should go see a doctor instead of being kept happy by developers.


Some of the motivation of the change can be read in https://bugzilla.mozilla.org/show_bug.cgi?id=366559

While 'bro' seems like a good abbreviation from my Nordic/Central European viewpoint, several people from North America expressed concerns. We needed a name *now*, and 'br' carries less risk to backfire at IANA registration. 'br' is also one less byte than 'bro', and clients need to upload these bytes to the server even when brotli is not supported by the server.


The motivation of the change makes me palm my face.


You're welcome! It's great to know others find it useful.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.653](http://teamcity.monogame.net/viewLog.html?buildId=10519&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 539, ignored: 6 Build time: 00:19:27


Why do you have a click handler in a table?


Why do you have a click handler here too? Are you even reading the class name?


This name is too confusing, name it setHint or something


Wrong.


@jyrkialakuijala You do realize that by immediately bending to peoples' will when they "express concern" (what a political way of putting it) over something, you are just making the problem worse. These people aren't gonna stop there.


Wrong. Init from constructor, make it final too


Fuck u Google!!


you didn't fix anything, liar


This wasn't tested.


I suggest using /* package */ here to clarify the visibility


@matjames007 can you just create an issue in Github now to capture that suggestion. That way we can add it to the roadmap.


or wrap with an `if (event.getCause().any(Player.class)) {`


La transition css du updateList et du deleteList durent trop longtemps, on a l'impression que rien ne vas se passer. A revoir...


I find the letters "br" extremely offensive for no particular reason. Please change it. I'm sure it won't be an issue for such a progressive project.


dfad


I am a nice comment


Lol. I meant that the reason behind the error was that.
But yes, it is better to just say that.


I am concerned by the cultural appropriation that is a connotation of using the country code of Brazil for this.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 243](https://teamcity.mesosphere.io/viewLog.html?buildId=56779&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:38


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 242](https://teamcity.mesosphere.io/viewLog.html?buildId=56778&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:47


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 245](https://teamcity.mesosphere.io/viewLog.html?buildId=56781&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:42


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 244](https://teamcity.mesosphere.io/viewLog.html?buildId=56780&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:56


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 246](https://teamcity.mesosphere.io/viewLog.html?buildId=56782&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:52


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 248](https://teamcity.mesosphere.io/viewLog.html?buildId=56784&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:51


What does VW stand for? Could someone explain why this is needed at all?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 249](https://teamcity.mesosphere.io/viewLog.html?buildId=56785&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:50


Sorry for the oversight. I hope it's all okay now?


@praneethkumarpidugu I plan to use [Ionic framework](http://ionicframework.com/) which is a wrapper of PhoneGap and AngularJS.
That way you can build native mobile application using web-application. And here I want to re-use the code of the front-end app.


当时测的是X220.
entrypoint或者relative entrypoint是程序入口点相对于文件开头的偏移，你要修改的话应该用编辑器打开文件，定位到这个位置，然后修改那个字节为0xc3.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 250](https://teamcity.mesosphere.io/viewLog.html?buildId=56786&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:55


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 257](https://teamcity.mesosphere.io/viewLog.html?buildId=56794&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:04


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 258](https://teamcity.mesosphere.io/viewLog.html?buildId=56795&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:13


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 251](https://teamcity.mesosphere.io/viewLog.html?buildId=56787&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:52


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 259](https://teamcity.mesosphere.io/viewLog.html?buildId=56810&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:31


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 260](https://teamcity.mesosphere.io/viewLog.html?buildId=56811&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:29


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 247](https://teamcity.mesosphere.io/viewLog.html?buildId=56783&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:06:36


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 261](https://teamcity.mesosphere.io/viewLog.html?buildId=56834&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:07


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 264](https://teamcity.mesosphere.io/viewLog.html?buildId=56836&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:07


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 262](https://teamcity.mesosphere.io/viewLog.html?buildId=56833&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:16


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 263](https://teamcity.mesosphere.io/viewLog.html?buildId=56835&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled (Exit code 137 (new)) Build time: 00:00:11


The parameter order is the same as the [Promises/A+ specification](http://promisesaplus.com) and the [ES6 Promise standard](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 252](https://teamcity.mesosphere.io/viewLog.html?buildId=56788&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:36


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 265](https://teamcity.mesosphere.io/viewLog.html?buildId=56853&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:07


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 266](https://teamcity.mesosphere.io/viewLog.html?buildId=56865&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:08


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 253](https://teamcity.mesosphere.io/viewLog.html?buildId=56789&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:41


I agree this method is redundant, but is common in promise implementations. The [ES6 Promise standard](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) includes a `catch(onRejected)` method that is simply a shortcut for `then(null, onRejected)` I don't feel very strongly either for or against having a separate method for assigning a callback for rejection. The interface certainly could function without it.


Could you please run the corefx tests - in particular the ones for System.IO contract that exercise this codepath?

https://github.com/dotnet/coreclr/blob/master/Documentation/building/testing-with-corefx.md


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 255](https://teamcity.mesosphere.io/viewLog.html?buildId=56791&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:53


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 254](https://teamcity.mesosphere.io/viewLog.html?buildId=56790&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:57


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 256](https://teamcity.mesosphere.io/viewLog.html?buildId=56792&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:57


By remove, of course, we mean, mark the object and any newly obsolescent deps as removed. Filtering the requiredBy has some small effect, but the `child.removed` flagging is actually much more important as we'll see…


:100: :x: :100:


What's wrong with depending on bash? It's not needed at runtime, after all.


add "else" to quit?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 268](https://teamcity.mesosphere.io/viewLog.html?buildId=56879&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:39


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 269](https://teamcity.mesosphere.io/viewLog.html?buildId=56884&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:41


Historically we were filtering a module out of the _children_, that is, the disk part of the tree representation, but only when running `npm install module@newversion`. This was pointless previously, as we already had to be able to handle that when a `package.json` necessitated a version change. Further it hid information from us later…


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 270](https://teamcity.mesosphere.io/viewLog.html?buildId=56887&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:56


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 267](https://teamcity.mesosphere.io/viewLog.html?buildId=56868&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:08


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 271](https://teamcity.mesosphere.io/viewLog.html?buildId=56894&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 187 Build time: 00:03:57


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 273](https://teamcity.mesosphere.io/viewLog.html?buildId=56896&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:54


a


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 274](https://teamcity.mesosphere.io/viewLog.html?buildId=56897&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:54


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 272](https://teamcity.mesosphere.io/viewLog.html?buildId=56895&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:27


awesome..hope I could learn through your commits.


Keep my old message. OLD COOT.


Thanks.


Without the above change, replaceModule wouldn't see this as a replacement because the module wouldn't be in the children, and as such `replaced` would always be empty.


So... do they loop or work? :p


:+1:  Thanks for your hard work!


asdfafdasdf


This should instead be included in the <head> tag section of the patients/summary_pat_portal.php script.

And will need to translate it with:
``````
<?php echo xlt('Patient Information'); ?>


missing "else" ??

```
if (!(dataItem instanceof observable.Observable)) {
            item.bindingContext = null;
} else {
            item.bindingContext = dataItem;
}
```


此处请修改


Stuck looping at 3ds boot logo on 4.5-9.2 old3ds.
New3ds; all works well.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 275](https://teamcity.mesosphere.io/viewLog.html?buildId=56898&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:08


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 276](https://teamcity.mesosphere.io/viewLog.html?buildId=56899&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:53


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 279](https://teamcity.mesosphere.io/viewLog.html?buildId=56902&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:48


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 277](https://teamcity.mesosphere.io/viewLog.html?buildId=56900&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:54


haha yeah fair enough will make the chainge


it shouldn't be an issue unless you explicitly use secondary parameters (eg: logout).  I made this pull because niemal wanted support for a logout parameter in addition to the mode.   You may want to talk to him if secondary parameters are a problem.

As it stands though, key will get the first name after ? regardless of how the URL is rewrote, which is what QUERY_STRING does, except QUERY_STRING included any &, = and trailing information as well - which you're not catching as a condition anyway in this code.

Now, if you want to turn logout into a separate mode, that seems fine, but adding script support to read secondaries shouldn't break anything in and of itself....

Another issue:  if you want to cater to other users, many people are not going to have access to .htaccess or be in an environment where they cannot url-rewrite, so you may want to be careful to keep support for regular URLs as well.


Nothing but you should require it in configure.ac then. It doesn't come by default with any BSD system and have to be installed from packages. Some folks even do bash -> zsh symlinks.


What on earth did you do?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 282](https://teamcity.mesosphere.io/viewLog.html?buildId=56908&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:39


キャッシュクラスの設定はFuelの既存通りに使えるように実装。


Somehow yes. Maybe something break in our mixer without this patch and interfere headset audio routing.


I'm getting a little weirdness with printing binary—it seems when you print binary, higher byte values are converted to their UTF-8 code point value, then back to binary. For example, the outcome of:

    print #{C3}  ; 169

is:

    #{C2A2}  ; UTF-8 "©"


Usado para testes


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 283](https://teamcity.mesosphere.io/viewLog.html?buildId=56925&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:57


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 280](https://teamcity.mesosphere.io/viewLog.html?buildId=56903&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:01


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 284](https://teamcity.mesosphere.io/viewLog.html?buildId=56930&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:07


Set the style at your formal event in this smashing gown by Alyce 2400 Claudine. The fitted, sleeveless bodice features a sheer illusion neckline that highlights a center plunge to the waist and floral appliques that detail the curves of bust, midriff and hips. Sheer flutters fall along the fluted skirt to an applique-adorned full-length. A translucent inset supplies a sensuous, barely-there accent along the upper back.
http://www.gbridal.com/special-occasion-dresses/evening-dresses-2015.html


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 278](https://teamcity.mesosphere.io/viewLog.html?buildId=56901&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:55


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 281](https://teamcity.mesosphere.io/viewLog.html?buildId=56905&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:06


 http://www.jvsdress.com/unique-vintage-prom-dresses/
Cultivate a classic vibe in this stunning sleeveless sheath by Alyce 2443 Claudine. The semi-sheer lace overlay features a jewel neckline and fitted styling through bust, waist and hips. http://www.chicornate.com/short-bridesmaid-dresses/
Tone-on-tone appliques, strewn with brilliant crystals, create a rich, dimensional look while tonal lining lends coverage from bust to full-length. A subtle flute makes an understated finish at the feet.


test


LGTM


You're right, I corrected the chart. Thanks for the notice.


Are these changes for speed of build or for portability?


It's probably a compatibility issue with some setting in the new RSF. I'll look into it in a bit.


nice :shipit:


Mostly speed of build -- it usually takes about an hour to build vtk, and this cuts it down quite a bit on the machines I tested it on. If we were really concerned about build speed of course we could also enable multiple cores, which would probably have a bigger effect.

However, we also  had an issue recently at EAO with not being able to build part of VTK after (I think) an openGL update (see my patch to Starlink/vtk earlier today). I thought it would be useful to minimise future potential issues by not building the parts we aren't using. We can always revert it if it causes problems or degrades performance of course.


.创建消息上面要添加的动作(按钮的形式显示出来)
[objc] view plaincopy在CODE上查看代码片派生到我的代码片
UIMutableUserNotificationAction *action = [[UIMutableUserNotificationAction alloc] init];
   action.identifier = @"action";//按钮的标示
   action.title=@"Accept";//按钮的标题
   action.activationMode = UIUserNotificationActivationModeForeground;//当点击的时候启动程序
   //    action.authenticationRequired = YES;
   //    action.destructive = YES;

   UIMutableUserNotificationAction *action2 = [[UIMutableUserNotificationAction alloc] init];  //第二按钮
   action2.identifier = @"action2";
   action2.title=@"Reject";
   action2.activationMode = UIUserNotificationActivationModeBackground;//当点击的时候不启动程序，在后台处理
   action.authenticationRequired = YES;//需要解锁才能处理，如果action.activationMode = UIUserNotificationActivationModeForeground;则这个属性被忽略；
   action.destructive = YES;
2.创建动作(按钮)的类别集合
[objc] view plaincopy在CODE上查看代码片派生到我的代码片
UIMutableUserNotificationCategory *categorys = [[UIMutableUserNotificationCategory alloc] init];
    categorys.identifier = @"alert";//这组动作的唯一标示
    [categorys setActions:@[action,action2] forContext:(UIUserNotificationActionContextMinimal)];

3.创建UIUserNotificationSettings，并设置消息的显示类类型
[objc] view plaincopy在CODE上查看代码片派生到我的代码片
UIUserNotificationSettings *uns = [UIUserNotificationSettings settingsForTypes:(UIUserNotificationTypeAlert|UIUserNotificationTypeBadge|UIUserNotificationTypeSound) categories:[NSSet setWithObjects:categorys, nil nil]];
4.注册推送
[objc] view plaincopy在CODE上查看代码片派生到我的代码片

[[UIApplication sharedApplication] registerUserNotificationSettings:uns];
<pre name="code" class="objc">[[UIApplication sharedApplication] registerForRemoteNotifications];

UserRequires call to registerUserNotificationSettings:• SilentInfo.plist UIBackgroundModes array contains remote-notification•
Can use both
离线push数据包带上特定Category字段（字段内容需要前后台一起定义，必须要保持一致），手机端收到时，就能展示上述代码对应Category设置的按钮，和响应按钮事件。
// payload example:  {"aps":{"alert":"Incoming call", "sound":"default", "badge": 1, "category":"incomingCall"}}
重大修改： 离线push数据包之前能带的数据最多为256字节，现在APPLE将该数值放大到2KB。 这个应该是只针对IOS8的。
5.发起本地推送消息
[objc] view plaincopy在CODE上查看代码片派生到我的代码片
UILocalNotification *notification = [[UILocalNotification alloc] init];
   notification.fireDate=[NSDate dateWithTimeIntervalSinceNow:5];
   notification.timeZone=[NSTimeZone defaultTimeZone];
   notification.alertBody=@"测试推送的快捷回复";
   notification.category = @"alert";
   [[UIApplication sharedApplication]  scheduleLocalNotification:notification];

   //用这两个方法判断是否注册成功
   // NSLog(@"currentUserNotificationSettings = %@",[[UIApplication sharedApplication] currentUserNotificationSettings]);
   //[[UIApplication sharedApplication] isRegisteredForRemoteNotifications];
6.在AppDelegate.m里面对结果进行处理
[objc] view plaincopy在CODE上查看代码片派生到我的代码片
//本地推送通知
-(void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings
{
    //成功注册registerUserNotificationSettings:后，回调的方法
    NSLog(@"%@",notificationSettings);
}

-(void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification
{
    //收到本地推送消息后调用的方法
    NSLog(@"%@",notification);
}

-(void)application:(UIApplication *)application handleActionWithIdentifier:(NSString *)identifier forLocalNotification:(UILocalNotification *)notification completionHandler:(void (^)())completionHandler
{
    //在非本App界面时收到本地消息，下拉消息会有快捷回复的按钮，点击按钮后调用的方法，根据identifier来判断点击的哪个按钮，notification为消息内容
    NSLog(@"%@----%@",identifier,notification);
    completionHandler();//处理完消息，最后一定要调用这个代码块
}

//远程推送通知
-(void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
    //向APNS注册成功，收到返回的deviceToken
}

-(void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
    //向APNS注册失败，返回错误信息error
}

-(void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
{
    //收到远程推送通知消息
}

-(void)application:(UIApplication *)application handleActionWithIdentifier:(NSString *)identifier forRemoteNotification:(NSDictionary *)userInfo completionHandler:(void (^)())completionHandler
{
    //在没有启动本App时，收到服务器推送消息，下拉消息会有快捷回复的按钮，点击按钮后调用的方法，根据identifier来判断点击的哪个按钮
}

运行之后要按shift + command +H，让程序推到后台，或者按command+L让模拟器锁屏，才会看到效果！
如果是程序退到后台了，收到消息后下拉消息，则会出现刚才添加的两个按钮；如果是锁屏了，则出现消息后，左划就会出现刚才添加的两个按钮。
效果如下：

现在只是能让消息中显示出按钮的形式，带输入框的还在研究中，如果大家研究出来了，也谢谢能分享一下啊，大家一起提高！


好的，我怕弄错了，请再帮我看看，万分感谢。我用UEFItool查看后定位到PE32 image section的entrypoint是F9Ch，然后把这个导出到wl.efi，使用wxMEdit定位offset到F90这一行、0C这一列，数值是48，改成C3保存再替换回去，再把UEFI生成的新BIOS文件用编程器刷入EC就可以了？


> Our d2f

This sounds  like a fun activity. What does it entail?


That's fair. I think the bash version of the script is more readable, so I'd rather, as you suggested, require it during configure.


What were these technical difficulties? Is it possible for other clubs to run into these issues?


The client shouldn't use a default port unless one is specified.


the UID, we get it from http://docs.oracle.com/javase/6/docs/api/constant-values.html#java.security.Key.serialVersionUID


Here is an example: http://issues.wenzhixin.net.cn/bootstrap-table/#options/no-bordered.html


this commit actually breaks it you get a self.auth_path that looks like /api/v1//user which is why i could not authenticate. the os.path.join could be a good library to use for this. Im happy to contributed if you find needed.


This doesn't look correct.  If node is set but service is NULL, both are ignored.  Likewise, if node is NULL and service is set, both are ignored.


you inversed the values to go from `no_*` but then later dont remove the `not` to test..


XD


wrong spelling


We're defeating the purpose of moving to common code if we're adding the same function to every test.


:+1: :100:


This appears to break the tests.


```
[13194/15666] TestSocket_UDPSocket#test_bind = 0.00 s
  1) Failure:
TestSocket_UDPSocket#test_bind [/home/crdaviso/gh-craig65535/ruby-master/test/socket/test_udp.rb:35]:
[ruby-dev:25057].
[IOError] exception expected, not.
Class: <Errno::EBADF>
Message: <"Bad file descriptor - bind(2) for #<Object:0x007fa4848273e8> port 2000">
```

```
[13197/15666] TestSocket_UDPSocket#test_connect = 0.00 s
  2) Failure:
TestSocket_UDPSocket#test_connect [/home/crdaviso/gh-craig65535/ruby-master/test/socket/test_udp.rb:23]:
[ruby-dev:25045].
[IOError] exception expected, not.
Class: <Errno::EBADF>
Message: <"Bad file descriptor - connect(2) for #<Object:0x007fa48485eaf0> port 1">
```


Ok. Thanks. It would be helpful if things like this were filed as Github issues so that external people can see what's happening :smile:

PS Please consider updating VTK (especially in light of build issues). v6.3.0 is out now. I used to do all the upgrading in Starlink but no longer have the time.


it works :)


webMAN MOD 1.43.07
src: http://aldostools.org/temp/test/webMAN_MOD_1.43.07.rar
bin: http://aldostools.org/temp/test/webMAN_MOD_1.43.07_Updater.pkg

There are some minor tweaks and fixes, but the major change is the integration with the VSH Menu.

VSH Menu for webMAN now can be installed optionally (Holding R1 when launching the Updater)

The source code for the VSH Menu project is included under the folder "vsh_menu".

webMAN MOD now supports http requests through a local file interface (/dev_hdd0/tmp/wm_request)
Example: "GET /mount.ps3/dev_hdd0/PS3ISO/MyGame.iso" (sans quotes)

Now it should be easier for devs to integrate their homebrews with webMAN MOD.

Special thanks to littlebalup, Mysis, 3141card and Orion for the VSH Menu.


Good point Jon, I think we'd prefer a more formal URL join method than` format`.


Today was apparently my day for fixing bugs I'd forgotten to file issues about...

Unless anyone else is keen on doing it, I'll try and take a look at doing an update this month, before I forget everything about VTK.


I've already been experimenting, but no luck yet finding the cultprit setting. :/


still *isn't* the case in python 2.


Notar por favor que he utilizado una nueva librería llamada [webhelpers](https://pypi.python.org/pypi/WebHelpers/1.3), incluiré la librería en el requirements.txt la próxima vez que haga un commit.


The first thing that comes to mind is the ControlProcessMemory line and the N3DS settings. Try commenting each of those out and see what happens.


@egamma I finished the "promise-must-complete" rule and you can see all the testing scenarios here. We don't use promises on MSE though so I don't have a large codebase to test this rule against. It would be great to test it out on one of your code bases next week.


You can do `_ = var!(attrs)` or add a guard, especially if you expect it to be a map.


I think it makes sense to move this test, and the one for jq, to a conditional around the "complete -F _fb_adb_complete fb-adb" at the end of the script. That way, when we warn, we don't install a completion handler that users end up being unable to actually use.


OK, I will modify it.


Consistency is Key. These two variables were declared using snake_case and camelCase conventions. It's generally a  rule of thumb to be consistent across board. Decide which one you feel like using and stick to it. Nice work man!


I have tried to be very diligent about removing unused headers. I guess this one was overlooked when I converted back to using a zone directly rather than a unique_ptr.


Because I return entry will decrease the performance. I try to return lname that will reduce cache-miss.


nothing but a hollow shell so far (copied from another draft), but if you're interested in joining forces, @npdoty, this would be a starting point. i have no build process, i just use the online xml2rfc converter to generate the TXT/HTML from the XML source.


I will notice the limit of title commit messages.


 # código TP_1

setwd('D:/R_proyectos/CyT')
glx <- read.csv("COMBO17.csv", header = T, stringsAsFactors = F)
glx$e.W420FE <- as.numeric(glx$e.W420FE)
glx_sin_outliers <- glx[!apply(sapply(glx[,-1], function(x) { abs(scale(x)) >= 3 }), 1, any), ]
variables_de_interes <- c(1,2,3,4,10:29)
names(glx_sin_outliers)[variables_de_interes]
glx_sin_faltantes <- glx_sin_outliers[complete.cases(glx_sin_outliers[,variables_de_interes]),]

glx.sin<- glx_sin_outliers[complete.cases(glx_sin_outliers[,variables_de_interes]),]

## codigo TP_

## armo data frame con las variables de interés

glx.df <-glx.sin[,c("Nr", "Rmag","e.Rmag", "ApDRmag", "Mcz", "UjMAG",
"BjMAG", "VjMAG", "usMAG","gsMAG","rsMAG", "UbMAG","BbMAG","VnMAG","S280MAG")]

head(glx.df) # salio todo bien

## ahora que ya tengo el data frame armadito, comienzo con K medias

## primero seria criterioso comenar a indagar por cluster jerarquicos a ver qué grupos hay

plot(data$e.Rmag, data$Rmag, xlab="variable 1", ylab="variable 2", main="plot de variables", pch=20)


@igorbt, I reviewed this PR, good work overall :+1:
However, This line won't work because ```percent``` does not equal to ```this.state.percent```
```
  _dragX(e, pos) {
    let max = React.findDOMNode(this.refs.track).clientWidth;
    if (pos < 0) pos = 0; else if (pos > max) pos = max;
    this._updateWithChangeEvent(e, pos / max);
  },
```
In the code above, ```percent``` will give out different every time mouse moves, I would suggest you to change the update function to:
```
  _updateWithChangeEvent(e, percent) {
    if (this.state.percent - percent < this.props.step ) return;
    this.setPercent(percent - percent%this.props.step, () => {
      if (this.props.onChange) this.props.onChange(e, this.state.value);
    });
  },
```


I'll add it, the commit message was just for you to try. Thank you @syohex

Syohei YOSHIDA さんは書きました :

>Please write how to install fast-rcnn, where is installed, requirements information etc like this commit message to README.md where is top directory too. Usually Autoware users does not see commit log, they see README.md.
>
>—
>Reply to this email directly or view it on GitHub.￼
>


Yeah, they are valid.


2015-10-10 11:41 GMT+08:00 gujinwang <notifications@github.com>:

> 好的，我怕弄错了，请再帮我看看，万分感谢。我用UEFItool查看后定位到PE32 image
> section的entrypoint是F9Ch，然后把这个导出到wl.efi，使用wxMEdit定位offset到F90这一行、0C这一列，数值是48，改成C3保存再替换回去，
>
你已经看懂了，就是这样操作。

> 再把UEFI生成的新BIOS文件用编程器刷入EC就可以了？
>
是刷到BIOS芯片，EC是另外一块芯片，不要搞错了。你应该用编程器读出过芯片的内容吧，要刷的也是那块芯片。

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mytbk/firmware_notes/commit/74f61e82e90671016df481932700ac920c6b8f50#commitcomment-13699006>
> .
>


Please improve your GIT commit message. Read this article carefully: https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message


Don't depend on the misleading `_PHONEBOOK_H_orig`. Instead, specify the exact implementation identifier.


Don't change the original coding style.


Urvish Bhagat


First, this function is Stable. I've already tested.

All the previous commits has led to the making of this function, and from here, it entails a large change to system core. We can substantially remove breadcrumbs generation functions using this one, but it doesn't affect any appearance or errors.

I'll slowly replace them in due time after further testing on performance. The forum breadcrumbs, for example, may consume up to 5 sql if nested 5 level down while this function uses none. Compared this to 1 nested = i.e. 1 sql count, and this function may consume up more memories maybe due to minimum of 3 foreach loops during its calculation.


I'm puzzled. I expected

-	emake DESTDIR="${ED}" install || die "emake install failed"
+	emake DESTDIR="${D}" install

but it's the other way around


Thank you. :)


"пучтой группы" - пустой группы.
// не знаю, как править сообщения коммита на гетхабе.


LOI FBJBJFN


 net-dialup/freeradius-client: Fix cross compilation by letting user m…

…anage ac_cv_struct_utsname and ac_cv_file__dev_urandom, bug #373369

The commit msg appears to have been line feed forced by this page suggesting it needs re-formatting.

manage ac_cv_struct_utsname and ac_cv_file__dev_urandom, bug #373369

The initial line should be a standalone sentence, >=Line 3 a further detailed outline.

Who authored the freeradius-client-1.1.6-BJA-cross.diff. This is generally outlined in the opening line(s) of a patch


Don't mix several independent changes into single GIT commit.


we probably don't need this branch anymore.  I'm not even sure what it is.


r=graydon


Didn't work.

Commented out controlprocessmemory and this 5 line block:
https://github.com/Steveice10/citrus/blob/master/tools/template.rsf#L78


jedmccaleb/stellar-core/master = d994396e merged ok, testing candidate = 9168dfa8


saw approval from graydon
at https://github.com/jedmccaleb/stellar-core/commit/d994396e0fdb5c2e270c24d0a59b3403f774bb4d


merging jedmccaleb/stellar-core/master = d994396e into auto


Hmm, the first one seems to fail for the distinct query which returns the wrong result. I have an idea of why this is and will try to sketch out an explanation later this weekend.


@justjavac 首页上给Documentation的链接是到http://mithril.js.org/mithril.html

我们翻译的这个貌似是Guide。。。


It's definitely something in the rsf.
I reverted to your old cia rsf template minus the Exefs stuff and it worked.


I had this in mind, the action may not always be "list" even though it's returning a list. Since ``data`` will always be assigned to ``serializer_data``, perhaps starting from line [115](https://github.com/django-json-api/django-rest-framework-json-api/blob/f58902c2a3f9b72a20c89b4b11ed90a05b44946f/rest_framework_json_api/renderers.py#L115) ``data`` should be renamed as well so that a common name is used.


*stare*

Other than that, looks good :)


Хорошо, только в следующий раз разбивай такой коммит на несколько:
1) Подключил 2 шрифта
2) изменил имена классов
3) убрал позиционирование
4) убрал <br>
5) прописал href для ссылок
6) "причесал" код !

Таким образом должно быть 6 коммитов разных, а не один!


больше табов нигде нету?) ок


Example transformer
```ts
const htmlTransformer: Transformer = {
	url: (url: string): string =>
		'<a href="${url}" target="_blank" class="url">${url}</a>',
	screenName: (screenName: string): string =>
		'<a href="${config.publicConfig.url}/${screenName}" target="_blank" class="screen-name">@${screenName}</a>',
	bold: (boldText: string): string =>
		'<b>${boldText}</b>',
	newLine: (): string =>
		'<br>'
};
```


I try to update a minutes array(this array is not exist) with upsert & $ positional operator. I need it automatic create a minutes array, but created a minutes object.


@wkennington Without some kind of noreturn patch, `python2.7-gevent` no longer builds on Darwin.


Oh its broken on darwin.... Mind updating this for the new version?

On Fri, Oct 9, 2015, 22:07 John Wiegley <notifications@github.com> wrote:

> @wkennington <https://github.com/wkennington> Without some kind of
> noreturn patch, python2.7-gevent no longer builds on Darwin.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/NixOS/nixpkgs/commit/cbc1eaa1ea5354f65d0dcb94775b48368b80bfb2#commitcomment-13699221>
> .
>


Which version of what?


¿Y esto? @mkt101


I believe I removed the patch because it didn't seem needed and did not
apply to the new version of libev.

On Fri, Oct 9, 2015, 22:10 John Wiegley <notifications@github.com> wrote:

> Which version of what?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/NixOS/nixpkgs/commit/cbc1eaa1ea5354f65d0dcb94775b48368b80bfb2#commitcomment-13699225>
> .
>


Since I don't quite know what you mean, can you show me what the patch looks like and I'll try it?


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/84625200


fast-forwarding master to auto = 9168dfa8


TeamCity pull requests :: netty-tcnative [Build 28](https://garage.netty.io/teamcity/viewLog.html?buildId=2176&buildTypeId=pulls_netty_tcnative&guest=1) is now running


Lets not translate the +1 stuff for now then.


TeamCity pull requests :: netty [Build 396](https://garage.netty.io/teamcity/viewLog.html?buildId=2177&buildTypeId=pulls_netty&guest=1) is now running


TeamCity pull requests :: netty-tcnative [Build 28](https://garage.netty.io/teamcity/viewLog.html?buildId=2176&buildTypeId=pulls_netty_tcnative&guest=1) outcome was **SUCCESS**
Summary: Running Build time: 00:00:46


Don't mix independent changes into single GIT commit.


You can use input() instead of raw_input() for reading integers. I don't know if there is a performance difference, but in my opinion, using input() looks better than raw_input() and int().


TeamCity pull requests :: netty [Build 397](https://garage.netty.io/teamcity/viewLog.html?buildId=2178&buildTypeId=pulls_netty&guest=1) is now running


HackerRank uses raw_input instead of input in their tutorial, but I will keep this in mind.


Second


Seems interesting. One thing I haven't addressed yet is some session stuff (not a big deal and plan to get to it on a future review) which can cause real heartache when open up new popups/frames(the solution to avoid session):
http://www.open-emr.org/wiki/index.php/OpenEMR_System_Architecture#PHP_Sessions_and_Browser_Windows
(note the solution relies on a function in the top frame which is why breaking out into another popup or frame can cause session contamination issues)


Regarding discarding of changes, just remove it on your end in a commit. At next code review will bring in all your new code and rebase it again (I have a base commit to start from on your original repo, so it won't be that hard to do when get there).


Regarding above comment, this means just keep developing as you are on your master branch.


I see. The creation of the new branch is an optional step, I may end up adding a note for that in the configuration documentation.
The purpose is to make sure that you can make changes to V8 if you need them.

Are you saying you couldn't get V8 to compile? If so, what are your system specs and can you share the full build log?


borde inte vara svårt för er att implementera popup funktionen om ni använder det jag skrivit.

observera följande:
-main skapar en ny tråd som kontinuerligt letar efter rätter som är readyToServe och ger popup.
-tråden körs enbart från MainActivity; bara där du får popup.
-applikationen behöver använda ändra order status med api:t för att ta bort readyToServe. (annars får du massa popups hela tiden).


Tap


sen behöver den förstås bara skapa tråden när en person är inloggad som servitör


ouch.. which compiler? I used gcc.


金融问题修复


金额问题修复


TranslucentStatus/README.md


TeamCity pull requests :: netty [Build 396](https://garage.netty.io/teamcity/viewLog.html?buildId=2177&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5219, ignored: 21 Build time: 00:20:52


TeamCity pull requests :: netty [Build 398](https://garage.netty.io/teamcity/viewLog.html?buildId=2179&buildTypeId=pulls_netty&guest=1) is now running


Errrrr, didn't notice this pull was on trunk and not yet released.  Checked out trunk, built it, tried it, and, guess what, works great.  Thank you!  Nice feature.


wew


@gafter #5804


Not sure, but I think (void)udata is better. The optimizer way optimize it away, but still....


you only need the debug config when correct one ain't found ;-;
y u no include commit history xD


Very useful fix, @insin hope, you will apply it.


I don't see `.fc` in that stackoverflow list.

Anyway, I'll send you a pull request to make GitHub detect `.fc` as Forth.


Mate,

You should reverse this merge, this introduces incompatible changes that is not supported. Master branch should never be merged into the 6.04.01. Master is meant for the lastest pcgen developments. The versioned branch of 6.04.01 is meant only for changes that pcgen version 6.04.01 will support. Attempts to run this branch on 6.04.01 will be chaotic at best, and fail at worst.


Yeah, I think I actually like your version better. It looks cleaner. It avoids having to use an actual "Monster" class at all.


@jakcron Are you certain that template RSF works? I tried it with only the service list modified, and I've been told it loops on the Nintendo 3DS screen on 9.2 O3DS. I can't even install it without getting an error (Invalid title version? 0x27).


I realise this commit has temporarily broken some Travis tests - will update the reference images when I've fully solved 11522


Good catch, thanks.
https://github.com/NicoHood/HID/commit/7151a55577593d4c6f681ad113084e527d0d4a7b


thanks!


コメントありがとうございます！なるほどです。

FYI 【 For Your Information 】の意味も初めて知りました笑


This should be referencing #104, not #114... oops


This should be referencing #104, not #114...


> concatした場合などにうまく動かなくなる
なるほどです。


Therefore, I can use
1. `make perf` for original perf analysis
2. `make perf GOAL=./phonebook_opt` for optimal's
I'm not sure if these make sense...


why?


I got it.
I'll correct it next time.
:smiley:


maybe forget the journaling?
{RBD_FEATURE_JOURNALING, "journaling"}


Okay...
Maybe `deleteList` next time?


#2 for the platform part


Done


Sorry, I can't follow you.
Do you mean line 131 to line 135 should be wrote in a function?


Previously, the 4 classes CRUD, ShowDays and SortAndShow could not be compiled
using Command Line Prompt
as

private static final Logger logger = Logger.getLogger(Flex.class.getName());

was preventing them from doing so.

"Flex" in  this statement in each class, has been changed to the name of each class (without ".java"),
so compilation using Command Line Prompt now works.

Using Command Line Prompt:
1. In the Command Line Prompt Window, type “javac Task.java”.

2. In the Command Line Prompt Window, type “javac FlexWindow.java”.

3. In the Command Line Prompt Window, type “javac LastAction.java”.

4. In the Command Line Prompt Window, type “javac Checker.java”.

5. In the Command Line Prompt Window, type “javac SortAndShow.java”.

6. In the Command Line Prompt Window, type “javac ShowDays.java”.

7. In the Command Line Prompt Window, type “javac CRUD.java”.

8. In the Command Line Prompt Window, type “javac Flex.java”.

9. Flex has now been fully installed. To run the program, in the Command Line Prompt
Window, type “java Flex”.


TeamCity pull requests :: netty [Build 397](https://garage.netty.io/teamcity/viewLog.html?buildId=2178&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 5624, ignored: 21 Build time: 00:45:28


TeamCity pull requests :: netty [Build 399](https://garage.netty.io/teamcity/viewLog.html?buildId=2180&buildTypeId=pulls_netty&guest=1) is now running


是 http://mithril.js.org/getting-started.html 啊。

哪个页面是 http://mithril.js.org/mithril.html？


I don't understand this one QAQ
I thought I used `astyle`, so it changed my code to this type...


I was busy so just downloaded tar file and then pushed ;_;


for test


You should try it with lodash instead ;)


What is its advantage?


Wow, that's awesome!!


std::regex_search may cause the error,
 when I use commands:
 rbd create/info

 ceph version 9.0.3-1941-g27d209d (27d209d7d534c9618a4ab2f09089be2d520147d8)
 1: (()+0x22024a) [0x7fc63d34724a]
 2: (()+0xf130) [0x7fc6376f8130]
 3: (gsignal()+0x37) [0x7fc635f9e5d7]
 4: (abort()+0x148) [0x7fc635f9fcc8]
 5: (__gnu_cxx::__verbose_terminate_handler()+0x165) [0x7fc6368a29b5]
 6: (()+0x5e926) [0x7fc6368a0926]
 7: (()+0x5e953) [0x7fc6368a0953]
 8: (()+0x5eb73) [0x7fc6368a0b73]
 9: (std::__throw_regex_error(std::regex_constants::error_type)+0x35) [0x7fc6368f5f55]
 10: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_bracket_expression()+0xc6) [0x7fc63d24c286]
 11: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_atom()+0x5a) [0x7fc63d24c4ba]
 12: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_term()+0x2a) [0x7fc63d24ccca]
 13: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0xe) [0x7fc63d24cd6e]
 14: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_disjunction()+0x24) [0x7fc63d24cee4]
 15: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_atom()+0x4d3) [0x7fc63d24c933]
 16: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_term()+0x2a) [0x7fc63d24ccca]
 17: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0xe) [0x7fc63d24cd6e]
 18: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0x57) [0x7fc63d24cdb7]
 19: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0x57) [0x7fc63d24cdb7]
 20: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_disjunction()+0x24) [0x7fc63d24cee4]
 21: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_atom()+0x4d3) [0x7fc63d24c933]
 22: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_term()+0x2a) [0x7fc63d24ccca]
 23: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0xe) [0x7fc63d24cd6e]
 24: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_alternative()+0x57) [0x7fc63d24cdb7]
 25: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_M_disjunction()+0x24) [0x7fc63d24cee4]
 26: (std::__detail::_Compiler<char const*, std::regex_traits<char> >::_Compiler(char const* const&, char const* const&, std::regex_traits<char>&, unsigned int)+0x242) [0x7fc63d24d262]
 27: (std::shared_ptr<std::__detail::_Automaton> std::__detail::__compile<char const*, std::regex_traits<char> >(char const* const&, char const* const&, std::regex_traits<char>&, unsigned int)+0x28) [0x7fc63d24d618]
 28: (rbd::utils::extract_spec(std::string const&, std::string*, std::string*, std::string*)+0xe0) [0x7fc63d247df0]
 29: (rbd::utils::get_pool_image_snapshot_names(boost::program_options::variables_map const&, rbd::argument_types::ArgumentModifier, std::string const&, std::string*, std::string*, std::string*, rbd::utils::SnapshotPresence, bool)+0x5de) [0x7fc63d24855e]
 30: (rbd::action::info::execute(boost::program_options::variables_map const&)+0x90) [0x7fc63d2685a0]
 31: (rbd::Shell::execute(int, char const**)+0x796) [0x7fc63d242db6]
 32: (main()+0x62) [0x7fc63d21d952]
 33: (__libc_start_main()+0xf5) [0x7fc635f8aaf5]
 34: (()+0x1089c9) [0x7fc63d22f9c9]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

I think the
std::regex, std::smatch, std::regex_search exist a bug,
and them can by replaced by
boost:regex, boost:smatch, boost::regex_search


Sure, I'll clean this up in a subsequent commit.


This is the beginning of a project to create a USB Retro Game Controller for RetroPie.  This code is a derivative from the example files downloaded from the [PJRC.com website](https://www.pjrc.com/teensy/td_joystick.html).  Additions made to this code are examples of button macros that allow the player to execute complicated game maneuvers such as a Hadouken in Street Fighter with a single button press.  Please enjoy and make some kick ass finishing moves in your code.


oops! nice catch


embedded system


Added Notes.


> It seems like either Holodex or NRP can translate from whatever we decide to our code, I think all the information is included in either case?

i don't think it's always the same, but i'll try and continue this discussion in @elf-pavlik's [new issue](https://github.com/valueflows/valueflows/issues/52).


@kpengboy We plan to replace this page, FYI. You should open an issue and weigh in.


`about.md`, that is


很好的设计，赞！


[merge]


Lol why


Possibility of a signature issue here in the AST.

```
//JavaQuery, transform/map.yaml, #5
/* Original: r.range(3).map(r.range(4), lambda:0) */
```
**`ReqlExpr.java`** doesn't have a `map(Object expr, *ReqlFunction0*)` I think they all got replaced with `Javascript`.

https://github.com/rethinkdb/rethinkdb/blob/a4ea2a0751561f84683a20aba41f1a03fc168879/drivers/java/src/main/java/com/rethinkdb/gen/ast/ReqlExpr.java#L1049


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 285](https://teamcity.mesosphere.io/viewLog.html?buildId=56932&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:10:44


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 288](https://teamcity.mesosphere.io/viewLog.html?buildId=56935&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:45


Some first comment


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 286](https://teamcity.mesosphere.io/viewLog.html?buildId=56933&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:11


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 287](https://teamcity.mesosphere.io/viewLog.html?buildId=56934&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:17


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 289](https://teamcity.mesosphere.io/viewLog.html?buildId=56936&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:24


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 291](https://teamcity.mesosphere.io/viewLog.html?buildId=56939&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:41


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 290](https://teamcity.mesosphere.io/viewLog.html?buildId=56937&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:46


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 292](https://teamcity.mesosphere.io/viewLog.html?buildId=56940&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:45


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 294](https://teamcity.mesosphere.io/viewLog.html?buildId=56942&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:43


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 296](https://teamcity.mesosphere.io/viewLog.html?buildId=56944&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:33


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 297](https://teamcity.mesosphere.io/viewLog.html?buildId=56943&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:30


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 293](https://teamcity.mesosphere.io/viewLog.html?buildId=56941&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:43


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 295](https://teamcity.mesosphere.io/viewLog.html?buildId=56938&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:42


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 299](https://teamcity.mesosphere.io/viewLog.html?buildId=56946&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:09


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 302](https://teamcity.mesosphere.io/viewLog.html?buildId=56949&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:32


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 300](https://teamcity.mesosphere.io/viewLog.html?buildId=56947&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:57


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 298](https://teamcity.mesosphere.io/viewLog.html?buildId=56945&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:05:41


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 301](https://teamcity.mesosphere.io/viewLog.html?buildId=56948&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:16


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 303](https://teamcity.mesosphere.io/viewLog.html?buildId=56950&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:45


Lol


I have patches for [openocd](http://openocd.org) which let you read the [DNA from a Spartan-6](http://openocd.zylin.com/#/c/2960/). I wonder if they will work on the Artix-7? I should get my Nexys Video working....


Could You tell me the op comand


TeamCity pull requests :: netty [Build 400](https://garage.netty.io/teamcity/viewLog.html?buildId=2181&buildTypeId=pulls_netty&guest=1) is now running


TeamCity pull requests :: netty [Build 398](https://garage.netty.io/teamcity/viewLog.html?buildId=2179&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 4777, ignored: 21 Build time: 00:55:12


Great work using a separate include statement and playing around with different mixins!


Closes #80


When using an offsets Telegram clears the list of updates. So, there is no chance of stale messages being sent down the socket.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 312](https://teamcity.mesosphere.io/viewLog.html?buildId=56958&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:10


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 316](https://teamcity.mesosphere.io/viewLog.html?buildId=56960&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:10


[From the documentation:](https://docs.python.org/2/library/stdtypes.html#str.splitlines)

>Unlike `split()` when a delimiter string *sep* is given, this method returns an empty list for the empty string, and a terminal line break does not result in an extra line.


Hi, what I should change in kernel code to be compatible with this commit?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 309](https://teamcity.mesosphere.io/viewLog.html?buildId=56959&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:19


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 310](https://teamcity.mesosphere.io/viewLog.html?buildId=56956&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:20


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 307](https://teamcity.mesosphere.io/viewLog.html?buildId=56954&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:22


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 315](https://teamcity.mesosphere.io/viewLog.html?buildId=56961&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:22


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 311](https://teamcity.mesosphere.io/viewLog.html?buildId=56952&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:23


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 318](https://teamcity.mesosphere.io/viewLog.html?buildId=56965&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:22


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 317](https://teamcity.mesosphere.io/viewLog.html?buildId=56964&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:23


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 304](https://teamcity.mesosphere.io/viewLog.html?buildId=56951&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:24


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 305](https://teamcity.mesosphere.io/viewLog.html?buildId=56953&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:24


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 306](https://teamcity.mesosphere.io/viewLog.html?buildId=56955&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Failed to start build Build time: 00:04:24


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 313](https://teamcity.mesosphere.io/viewLog.html?buildId=56962&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:23


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 308](https://teamcity.mesosphere.io/viewLog.html?buildId=56957&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:04:24


TeamCity pull requests :: netty [Build 399](https://garage.netty.io/teamcity/viewLog.html?buildId=2180&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 4777, ignored: 21 Build time: 00:35:08


TeamCity pull requests :: netty [Build 401](https://garage.netty.io/teamcity/viewLog.html?buildId=2182&buildTypeId=pulls_netty&guest=1) is now running


然而我们做的都是汇编（


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 314](https://teamcity.mesosphere.io/viewLog.html?buildId=56963&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:05:35


Mate, this branch is unusable. I will not be able to accept any PRs from this branch. You have corrupted the 6.04.01 branch by merging in the Master branch on top of it. Master is incompatible with 6.04.01.
Either reverse your earlier Master merges, or start fresh by simply branching from 6.04.01 and then make your new changes on top of that.


mycat-web新版界面


Here, you don't need to use id="marketing" unless you're going to style this element using #marketing{...}


Nice touch :)


YT Player.


@pmuir, are you sure this Ansible playbooks can be run using 'localhost' for master and nodes? The running box has the master and node processes running (started via their systemctl proesses), but when running Openshift and trying to build anything, the build gets stuck since the master does not seem to be able to see the node and hence cannot schedule a pod/container for execution. Sounds familiar. I am having more luck, if I start an all-in-one server via 'openshift start' (while stopping the systemctl services).

However, I am running then into another problem later. Now builds start working and containers (eg a db container) start up, but when trying one of the sti example, the builds will time out due to an error message that the build container is not able to clone the specified git repo. When connecting to the container, I can indeed not do a git clone. This seems also unrelated to Openshift/Kubernetes. Just starting an independent container, I see the same issue. I am wondering whether there is a problem with the docker daemon or whether selinux is problem!? Rings a bell?


The execute time of append() is faster three times, findeName() is faster two times.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 329](https://teamcity.mesosphere.io/viewLog.html?buildId=56975&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:56


You are thinking with a Binary Son - Brother tree logic. What we are doing is a N-Tree that is merely represented has a binary tree.
The heuristicvalues start at the leaves and then go directly to the father.
The brother value is calculated at line 41 when you are deciding what value you father has.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 336](https://teamcity.mesosphere.io/viewLog.html?buildId=56977&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:40


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 335](https://teamcity.mesosphere.io/viewLog.html?buildId=56979&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:40


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 331](https://teamcity.mesosphere.io/viewLog.html?buildId=56981&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:41


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 332](https://teamcity.mesosphere.io/viewLog.html?buildId=56983&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:41


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 330](https://teamcity.mesosphere.io/viewLog.html?buildId=56978&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:42


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 334](https://teamcity.mesosphere.io/viewLog.html?buildId=56980&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:41


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 328](https://teamcity.mesosphere.io/viewLog.html?buildId=56976&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:03:42


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 333](https://teamcity.mesosphere.io/viewLog.html?buildId=56982&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:05


Is there a reason not to use `uglify-js`? Or you just don't want to promote it?


Bash (.sh) and Shell (.bat)


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 337](https://teamcity.mesosphere.io/viewLog.html?buildId=56984&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:31


The cache miss is reduced five times better. It's lots of advantage of this change.


Is Slim stable right now?
Something I can try to help with?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 342](https://teamcity.mesosphere.io/viewLog.html?buildId=56991&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled Build time: 00:00:21


On building Cxx, I get
~~~
ld: library not found for -llldbPluginLanguageRuntimeGo
~~~
on julia HEAD.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 349](https://teamcity.mesosphere.io/viewLog.html?buildId=56998&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **UNKNOWN**
Summary: Canceled Build time: 00:00:10


Just wondering how this affect the loading times and file size. I know it's not very convenient to have another file but I when I was playing with this setting I could see the difference.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 338](https://teamcity.mesosphere.io/viewLog.html?buildId=56987&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:11


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 339](https://teamcity.mesosphere.io/viewLog.html?buildId=56988&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:05:27


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 340](https://teamcity.mesosphere.io/viewLog.html?buildId=56989&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:43


法国恢复


update


快快快快快


@kai as I have no other way to contact you, by any chance, as you seem not be very active on github, could you imagine to delete your account so I can take over your user name? I'm very active at gh and really would like to use may real first name as github username. ;-)


... or maybe that you just change your user name?


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 355](https://teamcity.mesosphere.io/viewLog.html?buildId=57004&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:58


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 354](https://teamcity.mesosphere.io/viewLog.html?buildId=57003&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:05:56


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 343](https://teamcity.mesosphere.io/viewLog.html?buildId=56992&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:08:09


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 357](https://teamcity.mesosphere.io/viewLog.html?buildId=57006&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:45


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 341](https://teamcity.mesosphere.io/viewLog.html?buildId=56990&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:08:46


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 345](https://teamcity.mesosphere.io/viewLog.html?buildId=56994&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:07:52


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 356](https://teamcity.mesosphere.io/viewLog.html?buildId=57005&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:08


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 346](https://teamcity.mesosphere.io/viewLog.html?buildId=56995&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:07:45


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 344](https://teamcity.mesosphere.io/viewLog.html?buildId=56993&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:08:18


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 348](https://teamcity.mesosphere.io/viewLog.html?buildId=56997&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:07:57


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 347](https://teamcity.mesosphere.io/viewLog.html?buildId=56996&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:08:19


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 351](https://teamcity.mesosphere.io/viewLog.html?buildId=57001&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:08:17


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 353](https://teamcity.mesosphere.io/viewLog.html?buildId=57002&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:08:31


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 350](https://teamcity.mesosphere.io/viewLog.html?buildId=56999&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:08:54


Updated the Linux Simple and LVM partitioning scheme tutorials


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 352](https://teamcity.mesosphere.io/viewLog.html?buildId=57000&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:09:03


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 358](https://teamcity.mesosphere.io/viewLog.html?buildId=57007&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:50


Hey,

Awesome.

I haven't touched this code in many many years, so it is possible. I would need to go over it when I get back from vacation, next week.

If you have a fix, please do submit a pull request :)


To me, for (;;) looks confusing, Isn't it easier to just do

    while (buf instanceof WrappedByteBuf) {
        buf = buf.unwrap();
    }


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 361](https://teamcity.mesosphere.io/viewLog.html?buildId=57010&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:08


TeamCity pull requests :: netty [Build 401](https://garage.netty.io/teamcity/viewLog.html?buildId=2182&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 4779, ignored: 21 Build time: 00:30:24


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 365](https://teamcity.mesosphere.io/viewLog.html?buildId=57014&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:58


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 362](https://teamcity.mesosphere.io/viewLog.html?buildId=57011&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:14


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 359](https://teamcity.mesosphere.io/viewLog.html?buildId=57008&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:05:00


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 360](https://teamcity.mesosphere.io/viewLog.html?buildId=57009&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:04:53


Sinon 2 will probably be released when #834 has been resolved. AFAIK the two last items have yet to be checked (pulls welcome), but the first two are pretty close. After #873 has been merged, there still might be some lingering changes remaining that should be common-ified as well, but we are pretty close.


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 367](https://teamcity.mesosphere.io/viewLog.html?buildId=57016&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:55


bwahahaha :p jsuis pas tout seul alors! xD


神様の言うとおりとは笑


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 363](https://teamcity.mesosphere.io/viewLog.html?buildId=57012&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:04:56


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 364](https://teamcity.mesosphere.io/viewLog.html?buildId=57013&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:04:53


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 366](https://teamcity.mesosphere.io/viewLog.html?buildId=57015&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:04:43


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 368](https://teamcity.mesosphere.io/viewLog.html?buildId=57017&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:06


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 369](https://teamcity.mesosphere.io/viewLog.html?buildId=57018&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:03:56


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 370](https://teamcity.mesosphere.io/viewLog.html?buildId=57019&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 187 Build time: 00:03:56


Currently it is safe to unwrap any WrappedByteBuf because child classes do not touch addressing like SlicedByteBuf. Will this hold in the future? Adding another WrappedByteBuf implementation can break this code.


windows下应该是radare2 -w -c "wa ret" whitelist.efi，命令成功执行，但是系统提示radare意外关闭，比较radare和wxMEdit修改的文件，没有差别。再次感谢楼主～


追加部分?


返信テスト
コード内にコメント追加


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 371](https://teamcity.mesosphere.io/viewLog.html?buildId=57020&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 186 Build time: 00:04:48


Is this comment needed? Unwrap is already implemented :-)


TeamCity OSS :: Kubernetes Mesos :: 5 - Smoke Tests (docker/mesos) [Build 372](https://teamcity.mesosphere.io/viewLog.html?buildId=57021&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:47


Travis can compile a lot faster if we add the flag "sudo: false"