Ah ok cool

On 8 December 2015 03:44:58 CET, Ning Sun <notifications@github.com> wrote:
>@untitaker don't worry, I will update this before I release 0.10.0
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/sunng87/handlebars-iron/commit/fadb9cacc5a37c13e2436d0e4bf89c889dd0d777#commitcomment-14837804

--
Sent from my phone. Please excuse my brevity.


This is good, we're now just testing the application specific requirements, not infrastructure which is covered already in the ES package


I am not sure this would work with earlier dockers though ... -f on version is quite recent ... perhaps you need to suppress the error if it fails


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8456](https://teamcity.mesosphere.io/viewLog.html?buildId=87950&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:13


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8469](https://teamcity.mesosphere.io/viewLog.html?buildId=87973&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:04:42


I prefer the wording, but I don't think buttons above and below the screen table would look good? I like:

"Change working screen? All changes on this screen will be lost."
[screen list]
[cancel][return to screen selection]

With the [cancel] and [return to screen selection] buttons in the footer, floated right.


#4702-AirloopHVACUnitarySystem-autosizing-incorrect-for-heating-only-systems-when-using-FlowPerHeatingCapacity (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1971 of 1979 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.6%25-yellow.svg)


There was some sort of glitch on the website where the link wouldn't apply properly. I don't know if it was a temporary glitch, but I'm going to try to apply the link again.


fast-forwarding end-to-end/timeseries to borshop-integration-101-feature/jrd/toggle-pb-t2b = 57dffc9d


do you mean `if (f(*it))` ?


#4702-AirloopHVACUnitarySystem-autosizing-incorrect-for-heating-only-systems-when-using-FlowPerHeatingCapacity (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


MAKE STEVE*


Ah you did cherry pick. I was just prepping a PR. :smile:


Agreed... Parallelism is more like a LibreOffice nightmare.


Actually I don't think we should do this. If I'm not that wrong, all `make` called directly in a `makefile` will get parallelized by a jobserver…


Good to submit to starting


> Actually I don't think we should do this. If I'm not that wrong, all make called directly in a makefile will get parallelized by a jobserver…

Yes, that's the point of a parallel build.


why change in name?
I can fix the collections/shim error - it is coming from Q library


不是。。我的意思是，这个地方我写漏了，写错了。。

直接用 `logger.error(err)` 才行


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8457](https://teamcity.mesosphere.io/viewLog.html?buildId=87954&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout (new) Build time: 01:00:10


Do not use `source`.


Horror shitty thing I'd rather use a minimal PMless version of ab…


What is the difference between `source` and a dot? This is a question of mine...


`source` is toooooo long, and non-POSIX. Zheng used to call these scripts with `sh`, so we can expect failures…


Actually, the commit is faulty - because it does not change the allocation; it removes the allocation.
This was not meant as "static" (i.e. global) class variable, but as "non-pointer" variable. Was that your problem?
I'll force-push a fixed version of this commit.


TeamCity LabKey :: Trunk :: Premium :: Git postgres 9.4 [Build 831](https://teamcity.labkey.org/viewLog.html?buildId=290297&buildTypeId=LabkeyTrunk_GitPostgres) outcome was **FAILURE**
Summary: Tests failed: 24 (1 new), passed: 256 Build time: 01:46:39
### Failed tests
```
org.labkey.test.Runner: org.labkey.test.tests.ScrumtimeTest: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyColorStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyStudyAndTreatmentVars: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyDensePlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyGutterPlotBrushing: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testDatasetExport: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testSelection: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testSelectingEmptyMeasure: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStickyFinderFilterOnDataset: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testStickyFinderFilterOnStudyNavigator: <no details avaliable>

org.labkey.test.tests.DataFinderTest.testGroupSaveAndLoad: <no details avaliable>

##### there are 14 more failed tests, see build details
```


I love this idea @maykeit1 !


hi @holbrojm
cool choice of emoji!  :+1:


Oh man, I thought I had a trademark! Guess I'll have to find a new emoji totem.


You forgot here


@jmfradkin
cool choice of emoji!  :+1:


and here


HBIRE_vector_take2 (Myoldmopar) - i386-Windows-7-VisualStudio-12: Tests Failed

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-47.15%25-red.svg)


hi @JordanGoodspeed
interesting, your emoji did not render.
:grin:


@maro01507i Mira este último commit: solo lee mi texto que explica el quinto cambio (el > número 5 en el texto del commit). #dato #info #EstoNoEsTwitterPeroComoSiLoFuera


hi @jstnstwrt
cool choice of emoji! :+1:


hi @outsideken
cool choice of emoji!  :+1:


+1 looks good!


In short: I wasn't able to make up my mind.

And now for a longer story. These are the names of the nodes that are reserved - user cannot use them to name his nodes. Because of that, I tried to make them more unique by adding underscores. However, the names of the nodes are directly displayed in the image and it turned out that the underscore versions don't look visually pleasing. So I reverted the change.


@wfenchel, Thank you very much!


I've opened the PR here: https://github.com/kategengler/ember-feature-flags/pull/32


hi @kzecchini
cool choice of emoji!  :+1:


Не про этот PR, но в `operator << (std::ostream &stream, const std::vector<T> &vector)` у тебя есть "TODO" про баг (gcc <= 4.6), его можно уже исправлять, т.к. с libmds gcc >= 4.8.


Explicit `geojsonvt::` prefix shouldn't be necessary inside the namespace.


hi @mdlai
cool choice of emoji! :+1:


No it is in the way because loading help vocabs can cause unloaded vocabs to become loaded too. Like the `ui` vocabs docs loads the `ui.gadgets.books` vocab which otherwise wouldn't have been included.


Nit: capitalize "ID" in commit message


Thanks!

> On Dec 8, 2015, at 15:04, Reshama <notifications@github.com> wrote:
>
> hi @outsideken
> cool choice of emoji!
>
> —
> Reply to this email directly or view it on GitHub.
>


Yeah that'd be nice. Remember that collision/explosion/carpark still need to bypass armour when it's all disabled.


Since you need to preserve ordering maybe an ARRAY literal (an array of strings) would do the job. But I don't remember whether we support RexLiteral of type ARRAY, because SQL doesn't support ARRAY literals, only ARRAY constructors whose arguments all happen to be literals. I suppose you can give it a try, but if it doesn't work don't push it.


Cool! :)


How do you want to style this? Each case its own line (one of them empty):

```
case kGIAlertType_Stop:
case kGIAlertType_Danger: self.icon = [[NSBundle bundleForClass:[GILayoutManager class]] imageForResource:@"icon_alert_stop"]; break;  // TODO: Image is
```
or both cases in the same line:

```
case kGIAlertType_Stop: case kGIAlertType_Danger: self.icon = [[NSBundle bundleForClass:[GILayoutManager class]] imageForResource:@"icon_alert_stop"]; break;  // TODO: Image is
```


Ok


Good catch.


What if an extension adds a method which wants to call super.foo()?

All this started with @jckarter told me and @bitjammer that inserting a class in the inheritance chain is resilient provided the availability of the class is not back-dated. Clients cannot observe the change, after all (since the class was not available in the past, there are no 'foo is Bar' checks that might yield a different result).


hi @natalieretamar
cool choice of emoji!
is there a way to get it to render in markdown?
:dancer: How about this?  :+1: :smile:


@adambbecker You can basically just remove this line here, I think.


This is where we are in compilation time with MemoryBehavior caching.

Running Time	Self (ms)		Symbol Name
15394.0ms   26.8%	64.0	 	       swift::SILPassManager::runFunctionPasses(llvm::ArrayRef<swift::SILFunctionTransform*>)
2835.0ms    4.9%	4.0	 	        (anonymous namespace)::SimplifyCFGPass::run()
2518.0ms    4.3%	8.0	 	        (anonymous namespace)::ARCSequenceOpts::run()
2318.0ms    4.0%	6.0	 	        (anonymous namespace)::SILCombine::run()
1728.0ms    3.0%	98.0	 	        (anonymous namespace)::SILCSE::run()
1710.0ms    2.9%	128.0	 	        (anonymous namespace)::RedundantLoadElimination::run()
1394.0ms    2.4%	30.0	 	        (anonymous namespace)::DeadStoreElimination::run()
755.0ms    1.3%	137.0	 	        (anonymous namespace)::DCE::run()
399.0ms    0.6%	8.0	 	        (anonymous namespace)::SILCodeMotion::run()
299.0ms    0.5%	6.0	 	        (anonymous namespace)::ABCOpt::run()


Remove this one, too.


It contains at least one letter that appears twice in a row takže to může být i zz xx ll rr


I'm not sure if there's a coding guide for this project. In case of PSR-2 it says: "All PHP files MUST end with a single blank line."

* RiakStorageTest.php
* YamlDriver.php
* XmlDriver.php

doesn't seem to have one.

Maybe I am just nitpicking about that and it's not that important for KeyValueStore. :-)


hi @nisharma85
cool choice of emoji!
but, try this to get it to render in markdown.
:smile: :+1:


Logical layout:  All OpCapability instructions come first, if they exist.
This and other tests below.


As in, straight to health? Easy.


I don't think the test in main is appropriate, so I'm going to remove it. I do think we should add to the output from `cf --version` what version of go it was built with, though.


many thanks, I have the official 7“ DSI Display. I ran sudo rpi-update and then I entered disable_touchscreen=1 into the command line. It is not working for me. The touchscreen remains active. :-(

> Am 07.12.2015 um 21:37 schrieb popcornmix <notifications@github.com>:
>
> disable_touchscreen=1
> this is the Pi's DSI LCD touchscreen)
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/Hexxeh/rpi-firmware/commit/c213b61355d6ebcd805157b57440b00b4e3de04d#commitcomment-14831147>.
>


stačí "aeiou"


This will be fixed sometime in the future. Using subprocess because with urrlib there's an SSL handshake error because of the server (most probably.)


hi @ozzieliu
cool choice of emoji!  :+1:


Note:I used open source web template.


Yeah. It would be best just to keep it in the if-statement as done previously.


Thought @easye and you might like it :)

You still need to have ansible (`brew install python; pip install ansible`) and the credentials for gitlab & spire, but we can handle that offline or you just ping me for that last step.


You can probably add this to the devmode.sh script


There are three things that could just be removed from the SVG code:

- The `xmlns:sketch` attribute from the `<svg>` tag
- The `Generator: Sketch` comment
- The `<desc>` tag
- I see some `sketch:type` attributes scattered throughout.

We remove all of these with `svgmin` in the Gridicons repo, so perhaps just use NPM to install svgmin globally and run that on this file?


What's going on here? Could you point me to a build that failed with this?


What would be the plan of action in here? Create a separate model and extract DOM there? I do not want to break what I already have for time being.


hi @SpeedCoder5
cool choice of emoji!  :+1:
:wink: :ok: :smile: :grin: :grinning: :wink:


Yeah that's why I had it commented I figured it would still be needed otherwise.


on the left


The constant `WORKER_RESTARTED_ERROR` should be removed since it is no longer used.


on the right


hi @scullem
cool choice of emoji! :+1:


Done.  I did the same in the Desktop directive too.


Желательно именовать приватные члены консистентно, может `m_handler_name`?


Constant definitions have to precede function declarations and definitions.


hi @Threynaud
cool choice of emoji!  :+1:


Done.


Move constant definitions to before functions.


`git show HEAD~1:weapon-config.inc` :-)


move constant up


Have you executed `mkfs.s3ql`?


saw approval from macintux
at https://github.com/basho/riak_kv/commit/84040cfafc985a221c3bcd537a0d97dcda5565d5


merging basho/riak_kv/fix/az/test-for-ranges-spanning-exact-multiples-of-quanta = 84040cfa into borshop-integration-1292-fix/az/test-for-ranges-spanning-exact-multiples-of-quanta


basho/riak_kv/fix/az/test-for-ranges-spanning-exact-multiples-of-quanta = 84040cfa merged ok, testing candidate = 2541aecb


Yes, I was being perhaps overly cautious with the `SoupSession`.  Though it's probably safe to do here, `SoupSession` is not designed to safely have its properties changed from multiple threads.


As far as I not it is not possible. But I would be very interested in an alternative solution. ;-)


Не проходила спека, проверял тот ли пользователь приходит, забыл удалить(


Are you sure CHECKIMAGERESULT is good here?


@delannoyk what do you think this should do in this case


hi @shermanash
<br>
To see what version of python is running:
```
$ python -V
$ python --version
```


I think this should work now.


@geerlingguy Not sure if this is what you like to see. Maybe you can improve it a bit, I'm a bit busy to get some systems running here :)


complete


Instructions are not for AARCH64.


This is without the MemoryBehavior caching. we reduced the compilation time of DSE quite a bit.

Running Time Self (ms) Symbol Name
15454.0ms 26.7% 85.0 swift::SILPassManager::runFunctionPasses(llvm::ArrayRefswift::SILFunctionTransform*)
2771.0ms 4.8% 9.0 (anonymous namespace)::SimplifyCFGPass::run()
2525.0ms 4.3% 15.0 (anonymous namespace)::ARCSequenceOpts::run()
2369.0ms 4.1% 8.0 (anonymous namespace)::SILCombine::run()
1653.0ms 2.8% 146.0 (anonymous namespace)::RedundantLoadElimination::run()
1635.0ms 2.8% 103.0 (anonymous namespace)::SILCSE::run()
1582.0ms 2.7% 42.0 (anonymous namespace)::DeadStoreElimination::run()
771.0ms 1.3% 121.0 (anonymous namespace)::DCE::run()
399.0ms 0.6% 7.0 (anonymous namespace)::SILCodeMotion::run()
279.0ms 0.4% 11.0 (anonymous namespace)::ABCOpt::run()
211.0ms 0.3% 41.0 (anonymous namespace)::SILSROA::run()
203.0ms 0.3% 3.0 (anonymous namespace)::SILMem2Reg::run()
144.0ms 0.2% 1.0 (anonymous namespace)::ConstantPropagation::run()
135.0ms 0.2% 57.0 (anonymous namespace)::SILLowerAggregate::run()
112.0ms 0.1% 0.0 (anonymous namespace)::StackPromotion::run()


How are then individual interfaces on device modelled? There is no ifIndex or anything similar that would point to which interface statistics apply to ...


@hanwen Can you share context as to why `jvm_flags` does not support `$(location)`? Am I mistaken in that understanding?


CLOSED - see separate discussion 2 comments above


OpConstant can't go here.
Constant can't go here.  Move it up, and then at this point do something like:
```
%trueCopy = OpCopyObject %boolt %true
```
and use %trueCopy for the condition on the branch.


can this be reviewed and merged back into the `master` branch and repo at your earliest convenience?


constant moves up


Uhm, no. Is that needed the first time?


without pycrypto or m2crypto we don't advertise 3DES ciphers (as we don't have pure python implementation of them) so the number of cipher suites advertised not only will change between version of tlslite-ng but depending on the packages installed in system!

that will cause the check in line 162 to fail as the beginning of extension will land in different places

I think you are a bit too restrictive with this checks - this is more appropriate for the unit tests, as there you can guarantee that the size of client_hello under test won't ever change


Where is THORIN_RUNTIME_PLATFORMS now defined?


Good enough for now—I'll tweak it a little.


thanks


does not exist


Какие мысли насчет executor'а здесь?


The namespaces shouldnt be here


These are more generally called "routines" in the sql spec.


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 94](https://teamcity.labkey.org/viewLog.html?buildId=290366&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:02:07


It should go in config.txt.


@pb00068 , no problem.  nice patch =)  Looking forward to LTC and other thread counts.  I'm glad you have continued refining these ideas!


opconstant moves up


typo fixed


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8575](https://teamcity.mesosphere.io/viewLog.html?buildId=88308&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:22


The hitArea doesn't seem be adhered to after this? Attempting to root cause it.


never mind... just saw you moved the examples to the wiki... I may work on stripping out the logic used for this, it might speed up the CI testing.

Also, I noticed you wanted to test with GCC5. We could probably do this, but it would mean migrating back to the legacy infrastructure, away from the faster container based builds.


Why not just remove this? ``public void OnError(Exception error)`` should be enough, and it's fine to throw a ``NotImplementedException`` there.


aaah... now I understand... last friday, when deployig packages,  I got an error related to this in cdev, it was because it was running your umerged patch for this PR.

please, rebase the PR against develop, commit 37672d4caf1d already has this addition


I like what I see


cert, singular, right?


Is the current one ok? Or should we make a different version? Another option I've seen on the dota sprites is this: http://puu.sh/lN4YJ/b86a19b694.jpg but its low def (needs to be at least 1024 px), but can easily make one from scratch


Fixes #2.


hi @BryanBumgardner

To see what version of python is running:
```
$ python -V
$ python --version
```


Real nice refactor


replace with `!tiles.empty()` is more efficient


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1444 of 1444 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


@mjwitte @Myoldmopar OK.  I defaulted three autosizable input fields to autosize for indirect and direct research special evaporative cooler objects. These fields are: Primary/Secondary Air Design Flow Rates, Secondary Fan Power, and Recirculating Pump Power.

The CI machine shows regression results diffs in six example files. These diffs are expected: increased the default fields count, sizing reporting variable change, and others in the html summary diffs.

Added two unit test that check whether blank input fields with default autosize, are sized correctly.  The unit tests run OK. I will push the branch to remote.


Need "OpCapability Int8" if you use 8-bit ints.


This is what made the difference.


This is an older commit.


This made the difference too!!


we are missing test coverage for the above line


přepiš to na
for i in range(1,len(string)):


ping @Plamen5kov


if charr in lW přepiš na  if string[j] in lW


`string[]`


@martint should review `PropertyDerivations`


would it make sense to cache this? thinking lru


Yeah, sometimes for trivial switches, I put them on a single line. In this case, it's 1 line per "effective" case, so `case x: case y:`.


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1446 of 1446 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


lowercase please


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 95](https://teamcity.labkey.org/viewLog.html?buildId=290350&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:06:34


Maybe this is uncommon, but these data are indeed used in some cases. Here is an example I have made for helping someone in his project some weeks ago in which I use zoomLevel, zoomX and zoomY data : http://jsfiddle.net/neveldo/h9e2dgeL/ .


but it tests for a specific id here, what's the empty equivalent?


Thanks!


Iptables_Semantics: theory Code_haskell
Timing Iptables_Semantics (8 threads, 139.861s elapsed time, 809.748s cpu time, 80.608s GC time, factor 5.79)
Finished Iptables_Semantics (0:03:41 elapsed time, 0:17:11 cpu time, factor 4.66)
Building Iptables_Semantics_Examples ...
Iptables_Semantics_Examples: theory Analyze_TUM_Net_Firewall
Iptables_Semantics_Examples: theory Analyze_SQRL_Shorewall
Iptables_Semantics_Examples: theory Analyze_Ringofsaturn_com
Iptables_Semantics_Examples: theory Parser_Test
Iptables_Semantics_Examples: theory SNS_IAS_Eduroam_Spoofing
Iptables_Semantics_Examples: theory SQRL_2015_nospoof
Iptables_Semantics_Examples: theory TUM_Spoofing_new3
Iptables_Semantics_Examples: theory iptables_Ln_tuned_parsed
Iptables_Semantics_Examples: theory Analyze_Synology_Diskstation
Iptables_Semantics_Examples: theory TUM_Simple_FW
Timing Iptables_Semantics_Examples (8 threads, 2471.736s elapsed time, 10270.088s cpu time, 740.540s GC time, factor 4.16)
Finished Iptables_Semantics_Examples (0:44:17 elapsed time, 3:00:22 cpu time, factor 4.07)
Running Iptables_Semantics_Examples2 ...
Iptables_Semantics_Examples2: theory IP_Address_Space_Examples_All_Small
Iptables_Semantics_Examples2: theory IP_Address_Space_Examples_All_Large
Timing Iptables_Semantics_Examples2 (8 threads, 9595.984s elapsed time, 60936.088s cpu time, 922.908s GC time, factor 6.35)
Finished Iptables_Semantics_Examples2 (2:40:08 elapsed time, 16:55:48 cpu time, factor 6.34)
Finished at Di 8. Dez 19:43:02 CET 2015
3:29:34 elapsed time, 20:19:45 cpu time, factor 5.82
../memusg ../Isabelle2015/bin/isabelle build -d . -v -c   72917,08s user 268,16s system 581% cpu 3:29:34,89 total
memusg: peak=722592


Looking much closer.  Cleaner tests!
Only issues are logical ordering:  OpCapability must be first if they exist, and OpConstant always precede function declarations and definitions.


It looks OK


samsung in htc kernel? xD


#4702-AirloopHVACUnitarySystem-autosizing-incorrect-for-heating-only-systems-when-using-FlowPerHeatingCapacity (rraustad) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1444 of 1445 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.93%25-yellow.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-70.54%25-green.svg)


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8587](https://teamcity.mesosphere.io/viewLog.html?buildId=88352&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8578](https://teamcity.mesosphere.io/viewLog.html?buildId=88323&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:19


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8576](https://teamcity.mesosphere.io/viewLog.html?buildId=88320&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:19


Can you create an issue for all of these TODO's explaining what exactly there is to do / check?


True, I am going to remove that particular check.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8582](https://teamcity.mesosphere.io/viewLog.html?buildId=88328&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:23


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8581](https://teamcity.mesosphere.io/viewLog.html?buildId=88322&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:23


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8580](https://teamcity.mesosphere.io/viewLog.html?buildId=88321&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8577](https://teamcity.mesosphere.io/viewLog.html?buildId=88326&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8579](https://teamcity.mesosphere.io/viewLog.html?buildId=88327&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8583](https://teamcity.mesosphere.io/viewLog.html?buildId=88329&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8585](https://teamcity.mesosphere.io/viewLog.html?buildId=88335&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8586](https://teamcity.mesosphere.io/viewLog.html?buildId=88337&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:24


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8584](https://teamcity.mesosphere.io/viewLog.html?buildId=88334&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:25


Your are right, you can ignore this comment :)


I would set expiry inside the except block


So I didn't go that route because in certain cases you might not use hadoop. For example if you are running just spark. I agree, the general case would likely use it. I'll add it in.


NACK libconsensus' verifyTx (if we ever have time to expose that) would need yet another parameter ```std::vector<bool> *fSequenceLocked``` which is not C API ready and its not CBlockIndex nor CCoinsViewCache (the only 2 data storage dependent parameters that would need to be abstracted out). This is not necessary.


В <div class="info"> лишние <p> можно обойтись одним и задать ширину.


I have changes it to OGDF_ENABLE_TESTS.


`checkArgument`


It still seems to me that it would be good to add something to assure we always get at least 32 bit values from `InputIterator`.  Perhaps something like:
```
        using InType = typename std::iterator_traits<InputIterator>::value_type;
        static_assert (std::numeric_limits<InType>::digits >= 32, "");
```
That would prevent someone from sending in, say, a string of `char`.  But I'll leave that to your discretion.


I have removed these changes.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8588](https://teamcity.mesosphere.io/viewLog.html?buildId=88365&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:14


sry tady for j in ...


@chuckwondo
GREAT job!  good touch on the virtual environment too!  :+1:


@alketh do we need this line? I think line 36 is sufficient right? I was more referring to other functions that use the pipe.


Well, it would be a bit tricky to get there, we would need to enlarge clientHello to >=256 bytes without usage of an extension. Any ideas?


i think sticking with hex is the expected behavior, so we should keep doing that.  512 bytes is a lot of data, SHA512 is only 64.


How about something a bit more clear:

```java
private static byte[] accumulateBytes(final Stream<byte[]> stream) {
    return stream
            .reduce(new ByteArrayOutputStream(), new BiFunction<ByteArrayOutputStream,
                    byte[], ByteArrayOutputStream>() {

                @Override
                public ByteArrayOutputStream apply(ByteArrayOutputStream out, byte[] bytes) {
                    try {
                        out.write(bytes);
                        return out;
                    } catch (IOException e) {
                        throw new RuntimeException(e);
                    }
                }

            })
            .map(new Function<ByteArrayOutputStream, byte[]>() {

                @Override
                public byte[] apply(ByteArrayOutputStream out) {
                    return out.toByteArray();
                }

            })
            .next().get();
}
```


I'd break out dispensing into another file. It'll make this one much smaller and easier to manage. Also make sure you triple check your while loop logic, just to be certain you can't get into a weird situation with that.


В <div class="form">
<input type="submit" id="submit" value="SUBMIT">  должно быть <textarea>


Ahh yes, sorry I misread what you were suggesting (e.g also converting the jsdoc to actual HTML for the gh pages).

It would likely be quickest to use [grunt-jsdoc](https://github.com/krampstudio/grunt-jsdoc) to generate the HTML.  If we want to temporarily make it look good we could also add [docstrap (ink-docstrap)](https://www.npmjs.com/package/ink-docstrap) and within the `jsdoc` grunt config, just set the template to one of those provided.  There's a descent article (albeit old), [here](http://samwize.com/2014/01/31/the-best-documentation-generator-for-node/).

If we go that route, I kind of like the [Cosmo](http://docstrap.github.io/docstrap/themes/cosmo/) or [United](http://docstrap.github.io/docstrap/themes/united/) themes.  Just my 2 cents :smile:


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8591](https://teamcity.mesosphere.io/viewLog.html?buildId=88383&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:17


Arreglar lo de eliminar administrador, que cuando sea un administrador que
accese al sistema se vean sus datos y creo que modificar administrador.
Ademas de lo de la reserva de libros pero del lado del administrador y lo
del conteo de libros disponibles
On Tue, Dec 8, 2015 at 3:16 PM albe211 <notifications@github.com> wrote:

> Hellen, cuales eran las 3 cosas que te ibas encargar?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/HellenOgando/ProyectoSistemaBiblioteca/commit/b849503c2c0c9f6fb753f6805bb329fd501b5a5e#commitcomment-14855904>
> .
>


LGTM!


hi @yawitzd
ok, but how do you check what version of python is installed?

To see what version of python is running:
```
$ python -V
$ python --version
```


Hi @curran -- it is available via this statement:
`window.chorus.session.get('sessionId')`

If you look at the frontend/app/assets/javascripts/chorus.js.erb ... (https://github.com/Chorus/chorus/blob/8bbfae78c310639085dec8628c3b095699538924/components/frontend/app/assets/javascripts/chorus.js.erb#L26-L26)

... you can see how there's this global "chorus" object ... it's defined in the body of that file as window.Chorus (capitalized) ... and then, at the bottom of that file, it's initialized into window.chorus (lowercase):

`window.chorus = window.chorus || new window.Chorus();`


no spaces between =
in kwarg


> But I guess I'd be able to see it in the profiler if I try.

Well, doesn't matter much I do believe it'd be faster anyway.

> What I was thinking about when writing this patch was to make the search cheap and basically independent of the length of the prefix so the "characters to type for autocompletion" settings could be eliminated. We could pop up the symbol list intelligently based on the number of results - now we pop up the list with 30 first results even if there are 10000 matching symbols - there's almost no chance that the symbol the user wants is in the list. We could delay the pop up until we get only 30 symbols or less so it's guaranteed that what the user wants is in the list. What do you think?

Interesting, but we'd still need to popup if a prefix is shared by all/most results, because of partial completion (using `<Tab>`), which makes incorrect results a lot more useful.  E.g. imagine typing `gt` with the GTK tags file, there will be endless results, but still proposing to complete `gtk_` is likely to be interesting.


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


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8602](https://teamcity.mesosphere.io/viewLog.html?buildId=88422&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8601](https://teamcity.mesosphere.io/viewLog.html?buildId=88417&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8594](https://teamcity.mesosphere.io/viewLog.html?buildId=88389&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8595](https://teamcity.mesosphere.io/viewLog.html?buildId=88396&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8590](https://teamcity.mesosphere.io/viewLog.html?buildId=88378&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8593](https://teamcity.mesosphere.io/viewLog.html?buildId=88388&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8600](https://teamcity.mesosphere.io/viewLog.html?buildId=88416&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8599](https://teamcity.mesosphere.io/viewLog.html?buildId=88404&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8597](https://teamcity.mesosphere.io/viewLog.html?buildId=88403&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8596](https://teamcity.mesosphere.io/viewLog.html?buildId=88398&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8592](https://teamcity.mesosphere.io/viewLog.html?buildId=88387&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:17


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8598](https://teamcity.mesosphere.io/viewLog.html?buildId=88406&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:17


It's just an allert/reminder


I just copy pasted the whole Import section from my original package.
This basically ensures, that the pipeoperator can be used throughout the
package.

Am 08.12.2015 um 10:31 schrieb Kelli Johnson:
>
> @alketh <https://github.com/alketh> do we need this line? I think line
> 36 is sufficient right? I was more referring to other functions that
> use the pipe.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/r4atlantis/atlantisom/commit/92bd502666090586fe7293bfc682bc399739a696#commitcomment-14857852>.
>

--
<°)))>< ><(((°> <°)))>< ><(((°> <°)))>< ><(((°>

Alexander Keth
Institute for Hydrobiology and Fisheries Science
University of Hamburg
Olbersweg 24
22767 Hamburg
Germany
Tel.: +49 (0)40 428 38 6708
Fax:  +49 (0)40 428 38 6618

<°)))>< ><(((°> <°)))>< ><(((°> <°)))>< ><(((°>


Thanks, Robert

________________________________________
From: RobertFewinsKalb <notifications@github.com>
Sent: Tuesday, December 8, 2015 2:10:59 PM
To: courtrightd/MAXIS-BZ-Scripts-County-Beta
Cc: Risor, Tom
Subject: [MAXIS-BZ-Scripts-County-Beta] Defining "is_not_blank_excel_string" (eea818b)

Defining "is_not_blank_excel_string"

Now, the comparison function should work. @TRISOR should get credit for the 1 line :)

---
Reply to this email directly or view it on GitHub:
https://github.com/courtrightd/MAXIS-BZ-Scripts-County-Beta/commit/eea818bd7072a0f636a360f9eb24b25a52aba0bd


hmm is it possible to hit a TZ bug if the certificate is produced with a != tz than the box that is running mx?


Oh I see! I didn't know, since it wasn't in the documentation. I though it weird that it was in the data object. But now I understand.
Do you think it's bad to break it? Should we revert it back?


of the cert?


hi @same1009
good job!  :+1:
To see what version of python is running:
```
$ python -V
$ python --version
```


remove space after :


has new function called "check_disp_word" that checks the secret word to see if the entered letter matches up with any letters in the secret word (sec_word).  There are also different outputs to the screen to check what each thing outputs.


A TODO implies there is still something... _to do_.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8603](https://teamcity.mesosphere.io/viewLog.html?buildId=88423&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


Who knows? :)


fast-forwarding end-to-end/timeseries to borshop-integration-1297-bugfix/jdm-adjust-quanta-limits-for-exclusive-start-inclusive-end = cd53607d


Merge sha 2541aecb is stale.


merging basho/riak_kv/fix/az/test-for-ranges-spanning-exact-multiples-of-quanta = 84040cfa into borshop-integration-1292-fix/az/test-for-ranges-spanning-exact-multiples-of-quanta


basho/riak_kv/fix/az/test-for-ranges-spanning-exact-multiples-of-quanta = 84040cfa merged ok, testing candidate = 42044460


Should have a comment saying what this is doing.
It's interesting since it's a void function, so doesn't actually participate in checking correctness.
e.g.:
// Collects names of IDs for improved diagnostics.


This to catch exceptions from getWindowAttributes, as noted in https://github.com/xmonad/X11/pull/35#commitcomment-14662107

Again, I am mucking around using trial and error-style programming, so any suggestions for improvements are much appreciated.


Somehow these ascii double quotes got replaced by unicode double quotes. Could you switch them back? We don't want directional double quotes.


Optional: Remove these cases, since they're the same as the default case.


a matter of style... I'd just collect return_code and msg on each case, and call sendCode at the bottom of the method


Same as above, we want non-directional double quotes.


NACK this adds 3 parameters that aren't strictly necessary for CNB optimizations (which by the way, are supposed to be the goall of this patch but are not contained here).


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8604](https://teamcity.mesosphere.io/viewLog.html?buildId=88424&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


I would say `The state module name` instead of `The state name`


add trailing comma


Maybe clarify that the identifier can be either the `- name` parameter, or the ID declaration for the state? (the ID declaration is the first line in the state stanza)


It is like `format C:` in DOS.


все ещё смешно


Huh.  I was just looking at the various `rand_int()` signatures.  I don't believe any of them conflict with the others.  Since that's the case, I wonder if we might be better off using `static_assert` to constrain these templates instead of using `enable_if`.  In my opinion `static_assert` is often a better choice because it is more readable in the source code.  Also a programmer accidentally misusing the interface gets a better error message from `static_assert` than they do from `enable_if`.

If we were selecting for different type characteristics, then we'd have to use `enable_if`; `static_assert` would not be an option.  I don't think that's the case here, but I could be wrong.

Just for your consideration.


We prefer reinterpret_cast<const char*>  here.
C-style casts are frowned upon in the style guide.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8605](https://teamcity.mesosphere.io/viewLog.html?buildId=88425&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8612](https://teamcity.mesosphere.io/viewLog.html?buildId=88430&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8607](https://teamcity.mesosphere.io/viewLog.html?buildId=88427&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8606](https://teamcity.mesosphere.io/viewLog.html?buildId=88428&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8608](https://teamcity.mesosphere.io/viewLog.html?buildId=88426&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8611](https://teamcity.mesosphere.io/viewLog.html?buildId=88433&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8610](https://teamcity.mesosphere.io/viewLog.html?buildId=88431&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:12


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8609](https://teamcity.mesosphere.io/viewLog.html?buildId=88429&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:13


lgtm! nice writeup.


@MrWolvetech Lol, just use this repo as upstream


mm... totally! :stuck_out_tongue:


sorry, you're right. since `tiles` is a `std::map`, it probably doesn't make a difference, but if you just require the presence of one element, `tiles.find(id) != tiles.end()` may be faster in the generic case (e.g. for multisets/multimaps)


hi @emilyhoughkovacs
> good job! though you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


s/Extrackt/Extract/


hitArea doesn't seem to be adhered to after this commit. Trying to find the root cause


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8613](https://teamcity.mesosphere.io/viewLog.html?buildId=88435&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


Why?


Looks like this is actually clarified below. Might be worth adding it here as well.


ah... ok nao estava a evoluir a largura...


hi @ingrid88
>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


@bastianallgeier: Just found out the hard way that yesterday's "improvement" to the eMail tag had a fatal flaw: the strstr() function returns 'false' instead of something useful if no additional parameters ('?subject=...') are present in the eMail address. Used an array split instead, which performed as expected in all my tests.

Sorry for this.


Need #include <algorithm> to use std::transform.
Won't compile on GCC otherwise.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8618](https://teamcity.mesosphere.io/viewLog.html?buildId=88440&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


Oh ! Got it backwards. Thank you !


Hey Ivan, 2 things:

1.  This will break the logic.  At RootDepth=1, we don't know the previous score.
     So updating alpha/beta will be erroneous.

2.  Time spent when rootDepth <=5...is literally nanoseconds.  The search probably spends about 0.000000001% of it's time there.  So updating those values at such a shallow depth will be meaningless in the grand scheme of things.  It will spends at most a couple thousands nodes total at those depth.


We need
`#' @importFrom magrittr %>%` in every file that uses it
and
`magrittr` listed in the DESCRIPTION file, which it already is.


So -- we are inside a view, the purpose of views is to render models ... the model this view is associated with is 'hdfsDataSource' (which is what we need) ... so this object must be available.

And, it is, this statement (used within this view) will retrieve the HdfsDataSource ... and we can get the id and other such things off of it:

`this.model.get('hdfsDataSource')['id']`

... you can browse all the stuff defined inside of that model in the Chrome console:

<img width="1650" alt="alpine chorus-1" src="https://cloud.githubusercontent.com/assets/486640/11667928/6a3b9492-9da9-11e5-9a81-3883d5cfa425.png">


:kiss: :kiss:


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8614](https://teamcity.mesosphere.io/viewLog.html?buildId=88436&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


Should have a blurb
// Returns true if the substr is a substring of message.


Good point. I will have to think about his and make a change in a future PR.


watch out for whitespace


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8615](https://teamcity.mesosphere.io/viewLog.html?buildId=88438&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8616](https://teamcity.mesosphere.io/viewLog.html?buildId=88439&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8617](https://teamcity.mesosphere.io/viewLog.html?buildId=88437&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


Does this also fix #39?


Perhaps it has to do with this? https://github.com/npm/npm/issues/9518


I would like to leave these here just in case I want to add functionality for this later.


code we will be taking from


Why is this a separate thing? "procedures" or "routines" are just like regular functions, except that they have some additional attributes.


Redundant else


In the original design, all escape codes were valid UTF8 strings, so that output could be parsed over code points instead of bytes.

I moved away from this with attachments, but not arguments, because it is more complicated to parse, because we'd have to define a length and endianness for each component of each argument, and because it wouldn't significantly reduce the length of codes, which is the only advantage.

This document is out of date; in HEAD attachments are back to being base64 encoded without a length attribute and these codes are now UTF8. It turns out that there are a problems with including any binary data in these commands, mainly that they can become mangled by the tty if it hasn't been set to the correct mode.


Fixes sub-issue described in #12 - locks in simulation mode.


The ContinueTarget (operand index 1) can be forward declared also.
So SpvOpLoopMerge should be in the first set of cases.


Wait for my thread implementation! :sunglasses:


This should be planned and executed as a regular query (e.g, similar to VALUES, etc). In fact, routines that return results can be invoked wherever there is an expression (see Section 6.3 - value expression primary in the spec)


I think this can be
```java
int[] hashChannels = IntStream.range(0, partitionChannelTypes.size()).toArray();


Also, functions and routines should be in the same namespace.


This renders null the idea of not having the context anchored. You need to create a static class.


This explanation really argues that getStorageClass needs to be fixed, not that callers should check for Booleans.


will do


@pjsier, how were the *.txt files generated?


ok actually I stole this from the internet


looks good! works on electron

should we add another flag to report for electron?


RE:  python install

@jamesevers

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


"%func1 = OpLabel " doesn't belong.  In particular, its basic block doesn't end with a branch or return.


The idea of having this code as it was is keeping the placeholder for future validations. It does not matter, but may be a comment is in order.


hi @jmfradkin

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


Forgot to mention! I used pdf2txt.py from PDFMiner. It made it a lot more doable to parse instead of dealing with the pdf


"A block always ends with a branch instruction"  (branch, return, kill, unreachable, switch.)


This looks good.  Would be nice to see a test change due to it.  Shouldn't require a new test file.


Thanks for the update!

I will merge this update as soon as you adjust your changes to our latest ways of formatting our code.
This includes putting spaces before and after operators and spaces after a **(** and before a **)** if there is content between the parentheses.
Additionally the line "*// vim: set ft=cpp:*" at the very top ensures that all .gsc files are highlighted as C++ files on Github, so please do not remove this one, either.

I myself do not have that much experience with coding, but putting your changelog within the file is counter productive (this will fill it up sooner or later). The changelog will be powered by looking through all commits.
Concerning the editing of your name into the "code contains" part in the header: I fully respect that, but we might put all these credits into the CREDITS.txt, because keeping track of all submissions within the file itself is a little stressful.


hi @holbrojm

To see what version of python is running:
```
$ python -V
$ python --version
```


But am I going to lose all the existing uploaded information?


yes, I read the Issue latter and understood. It's too bad that there is no way to say, ignore next N bytes if you dont support X. :/


You only need a context here, not a full Activity. Why not just use findPreference?


Well done thanks


You need to rebase this one. I changed some things and squashed. Sorry about that.


Indentation does not match up.


As long as it is returned by value there is no point in applying `const`.


Sorry, didn't mean to leave you hanging, but unfortunately I'm going to need to leave you hanging a bit longer. I understand why you might want a fiddle to explain what I'm talking about, I just don't have time to make it right now. I'm about to go on a trip. I'll make it when I get back at the end of December.


thank you!! u Helped me


ObjC uses YES/NO ;)


Yeah, that .pdf is a mess. Do you still have that code that you could add for completeness?


Add


It looks like this is already covered by ValidateObjectMetaUpdate


Some of these formatting changes seem silly, e.g. this one, awkwardly breaking a line to make it 4 characters shorter.


Could you please add a test for ValidateConfigMapUpdate


Okay, thanks!


Yeah, it may be clearer, but it is still [math]O(n^2)[/math] and does a lot of `byte[]` allocations and copying. In Java 8 it is much clearer! :smiley:

What I would _really_ like is a way of comparing two `byte[]` streams, byte-for-byte, without assembling the complete array at all! But I couldn't work out how to do that.


I agree with the `is_integer` check, but why remove the elseif?


Shouldn't this be `"history": "1.13.x"`?


Also, I think NORMAL=1 is somehow special for legacy reasons. I think Tridge has mentioned he likes it first because lots of people fly auto missions that don't use auto takeoff/land and that somehow matters to the enum order. Enum should go:
NORMAL=1,
TAKEOFF_WAIT=2,
TAKEOFF=3

I'll ask Tridge about it. Personally I think NORMAL should be = 3 after the takeoff


Apart from using something like CanCanCan (which may be OTT for this app), you can add a `before_filter :load_quote` to load the quote for all three actions.  A separate before filter (or `before_action`, same thing) could load the vote for the update and destroy actions.


I would hope and think the `IOConfig` object could be immutable; the ability to test is in my opinion not sufficient reason to introduce mutators.


Зачем так жестоко


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8624](https://teamcity.mesosphere.io/viewLog.html?buildId=88466&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8625](https://teamcity.mesosphere.io/viewLog.html?buildId=88467&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


I actually just run the command pdf2txt.py on the file after installing PDFMiner, so there isn't any more. Could add something to a README.md though


This is one of those things for which java get a bad reputation. Your only guarantee of the contract is the documentation (if you pass a big enough array) since dirs is of type List interface. Just a note to be careful.


done


what a wonderful command of this "TINT COLOR" Well Done!!!!


Xin, this change LGTM.  What is the hit rate of the cache?   (You can add counters and printf the hit-rate every 100th request or every invalidation request or something).


See above, but you'd ideally do `Vote.new(...)` rather than the above.


tohle ti nezkontroluje poslední písmeno v textu protože for máš range(0,len(string)-1)
někde přidej
if string[-1] in lW:
    fC += 1


This seems wrong. Bucket count should be the map size and this should validate that all bucket values are between zero and the size.


Yes it should be.


FWIW, I fixed a lot of previous indentation changes in https://github.com/onsip/rtpengine/commit/17ee5feed70adb1bf2f6de7573b0ea8493a0b492, with the idea being that a `git rebase --autosquash` before the eventual PR to https://github.com/sipwise/rtpengine would clean the commit history up.

That commit also added an EditorConfig file, to help avoid issues like this.


Tridge says it doesn't matter so lets go with:
TAKEOFF_WAIT = 1
TAKEOFF = 2
NORMAL = 3


Proč ne jenom:
for string in text:


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8627](https://teamcity.mesosphere.io/viewLog.html?buildId=88469&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:13


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8626](https://teamcity.mesosphere.io/viewLog.html?buildId=88468&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:15


As long as we actually internalize both the input and output versions of the unified and formatted flags we should differentiate between the output and input versions of the file name.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8628](https://teamcity.mesosphere.io/viewLog.html?buildId=88470&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:16


hi @JordanGoodspeed
good job! :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


I just missed it - by the way, to perfectly emulate the semantics, I would have needed to call `beast::rand_int(9999999)` (intervals specified in `rand_int` are always closed, never open).


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8629](https://teamcity.mesosphere.io/viewLog.html?buildId=88472&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:13


Crafting recipe:
![2015-12-08_20 21 31](https://cloud.githubusercontent.com/assets/13855359/11668347/973cb544-9dee-11e5-8a66-106d35036fe1.png)


@bajtos: Probably it makes more sense to have an argument in MySQL.prototype.updateOrCreate for replace and if value true is passed, we get the fields by calling this.buildReplaceFields(model, data); as opposed to var fields = this.buildFields(model, data); so no need for duplicate code here, thoughts?

Aslo please note this is a very initial implementation


hi @jstnstwrt

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


Differing basic types is okay; the GLSL spec. says they don't have to match, and does not implicitly convert them.  Is there just a problem in the SPIR-V translation of mixed types?  The SPIR-V translator has smear logic in it, maybe it just needs to be applied.

Did you have a GLSL -> AST example of the wrong thing happening?


It was not


This should probably have a cap (one million?)


saw approval from zeeshanlakhani
at https://github.com/basho/yokozuna/commit/1007f15515ddf43719b69e8511ea190954ef9b34


merging basho/yokozuna/feature/jv/yz-faceted-search = 1007f155 into borshop-integration-571-feature/jv/yz-faceted-search


basho/yokozuna/feature/jv/yz-faceted-search = 1007f155 merged ok, testing candidate = 2288d41e


pryč


RE:  python install

hi @outsideken , good job :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


I can add this, but I'm not sure it gives us much. I see nothing wrong with passing in, say, `std::uint8_t[512]` instead of `std::uint32_t[128]`.


I think you can reduce that example to one line
```
Observable.interval(1000).subscribe((d) => console.log(`${d} seconds elapsed`));
```
I don't know if is there any reason for doing the example that way, but still.


the constructor executes code and registers the device into vdr. you can't control this sequence with "non-pointer" variables. this pattern should follow exactly the example vdr gives us:
http://projects.vdr-developer.org/git/vdr.git/tree/PLUGINS/src/dvbhddevice/dvbhddevice.c?h=stable/2.2#n37


That would be good--just enough so that it's reproducible.


Nicely done! This will work except for the case where you plug in, or reboot, with a dead battery. it will think it's a full battery with one lower cell count. Not sure what we can do about that but worth mentioning in the comments.


hi @kennmyers

good job :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


Yes, I saw the ```branch-api``` was updated to handle the problem in the same fashion, since it originally had similar bugs.  This was a first hack at it, the refactoring commit following this one has a slightly more elegant solution.  The reason for not jumping straight to the ```branch-api``` is to ease the migration process and to squash bugs until I get time to review this plugin's project path.


@ivanzaicev Удаляй все такие большие пропуски
Пропуски строк должны быть для выделения логических блоков, максимум 2 пустые строки, чаще всего -- одна


Is this method needed? I don't see a `Status` field in `ConfigMap`


Interesting


Is there any place where we log the PCAP file locations? That might be nice to have as debug statements. They come out in the `Response dump for 'answer'` log, but that doesn't seem like where we should actually log their creation.


FakeConfigMap is missing a trailing "s"


The build were running over themselves.  There were 3 build running and all vying for the same resources, so they all hung.  Dustin C. felt that removing this could help in the short-term while we try to fix it properly.


Interesting. I'll give it a try.


hi @kzecchini

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


**/ won't match ./ for some reason


Lowercase configmaps


Thanks :D


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8630](https://teamcity.mesosphere.io/viewLog.html?buildId=88473&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8631](https://teamcity.mesosphere.io/viewLog.html?buildId=88475&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:10


hi @mdlai
good job :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8632](https://teamcity.mesosphere.io/viewLog.html?buildId=88476&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8633](https://teamcity.mesosphere.io/viewLog.html?buildId=88477&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


Yep, I need to do more work on the public interfaces.


Escaping and quoting.


repaired


I think that could you move the methods typeCodeInput, typeCapacityInput and clickOnSaveButton, to other method, such as:
public ConferencRoomPage fillForm(roomCode,roomCapacity){
                 typeCodeInput(roomCode);
                 typeCapacityInput(roomCapacity);
                clickOnSaveButton()
 return new conferenceRoomPage();
}


Of course. s3ql is not able operate in a subdir. (I think.)


so altogether, it looks like:
```
context 'when using manual networking', manual_networking: true do ...
  it 'changes static IP address' do ... end
  it 'deploys multiple manual networks', multiple_manual_networks: true do ... end
end
```
is this right?


hi @natalieretamar

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


In a way, these changes to the code have exactly that effect. :-)


hi @nisharma85

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


Oh, yeah.  I should know better.  Thanks for catching my mistake.


Please make it into Release. :D


@ivanzaicev Сделай правильно форматирование: если пользуешься WebStorm, то в открытом проекте, нажми
`ctrl+shift+a` -> reformat code
Там можно ещё как-то по менюшке пошарить и сделать реформат во всём проекте


hi @jmfradkin

good job :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


You know you can do `$(patsubst %.c,%.o,$(wildcard $(SRC)/**/*.c $(SRC)/*.c))`, right?
Besides, you need the pattern to be `$(SRC)/%.c,$(BIN)/%.o`, anyway


Внутри `thead` не `tr`, а `th`
Так тоже работать будет, но `th` правильней


This seems kinda iffy to me (it might not be callable). Let's do an explicit `typeof(this.props.onSort) === 'function'`


will revise


calling `is.character(c(1,"a",2))` returns `c("1", "a", "2")` therefore we also need to check that the `length(param) == 1`


I know exactly when the constructor/destructor will be executed. It's all well-defined by the C++ language standard.

What is the specific ordering problem you worry about? What can go wrong, what's the worst case?

I think the VDR code was written that way because the author wasn't proficient enough with the C++ language. He was using pointers to have control over something instead of learning about how C++ works.


I didn't think this project was of interest to anyone so I stopped contributing to it.  However if you guys (http://adn-cis.org/forum/index.php?topic=3248.0) find it useful I can continue.


Hum, right


hi @scullem

good job :+1:

To see what version of python is running:
```
$ python -V
$ python --version
```


Uf, I have already uploaded with the web interface about 2TB, so it's not my intention to reupload all again. I tought this works the same as hubicfuse that takes what already exists on the container...


tab


I was thinking to do that.  I'd be happy to do it.  Do you have a way to
detect desktop?

On Tue, Dec 8, 2015 at 12:52 PM, Colin Diesh <notifications@github.com>
wrote:

> looks good! works on electron
>
> should we add another flag to report for electron?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GMOD/jbrowse/commit/380dd78902bfdfe37bfa841f748946f4dedaae55#commitcomment-14858308>
> .
>


To answer you question you may want to grep for Copyright in the source. I see 2002 but most are 2004.
I doubt that it was "designed not to be thread-safe" but more of get something working.

But best to ask @nmav  why the mutex code was removed, and what would it take to get to be thread safe.


For `CALL`, the spec says *"[subject routine] shall be an SQL-invoked procedure"*, so it seems that "procedure" is more specific (and better to use here since this can't be any other type of routine).


I think that the whole function can also be written without the `match.call()` function.
**Could you explain why is `match.call` actually necessary ?**


Don't you need to replace `_` with `server` and then call `defer server.Terminate(t)` after this?


hi @Threynaud

>> ok, but you lost the indent :(

To see what version of python is running:
```
$ python -V
$ python --version
```


PRYČ


The Slack notifications plugin for each job was waiting on the jobs running in parallel to finish before - causing a deadlock. We can look into this more if the serialization becomes a problem.


so here I went to see the code to check what'd be so bad about following the recommendation and passing the real sized array, and you basically avoid yourself from having this code:

```
    public <T> T[] toArray(T[] contents) {
        int index = 0;
        if (size > contents.length) {
            Class<?> ct = contents.getClass().getComponentType();
            contents = (T[]) Array.newInstance(ct, size);
        }
```

which at the worst is slightly slower, as it also ends up putting your old empty array reference to no use as it ends up re-assigning a new instance. so you save yourself an object instantiation and cleanup.


nesmí být v tom cyklu protože by to např 20 zkontrolovalo to stejné místo


Is this commented because there is no AdNetworkType available in the report yet?


[It is in v1.0.2](https://github.com/rackt/react-router/blob/v1.0.2/package.json#L44). This is for master, which is the in-progress v1.1.0.


done


Using `assert_that` adds additional dependency on `assertthat` package.
We could change it later, if this were a problem.


Is it possible to add a "real" mode for sneak by doing .sneak mode?


Favicon is gone... #126


ok


all tests pass:
success: http://buildbot.bos1/builders/test-riak_kv/builds/2894


This seems a bit too clever. Based on the name of the function (some comments would be nice BTW), I think this constructs an UPDATE statement that will update pg_class.relpages and pg_class.reltuples for a list of relations. However, it's really not obvious how all those maps, lambdas and zips will produce a string like that. I would suggest rewriting this using more simple constructs, like classic if-else statements. I'm not very good with Python, so maybe that's obvious to someone  more experienced, but also keep in mind that this code probably will be read and edited by many more people like me who don't know Python that well.

Also, check escaping and quoting...


--test


The `mockOnly` parameter comes from the outer function and allows us to implement some unit-tests.


extra line


oK


all tests pass:
success: http://buildbot.bos1/builders/test-yokozuna/builds/1483


Same comment as above about `defer server.Terminate(t)`, here and in TestGet, TestList, TestWatch.


Ok, see previous comment. This is even more "clever" :-)


is it really?


thanks, will start merging this now.


Apologies for the false alarm. I didn't read up on your release flow.


```java
final InputStream in = new ClassPathResource("v2/apps/GET_{id}_download_response.bin").getInputStream();
Streams.wrap(this.applications.download(request))
        .reduce(Boolean.TRUE, new BiFunction<Boolean, byte[], Boolean>() {

            @Override
            public Boolean apply(Boolean matches, byte[] actual) {
                try {
                    byte[] expected = new byte[actual.length];
                    in.read(expected);

                    return matches && Arrays.equals(expected, actual);
                } catch (IOException e) {
                    throw new RuntimeException(e);
                }
            }

        })
        .consume(new Consumer<Boolean>() {

            @Override
            public void accept(Boolean matches) {
                assertTrue("Array contents do not match", matches);
            }

        });
```


@SharangP @OstrichProjects  now this is a good idea


Yes.  Should I remove it for now?

On Tue, Dec 8, 2015 at 4:13 PM Gustavo <notifications@github.com> wrote:

> Is this commented because there is no AdNetworkType available in the
> report yet?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/googleads/aw-reporting/commit/9dd44ca8425ec7c0bd91cba69b7d531959dbd8d4#commitcomment-14858860>
> .
>
--

Allison Greene | Developer Advocate | allig@google.com | 201-913-0277


As mentioned in #120, the ```branch-api``` may be implemented or this plugin deprecated.

For now though, the new API would not be consumed in this plugin since the multi-branch projects from this plugin are limited to a single ```SCMSource```.  There is not a possibility for a child item to match more than one ```SCMHead``` based on the child name.

Are there any users of ```SCMHead.HeadByItem#findHead(Item)``` that could potentially interact with this plugin?


This is handy for debugging.


OK


Renamed check_disp_word to check_sec_word because it made more sense and created the disp_isnt_sec function.  disp_isnt_sec checks to see if the display word equals the secret word and returns a 0 if they are the same by checking every letter.  The function returns a 1 if the words are different. The function will be used along with a count value to determine if the game should continue.


No worries. I'm glad someone's paying attention to this stuff!


yea its so easy


> On Dec 7, 2015, at 11:18 AM, Michael Gottesman <mgottesman@apple.com> wrote:
>
>
>> On Dec 7, 2015, at 9:17 AM, atrick <notifications@github.com <mailto:notifications@github.com>> wrote:
>>
>> I don't know if this is overkill or not, but I want to point out a few things.
>>
>> The scan only happens for unreachable blocks which are typically tiny, so it's hard to say if the extra memory is worth it. This could actually be adding overhead. If hash entries were only added for unreachable blocks, it would be more efficient, regardless of whether it's an analysis.
>>
>>
>
> I am only hashing entries of unreachable blocks.
>> Making this a formal analysis does add some complexity in reasoning about its invalidation.
>>
>>
>
> I am fine if this is not a formal analysis and I just make a utility + context that I pass in between the loop arc functions.

Just an FYI, I have not forgotten about this. I need to make the multiple ARC pass scaffolding in order to remove this. I am doing that now.

>> As a side note, I want to point out that we should have a clear distinction between a "caching" analysis vs. a "decaying" analysis. A caching analysis such as this would at least never need to be serialized between passes (otherwise making it an analysis would definitely add too much complexity).
>>
>> —
>> Reply to this email directly or view it on GitHub <https://github.com/apple/swift/commit/05ac5962283ca03696c823e959f9ed476501f978#commitcomment-14826468>.
>>
>


It's probably worth modifying `validNewConfigMap()` to set some labels that would match here


Procedures are different: they have and can be invoked with named arguments. We can merge the namespace later, but they need to be separate for now. Functions are in a single global namespace but procedures are qualified with catalog/schema.


Agreed. Building on your last suggestion for this method, what about:
- (BOOL)loadSchemaForReferencePath:(NSString *)referencePath filePath:(NSString **)outFilePath pathComponents:(NSString **)outPathComponents error:(NSError **)outError

Then the parser can manage actually setting the properties, but know it's a valid file that produced a schema/node.

I do like adding an error, so the description can differentiate between 1) a file not found 2) a file that doesn't contain a valid schema


Oops, thanks.


I still can't figure out where to put the public access key. Do I have to put it somewhere in the code and compile the export? Or is there some function I need to override that returns the correct String?


like the mona lisa but for your pee


IMHO this should go to component-editor/doc


109649198_EvapCoolers (Nigusse) - x86_64-MacOS-10.9-clang: OK (1972 of 1978 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.7%25-yellow.svg)


Could you put in some valid matching fields, such as name=foo?


У `href='#'` есть проблемы небольшие. Эта ссылка никуда не ведёт, но её можно открыть в новой вкладке. Если у тебя здесь это стоит для того, чтобы обозначить никуда не ведущую ссылку, лучше просто убрать атрибут `href`


Please add a file header comment explaining what this program is, how it works etc.


Ok, I guess it's ok in this place, although I would say "a procedure", not a *stored* procedure, since it can be a procedure not defined and stored by a user.


Should probably ignore pg_temp_*, not just pg_temp_1.


s/watch/watches/


It wasn't ready yet, but the build-in POST function of DirectAdmin should work.

Let's move on with the new library now ;).


I think you can remove it for now. We can revisit this once more fields are added.


When I removed those, all of the pistols gave me perfectly generic items. I removed the whole pistols folder under items/active/weapons/ranged/tiered/pistols And it fixes the PGI issues.


inline стили -- плохо, убирай в файл .css


I already compiled .-. as i always do :stuck_out_tongue_winking_eye: just came here to check the number of commits


убирай inline-стиль


not quite sure what you want the change to be here--can you give us some more details?

we tried `su vcap` on the director, and below is output:
```
vcap@062b3bfe-015a-49fa-bb84-e4f4e89b158d:~$ su vcap
Password:
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
```


use http.Error()


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8634](https://teamcity.mesosphere.io/viewLog.html?buildId=88480&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:11


пробелы при задании атрибутов не ставятся `<img src='...'>`


```java
final InputStream in = new ClassPathResource("v2/apps/GET_{id}_download_response.bin").getInputStream();
Streams.wrap(this.applications.download(request))
        .consume(new Consumer<byte[]>() {

            @Override
            public void accept(byte[] actual) {
                try {
                    byte[] expected = new byte[actual.length];
                    in.read(expected);

                    assertArrayEquals(expected, actual);
                } catch (IOException e) {
                    throw new RuntimeException(e);
                }
            }

        });
```


Apparently I actually added it to the _reportCustomUsageStats here https://github.com/GMOD/jbrowse/commit/c939e5b903f4b434bd4f6d2e3e86ffde68bff886

I guess only the server side would need to be updated


Зачем здесь пустой блок nav?


109649198_EvapCoolers (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1978 of 1984 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.7%25-yellow.svg)


Working with files is a pretty surprising API. Wouldn't it be better to pass the query as argument, and return the dump as the return value? File access can be confusing, as you then have to set up a directory that's readable and writeable by both the gpadmin user that runs the server, but also the user running the client, which are not necessarily the same.


It gives an error message to the user who used `/kickbattle`.

If you call `room.leaveBattle` and wait for it to return `false`, it would instead give the error message to the user who was kicked and nothing to the user who used the command, which is undesirable.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8635](https://teamcity.mesosphere.io/viewLog.html?buildId=88482&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8636](https://teamcity.mesosphere.io/viewLog.html?buildId=88483&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


For consistency, should be a ``!`` method due to its potentially `exceptional` behaviour


Не нужно тут выходить. Просто верни пустой объект Profile


``request_confirmation`` seems more in line with its behaviour and purpose


Не смешивай свои файлы и файлы библиотек
Убери всё, что связано с bootstrap в libs/bootstrap
и подключай `<link rel="stylesheet" href="libs/bootstrap/bootstrap.min.css"/>` и `<script src="libs/bootstrap/bootstrap.min.js"></script>`


For the time being I had to switch to ruby 1.9.3


`MemoryUsage > limit` is more readable


Что это за слеш?


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


This should have been left as Java 8.  I set it that way intentionally.  I've set it back in 8fea3dd0af65218d4e202f750a6d6f0fdcc924d7.


This is the code used for real-time?


в css `body, html` описывай самыми первыми


109649198_EvapCoolers (Nigusse) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


после двоеточия -- пробел


Fantastic. Works exactly as expected. Again, many thanks!


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8638](https://teamcity.mesosphere.io/viewLog.html?buildId=88487&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8639](https://teamcity.mesosphere.io/viewLog.html?buildId=88488&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


#29

I force pushed over this, so re-pinging


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1446 of 1446 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


Yeah, this one in particular looks weird, I guess I just need to cut that comment because otherwise it can't fit the code into 100 chars. That's why I suggested bumping to something like 120.


new files added for the first unit test


The convention we have for Validate*Update is to have the new object as the first function argument, and the old object as the second. Would you mind changing it here, and in strategy.go?


It will still appear in the list with the hash, it's just removing it so that it's treated the same as the tags in the tags management screen.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8640](https://teamcity.mesosphere.io/viewLog.html?buildId=88489&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8641](https://teamcity.mesosphere.io/viewLog.html?buildId=88490&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Error while applying patch Build time: 00:00:14


why the optional `fn`?


I'd call this `ConfigMapToSelectableFields` to be consistent with similar methods in other files.


what does `fn` do?


Not yet. It is blocked behind us moving to the .NET Core version of msbuild as well as the .NET Core version of csc/Roslyn. Once we get to that point where we are restoring and using that toolset for our repo then we will start allowing C# 6.0.


I think that's a bad idea. Technically, any function that is not defined in the standard is a "routine", so some of the built-in presto functions and those provided by connectors should be treated as such. This means that they should be resolved according to the sql-path rules, etc. (even custom types should follow these rules).

If we don't put them in the same namespace, it will be very hard to unify them later without breaking backward compatibility and introducing conflicts, since there's no distinct syntax to invoke them when used in an expression.

Regarding named-arguments, that only applies to the CALL syntax, so it's just a usage-site contraint.


No, see Section 10.4 Syntax Rules 5.b *"If RI is immediately contained in a \<method selection>, then an SQL-invoked routine R is a possibly candidate routine for RI if R is an instance SQL-invoked method ..."*

For contrast, see 5.a *"If RI is immediately contained in a \<call statement>, then an SQL-invoked routine R is a possibly candidate routine for RI (...) if R is an SQL-invoked procedure"*.

Note the distinction between "SQL-invoked method" and "SQL-invoked procedure".


Please don't expose this publicly - I don't think it's a safely fixed API... maybe src/core/support/slice_helpers.h?


:+1: Let's get it in! I haven't reviewed all details. Will need to spend some time playing with the API to see if they work well, but for now looks good.


The rest of the code base either calls this Match<resource name> or just Matcher. Most of it uses the former approach. I'd probably go with MatchConfigMap.


That's the thing, what implementation are you looking at? dirs is a List interface. No way you can be sure it is that way. In this case is LinkedList, we know it, but what if the actual type's instance is unknown?


YAY


TeamCity LabKey :: Trunk :: Community :: CDS postgres 9.4 [Build 28](https://teamcity.labkey.org/viewLog.html?buildId=290374&buildTypeId=LabkeyTrunk_CdsPostgres94) outcome was **FAILURE**
Summary: Tests failed: 18 (1 new), passed: 30 Build time: 01:05:09
### Failed tests
```
org.labkey.test.tests.CDSVisualizationTest.verifyBoxPlots: <no details avaliable>

org.labkey.test.tests.CDSHelpCenterTest.verifyHelpCenter: <no details avaliable>

org.labkey.test.tests.CDSTest.verifyCounts: <no details avaliable>

org.labkey.test.tests.CDSTest.verifyGroups: <no details avaliable>

org.labkey.test.tests.CDSTest.testLearnAboutStudyProducts: <no details avaliable>

org.labkey.test.tests.CDSTest.clickOnLearnAboutStudyProductsItem: <no details avaliable>

org.labkey.test.tests.CDSTest.verifyFilterPane: <no details avaliable>

org.labkey.test.tests.CDSTest.testLearnAboutStudyProductsSearch: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyDensePlotBrushing: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifyTimeAxisWithMultipleSchedules: <no details avaliable>

org.labkey.test.tests.CDSVisualizationTest.verifySubjectCountsWithFiltersAdvancedOptions: <no details avaliable>

##### there are 8 more failed tests, see build details
```


Moved constructor to top of class. I'm aware that this is missing coverage but there is no test class for GeometryExpressions.


I think listing a specific command-line example (perhaps using the project in `toto-build-and-test/examples/*`)  would be helpful here.  What is the expected output of running `python main.py` ?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8642](https://teamcity.mesosphere.io/viewLog.html?buildId=88491&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


Moved constructor to top of class. I'm aware that this is missing test coverage but there is no test class for JTSGeometryExpressions.


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 96](https://teamcity.labkey.org/viewLog.html?buildId=290388&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:02:04


We don't have namespace for functions, so we would need to revamp all the function stuff to have namespaces first. Currently it is impossible to conflict because the namespaces are separate.

Named arguments (and defaults) matter because these are not `SqlFunction`, so they can't go in the map.


I have some skin in the game now with https://github.com/ninja/ruto ;)

Gratitude for the maintenance of this and the history module!


regex is not an option in tiny-process-library as it is not supported by gcc4.8 which is commonly used still. std::replace(_if) is not general enough either. Although I think I can make the whole thing cleaner, and maybe replace \\\\\\ with \\\\ hopefully on line 111.

@zalox By the way, send you an email to (jorgen@....org), you still using this?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8644](https://teamcity.mesosphere.io/viewLog.html?buildId=88504&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8643](https://teamcity.mesosphere.io/viewLog.html?buildId=88503&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8645](https://teamcity.mesosphere.io/viewLog.html?buildId=88505&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


Should these args just be deleted instead of underscored?


Merci


In another PR I was using this to format into the docstring so that it always read the correc default port automatically. Is there a better place to read the default port from?


Good point about the extension, thanks. I hope we can "devirtualize" the lookup when we have perfect information, then.

The (very few) times I've seen inheritance chain inserts before, the new superclass previously existed, which means that argument isn't valid. (And clients can always observe the change by explicitly asking for the superclass, but I'm okay with saying that doesn't count.)


forgot about that


OK, I have made an attempt against a new account to see, and there's no data lose, but what is created is a totally new "filesystem" over the storage, creating some metadata and seq files, and one "s3ql_data_*" per file (if not larger than the maximum block size). This is not what I expected, and I'm not sure if this is what I want, because this way I'm loosing access via the mobile application... What a dilemma!


Indeed, but we need to decode instead of just copying data to memory.
Compatibility is worth it though.
On Dec 8, 2015 18:09, "withoutboats" <notifications@github.com> wrote:

> In a way, these changes to the code have exactly that effect. :-)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/withoutboats/notty/commit/b9ec450681ad445aca96c4c9bcbee8ea95ea5c82#commitcomment-14858767>
> .
>


WE WANTED ->Suicide() :(


Just noticed this comment after publishing this, sorry. I don't think it's a huge deal because it's an explicit method name on the object. Considering that's the only thing find-and-replace does currently I'm not too worried about it. We could always expand the namespace later if needed.


The README specifies the `--infile` command-line option.


I think you didn't remove this lines on purpose.


Hi VoyagerOne,

thank you for an explanation. I'll delete this test.


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1444 of 1444 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8646](https://teamcity.mesosphere.io/viewLog.html?buildId=88506&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8647](https://teamcity.mesosphere.io/viewLog.html?buildId=88507&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:09


HBIRE_vector_take2 (Myoldmopar) - Win64-Windows-7-VisualStudio-12: Tests Failed

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-72.94%25-red.svg)


Thanks for the update.
Can I assume this is an adequate cutoff point for a release?
Are there any other necessary changes before locking down a release point?


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1108.d803e3325b8b20c04fcad9c56fb5dff6f6ca5ddd](http://build.palaso.org/viewLog.html?buildId=67035&buildTypeId=bt431) outcome was **FAILURE**
Summary: Execution timeout; tests passed: 501, ignored: 4 Build time: 00:35:42


I think it would be more correct to initialize nMinHeight to -1, so hypothetically txs in a 0 height block could pass (and return the -1 below in line 728)


I've added this in drelyn86/atom-terminus along with better defaults based on which terminals are present in /usr/bin/


updated install.txt to add multiplayer


```
clientHello.create((3,0), bytearray(32), bytearray(0), [range(0, 129)])
```


Tyler Coy


fixes network selection


If it doesn't give us anything then leave it out.  It was just a thought.  I was remembering that the latest draft of the C++ Standard requires 32 bit values or greater in "Seed sequence requirements", section 26.5.1.2.  If we don't have the same requirements that's cool.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8648](https://teamcity.mesosphere.io/viewLog.html?buildId=88508&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


it's in bokeh.resources that's where Server gets it


I don't think this test is necessary


I've applied this in [atom-terminus](https://github.com/drelyn86/atom-terminus)


It doesn't matter. Here I make nametag black and then hide it with `a = 0`. Furthermore, [as per docs](https://github.com/minetest/minetest/blob/9a5a538e8d1981fb3c2dd69ca3d37e4f9c426cf5/doc/lua_api.txt#L1668-L1676), only `a` is optional (however, if I not specify `rgb` approach still works).


Done.


done except for doc


De base ce header n'était pas présent dans la requête ?


Most of these arguments, like `FeverAPI::Authentication#call(params)` are parts of protocols, so I'd prefer to keep them. `finder` can probably be removed from `get_feed_for_url`, though.


So now we don't need to create this object, I can fix it


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


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8649](https://teamcity.mesosphere.io/viewLog.html?buildId=88512&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


complete


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8650](https://teamcity.mesosphere.io/viewLog.html?buildId=88513&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:25


Ah - okay, that's fine. Thanks.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8652](https://teamcity.mesosphere.io/viewLog.html?buildId=88515&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:10


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8653](https://teamcity.mesosphere.io/viewLog.html?buildId=88516&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:11


we removed all methods like `@requirements.stemcell.supports*` in stemcell.rb, and put tags for tests using them.


it's something @pkieltyka wanted - fn is a function that is called instead of sending SIGTERM to the process - it is supposed to shut it down (cleanup and stuff). You'd use it if your process doesn't or can't gracefully stop otherwise.


No problem, register another free 25 GB hubic account.


The not a web-dev contributor would like to contribute to this discussion.

Direct db interactions seems more brittle to me. I prefer using the server
code which the application relies on so that errors are brought to our
attention sooner. That code should definitely have hard checks.

On Tue, Dec 8, 2015 at 2:15 AM Yash <notifications@github.com> wrote:

> Yeah, I get your point about implementing error checking but I think we
> would trust whoever runs the server to have a basic idea of what they're
> doing and I think that won't be too hard of a problem to track down.
>
> So Node basically uses mongo's client to do all the write operations
> anyway so I removed the extra scaffolding and just went straight through to
> the mongo shell API.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/YashdalfTheGray/flintandsteel/commit/d9eb7d05db1e9d95504c025cadfafcb561fcdeaa#commitcomment-14840458>
> .
>


I see why this happened @michaelrutherford :D


Can you describe the use case for these? Why should they be defaults vs. you putting this in your settings? It seems somewhat implementation-specific for whatever your use case may be.


Thanks.

On Tue, Dec 8, 2015 at 1:20 PM, Colin Diesh <notifications@github.com>
wrote:

> Apparently I actually added it to the _reportCustomUsageStats here c939e5b
> <https://github.com/GMOD/jbrowse/commit/c939e5b903f4b434bd4f6d2e3e86ffde68bff886>
>
> I guess only the server side would need to be updated
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GMOD/jbrowse/commit/380dd78902bfdfe37bfa841f748946f4dedaae55#commitcomment-14859030>
> .
>


@Justinzobel Gotta start somewhere :D


Пусть возвращается отсюда ошибка: передай Profile в параметры
ERROR_CODE FileReader::ReadModelProfile(const std::string& ModelName, Profile& profile)


done


Should there be instructions on generating public / private keys?  I guess main.py automatically generates the signatures?  This is unclear from only looking at the README.


Добавь, плиз, метод IsValid(), который проверит, правильные ли там значения полей.


@gi0baro is this not wrong again? `redirect(self.auth.url('request_reset_password'))` if user is disabled OR banned. I think disabled and blocked should be separately managed?


What's up with this?


Do we still need the user_id?

Can we make this: `new_project(name, code, parent_id=None)` or instead of `None`, `-1` would be fine too?


This is what you call a safe cast.


the `deploymentprofile` its required and needs to be set in **local** to work with that profile


Probably need to add a `code` from here too and adjust the namedtuple.


Casting like (T) with generics is BAD practice!


Now I see why the results for SNLI were not so great!


Also here `-Ddeploymentprofile=cloudhub` must be configured


:+1: tried out 1.33 after removing the empty `/var/.cloud66_env` I created for myself on the lb. Works for me. Thanks!


JSON doesn't work with my version of Postgres yet. It won't insert. I'll let you know when it does.


For everything else it's fine though.


I think it's lookin good :) this whole thing with the Bio samtools is kind of annoying since it's a legacy feature, but it prevents warnings from being spit out when user runs setup.sh so it helps. I'd pick off the tip of master right now for release tag