Hi Kit-

We should be careful not to check in the .class and .jar files. These are typically created by the build process when source files are modified.  We should setup a .gitignore file so that Git does not automatically check in these files.

Regards-
Tom


Tu aurais pu éviter de commiter les traces...


Done.


Pointless checks, remove


Ok, I didn't know, but aren't we making some pretty big changes that could affect documentation? The whole system of up/downgrading versions was introduced in 1.2.1 and is not part of 1.2.0, if someone wants to look at the docs for 1.2.0 they'll be getting all kinds of stuff that won't exist in their version.


**Задание 2**
Напишите программу, которая бы выполняла следующие задачи:
выводила название программы "Общество в начале XXI века";
Запрашивала у пользователя его возраст;

- Option 1
Eсли пользователь вводит числа от 0 до 7, то программа выводила надпись "Вам в детский сад";

- Option 2
от 7 до 18 - "Вам в школу";

- Option 3
от 18 до 25 - "Вам в профессиональное учебное заведение";

- Option 4
от 25 до 60 - "Вам на работу";

- Option 5
от 60 до 120 – "Вам предоставляется выбор";

меньше 0 и больше 120 – пятикратный вывод надписи "Ошибка! Это программа для людей!"

_В программе желательно использовать все "атрибуты" структурного программирования:ветвление и цикл._


Shouldn't `4, 5, 6` be repeated 3 times according to `for i in 0..<3:`?


Consider just returning a resolved promise, because `findLayer` will always return null in this case.


I figured, but just wanted to make sure you knew it wasn't a necessity.
Your assignment was so well done I was having a hard time coming up with
any feedback :)
On Feb 10, 2016 3:42 AM, "MikeSchincariol" <notifications@github.com> wrote:

> Sometimes I do that as a placeholder to add additional logic later. But
> sometimes I do that just to be explicit that I meant to do nothing (it
> helps others less familiar with Python constructs that read my code at
> work).
>
> Mike
> On Feb 9, 2016 3:40 PM, "Summer Rae" <notifications@github.com> wrote:
>
> > This is awesome!
> >
> > I'm curious if you're using try/except/finally and passing 'pass' to
> > finally because you are planning for more error catching downstream?
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/MikeSchincariol/IntroPython2016a/commit/b7a21ede3fb7f855b89963cf33291e457da379e0#commitcomment-15988754
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/MikeSchincariol/IntroPython2016a/commit/b7a21ede3fb7f855b89963cf33291e457da379e0#commitcomment-16002783>
> .
>


By mistake a conflict occurred in a file and then few unnecessary and erroneous commits were done. The DataAccessLayer branch, hence, was rebased to the last merge from DataAccessLayer to ContactsManagement to bring revert things back to the point where everything was good.


Ah, m_sensitive is public member. I'll remove this setter and access the flag directly.


Bumping uncss to 0.13.0 fixes #173.


Rajoute ptetre une remarque sur PhP ;)


Fixed.


Changed b/c "default root domain" sounds right for things like "cfapps.io" but not for "cloud09.cfapps.io" which is a subdomain, not a root.  Want to make it clear that you're using the full domain here, e.g. "cloud09.cfapps.io" in the example, in which case your apps will run at myapp.cloud09.cfapps.io -- hope that makes sense, or LMK.  Either way, I think the example helps.


I missed one, sorry.


这个不至于吧？


The type of pscope is string. Should be the name of the argument where `o` is received in the caller. Also, it should be marked as optional and nullable:
`@param {?string} [pscope] ...`


@garyburd this commit was referencing: https://github.com/golang/go/issues/6885 where they were going to add generic, CamelCase references


Totally, I agree, great idea.


Tweet classification using rule based classifier


ок, все подправим))


`o` is nullable: `{?object}`
Also it should be documented something like "The object ...", but keyword arguments seems out of context here.


oh thanks, I completely misunderstood your comment, fixed in 01033647ccbe2f5c96b3ae5abd91d0d4ce4c9526


Consider a class-level doccomment more obviously explaining that this just acquires permission to search NuGet.org. I know the type name clearly indicates this, but that might be easy to miss for a reader who doesn't know of the permission problem.
Or, consider changing "If so, do nothing" to "If not, then offer them the choice"


zxZz


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


How come the `Installer/MainInstaller.txt` was removed and re-created?


AddWarningWhenDElightAndShading (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2112 of 2112 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)


True-- but you do need bosh-init for the next step in this multi-step deployment process, and I'm not sure anyone will just stop after doing the first step.  Will reword "To complete this tutorial, you need..." as "To complete this deployment process, you need..." to clarify.  It's not really a tutorial anyway, so that's good to change!


So basically the name is whatever it is, and this tells you whether that name is original or an alias?


Yes - because I wanted to add the header to [`documentation/manual/working/javaGuide/main/sql/code/jpa.sbt`](https://github.com/mkurz/playframework/commit/74889554bbf344c23b149ddbc9d33ba746dc3e0f#diff-428053ca771f57ed5e84aabfd4eaaeb5R2). I had to add this identifier otherwise also the header inside `jpa.sbt` would show up in the user documentation.


Is there a good reason (other than visual) that units deactivate before they are fully *landed*?


Sorry, I can try less-harder next time if you like 😆 At work, I often put
I'm Easter Eggs just to see if people actually read my stuff.  I can toss a
few in if you like. ☺

I was listening to you and you present the examples in class well. I don't
know how you read code so quickly. Both you and Rick seem to be able to
read other people's code quite fast and quickly make sense of it. Have you
always been able to do that?

I think you said you are I'm bioinformatics? What is that?
On Feb 10, 2016 1:53 PM, "Summer Rae" <notifications@github.com> wrote:

> I figured, but just wanted to make sure you knew it wasn't a necessity.
> Your assignment was so well done I was having a hard time coming up with
> any feedback :)
> On Feb 10, 2016 3:42 AM, "MikeSchincariol" <notifications@github.com>
> wrote:
>
> > Sometimes I do that as a placeholder to add additional logic later. But
> > sometimes I do that just to be explicit that I meant to do nothing (it
> > helps others less familiar with Python constructs that read my code at
> > work).
> >
> > Mike
> > On Feb 9, 2016 3:40 PM, "Summer Rae" <notifications@github.com> wrote:
> >
> > > This is awesome!
> > >
> > > I'm curious if you're using try/except/finally and passing 'pass' to
> > > finally because you are planning for more error catching downstream?
> > >
> > > —
> > > Reply to this email directly or view it on GitHub
> > > <
> >
> https://github.com/MikeSchincariol/IntroPython2016a/commit/b7a21ede3fb7f855b89963cf33291e457da379e0#commitcomment-15988754
> > >
> > > .
> > >
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <
> https://github.com/MikeSchincariol/IntroPython2016a/commit/b7a21ede3fb7f855b89963cf33291e457da379e0#commitcomment-16002783
> >
> > .
> >
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/MikeSchincariol/IntroPython2016a/commit/b7a21ede3fb7f855b89963cf33291e457da379e0#commitcomment-16013912>
> .
>


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1290.2086761102e9e06789af6877be9bf2a3c6feab9d](http://build.palaso.org/viewLog.html?buildId=69077&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 961, ignored: 12 Build time: 00:09:16


Yes. the level on edit forms was disabled.


ใช้เวลาประมาน1ชั่วโมงนิดๆ ในการรันค่ะ


I see your point, the KeyError would be the more unusual scenario. I'll update with your suggestion


@raphaelfabeni Aqui você pode retornar o próprio `foo` ao invés de `aloha`. Seria o equivalente a:

```js
function fn(foo) {
  return foo;
}
```


It was interesting to learn that iPhone 6 and up require a loading screen or splash screen on your app. Like any mobile platform, dealing with icons is tedious. You need to have a different size asset for each type of screen. The GUI for this did make it easier to understand the requirements of the images... once you know what it meant. Adding cross fade to the app when selecting a new target was simple enough but I feel I will need to explore this more as it seems like there is a lot you can do with QuartzCore.


Thanks @juraji for the help! <3


git goes all reddit


We can get the full list here:
https://docs.openexchangerates.org/docs/supported-currencies


@wsargent Here I am going to use `jpa-externalize-resources`.


@raphaelfabeni Com a mudança que sugeri acima, você poderia mudar o seguinte para ter o output `aloha`:

```js
console.log(`${fn('aloha')}`);
```


Please compile this with apktool binary, i need it


no '-doc.noarch'


remove


@mattn

- 細かいですが、「設定」の前に「は」を挟んだほうが良いかもしれません。
- あと、「指定のフラグ」というより「個別のフラグ」ぐらいが良いのではないでしょうか。ユーザーが検索したいフラグを表す曖昧な表現なので、「指定の」というのは個人的にちょっと違和感を持ちました。


Thanks for the comment, will change to 16 MB


should test the case where `o` is _nully_


no need for field specification, refactor


Let's keep a space after the commend


113008903Provide-a-better-warning-message-for-a-triangular-window (lgu1234) - Win64-Windows-7-VisualStudio-12: OK (2080 of 2080 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)


This should be an Enum of the countries we currently support.


Ditto


AddWarningWhenDElightAndShading (mjwitte) - 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)


Maybe better: "Configuration file to specify target parameters


I just realized that strings return true with `nengo.utils.compat.is_iterable`. Is this the functionality that we want? I'm wondering if this has problems other places we use `is_iterable`, because my first instinct when I saw your comment was to use that here.

So do you think we should check explicitly for strings? Would a string just throw an error then, like an int or something would?


This exposes an Awkward interaction between "error" condition and IdleState and the notion of a ClientModule including the deadline as a property.  There were two ways to fix this:

1. Pull out the deadline so we can have a deadline with a null ClientModule in the error case.
2. Explicitly encode the blank screen as a client module and use that in place of a null.

I went with option 2 to see how it works out.  It adds a small amount of complexity to ClientModule, but eliminates all the null checks in client_state_machine.js and allows the state machine to be simplified (Idle folds into Display of an empty module).  Thoughts?


The line will draw whereever the zero value is on the axis. Or what exactly do you mean? :-)


Maybe better: "such as: the kind of platform/board and the login credentials."


Setting $val to a setting stored in cookie should be done conditionally (depending on $useCookie)


It is setting the available space of the table in bytes. So it should be `capacity()`?


2 is totally the right call.


The topic here is "Setting up an AWS Environment for Cloud Foundry with BOSH AWS Bootstrap", which does require > 20, so I think that's needed here.  But I'll add a prominent Note that this is just one, standard deployment and that other deployments don't require so many (or might require more).  That's a great thing to add, so people don't get an incorrect view of CF's VM demands-- important to include, thanks!


Okay that's what I thought, I was planning on working on it more. The way
Andy had it written was very confusing and I had to eat lunch. I'll fix it.

On Wed, Feb 10, 2016, 1:49 PM Alexander Brown <notifications@github.com>
wrote:

> Megan:
> Is it a typo that all of these are Rpq1 crossed with each unit vector?
>
> Also, I may not be following 100% here, but don't you need to account for
> the distance between the CG of the platform and the connection point? In
> other words, why are you crossing Rpqi with ei, rather than ei with the
> vector going from the Pi to the center of the platform?
>
> I think you're confusing this issue because *eventually* you will want to
> find the torque on the motor. But remember, we're currently just trying to
> find the forces in each connecting rod.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Alexanderallenbrown/MotionBase/commit/35398cf3b0b0424e945b6203c32819d215dd711d#commitcomment-16013789>
> .
>


Document the meaning of -1 here


Maybe better: "NOTE: all commented parameters are optional and reports their default value"


that one is deliberate!


Released `0.4.5`


* should test the case where `o` is _nully_.
* should test that `null` is considered a defined value
* should test that `undefined` is considered an undefined value
* should test specifying the default value `dv`


It seems that we have one more columns for the end of line, compared to the following comments.
Can you please check and reformat the text if needed?


I'm afraid this stops compiling the sc-lib + quarks:
```
	compiling dir: '/Users/mz/Library/Application Support/SuperCollider/downloaded-quarks/ModalityTests'
	pass 1 done
ERROR: Superclass 'UnitTest' of class 'TestMKtlDesc' is not defined in any file.
/Users/mz/Library/Application Support/SuperCollider/downloaded-quarks/ModalityTests/Classes/TestMKtlDesc.sc
ERROR: There is a discrepancy.
numClassDeps 1865   gNumClasses 3728
```


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


So `a_slice` or `b_slice` can also be sets of indices, in which case we can't make a view on the signal representing the slice and have to do it specially.


@mattn
`ft-<filetype>-<functionality>`
これ訳さなくて大丈夫ですかね？
例えば `ft-<ファイルタイプ>-<機能>` みたいな感じで。


concate
if the list -> of the list


Should implement `htsjdk.samtools.util.CloseableIterator<AlignmentContext>`


Maybe we should be more generic: "Wait time before trying to access the target after a reboot"


@bgerstle Because its a scroll view and a scroll view changes its bounds when it has a content offset. This is problematic if you want to add a subview and makes sure it is visible. If you have a content offset (i.e. scrolled down the table), then the empty view may be off screen.


This one returns the number of items currently stored in the table. Should be `size()` ?


You made a typo in the commit headline. (Actually, what is a _qucik_?)


Also added a nice progressbar for splash screen and login menu.
Also optimized the network transmissions. Such as when it fails to handle this or when the app receives error 500 from the server.


If it fail, we can't just disable it. Why it can fail? Is this safe? Put that information in a comment here.


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


AddWarningWhenDElightAndShading (mjwitte) - Win64-Windows-7-VisualStudio-12: OK (2080 of 2080 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)


TeamCity Chorus :: chorus-precise64-master Continuous [Build 2.6.585.8515507208c1539220ebee854cf5e7e479e1de6d](http://build.palaso.org/viewLog.html?buildId=69080&buildTypeId=bt323) outcome was **SUCCESS**
Summary: Tests passed: 931, ignored: 56 Build time: 00:21:31


I'm afraid in Ruby many people would misinterpret the meaning of `hash` in this context.


Minor corrections suggested and than for me it can be merged.


Ok, crud removed.  Copyright lines (Dallas, et. al.) in the .c file only.


@tarunkapadia93 No problem


this reminds me, we _really_ need to support [pluralization](https://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPInternational/StringsdictFileFormat/StringsdictFileFormat.html)


@jasnell I don't think you meant to change this?


I guess that's left over debugging stuff?


这个是这样的，当 `configure` 传入 `--disable-lynx` 的时候，`doc/Makefile.am` 是不会产生 `README` 目标的，于是就出错了。只好先这样修理一下。


nope


now is.fail() always true for me (freebsd 10.2-RELEASE)
previous is.bad() working fine.
Failed to decode axyz (freeminer) coordinate string from database (a-165,-7,-11) : c1=, c2=, x=-165 fail=1 eof=1


This seems a bit arbitrary (both the constant and the decision to treat shorter strings differently).


good thing it can be force pushed :P


Will add to commit message and remove from comment block.  I'm a big believer in giving credit where credit is due.


test note


This makes the interface particle sounds stop while switching between menus, and that sounds a bit glitchy


Shouldn't they come to staff hours instead of BoD meetings?


+1. This is better than adding direct dependency to _a_ compiler.


10 кб


Sorry, @bbatsov, don't understand what you're suggesting.


@Mason8r yes! :smile:


Hello darkness, my old friend.


Yes, though it's only global to the file (file scope).  Used by the search functionality to maintain state during calls, since a typical search calls the search function many times, and it needs to know where it 'left off'.


@bcamper @nvkelso trying to add a darker wave shader at z14, am i writing this wrong? not seeing it


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


OK, let me change it to `digest`.


Okay this LGTM. We probably want to provide a real definition for that empty-module (perhaps 'solid' with a black color?) or an error module or something? But we can save that for another CL.


@megantuttle sounds good. just wanted to make sure it was on your radar.


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


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


lines 916 to 921


It would be nice if A) mraa_boolean_t was an enum with defined values for true/false, or B) mraa_boolean_t was based on something like stdbool.h.  At any rate, I've removed these and replaced them with hardcoded 0 and 1.


So my fear was correct. I'll open a thread on ZDForums for the purpose though.


:clap:


Flowers killed. :(


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


We would prefer human-readable names, but in any case we don't want collisions. With short names, we can trivially avoid collisions by using them as-is. With long names, we are forced to use some kind of digest.

We could just always use the digest if you prefer.


I'll remove it right now then.


Ah, I forgot - I thought the fetching the jar path was in JarTask, but I'm thinking of PicardTask.


We never serialize these objects to json so omitempty has no effect.


TA-ism and legacy probably


No, staff hours are not the place to discuss policy concerns; they're there for people who need help with our services. BoD has indeed always the place for public comment on the state of the OCF. Besides, we can't expect each individual staff member to be able to justify the decisions of the entire board; would you even want to be stuck doing that when you have other things to do?


@unixmonkey That's indeed a typo. Will fix this. Good catch!


I think so (for write_byte() only).  I will test and see.


heheheh, nem te preocupa vei!


It updates the targets array above (ie: stores it). This is the array returned to the UI.


unused variable.


As an example, the following code would have taken 3 'step-in' actions to execute, one for each `__ = __` node.
```javascript
var a = 1,
    b = 2,
    c = 3;
```
Now we break once on the `var ...` node.


You're opening the contest twice: once on a new window through the link on line 10 (with target="_blank") and once in the current window through javascript. You're also overwriting whatever changes the user made and hasn't saved yet.


This is a valid check, but in our current implementation this should never happen.
How can this be ever triggered?


Do you have test fixtures to run against?


wrt PR #934


develop (mjwitte) - Win64-Windows-7-VisualStudio-12: OK (1529 of 1529 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)


I'm sorry, do I know you?
On Feb 10, 2016 2:13 PM, "armac" <notifications@github.com> wrote:

> Hello darkness, my old friend.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/optc/optc.github.io/commit/10ff355e3fc6af71030ea6c8bb2f8c1fe760a753#commitcomment-16014405>
> .
>


It looks like, with this commit, we no longer have any testing that we return a 403 in this case.  It seems like one of these test cases should stay around to cover that.


this is a callback, so content will always be empty, we have to use it in a callback style


Good Work Buddy! :+1:


Good question. rqrcode-rails3 does some useful integration we use [here](https://github.com/samvincent/rqrcode-rails3/blob/master/lib/rqrcode-rails3.rb), but it itself depends on rqrcode code for the heavy lifting.


If you place a PR without the change of facade referring, I will accept the contracts as parameters while we discuss this.


this function name doesn't describe accurately what it does.

make_context_callback? context_callback? Maybe preface with a _ as well.


I think this should be done but I'm not going to do it in this PR. I'm hoping that each subteam does this for their respective components since they have the most context on how config can be grouped into subobjects.


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


Tests are good but need to check existence of ACL as well and that the pref file is not empty and it is valid ttl [by Nicola]


Gr:8ball:t Idea


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


Nice


Ouch, right. `anotheriterator` stores its state, hm.


For speed (which is important), and because the current UART functionality does not create a termios that works properly when used in the way we are using the UART.  I suspect the cfmakeraw() calls do not quite setup the termios structure in the way required (maybe .c_lflag or .c_cc, not sure).  I did not do a field by field comparison of the default MRAA behavior though.


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


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


This was preventing me from loading this gem on Ruby 1.8.7.


I, uh. probably not. I just use this tool a lot. And I was quoting a song.
Sorry for the confusion.


it looks weird to have a newline between `loop` and these bindings


Deleted with extreme prejudice.


Will do.


Done.


Will investigate.


Once we have decided where exactly all that lives we should add unit test for that specific method (maybe you already have them).


Handle the "dir" parameter in the RSS feed.


AddWarningWhenDElightAndShading (mjwitte) - i386-Windows-7-VisualStudio-12: OK (2080 of 2080 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)


Hmm, what is the recommended way to represent non integer numeric types tghen? I suppose I'll change this to an int64.


assuming you care about the order in the list?
the same applies to blockModeList


sounds reasonable


:fappa:


ты в цикле каждый раз создаёшь новый сканнер. Зачем? не надо так ))


see https://github.com/fulcrumgenomics/dagr/issues/65


I think this would be a little cleaner if it was two separate sets instead of nesting them in a map, both here as well as in `loop` below.


okay


:clap:


nit: "\n block mode list: "
the same applies to purpose


ofc lol


lgtm


So the whole point of having a qualifiedOriginTable is so that when the relation is aliased, you still know its origin in the output?  (I haven't finished going through, but I don't see other cases where you have a relation alias that's different from the qualified origin table).  Also, if that's true then why don't we care about the original column name?


Ya, seems like a period, not a frequency. It's a duration on master so I would be inclined to leave it that way.

https://github.com/kubernetes/kubernetes/blob/master/cmd/kubelet/app/options/options.go#L182


You do have a good point. I'm not always good at explaining things though ;/ . I'll try and think of a good way to explain it.

As for the issue you brought up about wired potentially being >= 32, I figured that I should spend a bit more time before addressing that issue. To my understanding (based on reading the manual), just doing ```wired = g_Reg->WIRED_REGISTER & 31;``` should suffice. But I'm not entirely confident about that.


The format of your configuration is incorrect. `rabbitmq_hosts` expects a hash, see the template: https://github.com/roobert/sensu-puppet/blob/sensu_multi_rmq/templates/rabbitmq.conf.erb

Here's a (valid) example hiera config:

```
sensu::rabbitmq_hosts:
  - host: "sensu0.xxx.net"
    ssl: true
  - host: "sensu1.example.net"
    ssl: true
  - host: "sensu2.example.net"
    ssl: true
```


Should be fixed in most recent commit.


Solid!


When someone makes a pull request on one of your repo, you get a notification (look for the bell icon on the top right of github).
In this notification, there will be a link to the page of the pull request.
On the page of the pull request, there should be a “merge” or “pull” button or something. It'll probably be in green.


I'm going to remove all omitempty until we start serializing these to json


A simplification could have been to always use standardOffset.


To get the tests to pass, you will need to update your code with the latest .travis.yml. Thanks!


simple comment


а зачем у тебя count типа double? int вполне достаточно для счетчика


I'd prefer `x.y.z` over `x.y-z` (the latter seems to exist only in the R world), but it does not really matter.


Looks like that's the only reference for composer https://github.com/GlotPress/GlotPress-WP/blob/d0a12dc03549c12341549a29705cf986acf7ae78/tests/bin/run-unittests.sh#L42. I think it's safe to remove it.


зачем Double?


ok, that can go then.


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1291.4e65f3527174edb3a18c5ff0a141542dc404ac15](http://build.palaso.org/viewLog.html?buildId=69092&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 947, ignored: 12 Build time: 00:07:16


@hjmjohnson @reginakim :  Please review new parameters set for multimodal segmentation in Atlas definition file. I also changed one line in code about probability tissue thresholds for candidate regions. Moreover, a set of values are suggested for pure plugs threshold (0.1 for 1.5T MR data, and 0.2 for 3.0T MR data).


se regreso version


TeamCity Chorus :: chorus-precise64-chorus-2.5 Continuous [Build 2.5.1023.bab9ad24dc6ac370cd6b01ef876ee8b815ba2fe8](http://build.palaso.org/viewLog.html?buildId=69083&buildTypeId=ChorusPrecise64v25Cont) outcome was **SUCCESS**
Summary: Tests passed: 862, ignored: 54 Build time: 00:20:22


Note: together with https://github.com/plone/Products.CMFPlone/commit/9efcfe328e22bb678062db8e39291a1b05ddd839


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


Note: together with https://github.com/plone/plonetheme.barceloneta/commit/bf37168476797252602d14ef0a1ab98200d15cd7


I'll change it


consider deep copy?
this.blockMode = new ArrayList<BlockMode>(blockMode);


Hi Marek!

This is looking great. I noticed one small typo, could you change VC4_1K_SUB_TILE_SIZE_BYTES to VC4_1KB_SUB_TILE_SIZE_BYTES for consistency?

Thanks!

Regards,
Jeff


Oops, that was a typo. I'll change it


@afollestad have a look at this. Not sure if I'm too strict at my point.


Totally agree that in general duplicating is a bad thing-- we're discussing.  On CF docs side it would have to be more complicated than just saying skip the AWS setup steps.


If a hard cast is appropriate, and this is a static method, why isn't that just the type of the parameter?


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


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


A message to the same effect as the comment would be good.


Why did you remove the `-` from the end? It was "closing" the one in the beginning.


Aren and I were talking about this, and we decided two things:
1) This should never happen
2) If it does happen, the worst case scenario is popping a breaker, but the best case scenario is slightly diminished control, so shutting down the robot if it happens is kind of silly

This should never happen because there is no way currently to access the individual talons


This appears to be missing `items`


```java
 row = rowsToDelete.nextClearBit(row + 1);


If this part (or even, this entire file) really necessary? There is no `dlang-pegged` mode for emacs.


can probably get rid of the suspend/resume now


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


The setup is to check that `talon1.get() == talon2.get() == talon3.get()`, which should always be true but it;s good to check.


AddWarningWhenDElightAndShading (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (978 of 978 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-28.32%25-green.svg)


This is wrong. It should be:
String prefix = resource.getDefaultPath();


okay


add a UL


Who is writing that length? I don't see it here...


That's good. I like that much better...

Before we were tweaking the time (essentially adding 1 month + 1 hour) to make sure transformation with new timezone (PDT) ends up giving a LocalDate on the correct date.

Now, we do the opposite, we add exactly 1 month (so end up with same reference time) but we compute our TimeZone to be fixed and therefore also  giving up a LocalDate on the correct date.


On Wed, 10 Feb 2016, Markus Elfring wrote:

>
>       What part is not clear?
>
>  *  What is a "function file"?

There used to be a function called file.  This function has been renamed
files.

julia

>  *  Is an other wording more appropriate than "… has become files …"?
>
> —
> Reply to this email directly or view it on
> GitHub.[AAesmpg3Uuz9AuKfGAQHC2-LLC6eIelTks5pi3fYgaJpZM4HXW-y.gif]
>
>
>


This could be
```java
do {
...
}
while (row < inputRowCount);

return new OrcFileInfo(rowCount, uncompressedSize);


What's the usual rule there? Pegged is released under the MIT license, as that's the most common license for D sources. Is that the copyright for the debian package, or for the original source code?


If there is `ItemResponse` I think this should be named `ItemRequest`


I think I merged the pull request without this hunk -- I hadn't realized those were needed.  Can you submit a new PR for just updating these versions?  Since we're pinning all the versions here, it'd be best to just change the number to the new latest version rather than doing a `>=` -- that'll have more predictable results and handle the case where a future change to cffi breaks something.


113360729_HumidifierOASys (Nigusse) - x86_64-MacOS-10.9-clang: OK (2076 of 2076 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)


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


You ate a pipe. Nice! :+1:


Maybe the author information was lost or garbled while publishing? Your internet connection might have cut out for a tiny amount of time. I'm just guessing though ¯\_(ツ)_/¯


it fails on macosx 10.11.3 with

eschalot(566,0x700000081000) malloc: *** mach_vm_map(size=9223372036854779904) failed (error code=3)

different sizes of course

any idea?

Burgerwaanzin


I do not really know why or how does it happen, so Jacob is helping me
right now.

Kit

On Wed, Feb 10, 2016 at 1:52 PM, Tom Amlicke <notifications@github.com>
wrote:

> Hi Kit-
>
> We should be careful not to check in the .class and .jar files. These are
> typically created by the build process when source files are modified. We
> should setup a .gitignore file so that Git does not automatically check in
> these files.
>
> Regards-
> Tom
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mtmustski/FRC-Robotics-2016-Team-2262/commit/166aa5db50f12cc3e1afadfa0fdf2776930e2eeb#commitcomment-16013884>
> .
>


Nit: I would recommend using set literals here: `{'en'}`

In addition to the cleaner syntax, you save the compiler some work.  The old syntax causes python to build a list and then call the `set()` function on that list, and convert the data.  Set literals just build the set directly from the objects included in it.


This check isn't needed, since we verify that the file has enough rows in the caller


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


@PEMapModder We are genius and we know the values out of our head ;)
What else.

> @thebigsmileXD btw, regarding your question PocketMine/PocketMine-MP#3918: I have recently become an outside collaborator of PocketMine-MP. Also I edited the comments there to make the conversation line look more useful.

> I respect your freedom of speach

I see, weather you lied in your forums signature or you forgot that or you still hate us.


OK, но ты слегка переусложнил задачу. Тут не было никакого подвоха и по условию не требовалось найти все строки, у которых gc-content максимальный. Вероятность того, что у тебя при расчете в double будут одинаковые значения - очень мала. Т.е. смысл тут мог бы быть, если бы мы, например, ограничились только целыми процентами.
Ну и в принципе, замечание на будующее - никогда нельзя сравнивать числа типа double с помощью оператора ==, только целые числа. Иначе могут быть сюрпризы ))


If the object is called `ItemResponse` I think this should be named `ItemRequest` for consistency.


The `true` here, and on line 226, are not really obvious to me as a reader.  IIRC from above this was something about the direction of the message.

If the parameter can't be done away with for some reason; consider making there be two methods, MakeClientSignature, MakeServerSignature, which just pass the right boolean into the private backing method.


Added commit here to remove that reference, and another PR to remove composer from running the tests


В целом замечания по стилистике:
переменные с названием c[] - это ой
функция max(), которая считает maxLoss - это тоже ой
=)


great


Instead of EncryptOrDecrypt(true), how about Encrypt?


`CalculateBaseRequest` is also used in the response call, should calling it `Request` doesn't make sense. `CalculateBase` would be more appropriate.


:+1: this is my default, don't see why you would use something else


Done.


Looks good to me


Great Job, you guys rock!


seems like a fix to #2


Removed here:
https://github.com/brave/browser-laptop/commit/0c8fc087236bfcf242f1957b07f716e3439d8072


112331505_SurfaceHeightRange (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2112 of 2112 tests passed, 0 test warnings)

 * 6 tests had: AUD diffs.

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


Code looks good, but I'd like to better understand why this is useful.  Maybe we should ask in the call tomorrow.


Oh ok, fair enough, I just thought BoD was for staff only, but that makes a lot more sense. Thanks for clarifying.


for Wikitheoria project


we can make a note of improving the security i guess. Maybe an enhancement issue.


There's an `OperationUtils.cast()` function for this.  I've made the change in the following polishing commit.


Must debian packages have a manpage? This files (and the one related to it) do not really give any useful info. Users could be frustrated by trying them and finding them empty. Can we drop these files entirely?


this is a bit confusing as you only create a 1D kernel which can then be applied on each dimension of course. maybe we have to find a better naming here.


Done for this field. From a quick scan nothing else looked particularly problematic.


Так, ну допустим... Но это не все треугольнички ))


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


you can use the helper class `RAIs` to avoid warnings here.


You need to use a direct link to the image. The url should end with the name of the file extension.


This doesn't seem like a suitable exception


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


Fees are not a tax. But they will under this field. Should we call that something more appropriate?


hiiii


found!
its    "is >> std::ws" fail
remove both and anything ok


Done


There is an `amount` helper for formatting amounts of money


what happens with n-dimensional images here.


Other than the nit I mentioned, :+1:


ah yea - I've been struggling with that.. just trying to show what the
icons on PReP look like.. these are the screenshots I made

[image: Inline image 5][image: Inline image 4][image: Inline image 3][image:
Inline image 2][image: Inline image 1]

On Wed, Feb 10, 2016 at 2:42 PM, Volkan Unsal <notifications@github.com>
wrote:

> You need to use a direct link to the image. The url should end with the
> name of the file extension.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/citiesense/docs/commit/ada87f8df8e50f99a4caa9d5540b39a6508ede79#commitcomment-16015192>
> .
>

--
*Starling Childs   |   *www.starlingchilds.com


please only override whatever is required. a lot of these methods are already implemented in abstract class.


`RAI`s


javadoc is never wrong ;-)


this should be camel case `hsCode`


A nitpick, but can this be a separate function (`toActionValue()` or something like that) ?


Is it better to initialize to `{'en}` or to call `translation.add('en')`? I just realized that here, I've already initialized `translations` to an empty set.


:heart:


Removed some of these.


Why'd you revert it?


what about an image with an additional dimension?


Não é mais necessário adicionar o jar do alfresco client localmente


Yeah, I think there is a lot of incorrect usage of Frequency rather than period. I guess we can leave it for this first alpha API, and fix it when we clean this up.


avoid calling `ops()` in `compute`


FYI @simongoffin :
When you create a user with sidebar, it is not added
When you select a new favorite user, and check/uncheck, traceback
When you select/unselect a user, the calendar is not refresh with right filter


112331505_SurfaceHeightRange (Nigusse) - 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)


oooops ;-)


Class should utilize separate .h and .cpp files.


Please remove me from cc list. I am not the intended person.

Thanks,
Avijeet
On Feb 10, 2016 11:33 AM, "Paul Spinrad" <notifications@github.com> wrote:

> Revise per @agupta comments, possibly more TK [#85293086]
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/cloudfoundry/docs-deploying-cf/commit/01c34b7c6533164909f7a32e523dd5d3e19df8d5
>


UnitTest missing


@bqpd FYI


Why is that allowed to be null? Test purpose?


@eed3si9n there isn't some easier way here, is there?


what if i wanna read and write at the same time


add comparing unit test


We use this commit template:
https://github.com/pixelated/soledad/blob/develop/docs/leap-commit-template

Do you mind adding a `* Resolves: #7370` to the commit message?


Three rules for handling one component is a bit convoluted imho (specially when they only need to be applied on frontpage) but not as bad as making a new request to @@hero on every (front)page load.

Downside here would be editing `hero` contents, which would have to be done in index.html thus defeating the purpose of a CMS.


@jtoomim Was changing the author of the patch intentional?


Variables should be static so they can be accessed from static methods. They will need to be put in a .cpp file as well to actually exist. See CPFERotarySwitch.cpp for an example.

See: http://www.learncpp.com/cpp-tutorial/811-static-member-variables/


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.177.8515507208c1539220ebee854cf5e7e479e1de6d](http://build.palaso.org/viewLog.html?buildId=69087&buildTypeId=bt2) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 942, ignored: 50 Build time: 00:44:05
### Failed tests
```
LibChorus.Tests.dll: LibChorus.Tests.VcsDrivers.Mercurial.HgWrappingTests.RemoveOldLocks_WLockAndLockButNotRunningHg_BothLocksRemoved: <no details avaliable>

```


Nice work! We were intending to eventually do most of the secp256k1 math in 8x32 256-bit vector representation instead of field elements too but never got the time.

The Schnorr library can also be spend up a lot using field elements instead of big.Ints.


What is region?


This should be taken care of with an `Optional`.  I'll make the change in a following commit.


We also use the make_sun238 script, it's the sort that behaves differently.

Yes cubes would be tricky, but spectra shouldn't be.  I just though a generic
command name would keep our options open and be in keeping with the
rest of KAPPA.


Thanks. Not very elegant... But seems to be fast :smile:


This line and all below should be included in the class, perhaps in a method such as `static void update()`.


` see, WEATHER you lied in your forums signature or you forgot that or you still hate us.`
so. ok, weather he lied,
or actually he either lied


Looks good.


I can live with the current version.


itk_module -> vxl


Added *and return* to stop controller action and prevent double render.


I had to mark this test as incomplete as I wasn't 100% why it was failing. Can someone else look at this one please?

Basically $record was returning nothing which implies canCreate() wasn't performing as expected...


Is the encryption here a non-padded encryption?  Is message.Length always going to be (count - NtlmSignatureLength)?  If yes, can we assert that? If no, we should handle that.

I think this needs some more comments describing what things look like.  If I understand correctly:
```
{
    some optional stuff we've already processed (length=offset),
    NTLM Signature (length = NtlmSignatureLength),
    Encrypted Content (length = count - NtlmSignatureLength),
    maybe other stuff (length = buffer.Length - offset - count),
}
```
Meaning what we care about is
```
{
    NTLM Signature (length = NtlmSignatureLength),
    Encrypted Content (length = count - NtlmSignatureLength),
}
```
which we need to decrypt the encrypted content, making it
```
{
    NTLM Signature (length = NtlmSignatureLength),
    Plaintext Content (length = count - NtlmSignatureLength),
}
```

And then we're passing that whole segment of data to VerifySignature?


This is interesting for a short-term approach.

My current, long-term idea is to leave those tables as Lua upvalues in the `kong.lua` "main" file, responsible for the plugins event loop. The event loop would be updated to allow more granularity in the number of hooks proposed since Kong plugins need more granularity than OpenResty modules:

- ssl
- before balancing
- before auth (in access)
- before proxy (in access too)
- on headers
- on first body chunk (just some random ideas)
- on last body chunk
- etc..

The even loops would then execute those contexts for each plugin, and plugins would ultimately be built in a much more FP-oriented way (ditching out the current verbose, not-so-useful OOP pattern):

```lua
return {
  before_balancing = function(ngx, kong)
    -- just some random code:
    local api, err = kong.dao.apis:find()
    if err then
      return kong.exit(err) -- maybe some syntactic sugar
    end

    ngx.ctx = api -- this is not so FP, but we need to be able to mutate some state in ngx_lua

    -- maybe consider returning values to the event loop
  end,
  log = function(ngx, kong)
    -- in log_by_lua
  end
}
```

This approach would make the plugins much more unit-testable than the current ones, would allow for more granularity for developers, and one could imagine 2 plugins that are executed in the same hook could be triggered in any order, since the FP paradigm simply provides us with much more robust handlers.

---

Of course, on a short-term timeline, your approach has the benefit of cleaning the global namespace (and local accesses are much faster than global ones too). I would not be opposed to discuss it and include this in Kong if you want to submit it.


concate -> concatenate

And it seems I misread the other thing I've mentioned, so you can ignore it.


Can you explain more on why we need the setClusterVersionCallback? Is it necessary to have a different callback just for clusterVersion? I'm asking for what benefits this brings.


I didn't realise `utils` was available... thanks :)


How did you pick this delay? If you want 200Hz, you are assuming that all the other code takes 0ms, which is not going to be true.

For this reason, you should be using a timer and associated interrupts to call your sampling routines.


develop (mjwitte) - i386-Windows-7-VisualStudio-12: OK (1529 of 1529 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)


Aye, thank you for that. Sorry for the trouble


This produce a Warning "Unreachable code" if builded with VS2015


给锅子 pot 人（我是说 pottering）发个 bug 吧。


Looks like a pretty straight forward code to me (for a plugin code).


Do they need to be separate parameters if they can be out of sync?


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


Changes to survey-comparison.csv - did you check the change to % worked okay in Latex? You might need \% or \\%. Seems safer to me to keep as decimal, and make the % in knitr. But as long as it works okay.


Oops, looks like I accidentally left a call to a function that I was experimenting with but that was not required. I removed the call to updateEllipsis() and made a couple other improvements to the breadcrumb and navbar as a whole.


@Zteve Java doc doesn't appear to be correct.


For consistency with how you handle the `if not verify_assets` branch, I would say use `.add()`.


Initial commit


add `start` to fix #2 npm error: missing script "start"


Octree (DeadParrot) - x86_64-MacOS-10.9-clang: OK (2085 of 2085 tests passed, 3 test warnings)

 * 3 tests had: AUD diffs.
 * 2 tests had: EIO diffs.
 * 2 tests had: ESO small diffs.
 * 1 test had: SHD 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)


TeamCity Glyssen :: Glyssen-master Continuous [Build *.*.1292.fd2676eede719142db838e5717c60cf6b7effeca](http://build.palaso.org/viewLog.html?buildId=69099&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 961, ignored: 12 Build time: 00:06:12


Seems like non-standard indentation


`ItemResponse` should also have a `taxes` object, as salesTax, and duties are assessed at the item level.


Nope, it is for when caching is disabled (`NoCachingTenantBroadcastDao`, `NoCachingTenantDao`, etc.).


No... it's more what I didn't do: I didn't use `<butterfly-comments />` in my layout.html


Why are you eating all exceptions?


empd (nmerket) - i386-Windows-7-VisualStudio-12: OK (2076 of 2080 tests passed, 0 test warnings)

 * 550 tests had: AUD diffs.
 * 4 tests had: EIO diffs.
 * 4 tests had: ESO big diffs.
 * 2 tests had: RDD diffs.
 * 4 tests had: Table big diffs.
 * 3 tests had: MTR big diffs.
 * 1 test had: SSZ big diffs.
 * 1 test had: ZSZ big diffs.
 * 2 tests had: ZSZ small diffs.

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


@mathslinux if the formatter is xml formatter we need to call policy.to_xml(), not dump.. otherwise we get a different xml representation of the policy


what about the units type? i.e. Kg, L, etc?


Thx. Btw. I'll probably change IDecoder into ICoder. It should encode too.


Yay! That was the big thing in that commit. :smiley_cat:


Indentation


This should be a list of URL prefixes, not only a single one.....


I understand from this warning that if I use '.' characters but don't use any '_' characters I should be ok. Is this right? I am not using any '_' characters (although I do have some '.' characters), and I am getting this warning. I suggest that it should only be issued when *both* characters are found on a topic name, otherwise this warning will be issued is cases that are perfectly safe.


@bberenz can you review this approach please?  https://github.com/tresf/qz-print/commit/e13dd3bb8d9559341c18d58349275725103c7768

Note, this is on my personal branch and has not yet been committed.

I've looked and Node.js seems to support the [`setTimeout(...)`](https://nodejs.org/docs/v0.6.1/api/timers.html) method, so I don't think this will cause any portability problems.


remove


Rename this to be `price`


2045-draw-dual-ducts (kbenne) - Win64-Windows-7-VisualStudio-12: Build Failed

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


We should probably say a little bit more about how this works for people who have never used Go before. Do we have a BUILDING or INSTALL instructions somewhere?


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


We've been moving away from CamelCase variable names.


We might just want an exception here. This can still fail is someone does a find(list) involving a hasmany or belongstomany association.


Since this has the potential to be called from multiple goroutines, you're going to need a lock around `m.ldapConn` if multiple things can be using, comparing, or assigning to it.


Hmm, can we instead look at the expected fuzzy membership function(s) results?


This seems fishy. If iovec->iov_len == l, then context[i] can point to unitialized memory.


Overall great job on the hw. Good html structure. Keep up the good work.


There's a trade off for this, it makes the object declaration quite long.  Isn't there a way to make a jit-friendly method without making basic object declaration so ugly?

```haxe
var x = {y:null};
```
previous version:

```lua
	local x = _hx_anon("y", nil);
```

That's not perfect, but it's fairly short.

new version:
```lua
	local x = setmetatable({__fields__={y=true},y=nil},{__newindex=_hx_anon_newindex});
```


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


That just sounds a bit weird :-) Why not say: The math is a bit involved, but not really difficult...


# "working"


It looks like this branch is not hit anymore when `is_multicolumn is False`. See #6111.


I just started a new account and tested the building queue. It works for me.

What's not functioning for you?


May I port these changes back into the main repo? It certainly looks useful to have this option and since the main repo is actively maintained, it makes sense to get this in there rather than having to maintain your own fork.


Consider the use of a class instead of an id in this case.


Consider the use of padding/margin to create space between elements.


Overall good job on the hw. Please view the comments for best practices. Keep up the good work.


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


applications do you use if I may know please i want it


It might be nice here to explain that we have to wait for the lease to expire because doorman_shell does not do refreshes. Maybe we should implement a refresh command in the shell?


Some minor comments, but overall a very good piece of work! I love the idea of the doorman_shell. I can't do the tutorial right now, will wait for it to be committed and will then execute it.


Consider the use of a class instead of an id in this case. An ID can possibly override all class styling.


Should've clarified. The controls for the second goat are W,A,D (jump, left, right). I changed the debug key to 'F' to avoid the conflict.


True, it is. sorry, i didn't read it closely enough the first time - its been a long day.


It actually worked perfectly, and I was shocked


I see that a NUL byte is added below and not included in length l. So the code is OK, but maybe a comment is in order.


no need to define the height on elements generally. because the idea is to `let the content grow the parent`. `aside` element being the parent in this case.

Stephen


nice on the usage of classes instead of ids :+1:


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


I see your point but I'd claim its "risk" is _only_ as much as that of calling an OS API without reading its document or that of using an OS shipped with incorrect API documents :grin:


LGTM


Nice!

FYI for the c++ code we can use clazy to do a similar automatic port.


thanks to @ahmedbodi for this contrib :facepunch:


why not just declare the metatable here?  Why do we need to run an init function to initialize it?


Overall good job on the hw. A few things to keep note: classes should be applied more repeatedly for styling as ID are meant for special circumstances. With that in mind, you should consider selecting elements in css through the use of classes rather than tags. This can help you avoid nested selectors.


`n_iovec == 0` would be better, suggesting it can be < 0 is misleading.


thanks, that will probably prevent some collisions.  I believe we should also guard against using these terms as variable names in the code... haven't gotten to that yet.


No worries. I am just fixing minor things as i learn the code. ;)


Right. It's often hard to keep track of what the spec is talking about exactly (e. g. this comes from [RSA5](http://docs.ably.io/client-lib-development-guide/features/#RSA5)), hence my suggestion to refer to the IDL line, or univocally referring to a IDL field, as often as possible.

I'm guessing then that other fields in `TokenParams` that are included in `ClientOptions` or `AuthOptions` should be only in `TokenParams`, then. `clientId` and `capability` are in `ClientOptions` also. Should those be removed?


TeamCity FubuMVC Swank :: Deploy [Build 2.0.44.0](http://build.mikeobrien.net/viewLog.html?buildId=2497&buildTypeId=fubumvcswank&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:40


is there a way we can use a serialization tool that doesn't require creating invalid objects?


Great work, as always!


Fixed at 8b46f1039711de0b30dc5990e0e7b080cec523f9.


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


:bow:


This should be upshift.button, not upshift.port


noob


TeamCity FubuMVC Swank :: Deploy [Build 2.0.45.0](http://build.mikeobrien.net/viewLog.html?buildId=2498&buildTypeId=fubumvcswank&guest=1) outcome was **FAILURE**
Summary: Exit code 8 (new) Build time: 00:00:44


For example, in json libraries I've seen, there's a type adapter registry or a way to annotate a serialization constructor. Beyond worries about implicitly creating bad objects, these types of ctors smell of reflection.


Since we decided against using the Dream, we should just delete the classsubsystem and any methods or commands for it. I'll make a trello card.


Do you think it would be a good idea to store the returned `Task` from `IObservationPublisher.Publish`, and expose an API to let the consumer wait for all remaining publishes to complete before say an exit event?


We don't now. Before this commit, the argument was mandatory. All the tests have been fixed by regexp replaces, so some of them could use less arguments.

If you're asking why this is done _at all_, optionally or not, I was also quite appalled to find this is what you do in Objective-C. But yes, you're supposed to pass a NSError ** to whatever might be failing, so that way you tell the method if you're interested (by passing a valid pointer) or not (by passing nil) in the possible error, saving an unnecessary allocation if you aren't.


Nope. One should just use mat64.Row. This breaks the rules about Method vs. Function.


No, not really, it's just the way it was before. All paginated result callbacks are like this. The spec leaves this unspecified, so I didn't change it.


I think this is the wrong way to fix this. The code should not have used a `switch` statement in the first place in my opinion.


Whoops... nice catch - thanks for the PR :D


Framework looks good to me. including comments others have made.


## Task 1

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly demonstrates the use of **chained conditionals** to accomplish a task (2 pt)

## Task 2

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to sum 0 to 1000 [inclusive] (2 pt)

## Task 3

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to compute `e` (2 pt)

## Task 4

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the `input()` function (2 pts)

## Task 5

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the "argparse" module (2 pts)


Ok, makes sense. But then why does the RowColer interface exist? I guess I'm missing something.


task1:
program is correctly formatted, contains main and ifmain statement and chained conditional has been used.

task2:
correctly formatted, includes main and ifmain statement and program corectly uses recursion to sum 0 to 1000.

task3:
correctly formatted, includes main and ifmain statement and program corectly uses recursion to compute e value

task4:
correctly formatted, includes main and ifmain statement and program corectly accepts and uses the input value for maximum of range to compute e value.

task5:
correctly formatted, includes main and ifmain statement and program corectly accepts and uses the input value for maximum of range to compute e value using argparse module.


TeamCity FubuMVC Swank :: Deploy [Build 2.0.46.0](http://build.mikeobrien.net/viewLog.html?buildId=2499&buildTypeId=fubumvcswank&guest=1) outcome was **FAILURE**
Summary: Tests failed: 6 (6 new), passed: 393 Build time: 00:01:00
### Failed tests
```
Tests.dll: Tests: Tests.AcceptanceTests.should_have_connectivity_to_the_test_harness_site: <no details avaliable>

Tests.dll: Tests: Tests.AcceptanceTests.should_return_js_content: <no details avaliable>

Tests.dll: Tests: Tests.AcceptanceTests.should_return_specification_page: <no details avaliable>

Tests.dll: Tests: Tests.AcceptanceTests.should_return_specification_spec: <no details avaliable>

Tests.dll: Tests: Tests.AcceptanceTests.should_return_style_content: <no details avaliable>

Tests.dll: Tests: Specification: ActionSourceTests: Tests.Specification.ActionSourceTests.Tests.should_only_enumerate_actions_in_the_specified_assemblies: <no details avaliable>

```


possibly.  Though we're already foreaching over the collectoin.  So it didn't bother me to just handle this case in the foreach.  I'm not sure i like having code that both queries and foreaches over code.  Seems fishy to me.


Historical reasons. Dense used to have these methods. It should have been deleted but was not.


Does this set the coredump rlimit to infinity for all processes, or just the system ones?


This needs to be 'bool bret' ?


@brthor, this is the issue as why I wasn't getting all the references! I had a similar fix and backed out after sync.


Is this racy, or are we guaranteed that c->stop() won't return until the destroy hook is done?

(If racy, we could check whether c has the lxc.ephemeral config_item set to 1; if not racy, great :)


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


shouldn't this be `"lint": "eslint .",`


Storing the result of comparison in a local leads to less than ideal code generation
```
       4881F9FFFFFF7F       cmp      rcx, 0x7FFFFFFF
       410F96C0             setbe    r8b
       450FB6C0             movzx    r8, r8b
       4585C0               test     r8d, r8d
       741F                 je       SHORT G_M62539_IG06
```
instead of
```
       4881F9FFFFFF7F       cmp      rcx, 0x7FFFFFFF
       741F                 jnbe     SHORT G_M62539_IG06
```
Normally storing in a local like this adds some clarity due to the local name but in this case this seems unnecessary, requires(count < int.MaxValue) looks clear enough IMO.


My original call is on line 9:
```r
common(., query = "key1:value1 and _exists_:key2",
    field = c("key1", "key2"))
```
assume . here is an index.

The comment is that I think it'd be nice to allow query strings in the `query` arg of `common()` like `query = "key1:value1 and _exists_:key2"` in addition to the dsl. Would you tend to stick that in `Search(q=`?


So, can it be deleted now?


5452-controllerWaterCoil-IP-units (MatthewSteen) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1511 of 1511 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-70.71%25-green.svg)


Okay.


Misspelling.


I would've kept convention of plural in variable name: mParams


Hi USGS,
I apologize, but I made a small typo in my commit above. Line 19 should use the "month" function from the lubridate package instead of the "months" function. Thanks!

Best,
Doug


Since the input is unsigned it seems to me that the result should also be unsigned (`UIntPtr`) as well. That said, this would require the use of `div.un` and currently that generates slower code for non power of 2 divisors.


5429_ConstructionInternalSource (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2093 of 2094 tests passed, 0 test warnings)

 * 6 tests had: AUD diffs.
 * 1 test had: EIO diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: MTR big diffs.
 * 1 test had: ZSZ big diffs.
 * 1 test had: Table big diffs.

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


Just prior to this block, we have `if not self.force_interval` - it's hard to read.  Let's either make this if-else or come up with a new flow for this function.


We'll move it soon...


First update


MSDN only states that a function will return a non-zero value on success, not specifically a 1. That many functions do return 1 for non-zero is an implementation detail that shouldn't be relied on.


Just me stalking your recent activity.


Shouldn't need the cast to `G_OBJECT` here


@d42f @nervgh @atobies

Thanks for a plunker! I had no time for describing my situation, but this one seems to be the same.


Done. There's a todo on the top of the properties, but you made your comments on the commit itself, so this display wont' show you the change. You have to look at it in the pull request view to see the full change (from all the commits)


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


test


Noe clue. It was in jung-io.


It was in jung-io.  I'll see if it can build without this and woodstox.


JavaDoc ?


JavaDoc?


5429_ConstructionInternalSource (mitchute) - 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)


commit message wrong - translation of the brief to a basic structure from which we can all begin work


Turns out this commit broke void values, which are normally represented as "null", and need to be recognized for unions to work.

Fixed in 10e269d298189236881d038413950b0302610e9a.


Thank you!


This does not seem to be used anymore


Ah, OK. Hmmm, well, I think it's still wrong and will fail to parse as json, because the rollover data isn't prepended correctly. (It shouldn't be prepended as a list item before the first item, but it should be prepended onto the first list item itself.)

It doesn't crash, though, 'cos that's inside a "try" (it just silently fails to notice it).

I've managed to find how to force a rollover now (by setting a cloudvar to 100000 digits -always rolls over in that case), so I've found something that actually works correctly...

Here's the edited code (note that self._rollover becomes a string rather than a list):

````python
...
      self._rollover = ''  # CHANGED
...
  def check_updates(self, timeout, maxCount=10):
... # code is the same up to...
      if data[0]==123:  # starts with left brace, so don't prepend rollover
        self._rollover = ''  # CHANGED
      data = data.decode('utf-8').split('\n')  # split up multiple updates
# REMOVE LINE      data = self._rollover + data.decode('utf-8').split('\n')  # split up multiple updates
      if self._rollover:  # NEW
        data[0] = (self._rollover.encode('utf-8')+data[0].encode('utf-8')).decode('utf-8')  # NEW
      if data[-1]:  # last line was incomplete, so roll it over...
        print('Warning: last line of data incomplete?! ',data[-1].encode('utf-8'))  # FYI for now...
        self._rollover = data[-1]  # put it into rollover for next receive
      else:
        self._rollover = ''
...  # code is the same from here...
````

That does catch the 100000 digit cloudvar update for me, so I think it's working correctly.


This does not seem to be used


Ok - colt is not needed, woodstox seems needed at test-time.  I don't konw if that means it should be there at run-time, or if it's an artifact of how the test is using JUNG.


Yeah, `ERR_LOG()`'s interface is awkward.  I would want to remove that `errorbuf` argument altogether and simply put an `ERR_BUF_SIZE`-length buffer on the stack inside `ERR_LOG()`.  But that means modifying everyone that uses `ERR_LOG()`, which then involves removing error buffers, which could lead to a mess.  I guess I could leave the `errorbuf` argument there, but if it's `NULL` use a buffer from the stack.


> increasing the parse time

Parse time? I tought you are about readability here. Parsers are very fast, I hadn`t seen any regression on this.


well.. are you sure?
If the property is actually named

         controls/flight/elevator-trim

and you change the output to

       <output>controls/flight/elevator</output>

By removing the trim, only in the filter, then you will create chaos in the autopilot behavior.
the name of the property itself is less relevant than it being in accordance on all the source code :dart:


well I was joking so..... Goodjob??


Notably:  testInvalidGraphFactory() failed with an exception at test time (no build dependency).  I don't know if this implies that it should be a run-time dep or not (as in, if downstream callers should transitively be given woodstox in order to make JUNG behave as intended).

```
Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.044 sec <<< FAILURE!
testInvalidGraphFactory(edu.uci.ics.jung.io.graphml.TestGraphMLReader2)  Time elapsed: 0.006 sec  <<< ERROR!
java.lang.Exception: Unexpected exception, expected<edu.uci.ics.jung.io.GraphIOException> but was<java.lang.IllegalArgumentException>
	at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:110)
	at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79)
	at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87)
	at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
	at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
	at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
	at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
	at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
	at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
	at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
	at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.IllegalArgumentException: Graph objects connect 1 or 2 vertices; vertices arg has 3
	at edu.uci.ics.jung.graph.AbstractGraph.addEdge(AbstractGraph.java:50)
	at edu.uci.ics.jung.graph.AbstractGraph.addEdge(AbstractGraph.java:33)
	at edu.uci.ics.jung.io.graphml.parser.GraphElementParser.addHyperEdgesToGraph(GraphElementParser.java:250)
	at edu.uci.ics.jung.io.graphml.parser.GraphElementParser.parse(GraphElementParser.java:179)
	at edu.uci.ics.jung.io.graphml.parser.GraphElementParser.parse(GraphElementParser.java:40)
	at edu.uci.ics.jung.io.graphml.GraphMLReader2.readGraph(GraphMLReader2.java:267)
	at edu.uci.ics.jung.io.graphml.TestGraphMLReader2.readGraph(TestGraphMLReader2.java:431)
	at edu.uci.ics.jung.io.graphml.TestGraphMLReader2.testInvalidGraphFactory(TestGraphMLReader2.java:211)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59)
	at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98)
	... 22 more
```


let's make it olive oil


`Array.prototype` is nil here, so _hx_tabArray_mt.__index == nil. I am thinking about filling this field after Haxe Array class declaration.


Shaded is maven language for "bundling up all he dependencies and relocating them in an uber-jar".  It's maven build lore.


全てわかった。


ここは違う。


_hx_ prefix is standardised and guarded in next Haxe release. We should always use it, and no need to write own guards.


so question:
1) Why do we create the box here? Should someone not buy one first?
Even if we give something to someone, we should not create boxes for other people unless they actually bought one.
2) We should not have 1 function to give stuff into the deposit of other people and then another one that creates boxes and gives stuff at the same time. I would prefer to have a function that ONLY creates empty boxes and then another (this here?) to put stuff into it for code clarity.


Nice catch. Fixing


You could just use `GLib.idle_add(GLib.PRIORITY_DEFAULT, Lang.bind(this, this._updateOverview)))`
But I'm curious as to why that's really needed. What kind of error do you get? Maybe a better idea would be to still connect to the `shellwm` signal instead of having `ShellApp` emit `windows-changed` when a window is minimized?


_分かった。_


per example, examining the source code with

          grep trim * -r  #search all references to trim in the source

I found many other places in the code, where, as expected the correct name for the property is

      controls/flight/elevator-trim

as oppose to

       controls/flight/elevator

Result was

`DC-10-30ER.xml: <control-input axis="/controls/flight/aileron-trim" control="FLAP1" split="true" />
DC-10-30ER.xml: <control-input axis="/controls/flight/aileron-outer-trim" control="FLAP1" split="true" />
DC-10-30ER.xml: <control-input axis="/controls/flight/elevator-trim" control="FLAP0" />
DC-10-30ER.xml: <control-input axis="/controls/flight/rudder-trim" control="FLAP0" invert="true" />
DC-10-30.xml:   <control-input axis="/controls/flight/aileron-trim" control="FLAP1" split="true" />
DC-10-30.xml:   <control-input axis="/controls/flight/aileron-outer-trim" control="FLAP1" split="true" />
DC-10-30.xml:   <control-input axis="/controls/flight/elevator-trim" control="FLAP0" />
DC-10-30.xml:   <control-input axis="/controls/flight/rudder-trim" control="FLAP0" invert="true" />
Models/DC-10-hstab.xml:         <name>Elevator trim</name>
Models/DC-10-hstab.xml:         <property>controls/flight/elevator-trim</property>
Models/Flightdeck/DC-10-flightdeck.xml: <!-- Elevator trim -->
Models/Flightdeck/DC-10-flightdeck.xml:                         <property>controls/flight/elevator-trim</property>
Models/Flightdeck/DC-10-flightdeck.xml:                         <property>controls/flight/elevator-trim</property>
Models/Flightdeck/DC-10-flightdeck.xml:         <property>controls/flight/elevator-trim</property>
Systems/DC-10-flight-controls.xml:      <name>Outboard aileron trim locker</name>
Systems/DC-10-flight-controls.xml:      <output>controls/flight/aileron-outer-trim</output>
Systems/DC-10-flight-controls.xml:      <name>Outboard aileron trim driver</name>
Systems/DC-10-flight-controls.xml:          <property>controls/flight/aileron-trim</property>
Systems/DC-10-flight-controls.xml:      <output>controls/flight/aileron-outer-trim</output>
Systems/DC-10-flight-controls.xml:    <!-- Elevator trim -->
Systems/DC-10-flight-controls.xml:      <name>Autopilot elevator trim controller</name>
Systems/DC-10-flight-controls.xml:      <output>controls/flight/elevator-trim</output>
`


ok will add it here and commit.


# 本当は分からなかった。


I think I'd rather leave it if we have `0` if there are none, just saves us another check later for the `exists/update` checks.


I was about to as what you were doing here. [I see why now](https://bugreports.qt.io/browse/QTBUG-50001). Could you add a comment to make it clear that this is just a temporary workaround for that bug? I would do it myself but I don't think this justifies a PR :wink:


_全体的に分かった。_


IIRC this logic is meant to trigger an animation of the desktop icons opacity/saturation while the very last visible window is minimized, so that when the minimize animation completes, the overview snaps in immediately, without another animation. We should keep that behavior after the refactor


Bigold Project


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


Thus, I suggest to revert this commit, instead of attempting an unnecesary property renaming.


ここはどうか？


Unfortunately this is a change in public API contract that can break existing code that doesn't check for null ReturnType.


In Haxe code any variable either local or class field, so globals can not be overrided. The risky case is when `local type = ...` happens, and `type` used in the same scope, but we do not use `type` anywhere in code. But opposite for `setmetatable`, `_G.metatable` should be used when in local functions scopes.


I wouldn't mark these ```@Component``` cause that will cause them to be picked up by class scanning. Instead I would say they should be created within ```@Configuration``` classes and wired in that way.


지나가다가.. 결재선은 아마 사용자테이블이랑 관계를 맺는거 보다는 히스토리로 남겨두는게 유리할 수 있어요.
이유는.. 결재당시의 사용자 직위, 부서 정보가 중요한거라 관계를 맺는 경우 요런문제가 있을수 있습니다 뿅


Well, at least it makes it explicit that it seems as if the author has thought about the other states, even if we don't actually do anything about it. You might be right (it's a minor thing), and I am not sure which default case Morgan was talking about or what to do that would make sense here.


@rrgayhart How can I get my code to show up on the page for the actual app AND have my tests pass? If I put `module.exports = Ball`, my tests pass but nothing shows up in the browser.


do you even know what you're doing? in the last 10 days you've "fixed" nothing but remove code... So it doesn't clear players inventory anymore, let them all bring their battle weapons to the hub lmao


## Task 1

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly demonstrates the use of **chained conditionals** to accomplish a task (2 pt)

## Task 2

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to sum 0 to 1000 [inclusive] (2 pt)

## Task 3

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly uses recursion to compute `e` (2 pt)

## Task 4

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the `input()` function (2 pts)

## Task 5

- [ ] Program is correctly formatted with shebang, description, code (0.5 pt)
- [ ] Program includes `main()` function and "ifmain" statement (0.5 pt)
- [ ] Program correctly accepts (and uses) the user input value for the maximum of the range over which to compute `e` using the "argparse" module (2 pts)


Why are you creating a whole other interface/class for this instead of just using a Map which it looks like you're trying to do anyway judging by the API's


Updated it and added Bohr paper to my github


task1:
program is correctly formatted, contains main and ifmain statement and chained conditional has been used. main function is working without using print, I learned new thing.

task2:
correctly formatted, includes main and ifmain statement and program corectly uses recursion to sum 0 to 1000.

task3:
correctly formatted, includes main and ifmain statement and program corectly uses recursion to compute e value, but value of e is printing 1.718 which is mathematically incorrect (correct value is 2.718). I gave point because function is working.

task4:
correctly formatted, includes main and ifmain statement and program corectly accepts and uses the input value for maximum of range to compute e value.

task5:
correctly formatted, includes main and ifmain statement and program corectly accepts and uses the input value for maximum of range to compute e value using argparse module.


Lol. I promise to pull before pushing. I promise to pull before pushing. I...


why did you disable?  isn't `Time.zone.now` what rubocop desires?


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


So ist es gut. Danke Dir!


@robrich  Thanks for PR!!!


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


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


Rename to `amount` ?


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


add file `server.js` to fix #2 npm error: missing script "start"


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


I actually had started that way, but IIRC it triggered some changes in the tests. This seems like the closest to the current  behavior.


ACK.


Testing something for someone else.......


Kérjük szépen a hiányzókat is!


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


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


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


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


TeamCity Open-source Libraries :: BlogMonster :: CI [Build 2.0.47.0](http://build01:8888/viewLog.html?buildId=14184&buildTypeId=BlogMonster_CI) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 12 Build time: 00:00:15
### Failed tests
```
BlogMonster.Tests.dll: BlogMonster.Tests.WhenImportingPostsFromAnInstagramFeed.ThereShouldBeAtLeastOnePost: <no details avaliable>

```


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


k


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


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


Why did you wait to call `authorize! :read, @participant`?  I would have put it on line 23.


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


hey I'm not convinced CorrectionBasedBear helps here, wouldn't it be simpler to jhust add the params?


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


Much better already. Perhaps just remove the templates property alltogether. It's cached, so won't matter much anyways, performance wise. But only if you think that's a good idea too.


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


AppendableUtil should be changed to an enum with no instances.  The name changes are not desirable as they change the API.


I don't get this, needs a better description IMO


It wasn't until recently - I exposed it as part of the IE89 PR because IE8 lacks a ton of builtins, so it was either that or copy most of utils.js into shared_helpers, which seemed silly


Because I don't intend to write tests for this, and it works as is.


paran -> paren I think


1. I want a custom ('hand'-crafted) homepage.

I can think of designs where you would like to have 3 templates (index.html, post.html and pages.html) but that is currently not what I need right now :D


Do you have the position of the segfault or a stacktrace or anything else for this?


If you wanna quote like this use %r


this doesn't need to user timers, in-fact i think it makes it less obvious.


not fully sure thouhg


Makes sense. I'll do that.


unack anyways


`Building with Jack: /home/demian/Temasek/out/target/common/obj/JAVA_LIBRARIES/android-support-design-eclair-mr1_intermediates/classes.jack
target Package: ManagedProvisioning (/home/demian/Temasek/out/target/product/n7100/obj/APPS/ManagedProvisioning_intermediates/package.apk)
Building with Jack: /home/demian/Temasek/out/target/common/obj/JAVA_LIBRARIES/android-support-v14-preference_intermediates/classes.jack
Building with Jack: /home/demian/Temasek/out/target/common/obj/APPS/Settings_intermediates/with-local/classes.dex
Launching background server java -Dfile.encoding=UTF-8 -Xms2560m -XX:+TieredCompilation -jar /home/demian/Temasek/out/host/linux-x86/framework/jack-launcher.jar -cp /home/demian/Temasek/out/host/linux-x86/framework/jack.jar com.android.jack.server.JackSimpleServer
Launching background server java -Dfile.encoding=UTF-8 -Xms2560m -XX:+TieredCompilation -jar /home/demian/Temasek/out/host/linux-x86/framework/jack-launcher.jar -cp /home/demian/Temasek/out/host/linux-x86/framework/jack.jar com.android.jack.server.JackSimpleServer
Launching background server java -Dfile.encoding=UTF-8 -Xms2560m -XX:+TieredCompilation -jar /home/demian/Temasek/out/host/linux-x86/framework/jack-launcher.jar -cp /home/demian/Temasek/out/host/linux-x86/framework/jack.jar com.android.jack.server.JackSimpleServer
target Package: Shell (/home/demian/Temasek/out/target/product/n7100/obj/APPS/Shell_intermediates/package.apk)
Copying: /home/demian/Temasek/out/target/common/obj/APPS/SystemUI_intermediates/classes.dex
Copying: /home/demian/Temasek/out/target/common/obj/APPS/ThemeChooser_intermediates/classes.dex
ERROR: /home/demian/Temasek/packages/apps/Settings/src/com/android/settings/temasek/NotificationColorSettings.java:87: The method setDefaultColors(int, int) is undefined for the type ColorPickerPreference
ERROR: /home/demian/Temasek/packages/apps/Settings/src/com/android/settings/temasek/NotificationColorSettings.java:96: ic_action_reset cannot be resolved or is not a field
Building with Jack: /home/demian/Temasek/out/target/common/obj/APPS/Trebuchet_intermediates/with-local/classes.dex
Copying: /home/demian/Temasek/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.dex
make: *** [/home/demian/Temasek/out/target/common/obj/APPS/Settings_intermediates/with-local/classes.dex] Error 41
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/demian/Temasek'

#### make failed to build some targets (13:59 (mm:ss)) ####

trafalgar-square@codingcode ~/Temasek $
`


This causes a `ZeroDivisionError` when the `x` values are equal to each other.  This wasn't caught before since my branch had a very low probability of having an exact straight line, something which I want to fix. I suppose you also didn't have a test case for it.

This can probably be fixed by checking whether the `x` values are equal and setting `a` to zero in that case.


I went for the silly option :)


I think we can safely move lines 48-51 one block down. Up to you whether you want to do this.


this hostname seems weird.


This needs to be broken out into a `requestApplicationEnvironment` `private` method.  Remember that we're trying to keep a clear identifier about what would need to be mocked.


why?


are each of these sets internally wrapped  in a run-loop? I don't remember


deferred is not a promise


Thanks for clarifying. This change is integrated.


Итак: за идею и её реализацию - хвалю. Очень хорошо, мне понравилось.
Минус тут только за сам алгоритм - он имеет квадратическую сложность, а мы говорили, что это не хорошо. Т.е. на небольших наборах данных оно будет не заметно, но если массив будет большой - он будет считать очень медленно. Если будет вермя, подумай, как его можно переделать, не используя цикл-в-цикле.


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


Okay, that makes sense. I'll make a new line item to address this.


Is this an update to our current DutyRates API?

What about the API that lets you pass in a list of HS COdes and obtain the units type?


We're done here. Thanks!


looks good on first sight


This seems to be mixing up Conversions and Constraints.


Good find! I'll fix this in a minute and also try to add a test case for it.


StandardCharsets.UTF_8 or ISO_8859_1 would be preferable via a static import to make the sure the code isn't much more complicated.


The following doc(s) have been deployed to the [drupaldrus](http://drupaldrus-static-docs.pantheon.io/docs) Multidev environment:
- [docs/articles/local/drupal-drush-command-line-utility](http://drupaldrus-static-docs.pantheon.io/docs/articles/local/drupal-drush-command-line-utility)
- [source/docs/assets/images/desk_images/169655.png](https://github.com/pantheon-systems/documentation/commit/80bb4fb0bc1d2514a70de34aa6beac6885367e55/source/docs/assets/images/desk_images/169655.png)
- [source/docs/assets/images/drush-aliases.png](https://github.com/pantheon-systems/documentation/commit/80bb4fb0bc1d2514a70de34aa6beac6885367e55/source/docs/assets/images/drush-aliases.png)


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


I like this  error handling. I'm going to get rid of my "default" "fall-back" OFP_HOME and use this instead. I'll probably squash this into another commit.

Also, I think we could use pattern rules for generating `ocaf-foo.f90` operating on prefixes.  I'm going to refresh my gmake-fu and examine the feasibility of this approach.


coala and setup.py have to assert python version before imports
StringProcessing has a comment saying "dont change import order" - if i do, all tests fail


Ok, I've left these two internal functions, but they will now use the underlying mraa_uart*() functionality so the duplicate checks are no longer needed.

Also, I am not sure what you meant by "_in any case shouldn't it get a better name to match the rest of the internal functions_"


TeamCity ReOpenLDAP :: devel [Build 233](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=1814&buildTypeId=ReOpenLDAP_Devel&guest=1) outcome was **SUCCESS**
Summary: Tests passed Build time: 01:47:12


Not sure this is an improvement.


oh crap.. sigh ... hit the wrong flag :-(


It has always been like this. I think that it reads it in as text, so it
works. But, probably not the most robust.

On Wed, Feb 10, 2016 at 11:54 AM, andrew-edwards <notifications@github.com>
wrote:

> Changes to survey-comparison.csv - did you check the change to % worked
> okay in Latex? You might need \% or \%. Seems safer to me to keep as
> decimal, and make the % in knitr. But as long as it works okay.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/allanhicks/hake-assessment/commit/3d0031ea2411df4abe637a351943cf2bf58d266e#commitcomment-16015559>
> .
>


alright can you just add `# Ignore PyImportSortBear` comments above the lines?


I'll fix


The idea was to cache in `templates()` only, not in the other properties, that's why I kept it. We could make `templates()` a private `_templates()` method.


Do we have a sensor or something on the robot to get degrees from?


Why not change it to correctionbear ? Its a bear and it does correction,
has a single message for all corrections.

On Thu, Feb 11, 2016 at 1:34 AM, Lasse Schuirmann <notifications@github.com>
wrote:

> unack anyways
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coala-analyzer/coala/commit/8cb4d1b03ff87ea23342e24f139bc9d33dd3c499#commitcomment-16015816>
> .
>