The change to display:flex made this invisible off screen in Chrome 47 on Windows and OSX as well as Safari 6.2.8 on OSX. If I manually change display back to `display:block` in the developer tools, I can see the element again. I am not sure where the proper place to report this is since it has been included in the build for 7.4.0 Beta 2. @madsrasmussen


Well, I messed up that commit message. Can't figure out how fix it either. Oh well.


Well, that might take some time, but I think I can try to update it.


Foobar <!--IMAGECOMMENT_START{"x":"60.76","y":"55.56","originalComment":"This is a test comment"}IMAGECOMMENT_END-->


Foobar <!-- IMAGECOMMENT_START{"x":"60.76","y":"55.56","originalComment":"This is a test comment"}IMAGECOMMENT_END -->


Did it work?


what?


This is questionable


I am a jerk


Is this needed?


Foobar

<!-- IMAGECOMMENT_START{"x":"60.76","y":"55.56","originalComment":"This is a test comment"}IMAGECOMMENT_END -->


Doesn't seem to be used?


Foobar
<!--IMAGECOMMENT_START{"x":"60.76","y":"55.56","originalComment":"This is a test comment"}IMAGECOMMENT_END-->


remove the code


Gimme just a day to a couple. Trying to hurry. Obviously life/work gets in the way sometimes. Although, I dont like releasing stuff with bugs.


@KorvinSzanto @mlocati

Do either of you have better options for this function? Essentially CKEditor has it's own built in asset loading, which relies on me passing the appropriate language to the configuration. If I could I'd like to steer clear of these `file_exists` calls but I'm not really sure what my alternatives are.


what`s mean?


Leave a comment...


I AM A JERK WHO DOESN'T TELL SEAN ABOUT UNFINISHED CROSS STITCHES


109490574b-UnbalancedFlowWarning-4293-PlanB (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2088 of 2089 tests passed, 0 test warnings)

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


109490574b-UnbalancedFlowWarning-4293-PlanB (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (957 of 957 tests passed, 0 test warnings)

![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) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-26.85%25-green.svg)


You can probably get better results by using a half-circle path for the panning, instead of a direct line through the listener. Something like ```{ pan, 0.0f, -sqrtf(1.0f - pan*pan) }```. As it is here, anything <0 will pan hard left and >0 will pan hard right.


OK, going to pull the change in, we'll see if we'll make it conditional later on (maybe with a filter).


TeamCity Open-source Libraries :: YACLP :: CI [Build 1.0.4.0](http://build01:8888/viewLog.html?buildId=13884&buildTypeId=OpenSourceLibraries_Yaclp_CI) is now running


TeamCity Open-source Libraries :: Sourcerer :: CI [Build 0.0.4.0](http://build01:8888/viewLog.html?buildId=13883&buildTypeId=OpenSourceLibraries_Sourcerer_CI) is now running


TeamCity Open-source Libraries :: ThirdDrawer :: CI [Build 1.1.11.0](http://build01:8888/viewLog.html?buildId=13885&buildTypeId=OpenSourceLibraries_ThirdDrawer_CI) is now running


Such as?


What happened to the website? I love to use that not very smart when it comes to code and things of that nature.


Cool, just update the PR and we can merge it :+1:


TeamCity Open-source Libraries :: ThirdDrawer :: CI [Build 1.1.11.0](http://build01:8888/viewLog.html?buildId=13885&buildTypeId=OpenSourceLibraries_ThirdDrawer_CI) outcome was **SUCCESS**
Summary: Tests passed: 8 Build time: 00:00:56


TeamCity Open-source Libraries :: BlogMonster :: CI [Build 2.0.26.0](http://build01:8888/viewLog.html?buildId=13886&buildTypeId=BlogMonster_CI) is now running


TeamCity Open-source Libraries :: YACLP :: CI [Build 1.0.4.0](http://build01:8888/viewLog.html?buildId=13884&buildTypeId=OpenSourceLibraries_Yaclp_CI) outcome was **SUCCESS**
Summary: Tests passed: 20 Build time: 00:01:18


TeamCity Open-source Libraries :: MvcNavigationHelpers :: CI [Build 0.0.9.0](http://build01:8888/viewLog.html?buildId=13887&buildTypeId=OpenSourceLibraries_MvcNavigationHelpers_CI) is now running


I'd throw here an exception here because the support is not defined for null.


SAYS YOU


Если честно, не помню точно, но как-то вроде читал что для надежности лучше явно преобразовать в булевский тип при проверке.. Хотя, тут он и так уже проверен в предыдущей строке ))) Писал в полусне)) Поправлю


TeamCity Open-source Libraries :: Sourcerer :: CI [Build 0.0.4.0](http://build01:8888/viewLog.html?buildId=13883&buildTypeId=OpenSourceLibraries_Sourcerer_CI) outcome was **SUCCESS**
Summary: Tests passed: 13 Build time: 00:01:55


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.461.0](http://build01:8888/viewLog.html?buildId=13888&buildTypeId=ConfigInjector_CI) is now running


This one seems popular:

```
<COMP> = 135;
alias <MENU> = <COMP>;
```


LGTM.


TeamCity Open-source Libraries :: BlogMonster :: CI [Build 2.0.26.0](http://build01:8888/viewLog.html?buildId=13886&buildTypeId=BlogMonster_CI) outcome was **SUCCESS**
Summary: Tests passed: 13 Build time: 00:01:16


TeamCity Open-source Libraries :: NotDeadYet :: CI [Build 0.0.30.0](http://build01:8888/viewLog.html?buildId=13889&buildTypeId=OpenSourceLibraries_NotDeadYet_CI) is now running


TeamCity Open-source Libraries :: MvcNavigationHelpers :: CI [Build 0.0.9.0](http://build01:8888/viewLog.html?buildId=13887&buildTypeId=OpenSourceLibraries_MvcNavigationHelpers_CI) outcome was **SUCCESS**
Summary: Tests passed: 21 Build time: 00:01:09


normalized_power = power - features[VLF],
so we should calculate VLF before (VLF != pgram[1])


TeamCity LabKey :: Sprint :: Premium :: Git sqlserver 2014 [Build 14](https://teamcity.labkey.org/viewLog.html?buildId=298274&buildTypeId=LabKey_Sprint_2_LabkeyPremiumTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:02:13


Tu veux dire 2 properties ?
Cela pourrait être couteux d'avoir à interroger la db à chaque fois qu'on accède à la date du message.

En fait, je pense que c'est un vrai-faux problème. Il n'y a aucune raison d'imposer que la date de début de manche soit la date du message sur le forum. Ce n'est pas incohérent (juste curieux) si ces dates diffèrent, mais cela ne risque pas de provoquer un bug ou la fin du monde.

Pire : je pense que c'est incohérent que d'imposer cela. On pourrait décider de fixer la date de début d'une manche, et que lorsque cette date est franchie, un message est automatiquement créé sur le forum avec le texte de la manche (et donc potentiellement (1) la date de début est fixée sans que le message ne soit créé et (2) la date du message est postérieure d'au moins quelques millisecondes à la date de début).

Pour la date de fin, c'est encore plus flagrant : on pourrait fixer la date de cloture de la manche au préalable, simplement pour empecher que des réponses ne soient postées après cette date. Ensuite, lorsque la manche est validée (donc largement après la cloture, normalement), le message concernant les résultats de la manche sera posté. On est donc encore dans une situation où (1) la date de fin est fixée au préalable, sans que le message ne soit créé et (2) à moins d'être un sur-homme, le message ne sera pas posté dans un délai de plusieurs heures suivant la fin de la manche.


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.461.0](http://build01:8888/viewLog.html?buildId=13888&buildTypeId=ConfigInjector_CI) outcome was **SUCCESS**
Summary: Tests passed: 38 Build time: 00:01:24


Aaaah, ok, sorry, indeed


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


remove unnecessary argument


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


this seems wrong, AFAICT.  run.js is a server, and you want to main to point to the library.


@SubJunk Is there any way you could make instructions on how to test a renderer with it and making that available e.g on the forum? If instructed to use trace mode/dbgpacker while testing, advanced users could help test renderers unavailable to us.


Данный документ возникает шаг за шагом из многочисленных актов общения между людьми в нескольких социальных сетях, как результат совместно обсуждаемых важных жизненных и идеологических моментов. Метанаучный Синкретизм - идеология Единства (и Со-Частия) Представителей Разума Природы (=Человечества).


HF != pgram[3]
LF != pgram[2]
There can be features[HF] / features[LF]


We need to update the information here since it's still pointed to our old site.


File Formats/Images/UCG Image Format version 3.md

I'm going to go out on a limb here and assume you meant an _octet_. Don't worry, I'm writing up a terminology standard.


Visiblement, nos messages se sont croisés ;-) Par cohérence (mais pas par respect de la grammaire anglaise, du moins, je crois), on peut fixer ``start_message`` et ``end_message``.


Looks good.  (CentOS has python installed with core OS installation).


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/26019/testReport/) for this commit**


IMO drop this check entirely – we'll deal with not handling such hashes downstream.


Also in Murukesan14 is LF/HF


OK.

Je voulais juste dire de décorer le signal avec les deux modèles, mais en effet on peut carrément se passe de tout ça.


I pulled down the latest commit, `npm install`ed, and ran `gulp`. I did not receive an error, plus the messages I got are correct:

If I add the following code on L35:

```js
console.log('res: ', cli.files[0].filePath(), cli.files[0].messages.length);
```

I get:

```txt
[21:04:50] Using gulpfile ~/projects/oss/gulp-remark/gulpfile.js
[21:04:50] Starting 'default'...
res:  /Users/tilde/projects/oss/gulp-remark/README.md 6
res:  /Users/tilde/projects/oss/gulp-remark/example.md 1
[21:04:50] Finished 'default' after 169 ms
```

Maybe `rm -rf node_modules && npm install && npm install remark-html`?


Can you rename target libwebm in packager/third_party/libwebm/libwebm.gyp to mkvmuxer instead, which seems to be more adequate? Then we don't need to change the target name here.


TeamCity Open-source Libraries :: NotDeadYet :: CI [Build 0.0.30.0](http://build01:8888/viewLog.html?buildId=13889&buildTypeId=OpenSourceLibraries_NotDeadYet_CI) outcome was **SUCCESS**
Summary: Tests passed: 3 Build time: 00:03:32


Const ints aren't much different to constexpr ints from what I can tell, both can be used for array sizes


CloneToScriptContext has been implemented for all SIMD types for iframe marshalling as they are inherited from RecyclableObject.


Floats can't be constexpr either


Issue5276 (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2076 of 2085 tests passed, 127 test warnings)

 * 132 tests had: AUD diffs.
 * 136 tests had: EIO diffs.
 * 8 tests had: ESO big diffs.
 * 4 tests had: Table small diffs.
 * 3 tests had: ESO small diffs.
 * 3 tests had: MTR big diffs.
 * 5 tests had: Table big diffs.
 * 1 test had: MTR small diffs.
 * 1 test had: ERR diffs.

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


`(update-in req [:params "command"] str/replace "_" " ")`


Nit: Using `add` to include multiple transformers conflicts with standard library collection method naming conventions, where dicts use `add`/`update` for single/multiple objects, and lists use `append`/`extend`.  Might make sense to provide the same options here.  If `transformers` is meant to be a list-like collection, this would be `transformers.extend(COURSE_BLOCK_ACCESS_TRANSFORMERS)` followed by `transformers.append(ProctoredExamTransformer())`.


cc @wkennington @thoughtpolice


LGTM.


Pour ces aspects on pourra se contenter d'un manager? date_started est indexé.


Tu veux un index sur end_date?


assess.


Of course you are right. Thank you very much for this fix ... and the kind explanations.

Best
Deniss


Hi Cristi, thanx for this little Feature Update ;-) I've updated and it works as expected.


Use single quote for consistency, i.e. s/"xcode"/'xcode'/


J'avoue ne pas avoir été attentif à faire précéder toutes les URL par « sur ». Je pense que c'est la bonne préposition.


As mentioned above, consider making this more like standard python collections.  In addition to refining the naming conventions, it would be awesome to implement collection protocol methods (`__contains__`, `__getitem__`, `__iter__`, etc.) to allow more pythonic use of these collections.


If you use CrudRepository, it's one less bit of code tied to JPA. If this migrates to a non-JPA data store, you won't have to patch it.


Ok ! Si on devait placer les 2 décorateurs, j'aurai voté pour ne pas utiliser un modèle abstrait comme base commune, mais de redéfinir les champs explicitement dans chaque modèle. Le modèle abstrait donne l'impression qu'on peut profiter d'un comportement "commun" (sous-entendu : si un nouveau modèle hérite de ce modèle abstrait, on aurait pu s'attendre à ce que les signaux soient gérés automatiquement). Si ce n'est pas le cas (je ne sais pas mais j'en doute, je vais voir dans la doc), on risque d'avoir un "bête bug" si on crée un modèle héritant de ce modèle abstrait dans le futur.


Pressurestat (lgu1234) - x86_64-MacOS-10.9-clang: OK (2050 of 2050 tests passed, 0 test warnings)

 * 3 tests had: AUD diffs.

![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)


Thanks for the fix! It worked.


Ni simple, ni élégant :
http://stackoverflow.com/questions/2692551/how-do-i-use-django-signals-with-an-abstract-model


Awesome! Thanks for fixing my quick and dirty hack ;)


Thank you. :)


If you move to a non-JPA solution, then you can rip out @Entity and replace @javax.persistence.Id with @org.springframework.data.annotation.Id. That will nicely confine data store specifics on the build file.


Not at all. I don't see any difference in the battery life.


Got a typo here `automaticall`.


yeah. fixed already ;)


Yeah, I meant an octet
the terminology standard is a pretty good idea.


Issue5276 (wfbuhl) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


It would be much nicer if out CoC would be less of a penal code and more of a moral code.


You could define these 13/7 values to ease maintenance, I guess.


Cool, was looking for that, so big noise about it, and so small fix haha :) thanks for sharing


Cool I'm just about to try it and see if I notice a difference one way or another... thanks!


Don't we already have this? That's the RFC process.


No problem.  I've put the `merged-needs-deploy` label on issue #28 now.  When we've confirmed that that bugfix is deployed out to production, we can close the issue.


Fix the bug in the version:
https://github.com/jianminchen/Leetcode_C-/blob/master/317ShortestDistanceFromAllBuildings_BugA.cs


Sin comillas.. Es una referencia a una variable, así normal que no funcione jajajaja :-)


Something in the lines of ``console_print_blob()`` would do, no?


I don't think you should pass this return value back. This probably means you have to refactor the `check_crate_trait_impls` to not take a `ccx` but rather just a `tcx`, which I think ought to be fine. I think I might be inclined in general to move that code to its own module.


I think you meant to write pip-sync instead of pip-compile here, right?


@zensh , thanks! But there is one more issue.
`3` matches `([1-9])` but not `(\d)`.


Nit: I see no reason for this flag here; just write:

```rust
if let hir::ItemImpl(..) = i.node {
    check_trait_impl(self.ccx, i);
}
```


String.join(",", array) would be a bit cleaner solution.


does Iggy have its own book?


I'm not certain whether we need to abort here. Might make sense, but maybe we can be more resilient.


Ce n'est pas grave pour l'instant ?

Peux tu merger ce commit? ou il manque des choses?


@AlexandreDecan tu n'as rien dit ici


It would be nicer if we could replace this laundry list (which is too long for anybody to actually read it and still I'm sure is missing something) with shorter statement. I'll think about specifics.


Pour connaître la manche en cours, il faut regarder:
1. season == given_or_current_season
2. start_date <= now()
3. end_date is None

Non ? Sauf que (2) retournera beaucoup de résultats potentiellement (bon, ok, maximum 10 pour une saison donnée), donc (3) est utile à indexer. Bien que, de nouveau, les index sur une si petite table ne sont probablement pas très intéressants :)

Ok pour un manager ^^


Would you care to submit a PR for auto-type only to the master branch of the original source?
And possibly a second one for http?


The reason is to save `all_traits` whose are populated in first step of `typeck::check_crate`


By "no effect" I mean that actionForKey is called, and the "rotation" conditional is executed... returning the animation, but the shape doesn't animate.


Why not use the `CompositeDisposable` class for disposing: http://blog.atom.io/2014/09/16/new-event-subscription-api.html


Fix for #125


Just saw that, sorry.


The first three changelines are plain wrong. You re-introduce a bug i fixed.


For future reference: Changes to the data model can be aggregated between public distributions from release/ branches.


On n'a pas besoin de la manche en court. On peut poster dans une manche si elle a une saison, une start-date et pas de end_date.


Ok, then I will remove my added tests too.


cc @basharal @drTall

Would appreciate review before sending this upstream.


Je vois pas le problème d'avoir plusieurs saison/manches en parallèle, conceptuellement


x86_64-apple-unknown-version instead? since it may be built on other versions.


The following piece of code (example taken from CanBusMotionControl.cpp) shows how simple is to add a quick implementation to your low-level device.
``` c
bool CanBusMotionControl::getJointTypeRaw(int axis, yarp::dev::JointTypeEnum& type)
{
    CanBusResources& r = RES(system_resources);
    if (axis >= 0 && axis < r.getJoints())
    {
        type = JointTypeEnum::VOCAB_JOINTTYPE_REVOLUTE;
        return true;
    }
    else
    {
        return false;
    }
}
```
For more complex systems with advanced functionalities, it was defined for the xml configuration file a new parameter axisType (see ` icub-main\app\robots\iCubGenova02\hardware\mechanicals\left_lower_arm-ems2-mec.xml `)
```
<param name="AxisName">      "l_wrist_prosup" "l_wrist_pitch" "l_wrist_yaw"  "l_hand_finger"    "l_thumb_oppose"     "l_thumb_proximal"     "l_thumb_distal"   "l_index_proximal"    "l_index_distal"    "l_middle_proximal"   "l_middle_distal"    "l_pinky"  </param>
<param name="AxisType">       "revolute"    "revolute"    "revolute"    "revolute"   "revolute"       "revolute"     "revolute"    "revolute"    "revolute"    "revolute"   "revolute"    "revolute" </param>
```


I just copy-pasted. Each other function aborts on new errors.


\o/


Nevermind whether or not your code works better, it is borderline unreadable already. In half a year nobody will easily understand what this code does, and it will have to be re-done for any maintenance.


Thank you for the fix, dear Andreas. I have tested the changes and confirmed that the OpenCL filtering methods work on my system.


@wibeasley, sound veru much like the data-unshared which altogether exist as a separate folder


Again, bug


:shipit:


Ha! I believe it is. I went through a bunch of iterations of this code, so I'm sure at some point I changed it to this without thinking about it


nice catch


This part looks suspiciously like what you are pull requesting, basically


Sharl - you updated an older version


Why updating to NB 8.1?


:sparkles: :sparkles: It's a miracle! :sparkles: :sparkles:

**P.S:** Sorry for disturbing! :D


Do we want to define who are "project maintainers"?


Good day,

I am very pleased to see some new code appearing under this module.  It is an important feature that has been lacking for quite some time in FreePBX.

I hope you don't mind some positive feedback.  I have installed v.13.0.9 and the UI is so much better!  But unfortunately I must report that things do not presently seem to work for me.  Therefore, this feedback is part bug report and part feature request / suggestions:

1) Everything entered under settings does not save.  There is no "submit" button.  (bug)

2)  Can you please default the "Operator Mode" to 'Enabled' as per previous versions? (req)

3) Everything I enter under the Call List is ignored and not saved.  (I can set a local WUC by phone but not through the application UI).  The phone-based WUC is apparently stored, but does not show up on the list.  (I discovered this when I re-installed version 3.0 and it displayed the scheduled call which I had set using the phone when this version was installed). (bug)

4) The "Add" button opens a window that insists time is entered in 30 minute increments via a drop down menu.  This is not granular enough.  For example if I wanted to set a WUC for 02:05am, I am unable to do so from the application UI.

5)  The older version 3.0 (beta) module included a feature (although very clunky) to allow repeating wake-up calls.  (every day, every week).  Can this feature please be included and improved in the current development?

6) To facilitate the above (4) may I suggest a need to better define the Wake Up Call Clock and Calendar in "Settings".  This is so that Wakeup Calls are not necessarily synced to the system clock.  (e.g. It may be that the server is set to UTC while the user is actually in Dubai).  One possible solution may be to: Regionalise the Timezone by Operator number, as each operator could be entered on a separate line in a 3 column table in the format, "Operator | UTC offset | DST", (e.g. 500 | +4 | N) .  A simpler solution might be to set a UTC offset and DST globally for now.

7)  In a similar way, please can you give the option for dd/mm/yyyy or mm/dd/yyyy calendar format?

8) Please consider including an end date so that a WUC can be scheduled to Start on 21/01/2016 and End on 23/02/2016.  Maybe this schedule could then have an option to repeat on the same days for x number of weeks.  (e.g. mon-fri for 3 weeks)?  (default 1 week)

9)  Finally, perhaps consider putting some or all of these functions in the UAC, so that a hotel clerk can use them from a nominated "operator" extension in the UAC, without having to access the FreePBX Administration UI?

I realise that's a lot to ask and I perfectly understand if you have other priorities.  Many thanks for pressing ahead with this project which I am sure will prove to be another great contribution to the FreePBX community.


@alexcurylo great! Would like me to include these additions on 45 instead for this PR?


`string.Format` to eliminate the concatenation?


@oritwas the defer_user_update is needed so that we can do multiple modifications and then apply with a single user->update(). However, looking at the code it's not clear to me how this is supposed to happen, so it might be that your workaround is the way to go. Can you verify that?


Same here?


I think 30 minutes if fine. We wish the user will take action right away when they saw the warning and ideally in 30 minutes they will be able to move enough disk space and the warning message won't popped up again.


Terminado la descripción del proyecto
5e51f50e64af592cc494151b2d2808e54f469448

https://github.com/marioalvazquez/Curso-de-HTML5-y-CSS3---Octubre-2015/commit/5e51f50e64af592cc494151b2d2808e54f469448


Looks like it's almost done!


We don't currently target `<main>` elements with anything as far as I know. In this case it's just a wrapping element (to provide clarity like you said) and it shouldn't affect anything just by having it there.


this should return `callback({msg: err})` (note to myself, editing tomorrow). nice catch btw

But you're right this is a non-node way, we'll keep it that way for now. I'll investigate because it would be better with cb(err), this might be a breaking change though, especially if it's used for programatic use (ie modules)


Please bring this to our forums: http://community.freepbx.org


Here and in all other files it says v4.3.
Compare with the official CMSIS repos:
https://github.com/ARM-software/CMSIS/blob/master/CMSIS/Include/cmsis_gcc.h#L4


> On peut poster dans une manche si elle a une saison, une start-date et pas de end_date.

Non. C'est un détail, mais il faut que la start_date soit dépassée, et que la end_date ne le soit pas.

> Je vois pas le problème d'avoir plusieurs saison/manches en parallèle, conceptuellement

Conceptuellement, non. Techniquement, plusieurs saisons ne posent pas de problème, mais plusieurs manches au sein d'une saison peut être problématique, notamment parce que le calcul des progressions en terme de places prises/perdues d'une manche à l'autre sera dépendant de l'ordre dans lequel tu termines une saison. De façon générale, si on autorise plusieurs manches d'une même saison en parallèle (je suis contre ! ok pour débuter une manche avant que la précédente ne soit validée, mais pas ok pour débuter une nouvelle manche tant que la précédente ne l'est pas), il faut au moins s'assurer (ou imposer) que l'ordre des ``number`` soit respecté (ou que si start_date_1 < start_date_2 alors end_date_1 < end_date_2 !)


Do they come with macports or homebrew? Do we have to install something else to get the certs?


I think you mean the mediation team here, but this is not how we used the word "maintainer" in the past. In fact, some of the people on the team may not even have commit access, so calling them PHP maintainers would be incorrect. I think it needs rewording here.


I love it!


Oops, I guess I didn't run validation-tests. Thanks for catching this!


bash strict mode, I appreciate this! :clap:


This does appears better than my check, it has less comparisons.


power = np.mean(pgram) * (frequency_bounds[-1] - frequency_bounds[0])
isn't it?


Why the int conversion


Related to #2

@mato Let me know if you get a chance to have a look at this. Sorry for the short notice :)


You miss informing the user of errors. You have to check if errno != 0 and tmpbuf_endptr != tmpbuf after the call. Being the return type unsigned, we have to think of how to flag the error -- another arg?


I suppose this is my predisposition coming from a mapping beamline.  If you're doing a map that is a couple hours long you don't want to keep getting an error every 30 minutes when you don't have much you can do about it until the scan completes.  I would prefer 60 or configurable but to be perfectly honest, once is enough.


I think we should change this to check whether we are building for embedded. It is probably better to keep the destructor for boost_test. Agree?


I suppose such code:

  bounds_names = ['ULF', 'VLF', 'LF', 'HF']
  frequency_bounds = frequency_options['frequency bounds']
  power = np.mean(pgram) * (frequency_bounds[-1] - frequency_bounds[0])
  idx = []
  for i in xrange(len(frequency_bounds) - 1):
    idx.append((f > frequency_bounds[i]) * (f <= frequency_bounds[i+1]))
    features.append([bounds_names[i], np.sum(pgram[idx[i]]) / pgram[idx[i]].shape[0] * (frequency_bounds[i+1] - frequency_bounds[i])])
    features.append([bounds_names[i] + 'rel', np.sum(pgram[idx[i]]) / power])
    features.append([bounds_names[i] + 'peak', f[idx[i]][np.argmax(pgram[idx[i]])]])
    if i > 1:
      # features[3][1] = VLF
      features.append([bounds_names[i] + 'normalized', np.sum(pgram[idx[i]]) / (power - features[3][1])])
  # features[6][1] = LF, features[10][1] = HF
  features.append(['LF/HF', features[6][1] / features[10][1]])


This fixes issue #41 (Gnome Shell's WindowList extension compatibility)


Did you check if the current state (which has my intersection fix) still has the bug you are attempting to fix? I see, you extend bounding boxes for the checks instead of my getClosestDistanceBetweenBounds ... i'll admit that is probably smarter.


Ack


These last two are checking beyond the upper port range, one can be eliminated.


Maybe it's worth citing what does our implementation provide on that: client and server APIs.


Ok. Tu copies ça dans un ticket pour la suite?


a3140fa824e9f824d084183ee39a92c2fa9fe275
https://github.com/marioalvazquez/Curso-de-HTML5-y-CSS3---Octubre-2015/commit/a3140fa824e9f824d084183ee39a92c2fa9fe275

Se hizo una mejoría en los estilos de index.html


Is this default described anywhere?  Should it be?


These are an easy ack, We should probably grep for =&\s and fix them all.


Nutné měnit absolutní cestu ke složce "uploads" v projektu.


Can you remove this file? Thanks.


@yiyang-msft I did some very cursory work to sync with the first post-10.6 release but never got round to completing it. Apple's commits are deeply unhelpful, as many of them include a ton of radical changes; I was hoping for a steady stream of small patches so that I could incrementally update the code, but that's not really an option.

I still have an interest in the project, but don't have the time or resources to lead it.

For my purposes, I also want the thing to build with cl (clang-c2 might be good one day for existing Win32 projects but I don't think it's there yet), which is awkward because some of the new parts use blocks "natively" (rather than having block wrappers around the `_f` functions).


I can't think of any time when bash would NOT be in /bin, but ack.


This fixes issue #42 related to hiding the dock in overview mode.


I wasn't familiar with it. I haven't been following Atom development much lately, just providing support for this plugin as needed.


Hi KodyBentley/MyFirstW,

I'd like to add you to my professional network on LinkedIn.

- Kody

Confirm that you know Kody: https://www.linkedin.com/e/v2?e=0-ijnaaq9h-5u&t=ssuw&tracking=eml-guest-invite-cta&ek=invite_guest&sharedKey=cynwOFal&invitationId=6095673485240131584

You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe here: https://www.linkedin.com/e/v2?e=0-ijnaaq9h-5u&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&loid=AQENsnHxUWtTJAAAAVJgu2vTNeVOruIMKzr3IaT3y5qfG_BovgDwm2I93vcc2E18C-gc5Mt2WlQffOTOPNoVQxOVI9LfMysbmsEEfG7vpaN64USfYH5SYqIptVaSvq9hcZ6Sq-3gHKpTASTCGPD2XiUauf2WZx7NXkTo1_ywuN10V8di38u8D-XhIhb4JCiuRY-Y&eid=0-ijnaaq9h-5u

This email was sent to reply@reply.github.com.

If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=0-ijnaaq9h-5u&a=customerServiceUrl&ek=invite_guest

© 2016 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 94043. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn.


БД по новой!


Don't know why I thought it didn't exist.  The psx gpu doesn't but gte's its own thing.  The code's still horrible :P


I'm not sure "violate the Collaboration Guidelines" belongs here. Should we ask people to complain and do we promise to apply "strong action" if people write unclear prose or post more frequently than once an hour? Probably not. Let's separate "bad" behavior we want to intervene and suggestions which are merely that.


Why not just `source: :frontmatter`?  The way that is pretty expensive, even with literals compared to a symbol.


This is something turned up by one of the unit tests?


I would rather tighten the tolerances in the Substance class, than loosen them in the test. I just couldn't figure out how to do that. The thing is, the test will pass if setting `ST` is the only pair set in the function, and it would be much better if setting the state didn't depend on the starting state (or at least, not to the degree that it causes a failure). So it seems to be a deeper problem that I'd rather try to fix thoroughly, I just haven't figured out how yet.


Thanks. Will see if I can help debug the kernel panic.


I have a few changes to suggest but  can't figure out how to present them.

one is streamlining the form.

two is presenting the output as #C = #F = #K format.


(Tu vas dire que je suis ch... ^^) tu préfères pas mettre ça en TODO: dans le code ?

Si la réponse est "non", je vais créer un label pour ALDP, sinon je vais me noyer dans la quantité d'issue (je m'attaque à quelques unes vendredi normalement).


Ack


The comment above doesn't say anything the code doesn't. Consider removing it.


I think it's good to encourage the practice of minimizing migrations yes, if you don't mind.


The section above doesn't perform any verification, despite what the comment suggests.


discarding, did *not* hear


I'm hesitant to use gpg without an explicit path, because then /var/www/html/admin/libraries/BMO/gpg (which is writable by httpd) would be used if the others didn't exist.


Oh, I see why, I don't know what to think because if that has to happen things might be getting a bit complex.


Shouldn't we always prefer the newer openssl, even if it's via homebrew?


How'd you figure out out ref? Also, with proper GTE emulation, won't we get a lot closer to PSX compatibility?


s/has_access result/has_access_result/


Since SSL_LIB/CRYPTO_LIB no longer have any effect, please update the Makefile; I think it references them.


Remove console.log


Does freebsd keep it's unixodbc stuff here?


112083967_VentilatedSlab (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1504 of 1504 tests passed, 0 test warnings)

![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)


112083967_VentilatedSlab (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2088 of 2088 tests passed, 0 test warnings)

![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)


Is this leftover debugging?


I have been meaning to add something like this. Nice :shipit:


Issue5276 (wfbuhl) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (953 of 953 tests passed, 0 test warnings)

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


Ditto this


Phillis, can you help me hyperlink this savethedate2.png image to open a new window with the seminarseries_february.pdf file?  I couldn't figure it out.


ok.


Issues mentioned in this commit (1998c28ff92ced211d8e758f0fee45cbf2a4bd11):

* [Issue #4](https://bugs.mtasa.com/view.php?id=4)
* [Issue #900](https://bugs.mtasa.com/view.php?id=900)


Issues mentioned in this commit (1ad5eefd5f82ce505a397b0d39ccfba858dc8f7c):

* [Issue #900](https://bugs.mtasa.com/view.php?id=900)


right!


What happened to adding a `BasePage.rename()` method that does `clickAdminActionsSubMenuEntry("tmActionCopy"); return new RenamePage()`, just like we do for [copy](https://github.com/msmeria/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-test/xwiki-platform-test-ui/src/main/java/org/xwiki/test/ui/po/BasePage.java#L367) and for [delete](https://github.com/msmeria/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-test/xwiki-platform-test-ui/src/main/java/org/xwiki/test/ui/po/BasePage.java#L376)? I remember us talking about this last time.

As I've mentioned, the `gotoPage` method is not necessarily wrong, just that it is better suited for applications, while the rename is a core operation, specific to any page, so I believe it would better follow suit and be placed in the `BasePage` page object.


Regardless of this mistake (?), the files are from CMSIS 4.5, so I'll change the commit message.


Might be good to give this const 40 a name.


Issues mentioned in this commit (1998c28ff92ced211d8e758f0fee45cbf2a4bd11):

* [Issue #900](https://bugs.mtasa.com/view.php?id=900)


Also, that pdf doesn't seem to be displaying properly.  It displays properly in the raw tab, but not otherwise.  Maybe an issue with using layers in the pdf?


Sounds good, but I'm getting an error:

`java.lang.IllegalArgumentException: Not an managed type: class com.netflix.spinnaker.orca.controllers.Abc`

Is it possible to create a domain object that isn't coupled to the backing datastore? In this case, it wants @Entity, in Mongo's case, it wants @Document. Not sure about the other backing impls.


why  not if (!isset($amp_conf['AMPBIN']))?   That'll false on $amp_conf['AMPBIN'] == '' or null or false, too, which are *also* invalid settings?


@lencioni I plan on continuing to work on this tomorrow and add support for an `applies_to` option inside the local config. First up is `applies_to: 'file_being_imported'`, then `applies_to: 'package'`. The default (what I implemented here will probably be named `applies_to: 'file_being_edited'`.


Some people have only limited timeframes when they can read and respond to the list. In that case, such suggestion would effectively exclude them from the discussion. I'd put the second sentence first, and replace the rest of the two with something like:
Do not "rapid-fire" reply to the active topic, but instead take the time to compose and edit the reply containing all the information you wanted to convey.


Pending ack with comments


Would be good to add a few comments up here explaining that these were copied verbatim from openssl/ssl.h (double check that everything came from there), and a caveat that we won't notice if the values change in openssl.


# Assignment 1 Grading Rubric (15 points total)

## Screenshots

- [ ] Assignment 1 contains directory of files for user (0.5 pt)
- [ ] Repository contains screenshot of [github][] account (0.5 pt)
- [ ] Repository contains screenshot of [Slack][] session (0.5 pt)
- [ ] Repository contains screenshot of [Atom][] installed on users computer (0.5 pt)
- [ ] Repository contains screenshot of screenshot showing that user installed [linter-flake8][] (0.5 pt)
- [ ] Repository contains screenshot of the Anaconda [REPL][] on user's computer (0.5 pt)
- [ ] Repository contains screenshot, in the repository, displayed by Github Desktop (0.5 pt)

## jupyter notebook

- [ ] Repository contains ipython/jupyter mini-tutorial as ipynb file (0.5 pt)
- [ ] ipynb Task 1 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 2 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 3 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 4 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 5 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 6 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 7 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 8 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 1 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 2 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 3 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 4 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 5 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 6 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 7 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 8 appears to be answered correctly (0.5 pt)
- [ ] You can successfully re-run every step of the ipynb notebook (3.0 pt)

[screenshot]: https://en.wikipedia.org/wiki/Screenshot
[git]: https://git-scm.com/
[github]: https://github.com
[Slack]: https://biolprogramming.slack.com
[Atom]: https://atom.io/
[linter-flake8]: https://atom.io/packages/linter-flake8
[syllabus]: https://github.com/biolprogramming/syllabus
[ipython]: http://ipython.org/notebook.html
[jupyter]: http://jupyter.org/
[REPL]: https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop


This signature fits in one line.


Podľa mňa keď úplne odoberieš Mvc middleware tak nepôjde ani Web api.


Thank you sir. Im going to change it now!


Ack. Does anything actually USE that any more?


Nit: This is a long method, (mostly due to the verbosity of the error messages).  Consider breaking out the specific assertions into separate methods (your comments would make pretty good method names).


You don't have to change it, but for future reference: `= null` on a parameter marked with `?` is redundant.


112083967_VentilatedSlab (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


Order by lecture_id DESC so that schedule items without lectures appear first in the list. Good for "Session Chair" type of entries.


isset is also faster than array_key_exists


It's about the error messages. If we run into an issue parsing something, we should be able to tell the user where it came from.


Hi @sixtysecondrevit - Just wanted to let you know that your changes have posted to the Primer site :) Thanks again for the contribution!


The user should check the endptr by himself/herself. About the errno. I'm not so sure.


Should this be `.importjs.json`?


linked in was slightly different, but yes, we could have checked the last 128 bits and made the original raw-sha1 be the format used.

linked-in has been a problem format. There have been numerous times when it has had to be re-worked, or where latent bugs were found. I was just worrying that this new format may again end up doing this to maintenance time.

I am not sure why you would 'conditionally' check, unless you are planning on having 2 format structures with all (almost) the same function code.  There would need to be little tweaks in valid, binary, split and the cmp_*() functions.  Other than that, we could use 1 source file with 2 fmt_main structures at the bottom of it (or possibly 3 if we could also come up with a way to jam linked in into the mix).


Good catch. It turns out that we already have a `parentheses?` method in `util.rb`. I am changing this code to use that method.


Well sort of. I went to write the test for that method and realized it didn't make sense.


That implies every RFC has ultimately to be accepted, but it is not true - sometimes people just think the RFC is a bad idea. In that case, the suggested improvement would be "don't do it", and it's normal.
I would replace this with "When disagreeing, provide substantial reason instead of just saying "no". Try to outline specific points you disagree with and suggest ways of improvement.".


Current solution works too. `CompositeDisposable` is just a [wrapper around a `Set`](https://github.com/atom/event-kit/blob/v1.5.0/src/composite-disposable.coffee#L22).


@ldoktor I disagree, no need to expose the user to every single status, if not necessary.


Stalker :P
On 20 Jan 2016 21:20, Tezza <notifications@github.com> wrote:\o/

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


I think this should just be if $settings['category'] == $settingsProcessed['category'], shouldn't it?


Later on we can change that on both functions, as we've seen people are already not checking those error conditions on the original function.


Ack


hi @afedchin - I've tested this commit and there are lots of "green screen" video decoding issues. Many DVDs don't support being hardware decoded. That said, with current master there are several issues with stills again (I haven't followed for a few weeks so something must have happened in the mean time with VideoPlayer ... and I don't really have much time now to do anything beyond testing).
here are the test examples once again:
https://www.dropbox.com/s/j22rlb9ur8e4n47/TARZ.zip?dl=0 (stills issues)
https://www.dropbox.com/s/p9x4v4ddps5trbs/WILLEM.zip?dl=0 (green screen issues)


don't think this is needed anymore


Why use all caps for a class variable?  I would lowercase this.


I do not really understand - what does that fix solve?


Maybe we should return a Mock here?


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


this makes our tests pass and our actual code fail b/c cfbackup was passing -1 and leaving it up to this function to do the fileSize calculation :(


Thanks!


don't think it has to be like this. have you seen this? https://github.com/dimagi/commcare-hq/blob/master/corehq/apps/reports/tests/test_esaccessors.py


@sudonim1 maybe you were having a bad day? I dunno :P it seemed inherently ridiculous that they would redesign the R3000A without it, but then we weren't sure if it was on chip or not lol

@Nobbs66 the Play! guys had a test which they ran on a PS2 to test GTE ops


Meh.  It's a diagnostic. It certainly doesn't need to be preserved.  The mkdir() action, on the hand, is required.


I don't care particularly about the diagnostic message.  It can be removed.


How is the RelayNode.Id intended to be implemented? I assume it should return a global unique ID, but without a reference to a specific instance of the underlying data object I cannot figure out how to do that. In our current implementation any GraphType derived class is more or less singletons without any link to the instances of the type they are representing. What am I missing or are we doing it wrong?


111768812_VRFNoLoadOAFlow (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1508 of 1508 tests passed, 0 test warnings)

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


This is saying 'If the file /etc/asterisk/freepbx.conf exists, use that,  otherwise use /etc/freepbx.conf.

That's not how I would expect it to work, which is how it was - the other way round.  Also, /etc/asterisk/freepbx.conf is liable to be writable by the webuser, whilst /etc/freepbx.conf shouldn't be.


Approved


It looks like a much cleaner way to handle it. I'm going to have to deal with the disposables again probably when merging #24, so it probably makes sense to update to using `CompositeDisposable` then. Thanks!


The manner of the checking doesn't really matter to me.  I've seen (from my earliest attempts) the cascading failure later when AMPBIN isn't set.  So it ought to be trapped here, just as a sanity check.


How is this %c supposed to work here?


Hello Luc,

I would tend to think modern compilers decide to inline cleverly by
themselves (even w/o the inline keyword) as long as they are given the
opportunity to do it (by having code in the header file).

So, it's really as you like :-)

T.

Le 19/01/2016 09:24, Luc a écrit :
>
> Hi may be it is question of habits but when doing function in header
> the usage is to put then inline no ?
> like in storestrings.h
> |bool add (String & string) {return add(string.c_str());};|
> and others
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/treepleks/ESP8266/commit/f48c2ea5135be57ada53137dcbcf98d76b32647f#commitcomment-15524080>.
>


Issues mentioned in this commit (a041c3856fd6244a073e32014f41ab3ac07a9424):

* [Issue #1](https://bugs.mtasa.com/view.php?id=1)


Ok, not sure it's even used, but yeah, I agree the logic appears backwards.


Depois disto a minha reputação está arruinada, bolas!


Well, you can remove the final "} else {" clause and that ought to address your concern.


This would run it multiple times if found


@flippmoke I was surprised this threw an error and didn't just return `false`. Also surprised that the `name` parameter to this function is compared to the name in the layer's buffer, and not the name provided in the `append_layer_buffer` function. Would it ever be possible to have these two names be different?


This is a strange inversion.  Why not have the `TransformerRegistry` pull its settings from the settings module, rather than importing it the other way?  I always worry when I see the settings module importing application code, because I've seen it lead to import issues as code gets refactored, as settings need to be loaded fairly early on.


Gah, I hate Git. It told me my repository it out of date and asked me to update it then I pressed Yes and then it reverted all the changes instead of updating my local repository. *sigh*

Trying to figure out how to revert it. ^^;


good, thats better


No, not really, but I'm not using ODBC at this moment, and I didn't want to figure out how to configure it just so I could test it.  Ideally, yes, this too would be conditionalized, but for now I am just interested in getting the basic system going.


Just one minor correction I would make:

'Unable to get metadata of resource' should be 'Unable to get metadata for resource'
s/of/for

Thanks,
Chris


this would not even work with a valid buffer so its somewhat a bad test... the reason being that calling `get_string()` expects a previous length defined and would expect to be calling `next`, which I don't think it could ever do properly because it is missing a variant prior to this in the buffer. Layer reader above checks the layer for a name internally, so this is a little different.


Изменился порядок версий


Да это точно


This should be in a separate commit in devel since it is really a bug and it will fix #1158.


Шаблончік взято, можна чекати останнього тижня :D


The initial script only takes "KEGG" as a viable option, but my goal is to expand and copy over more of my old code for printing out the BioCyc data and also, as it follows, subsystems and maybe BiGG pathways.

This initial work, though it'd been a long time coming, was motivated by the need to create a microbial SubsystemAnnotation object which essentially is a list of KEGG maps and their reactions.


Don't comment this


As mentioned elsewhere, there should be a (simple) way to update the cache without returning the results.  It looks weird to use a `get_` method for its side effects.  Maybe `self.update_collected()` or `self.update_cache()` on this class.


@pestOO see fa56ff1


hmm shouldn't this be configurable instead of just ripping out bootstrap and replacing it with semantic?


In comparison, when we call `layer_reader` with the index argument, we get a `true` status, and no error is thrown. I don't know what the best result would be here, whether we validate the layer within the `layer_reader` function, or always return a layer reader and `true`, and let the user determine if the layer is valid.


Something fishy. This change gives freeze and reboot to me.


Title says.... not ready :)


I've rebased my PR to avoid passing *pgversion*.


I suppose so.  Adding a "break" after the run will address this comment.


Pardon, je me suis trompé, c'est exactement l'inverse : pourquoi "disponible sur" au lieu de "disponible à" ?


as a first step, store these, instead of printing them


Also pretty surprised that no errors were thrown on the bogus tile that was parsed from the bogus layer data. Do we want to have any errors throw here?


You need to rewrite your git history if you want to erase secrets...


A think it wold be better if you do it like this.
```python
self.active_offers = UserUserActivity.query
      .filter(UserUserActivity.from_user_id == current_user.id,
               UserUserActivity.start >= date.today())
      .order_by(UserUserActivity.start)
```


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


when you are calling bogus tile here, you are creating a tile object and the `parsefrombuffer` [here](https://github.com/mapbox/mapnik-vector-tile/blob/v2_spec/src/vector_tile_tile.hpp#L138) simply just returns false, we should likely throw if that returns false. The tile information is all just default data. It is important to check `hasVersion` for example in these situations.


weird also that when I turn off HW acceleration (in the video menu) the TARZ video has many problems with no highlights in the menu, or no menu headings displayed... My previous good build dates back to 17 January.


@Taloz lol


Why `i`?


`account_offers` is more suitable here


Where is the recording of the version of the software itself recorded in provenance?


Should always use NSDictionary+SafeExpectations.h methods.


nice!


This code is exactly equivalent to what was there before, only shorter and easier to comprehend.


Feel free to change its behavior in private rooms.


errno check :)


@timstclair I am going to clone your commit and try to get it in this week


Is pipeline configuration stored as blobs of text in a RDBMS? Files in a noSQL database? Files in a git repository? Many times the config will barely change from run to run so storing the whole thing each time seems wasteful. Maybe that is discussed later.


leftover debug code?


set


get


leftover debug code(2)?


++ built out and tested


The problem is the code that you removed ('prefer /etc/asterisk/freepbx.conf over /etc/freepbx.conf') is wrong, and shouldn't have been there.  We should always prefer /etc/freepbx.conf over /etc/asterisk/freepbx.conf, and in all honesty, I'm somewhat hesitant about even supporting the FREEPBX_CONF environment variable *at all*.

This is not your fault (or problem), and is something we're going to have to address.


# Assignment 1 Grading Rubric (15 points total)

## Screenshots

- [ ] Assignment 1 contains directory of files for user (0.5 pt)
- [ ] Repository contains screenshot of [github][] account (0.5 pt)
- [ ] Repository contains screenshot of [Slack][] session (0.5 pt)
- [ ] Repository contains screenshot of [Atom][] installed on users computer (0.5 pt)
- [ ] Repository contains screenshot of screenshot showing that user installed [linter-flake8][] (0.5 pt)
- [ ] Repository contains screenshot of the Anaconda [REPL][] on user's computer (0.5 pt)
- [ ] Repository contains screenshot, in the repository, displayed by Github Desktop (0.5 pt)

## jupyter notebook

- [ ] Repository contains ipython/jupyter mini-tutorial as ipynb file (0.5 pt)
- [ ] ipynb Task 1 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 2 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 3 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 4 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 5 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 6 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 7 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 8 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 1 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 2 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 3 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 4 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 5 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 6 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 7 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 8 appears to be answered correctly (0.5 pt)
- [ ] You can successfully re-run every step of the ipynb notebook (3.0 pt)

[screenshot]: https://en.wikipedia.org/wiki/Screenshot
[git]: https://git-scm.com/
[github]: https://github.com
[Slack]: https://biolprogramming.slack.com
[Atom]: https://atom.io/
[linter-flake8]: https://atom.io/packages/linter-flake8
[syllabus]: https://github.com/biolprogramming/syllabus
[ipython]: http://ipython.org/notebook.html
[jupyter]: http://jupyter.org/
[REPL]: https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop


You haven't any relations yet. You can easily add them.


Should use arrayForKey from SafeExpectations here.


Stop flooding my inbox. My email client already considered your emails as spam :D

No, this considers only if the ruins have an intersection, all other cases still have the issue. However, the old intersection check was not correct either.

Again, don't take it personally, I'm really just trying to help out. You did great work keeping this mod running and your overall list of mods you are maintaining is impressive, must be hard to keep them updated.

And yes, I forgot to change the method name in the first commit. I'm sorry for that.


    OK, I will rename and rewrite it tomorrow.

    On 1/20/2016 1:59 PM, Michał Trojnara
      wrote:

      Yes, we do need an internal function for raw key derivation. It
        probably does not need to be as complex as PKCS11_ecdh_derive().
      —
        Reply to this email directly or view
          it on GitHub.

    --

 Douglas E. Engert  <DEEngert@gmail.com>


what do you mean?  Like, should we delete that decorator entirely?


we could write a loop checking ports on `::` and `localhost` but we'd also have to pass in the user defined live reload host, if they chose to give one, into the loop instead in such a case. In the end forcing ipv4 with a known host(localhost or user defined live reload host) seems most deterministic. binding to ipv6 for purposes of live reload seems overkill unless there is a reason im missing

also my chrome comment at the end is way off, ignore that


So this timestamp and node information can be tracked back to the exact versions of all software systems that were in place at the time (not just DM software but also OS versions). Is that nominally tracked in the provenance system or is there a separate configuration management database linked to provenance?


This will make FiSH incompatible with older irssi versions...


you're right, this was one of the things I was trying for it to query the right index, but I think in the end that must've just been a delay caused by ES taking time to compute a facet.


I don't know it is very new to me


Will do. Thanks.


Will do!


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


I think we start to use "RFC" as generic term for "anything we want to vote on", and this is confusing. We should leave RFC for mostly technical and some meta-technical issues and have some other term ("community vote"?) for things like elections, CRT actions, etc.


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.462.0](http://build01:8888/viewLog.html?buildId=13890&buildTypeId=ConfigInjector_CI) is now running


saw approval from bsparrow435
at https://github.com/basho/lager/commit/063d628549b9bd1ec934f3be4ae715e8a17e6bb4


merging basho/lager/rabbitmq-close-file-after-timebased-rotation = 063d6285 into borshop-integration-316-rabbitmq-close-file-after-timebased-rotation


basho/lager/rabbitmq-close-file-after-timebased-rotation = 063d6285 merged ok, testing candidate = 43183f36


You should a a .gitignore entry for the node_modules directory, that content is managed by npm and should not be in git.

To keep your repo clean, I'd suggest you add the .gitignore, amend your last commit, and force push your branch.

(I ended up here after a google search because your repo has all of the source from your dependencies)


I am guessing that the defer_user_update falg is actually to avoid the ECANCEL error as we got here.
See for example RGWSubUserPool::execute_add that calls keys.add with the defer flag set to true.


it should not, server_ischannel is also defined in irssi 0.8.15


TeamCity Open-source Libraries :: ConfigInjector :: CI [Build 2.0.462.0](http://build01:8888/viewLog.html?buildId=13890&buildTypeId=ConfigInjector_CI) outcome was **SUCCESS**
Summary: Tests passed: 38 Build time: 00:00:38


So all provenance generating systems need to agree on the time? How accurately? My previous provenance system needed millisecond accuracy because some "tasks" were taking tenths of seconds.


ehhh at the moment whenever you start a test, all the indexes are created `test_<index_name>` instead of the regular name so it's much safer. though you can still directly access the index which is a bit dangerous. (you could do the same with sql by just specifying the table name but there's much less precedent to actually do anything beyond using the ORM). i just always think this scares people from testing ES when in reality it's pretty safe


This is difficult to learn!


I changed the code to use it but...

/home/falso/FiSH-irssi/src/FiSH.c: In function ‘decrypt_msg’:
/home/falso/FiSH-irssi/src/FiSH.c:264:37: error: macro "ischannel" passed 2 arguments, but takes just 1
  if (server_ischannel(server, target))
                                     ^
In every call to it.


Yes, I agree. If you have any suggestions as to improved wording, that' be fine. I think @heiglandreas already made a few though.


Ack, but is related to http://issues.freepbx.org/browse/FREEPBX-11371


"fewer" not "lesser"


Small typo in comments (desription)


Isn't it safer to use:
```
xmlDesc = xmlDesc.substring(0,begin) + graphElem + xmlDesc.substring(end + GRAPHICS.ELEM_END.length());
```


True. There is the RFC process for that. But that's the procedural process. What I meant here, was rather the Contributing Guidelines further down. I'll fix the wording.


Will fix that.


Docs karma and src karma are not mutually exclusive. This suggests doc karma person and src karma person must be different people. If so, this should be explicitly stated.


You don't really need to set `past_offers` and `active_offers' in `self`. Can you  show me some use cases where you would use self.past_offers? Maybe i am wrong.


gotcha, yeah can be confusing. this is the utility function we use to define the indexes (fairly new): https://github.com/dimagi/commcare-hq/blob/master/corehq/util/elastic.py#L9


The LOG_ in the enum name seems redundant now.


That particular idiom is rampant throughout the code.  In terms of supporting the environmental variable, the /etc/asterisk/freepbx.conf and /etc/freepbx.conf location.  In all likelihood, a bug should be filed for this, and then address the code in the entire repo at one time.


@rkday @vodik : I thought it might be time to make the 3.5.0 final. Lets say within a month or so.


i just re-uploaded and created a new pull request, i think i might copyed
and pasted what we did in class for glossory for the last one

On Wed, Jan 20, 2016 at 1:43 PM, Trismeg <notifications@github.com> wrote:

> This is incomplete
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/tonyanthonylin/glossary/commit/b3ee3a10b3003eac3aa9d7531c02e4cf6c97f5a3#commitcomment-15566072>
> .
>


thanks for the heads up.  was busy running through a plural sight tutorial and skipped this step.  Will add when I get off work.


@tarkatronic ping


This code should be removed anyway, as it allows an automatic clobber of /etc/freepbx.conf when that file exists.


That is terribly exciting! Yes it works very well.

Does the html file have to be left behind or could it be written into the session temp directory and viewed from there? Then you don't have these lying around your Project, needing to be gitignored.

This would be perfect as the default document format in `devools::use_readme_rmd()`.


I know we've traditional tried to make these behave like rails models, but I think in this case it makes things less clear -- because we're executing clone instead of save.

In general, I'm increasingly thinking that more transparently mirroring the underlying API rather than making things too ruby-ish might have been a better design pattern.


You'll need to wrap the _asset in backticks, otherwise markdown will render following in italics.


you will need to use
```
#ifdef ischannel
#undef ischannel
#endif
```
after including irc.h


# Assignment 1 Grading Rubric (15 points total)

## Screenshots

- [ ] Assignment 1 contains directory of files for user (0.5 pt)
- [ ] Repository contains screenshot of [github][] account (0.5 pt)
- [ ] Repository contains screenshot of [Slack][] session (0.5 pt)
- [ ] Repository contains screenshot of [Atom][] installed on users computer (0.5 pt)
- [ ] Repository contains screenshot of screenshot showing that user installed [linter-flake8][] (0.5 pt)
- [ ] Repository contains screenshot of the Anaconda [REPL][] on user's computer (0.5 pt)
- [ ] Repository contains screenshot, in the repository, displayed by Github Desktop (0.5 pt)

## jupyter notebook

- [ ] Repository contains ipython/jupyter mini-tutorial as ipynb file (0.5 pt)
- [ ] ipynb Task 1 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 2 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 3 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 4 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 5 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 6 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 7 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 8 is presented with a description explaining what is occurring (0.5 pt)
- [ ] ipynb Task 1 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 2 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 3 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 4 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 5 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 6 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 7 appears to be answered correctly (0.5 pt)
- [ ] ipynb Task 8 appears to be answered correctly (0.5 pt)
- [ ] You can successfully re-run every step of the ipynb notebook (3.0 pt)

[screenshot]: https://en.wikipedia.org/wiki/Screenshot
[git]: https://git-scm.com/
[github]: https://github.com
[Slack]: https://biolprogramming.slack.com
[Atom]: https://atom.io/
[linter-flake8]: https://atom.io/packages/linter-flake8
[syllabus]: https://github.com/biolprogramming/syllabus
[ipython]: http://ipython.org/notebook.html
[jupyter]: http://jupyter.org/
[REPL]: https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop


Shouldn't these be of type cubeb_devid? They're not necessarily strings on every platform.


could reduce it as follows:
```
if parsedMaxEBSVols, err := strconv.Atoi(rawMaxEBSVols); err != nil || parsedMaxEBSVols <= 0 {
  //log error
}
else {
maxEBSVols = uint(parsedMaxEBSVols)
}
```


In this case maybe it's saved by the method simply being clone rather than save, since that's what happens?


Good catch. You are right ! My mistake.


Yes the Dispose is placed in the auto generated designer code but that method is not "regenerated" and since the _server is an IDisposable I added that to the Dispose method.  There is no open issue that this would resolve.


this is a little worrying, since I can't easily confirm your comment just based on the diff. But I trust you.


This should now be include_once(getenv("FREEPBX_CONF")) as you've previously fixed


Spurious change.


OMG OMG OMG this is exactly what we've been hoping for!


Thanks


:+1: LGTM


What if it becomes a class method that takes the appropriate arguments and /returns/ a SignupForm object?


Sounds better.


I have a question about this one.  We use MySQL 5.6 and without setting ALLOW_INVALID_DATES.  I have not had any errors creating the initial database with /scripts/mysql.sql

Where is the error occurring? I don't believe the system should be set to allow invalid dates.


There must be something wrong with this line. My ARM build fails.

`Target: arm-linux-gnueabihf`

So I am not sure whats exactly wrong then.


Hey, sorry Ive been so long in replying. I will create a new branch with the changes, and submit a pull request. Tuesday was VERY good learning experience for GitHub and Terminal. Is it possible for me to reply to your comments above or do I need to do it down here at the bottom?


That seems to fix it. At least the building, going to run some tests. Thank you again.


Ack


nvm, its not there in the other commit i think.


Okay, the wording requires improvement.

The intention was that indeed, if people were overly "generous" with ignoring the Collaboration Guidelines and with several interventions from the Mediation Team, there should be "strong" action to do something about a particular member. IMO, a possibility that you would in an excessive case do get a "post-rate" ban if that's feasible.

But I doubt it would come to that, as I hope that other members on the list would point out to a person that serial-posting, that it's detrimental for effective collaboration to do so. After all, pointing out a mistake in a non-attacking way is something that happens in real life much more than being put behind bars.


111768812_VRFNoLoadOAFlow (Nigusse) - Win64-Windows-7-VisualStudio-12: OK (2057 of 2057 tests passed, 0 test warnings)

 * 6 tests had: AUD diffs.

![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)


Any reason not to remove this? The compiler error is probably preferable to silent changes to logging?


I think what they mean is "the members of the project". In that case, everybody who discusses on internals (and potential side channels). It's a social contract between all of us.


This is a reasonably non-standard default, but, I don't think freepbx uses any cgi's so it's probably not important.  It might be worth removing the ampcgibin variable totally.


Please remove `db.session.commit()` beyond the loop.


@wibeasley and @andkov could you please check description on this line?


We probably should be pointing to the interface not implementation here.


Thanks! I'd been using just `build`. Will sort that out going forward.


I dropped a line in the hardened issue #7220.


#146 fixed


@jpsim: This fixes an issue which was occurring consistently.


Actually, *I* did not mean anything yet. The Contributor Covenant is still the original one, and it needs work. In this case, it should mean "Mediation Team" as you originally thought.

I will collect a bunch of suggestions towards the wording of the Covenant, and then make a PR for it, so that it is easier to comment.


112083967_VentilatedSlab (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (956 of 956 tests passed, 0 test warnings)

![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) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-26.85%25-green.svg)


toying with idea of checking same port on multiple interfaces

https://github.com/eriktrom/ember-cli/commit/0382675d384e8ab33f3028c74fe4826877e3b963


Probably ought to check if c.conn is `nil` here? Since we may have been asleep on the lock for who knows how long.


Do you think we could use this code to spot failures in R tests when running them by CI?


I encourage you to split function `sendAudioData` to two separate functions:
```c++
void sendAudioData(int16_t *pcmData, int pcmLength);

void sendAudioData(float *pcmData, int pcmLength);
```


Thanks for pointing that out, it will be reversed with the next commit.


Can you explain why is this needed on OSX? Also where does 600 come from?


Oops


Thank you very much. I'll merge and review this locally.


That's a good suggestion. I will fix it unless a PR beats me to it ;-)


@lattner This broke the standard library build with assertions on:

```
[42/145] Compiling /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/macosx/x86_64/Swift.o
FAILED: cd /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core && /Applications/MuirTide/Xcode.app/Contents/Developer/usr/local/bin/cmake -E make_directory /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/macosx/x86_64 && /Applications/MuirTide/Xcode.app/Contents/Developer/usr/local/bin/cmake -E make_directory /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/./lib/swift/macosx/x86_64 && /Users/slava/src/new/swift/utils/line-directive /Users/slava/src/new/swift/stdlib/public/core/Algorithm.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBody.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBufferType.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayCast.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayType.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Arrays.swift /Users/slava/src/new/swift/stdlib/public/core/Assert.swift /Users/slava/src/new/swift/stdlib/public/core/AssertCommon.swift /Users/slava/src/new/swift/stdlib/public/core/Bool.swift /Users/slava/src/new/swift/stdlib/public/core/BooleanType.swift /Users/slava/src/new/swift/stdlib/public/core/BridgeObjectiveC.swift /Users/slava/src/new/swift/stdlib/public/core/BridgeStorage.swift /Users/slava/src/new/swift/stdlib/public/core/Builtin.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/BuiltinMath.swift /Users/slava/src/new/swift/stdlib/public/core/CString.swift /Users/slava/src/new/swift/stdlib/public/core/CTypes.swift /Users/slava/src/new/swift/stdlib/public/core/Character.swift /Users/slava/src/new/swift/stdlib/public/core/CocoaArray.swift /Users/slava/src/new/swift/stdlib/public/core/Collection.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/CollectionAlgorithms.swift /Users/slava/src/new/swift/stdlib/public/core/CompilerProtocols.swift /Users/slava/src/new/swift/stdlib/public/core/ContiguousArrayBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/EmptyCollection.swift /Users/slava/src/new/swift/stdlib/public/core/ErrorType.swift /Users/slava/src/new/swift/stdlib/public/core/Existential.swift /Users/slava/src/new/swift/stdlib/public/core/Filter.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FixedPoint.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Flatten.swift /Users/slava/src/new/swift/stdlib/public/core/FlatMap.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPoint.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointOperations.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointParsing.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/HashedCollections.swift /Users/slava/src/new/swift/stdlib/public/core/Hashing.swift /Users/slava/src/new/swift/stdlib/public/core/HeapBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/ImplicitlyUnwrappedOptional.swift /Users/slava/src/new/swift/stdlib/public/core/Index.swift /Users/slava/src/new/swift/stdlib/public/core/InputStream.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/IntegerArithmetic.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/IntegerParsing.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Interval.swift /Users/slava/src/new/swift/stdlib/public/core/Join.swift /Users/slava/src/new/swift/stdlib/public/core/LazyCollection.swift /Users/slava/src/new/swift/stdlib/public/core/LazySequence.swift /Users/slava/src/new/swift/stdlib/public/core/LifetimeManager.swift /Users/slava/src/new/swift/stdlib/public/core/ManagedBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/Map.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Mirrors.swift /Users/slava/src/new/swift/stdlib/public/core/Misc.swift /Users/slava/src/new/swift/stdlib/public/core/ObjCMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/Optional.swift /Users/slava/src/new/swift/stdlib/public/core/OptionSet.swift /Users/slava/src/new/swift/stdlib/public/core/OutputStream.swift /Users/slava/src/new/swift/stdlib/public/core/Pointer.swift /Users/slava/src/new/swift/stdlib/public/core/Policy.swift /Users/slava/src/new/swift/stdlib/public/core/Print.swift /Users/slava/src/new/swift/stdlib/public/core/REPL.swift /Users/slava/src/new/swift/stdlib/public/core/Range.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/RangeMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/RangeReplaceableCollectionType.swift /Users/slava/src/new/swift/stdlib/public/core/Reflection.swift /Users/slava/src/new/swift/stdlib/public/core/Repeat.swift /Users/slava/src/new/swift/stdlib/public/core/Reverse.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Runtime.swift /Users/slava/src/new/swift/stdlib/public/core/Sequence.swift /Users/slava/src/new/swift/stdlib/public/core/SequenceWrapper.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/SequenceAlgorithms.swift /Users/slava/src/new/swift/stdlib/public/core/SetAlgebra.swift /Users/slava/src/new/swift/stdlib/public/core/ShadowProtocols.swift /Users/slava/src/new/swift/stdlib/public/core/Shims.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Slice.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Sort.swift /Users/slava/src/new/swift/stdlib/public/core/StaticString.swift /Users/slava/src/new/swift/stdlib/public/core/Stride.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StrideMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/StringCharacterView.swift /Users/slava/src/new/swift/stdlib/public/core/String.swift /Users/slava/src/new/swift/stdlib/public/core/StringBridge.swift /Users/slava/src/new/swift/stdlib/public/core/StringBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/StringCore.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StringInterpolation.swift /Users/slava/src/new/swift/stdlib/public/core/StringLegacy.swift /Users/slava/src/new/swift/stdlib/public/core/StringUnicodeScalarView.swift /Users/slava/src/new/swift/stdlib/public/core/StringUTF16.swift /Users/slava/src/new/swift/stdlib/public/core/StringUTF8.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StringUTFViewsMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/SwiftNativeNSArray.swift /Users/slava/src/new/swift/stdlib/public/core/Unicode.swift /Users/slava/src/new/swift/stdlib/public/core/UnicodeScalar.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnicodeTrie.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnavailableStringAPIs.swift /Users/slava/src/new/swift/stdlib/public/core/Unmanaged.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnsafeBufferPointer.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnsafePointer.swift /Users/slava/src/new/swift/stdlib/public/core/Availability.swift /Users/slava/src/new/swift/stdlib/public/core/Bit.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/CollectionMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/CollectionOfOne.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/ExistentialCollection.swift /Users/slava/src/new/swift/stdlib/public/core/Mirror.swift /Users/slava/src/new/swift/stdlib/public/core/Process.swift /Users/slava/src/new/swift/stdlib/public/core/SliceBuffer.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Tuple.swift /Users/slava/src/new/swift/stdlib/public/core/VarArgs.swift /Users/slava/src/new/swift/stdlib/public/core/Zip.swift /Users/slava/src/new/swift/stdlib/public/core/Prespecialized.swift -- /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/./bin/swiftc -c -sdk /Applications/MuirTide/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -target x86_64-apple-macosx10.9 -F /Applications/MuirTide/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/../../../Developer/Library/Frameworks -Onone -g -D INTERNAL_CHECKS_ENABLED -I /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/./lib/swift/macosx/x86_64 -module-cache-path /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/./clang-module-cache -no-link-objc-runtime -nostdimport -parse-stdlib -module-name Swift -Xfrontend -sil-serialize-all -module-link-name swiftCore -force-single-frontend-invocation -parse-as-library -emit-module -emit-module-path /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/./lib/swift/macosx/x86_64/Swift.swiftmodule -o /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/macosx/x86_64/Swift.o /Users/slava/src/new/swift/stdlib/public/core/Algorithm.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBody.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayBufferType.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayCast.swift /Users/slava/src/new/swift/stdlib/public/core/ArrayType.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Arrays.swift /Users/slava/src/new/swift/stdlib/public/core/Assert.swift /Users/slava/src/new/swift/stdlib/public/core/AssertCommon.swift /Users/slava/src/new/swift/stdlib/public/core/Bool.swift /Users/slava/src/new/swift/stdlib/public/core/BooleanType.swift /Users/slava/src/new/swift/stdlib/public/core/BridgeObjectiveC.swift /Users/slava/src/new/swift/stdlib/public/core/BridgeStorage.swift /Users/slava/src/new/swift/stdlib/public/core/Builtin.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/BuiltinMath.swift /Users/slava/src/new/swift/stdlib/public/core/CString.swift /Users/slava/src/new/swift/stdlib/public/core/CTypes.swift /Users/slava/src/new/swift/stdlib/public/core/Character.swift /Users/slava/src/new/swift/stdlib/public/core/CocoaArray.swift /Users/slava/src/new/swift/stdlib/public/core/Collection.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/CollectionAlgorithms.swift /Users/slava/src/new/swift/stdlib/public/core/CompilerProtocols.swift /Users/slava/src/new/swift/stdlib/public/core/ContiguousArrayBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/EmptyCollection.swift /Users/slava/src/new/swift/stdlib/public/core/ErrorType.swift /Users/slava/src/new/swift/stdlib/public/core/Existential.swift /Users/slava/src/new/swift/stdlib/public/core/Filter.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FixedPoint.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Flatten.swift /Users/slava/src/new/swift/stdlib/public/core/FlatMap.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPoint.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointOperations.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointParsing.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/HashedCollections.swift /Users/slava/src/new/swift/stdlib/public/core/Hashing.swift /Users/slava/src/new/swift/stdlib/public/core/HeapBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/ImplicitlyUnwrappedOptional.swift /Users/slava/src/new/swift/stdlib/public/core/Index.swift /Users/slava/src/new/swift/stdlib/public/core/InputStream.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/IntegerArithmetic.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/IntegerParsing.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Interval.swift /Users/slava/src/new/swift/stdlib/public/core/Join.swift /Users/slava/src/new/swift/stdlib/public/core/LazyCollection.swift /Users/slava/src/new/swift/stdlib/public/core/LazySequence.swift /Users/slava/src/new/swift/stdlib/public/core/LifetimeManager.swift /Users/slava/src/new/swift/stdlib/public/core/ManagedBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/Map.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Mirrors.swift /Users/slava/src/new/swift/stdlib/public/core/Misc.swift /Users/slava/src/new/swift/stdlib/public/core/ObjCMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/Optional.swift /Users/slava/src/new/swift/stdlib/public/core/OptionSet.swift /Users/slava/src/new/swift/stdlib/public/core/OutputStream.swift /Users/slava/src/new/swift/stdlib/public/core/Pointer.swift /Users/slava/src/new/swift/stdlib/public/core/Policy.swift /Users/slava/src/new/swift/stdlib/public/core/Print.swift /Users/slava/src/new/swift/stdlib/public/core/REPL.swift /Users/slava/src/new/swift/stdlib/public/core/Range.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/RangeMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/RangeReplaceableCollectionType.swift /Users/slava/src/new/swift/stdlib/public/core/Reflection.swift /Users/slava/src/new/swift/stdlib/public/core/Repeat.swift /Users/slava/src/new/swift/stdlib/public/core/Reverse.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Runtime.swift /Users/slava/src/new/swift/stdlib/public/core/Sequence.swift /Users/slava/src/new/swift/stdlib/public/core/SequenceWrapper.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/SequenceAlgorithms.swift /Users/slava/src/new/swift/stdlib/public/core/SetAlgebra.swift /Users/slava/src/new/swift/stdlib/public/core/ShadowProtocols.swift /Users/slava/src/new/swift/stdlib/public/core/Shims.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Slice.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Sort.swift /Users/slava/src/new/swift/stdlib/public/core/StaticString.swift /Users/slava/src/new/swift/stdlib/public/core/Stride.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StrideMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/StringCharacterView.swift /Users/slava/src/new/swift/stdlib/public/core/String.swift /Users/slava/src/new/swift/stdlib/public/core/StringBridge.swift /Users/slava/src/new/swift/stdlib/public/core/StringBuffer.swift /Users/slava/src/new/swift/stdlib/public/core/StringCore.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StringInterpolation.swift /Users/slava/src/new/swift/stdlib/public/core/StringLegacy.swift /Users/slava/src/new/swift/stdlib/public/core/StringUnicodeScalarView.swift /Users/slava/src/new/swift/stdlib/public/core/StringUTF16.swift /Users/slava/src/new/swift/stdlib/public/core/StringUTF8.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/StringUTFViewsMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/SwiftNativeNSArray.swift /Users/slava/src/new/swift/stdlib/public/core/Unicode.swift /Users/slava/src/new/swift/stdlib/public/core/UnicodeScalar.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnicodeTrie.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnavailableStringAPIs.swift /Users/slava/src/new/swift/stdlib/public/core/Unmanaged.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnsafeBufferPointer.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/UnsafePointer.swift /Users/slava/src/new/swift/stdlib/public/core/Availability.swift /Users/slava/src/new/swift/stdlib/public/core/Bit.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/CollectionMirrors.swift /Users/slava/src/new/swift/stdlib/public/core/CollectionOfOne.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/ExistentialCollection.swift /Users/slava/src/new/swift/stdlib/public/core/Mirror.swift /Users/slava/src/new/swift/stdlib/public/core/Process.swift /Users/slava/src/new/swift/stdlib/public/core/SliceBuffer.swift /Users/slava/src/new/build/Ninja-DebugAssert/swift-macosx-x86_64/stdlib/public/core/8/Tuple.swift /Users/slava/src/new/swift/stdlib/public/core/VarArgs.swift /Users/slava/src/new/swift/stdlib/public/core/Zip.swift /Users/slava/src/new/swift/stdlib/public/core/Prespecialized.swift
Assertion failed: (!isPolymorphic() && "no args for polymorphic substitution"), function substGenericArgs, file /Users/slava/src/new/swift/lib/SIL/SILFunctionType.cpp, line 2030.
0  swift                    0x000000010faf899e llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 46
1  swift                    0x000000010faf8de9 PrintStackTraceSignalHandler(void*) + 25
2  swift                    0x000000010faf5589 llvm::sys::RunSignalHandlers() + 425
3  swift                    0x000000010faf9129 SignalHandler(int) + 345
4  libsystem_platform.dylib 0x00007fff9699352a _sigtramp + 26
5  libsystem_platform.dylib 0x00007fff635f08d5 _sigtramp + 3435516869
6  swift                    0x000000010faf8e0b raise + 27
7  swift                    0x000000010faf8ec2 abort + 18
8  swift                    0x000000010faf8ea1 __assert_rtn + 129
9  swift                    0x000000010a795bc2 swift::SILFunctionType::substGenericArgs(swift::SILModule&, swift::ModuleDecl*, llvm::ArrayRef<swift::Substitution>) + 162
10 swift                    0x000000010a9d0736 swift::Lowering::SILGenFunction::emitApplyOfDefaultArgGenerator(swift::SILLocation, swift::ConcreteDeclRef, unsigned int, swift::CanType, swift::Lowering::AbstractionPattern, swift::Lowering::SGFContext) + 470
11 swift                    0x000000010a97b65d (anonymous namespace)::ArgEmitter::emitShuffle(swift::Expr*, swift::Expr*, llvm::ArrayRef<swift::TupleTypeElt>, swift::ConcreteDeclRef, llvm::ArrayRef<swift::Expr*>, llvm::ArrayRef<int>, llvm::ArrayRef<unsigned int>, swift::Type, swift::Lowering::AbstractionPattern) + 8717
12 swift                    0x000000010a979432 (anonymous namespace)::ArgEmitter::emitShuffle(swift::TupleShuffleExpr*, swift::Lowering::AbstractionPattern) + 882
13 swift                    0x000000010a978477 (anonymous namespace)::ArgEmitter::emitExpanded(swift::Lowering::ArgumentSource&&, swift::Lowering::AbstractionPattern) + 1607
14 swift                    0x000000010a9776d2 (anonymous namespace)::ArgEmitter::emit(swift::Lowering::ArgumentSource&&, swift::Lowering::AbstractionPattern) + 162
15 swift                    0x000000010a977060 (anonymous namespace)::ArgEmitter::emitTopLevel(swift::Lowering::ArgumentSource&&, swift::Lowering::AbstractionPattern) + 128
16 swift                    0x000000010a976253 (anonymous namespace)::CallSite::emit(swift::Lowering::SILGenFunction&, swift::Lowering::AbstractionPattern, (anonymous namespace)::ParamLowering&, llvm::SmallVectorImpl<swift::Lowering::ManagedValue>&, llvm::SmallVectorImpl<std::__1::pair<swift::Lowering::LValue, swift::SILLocation> >&, llvm::Optional<swift::ForeignErrorConvention> const&) && + 563
17 swift                    0x000000010a9603ed (anonymous namespace)::CallEmission::apply(swift::Lowering::SGFContext) + 6125
18 swift                    0x000000010a95e5e6 swift::Lowering::SILGenFunction::emitApplyExpr(swift::Expr*, swift::Lowering::SGFContext) + 166
19 swift                    0x000000010a9e39c2 (anonymous namespace)::RValueEmitter::visitApplyExpr(swift::ApplyExpr*, swift::Lowering::SGFContext) + 66
20 swift                    0x000000010a9da79a swift::ASTVisitor<(anonymous namespace)::RValueEmitter, swift::Lowering::RValue, void, void, void, void, void, swift::Lowering::SGFContext>::visitCallExpr(swift::CallExpr*, swift::Lowering::SGFContext) + 74
21 swift                    0x000000010a9d3793 swift::ASTVisitor<(anonymous namespace)::RValueEmitter, swift::Lowering::RValue, void, void, void, void, void, swift::Lowering::SGFContext>::visit(swift::Expr*, swift::Lowering::SGFContext) + 3699
22 swift                    0x000000010a9cbdd9 swift::Lowering::SILGenFunction::emitRValue(swift::Expr*, swift::Lowering::SGFContext) + 201
23 swift                    0x000000010a9d114d swift::Lowering::SILGenFunction::emitIgnoredExpr(swift::Expr*) + 829
24 swift                    0x000000010aa8a2e2 (anonymous namespace)::StmtEmitter::visitBraceStmt(swift::BraceStmt*) + 978
25 swift                    0x000000010aa885bb swift::ASTVisitor<(anonymous namespace)::StmtEmitter, void, void, void, void, void, void>::visit(swift::Stmt*) + 91
26 swift                    0x000000010aa8ef91 (anonymous namespace)::StmtEmitter::visitForEachStmt(swift::ForEachStmt*) + 4481
27 swift                    0x000000010aa886ab swift::ASTVisitor<(anonymous namespace)::StmtEmitter, void, void, void, void, void, void>::visit(swift::Stmt*) + 331
28 swift                    0x000000010aa8a220 (anonymous namespace)::StmtEmitter::visitBraceStmt(swift::BraceStmt*) + 784
29 swift                    0x000000010aa885bb swift::ASTVisitor<(anonymous namespace)::StmtEmitter, void, void, void, void, void, void>::visit(swift::Stmt*) + 91
30 swift                    0x000000010aa88520 swift::Lowering::SILGenFunction::emitStmt(swift::Stmt*) + 48
31 swift                    0x000000010a9fbd6b swift::Lowering::SILGenFunction::emitFunction(swift::FuncDecl*) + 411
32 swift                    0x000000010a92feba swift::Lowering::SILGenModule::emitFunction(swift::FuncDecl*)::$_1::operator()(swift::SILFunction*) const + 346
33 swift                    0x000000010a928841 void emitOrDelayFunction<swift::Lowering::SILGenModule::emitFunction(swift::FuncDecl*)::$_1>(swift::Lowering::SILGenModule&, swift::SILDeclRef, swift::Lowering::SILGenModule::emitFunction(swift::FuncDecl*)::$_1&&) + 865
34 swift                    0x000000010a927ea5 swift::Lowering::SILGenModule::emitFunction(swift::FuncDecl*) + 245
35 swift                    0x000000010aa98179 SILGenExtension::visitFuncDecl(swift::FuncDecl*) + 73
36 swift                    0x000000010aa97b7c swift::ASTVisitor<SILGenExtension, void, void, void, void, void, void>::visit(swift::Decl*) + 620
37 swift                    0x000000010aa9728c SILGenExtension::emitExtension(swift::ExtensionDecl*) + 188
38 swift                    0x000000010aa94b4d swift::Lowering::SILGenModule::visitExtensionDecl(swift::ExtensionDecl*) + 45
39 swift                    0x000000010a940134 swift::ASTVisitor<swift::Lowering::SILGenModule, void, void, void, void, void, void>::visit(swift::Decl*) + 116
40 swift                    0x000000010a92d86c swift::Lowering::SILGenModule::emitSourceFile(swift::SourceFile*, unsigned int) + 220
41 swift                    0x000000010a92de2d swift::SILModule::constructSIL(swift::ModuleDecl*, swift::SILOptions&, swift::FileUnit*, llvm::Optional<unsigned int>, bool, bool) + 1325
42 swift                    0x000000010a92e596 swift::performSILGeneration(swift::ModuleDecl*, swift::SILOptions&, bool, bool) + 134
43 swift                    0x000000010a3c1cb0 performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&) + 7824
44 swift                    0x000000010a3bf54a frontend_main(llvm::ArrayRef<char const*>, char const*, void*) + 12842
45 swift                    0x000000010a3a68ad main + 4285
46 libdyld.dylib            0x00007fff8eb875ad start + 1
```


Nice code, Agent Reagan.


create.


This is going to reset whatever our current `c.conn` is rather than resetting `conn` which is our local copy. Are you sure this is right? I am thinking about the case where we make our local `conn` copy and then somebody else does a reset, and then we reset again here.


@voon, can you check to see if this is right?  I'm concerned that we will hang waiting for attitude data to be published since it's also part of the imu message.


I believe this needs `global writemime` before it.


An alternative would be to close `conn` and then in `resetConnection` check if the real `c.conn` is closed before discarding it.


This looks good but please add the c include before the c++ ones.


That's effectively what I meant. I think however, that even if you're fully against a specific RFC for whatever reason, you can still suggest improvements to it. If things don't go your way in the end -- you never know whether all the changes convince you to change -- you can always vote no.

The substantial reasoning is the most important bit though. I'll fix that too.


you're welcome, please test it. technically there used to be a ischannel macro in irc.h which was like fish_ischannel, and another **macro** server_ischannel which calls `(server)->ischannel()`. if that ischannel macro from irc.h is also in effect, then that call will get further expanded to `(server)->{expanded irc.h macro here}` which obviously bombs


This looks good.


I understand, I just don't think that `all_traits` is really needed by the code which checks whether an impl has all the items defined in the trait.


Yep correct.


Yes, I know the others do. I'm suggesting that this one doesn't necessarily have to, though.


I may open up a PR sometime. Thanks for quick replies.


Mltumesc mult man


Conceptually this looks similar to https://github.com/dropbox/godropbox/blob/master/resource_pool/resource_pool.go minus the specifics about Kafka? I don't mean to be That Guy suggesting you go use this other random thing, but I just thought I would FYI you.