This isn't going to work perfectly either. In the event of an error, it will notify the `destination` of the error, then continue one happily to return the `result`, which is `undefined`. `undefined` will then coerce to `false` which will trigger `notifyComplete(false)`... fortunately, at that point, the `destination` is already `isUnsubscribed` because of the previous call to it's `error` method.

What really needs to be done is:

1. Set `thisArg` in the _constructor_ with `this.thisArg = thisArg || this;`
2. Then:

```js
_next(value) {
  let result;
  try {
    this.predicate.call(this.thisArg, value, this.index++, this.source);
  } catch (err) {
    this.destination.error(err);
    return;
  }
  if (!result) {
    this.notifyComplete(false);
  }
}
```

You could try breaking that last `!result` assertion out into it's own function, but I'm unsure how much difference that will make.


Edit 2: Need to make push changes also in hotplug tab :)


I see, looks good for other parts!


Again, looking at the code for `bufio.Flush()`, any error that this call returns is "remembered" and will always be returned.
Regarding moving to next server, etc... is then processOpErr() that you have in mind?


I posted the fix for this issue to the linux-tegra mailing list; see:
http://patchwork.ozlabs.org/patch/577651/


@acoffman sorry, I didn't explain well. My problem is that I want to POST the `params


This is great!


If you pay attention to the crashes, most of them weren't flat crashes, they were custom crash messages I added specifically to detect bugs. One of those even detected an old bug in TI's learnset validator, which we fixed without TI making excuses about how long ago it's been.

See, there's a pretty big difference between what I did, which was to intentionally add crashes to help fix bugs (and immediately fix them), and what you did, which is accidentally write code that crashes (and not bother to fix them for half a year).

In other words, yes, our code were both buggy. The difference is, your code was very buggy and you didn't fix the bugs; my code was slightly buggy and I was a lot more proactive about finding and fixing those bugs.


Whoa. great!

MOZPROFILE

I wasn't even considering mozprofile because i recall it puts the output into some randomized /tmp/xdkjdkajasdf;asdasdas/path and it just seemed simpler to handle js files directly but....
 the fact that we can munge a bunch of files in a one-liner is reason enough to employ it instead.

PREFS - 3 FILE TYPES

this makes a lot of sense
[1]. global prefs - I couldn't think of a good name: _utils/prefs/global.json: perfect!
perhaps we could use the convention of:
global defaults
global env defaults??
[2]. (product) defaults prefs - I  like that each product would have a 'defaults' file
[3]. (product) environment prefs - 1 file per env / product
I think with that you cover all the bases.
In addition, covering the penguins file might be useful for cold environments, linux-related stuff, etc.

I prefer INI format for mozprofile input because if all our config files are 1 type, easier on the brain. but that's just me.

TEMP FILES

/temp, definitely could add an rm statement, however, if mozprofile does, in fact, dump things to a tmp dir, we could just leave the temp files there and let them get garbage-collected. probem-solved.

Awesome, Peter.  let's toss what i have and re-create an example with mozprofile.  thank you!


@kevinvangelder FYI: That extra exclamation point on the front turned it into a broken image. I'm assuming you just wanted it to be a link?


Thanks!


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


@torkelo @keis here is some feedback from my testing:

I added two singlestat panels and configured those as gauges, with the "Read IOPS" fetching metrics from
influxdb series "fio.read_kiops.gauge" and the "Write IOPS" singlestat fetching from "fio.write_kiops_gauge".  See below.  With 2 singlestats being displayed, for some reason the write stats are being shown on the read gauge and read gauge isn't showing any stats.  This may need looking into.  Let me know if you need help reproducing this.

![image](https://cloud.githubusercontent.com/assets/1857386/12769164/aeda4382-c9d2-11e5-9f18-6875562e1745.png)

![image](https://cloud.githubusercontent.com/assets/1857386/12769177/d77b097a-c9d2-11e5-93f8-e29a8ca96496.png)

![image](https://cloud.githubusercontent.com/assets/1857386/12769182/ea6f2a2a-c9d2-11e5-9699-d168d987b3a4.png)


@jeffbcross I think it served it's purpose. One of the problems was that the patch file output didn't always match 1-to-1 with the other implementations. It also forced strange file names in some cases.


Sweet! Great coverage.


Please wrap those lines too.


`request.protocol` also has the trailing `://`. Not much difference, but I'll just stick with this.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14267](https://teamcity.mesosphere.io/viewLog.html?buildId=122095&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 220 Build time: 00:02:37
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14270](https://teamcity.mesosphere.io/viewLog.html?buildId=122103&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 219 Build time: 00:02:30
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


n.b. EdgeHTML 14 in the title is a typo - these are In Dev starting in the EdgeHTML 13 milestone (now)


Could you do a PR ?


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


@edolstra Did you mean to invert the meaning of this one?


gettext would be most proper, but we've already started translating the text in those .jade files.  If we do have capacity to get started with translations now, but not to do the gettext ... then let it be, let the translations be in the .jade files - that's my opinion.  I suppose we will be doing quite a lot of localization work in those files anyway, translation is just a small part of it.

Translations can be done directly in the master branch, and they can be edited directly in github I suppose - but of course the most proper approach is to do a fork and a pull request.

I think we've decided that translating URLs was a mistake :-)


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


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


Thank you very much for your patch(es). Please address the inline comments. It would also be better to be consistent with the backticking, I think using a single backtick everywhere would be appropriate (instead of sometimes one, sometimes three).


Great!


I see some instructions for running the localization client against the codebase [here](https://github.com/fieldpapers/fp-web/blob/master/README.md#translation-and-localization) but it's not clear how to author strings-to-be-localized...?


awesome! Thank you very much!!!


This was fixed in https://github.com/docker-library/rabbitmq/commit/90918b05b23b85014454c24782518ccfd9fc4c68, and pushed with https://github.com/docker-library/official-images/pull/1390.  So you should be able to `docker pull` a fixed image.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14268](https://teamcity.mesosphere.io/viewLog.html?buildId=122096&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 219 Build time: 00:07:05
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


You know, a few days ago when I first started working on the validator, I even said "Hi, I'm not trying to insult you or anything, it's just my habit to comment on code that turns out to have caused a bug because I want to learn from my mistakes" when making my comments. And you still reacted badly to that.

I've done it to TI a whole bunch of times and it's never been a problem. I've done it to a lot of other programmers and they often thank me for teaching them. It's like a retroactive code review, the code review I would have done earlier but couldn't because either I didn't review it closely enough or they pushed it directly or something else.


Wrap them in `_()`. That'll be used as the default message. The `rake` task will extract them and put them in the strings file, suitable for pushing to Transifex.


Might add a comment about what stats and diff_type are and what the values can be.


@gkellogg I'll take a look.


Why'd mz get removed? It's still being used.


So I'm going to play the repo owner card now. When I fix bugs, I use `git blame` to find out what caused it, because if it's me, I want to learn from my mistakes, and if it's someone else, I comment because I want them to learn from their mistakes.

If you don't want to know when code you wrote caused a bug, you should GTFO my project. Thanks.


After thinking about it, I think we should let the readLoop detect the failure. I think having `nc.err` here set only if the flush() fails was ok.


Even maybe, if flush fails, and `nc.err` is not already set, then set it.


@weppos Is there a specific reason for going go ruby 2.3.0? A few things break with this change, such as bundler. Also rbenv only has a dev package for 2.3.0 currently.


> This isn't going to work perfectly either. In the event of an error, it will notify the destination of the error, then continue on happily to return the result, which is undefined.

I think it returns `false`. Not `undefined`. Or am I missing something?

> which will trigger notifyComplete(false)... fortunately, at that point, the destination is already isUnsubscribed because of the previous call to it's error method.

Yep. I was thinking it would be ok to call `notifyComplete()` once `destination.error()` was already called and it would not trigger `complete()`.


Reverted this particular change. See my comments on the commit for why.


Here is our second deliverable:
[DELIVERABLE 2.pdf](https://github.com/yemointer/COEN-6312-Project-Group/files/114904/DELIVERABLE.2.pdf)


\o/ :tada:


shouldn't this be a failure since your testing an unauthenticated user?


and everything else in this block


Yeah, I changed it when Colin questioned it. I misread the code without trying it out.


I think you mean "authorized user" or "signed in user" here


Good thinking on the params validation. For additional helpfulness, consider returning the specific problematic param, such as "'Width is missing or incorrect."


We wanted to be able to use zzuf as a crash detector only. Our use case is that the fuzzing is happening prior to invoking zzuf, so we just want zzuf to run the command line and report whether a crash occurred.


@skeptical I've now gone through the code every place the ```DLNAMediaAudio``` constructor is called. The only place I've found that doesn't set the sampling frequency is DVDISOTitle - and that class seems to have been ignored for a long time anyway (I've seen a lot of exceptions thrown from it and frequent support issues from people trying to use it).

From what I can understand, the source of this "log spam" must be jumpy? Instead of implementing some function to keep track of if the media has been parsed or not, isn't it better that jumpy just applies default when this is unknown?

As stated above, we need this information as we're obligated to send it to the renderers.


Would you add a test case for this?


@torkelo @keis here is some feedback from my testing:

I added two singlestat panels and configured those as gauges, with the "Read IOPS" fetching metrics from
influxdb series "fio.read_kiops.gauge" and the "Write IOPS" singlestat fetching from "fio.write_kiops_gauge".  See below.  With 2 singlestats being displayed, for some reason the write stats are being shown on the read gauge and read gauge isn't showing any stats.  This may need looking into.  Let me know if you need help reproducing this.

When in edit mode, the read singlestat shows correct value, but not on the dashboard ..

![image](https://cloud.githubusercontent.com/assets/1857386/12769164/aeda4382-c9d2-11e5-9f18-6875562e1745.png)

![image](https://cloud.githubusercontent.com/assets/1857386/12769177/d77b097a-c9d2-11e5-93f8-e29a8ca96496.png)

![image](https://cloud.githubusercontent.com/assets/1857386/12769182/ea6f2a2a-c9d2-11e5-9699-d168d987b3a4.png)

Apparently the first singlestat gauge panel keeps displaying the metric configured for the last one added .. :)

![image](https://cloud.githubusercontent.com/assets/1857386/12769480/8d4bc6a2-c9d5-11e5-82c7-6121fdf658c4.png)


I generally break controller actions into separate describe blocks.. ie `describe '#index'` and `describe '#show'`


:+1:  Thanks  i did not even seen that error. Anyway thanks man..


@dhleong This branch *does* support tag selection (`vat`, `vit`, etc.) thanks to #100. Could you please enable changing tags here an add some tests as well?


purpose of the override ?  ` - sudo pip install --upgrade docker-compose==1.3.3`


same question regarding the override?


Some programs are picky about file extensions, and opmode copy wasn't preserving the extension when it copied the file. So this change implements file extension preservation.


Why do you call it an excuse? You ask about a specific line, I'm telling you that I do not remember about it specifically because it's been long. It's not an excuse, that is called objectively explaining that I do not remember. I'm not hiding anything nor excusing myself: I just do not remember about the specific reason of this line on this commit.

My code didn't crash ever. In any case, in the course of time it's been demonstrated that the changes didn't fix the issue it intended to fix or it didn't behave as it was intended to. But it didn't actually crash. I mean, to say it didn't fix the issue is both true and adequate, to blatantly lie for some reason I can't understand is not right. Unless by "crash" as in "crash the server and send an e-mail about it" you mean "not working as expected". If that's the case, please do excuse me and let me recommend you to use a better wording that is less prone to confusion.

"Very" is a subjective term. In fact, the whole latter part of your paragraph just sounds like a bile vomit (pardon me the expression if it sounds excessive), as if you were paying with me some bad day, but I am going to think I'm just understanding it as that wrongly, and going ahead to response properly and with education: in this specific case, the command worked as expected in the moment it was implemented, as experienced by the users (well, that is what it seemed in the moment). In the unrelated case to this commit of changes for gen 1 and gen 2 team validator, which I'm assuming here (and I may be wrong!) you are referring to, there have been bugs introduced by some changes made by me, trying to fix other bugs. Yes, so what? Specific bugs were solved, people were happy about that, new bugs were uncovered time later. Other validation bugs, for instance for gen 5 egg moves combinations, were there for literally years, despite the so called proactivity. I don't think it has been a big deal, otherwise it would have been dealt with swiftly, as with other countless isues, right?

Continuing with your next comments, I'm merely answering, not reacting "badly" or anything. I don't even know what do you expect me to reply or want me to reply so it fits your expectations, I merely don't see the point on commenting on a very specific line from a commit a year old that is not even relevant nowadays. And, sincerely, I do not care what you do or you don't to TI, it is not relevant to me and it is not relevant to this commit either. I don't understand why do you insist on comparing a comment on this commit to other comment you may have made prior to other commit. Care to explain to me what is the point of that as well?

And, as for your last comment, quite aggressive and attacking (are you alright?), I am going to have to ask: what bug has been introduced by the introduction of this new command one year ago? What do I have to learn today from this commit I made a year ago? If you mean something else, why are you commenting it here? Where do I have explicitly denied the causing of a bug by accident?


No problem


Again, it would be interesting to see which params specifically have issues. I can't remember if ActiveShipping returns this feedback with any specificity, but if they do, then you could also bubble Active Shipping's error up to the user.


You dont test the response of index


ok perfect, thanks.


тут кодируем


既存のコードから改善が大きくないのであれば、既存通りで良いかと思います。

ただ、「Protectなメンバーに触っているため、Pylintチェック時にワーニング出た」は、
そこまで気にしなくても...とだけおもいました。
それを気にするとしたら、if分岐が多すぎるワーニングを潰す方が良いかと...


I'll change as you suggested. Besides the correctness, it may have some performance gains moving the `||` to the constructor and not calling `notifyComplete` when it isn't necessary.


Kudos on going with USPS as a carrier - I recall that service being particularly challenging to work with.


тут сравнимаем декодированный.
ты хотели закодирова или раскодировать?
для разных методов  - разные юнит-тесты!
да, куча якобы однообразного кода, но в этом вся соль.


ok sounds good.


actually this breaks theme-color computation; will fix in next commit


this one is great.  You might also want to test
1. that it is an Array `expect(response_hash['comments']).to be_an(Array)`
2. that the response is the post you requested


Don't forget to test that the index returns an array of posts


So prroffessionnall

<img src="http://vignette1.wikia.nocookie.net/joke-battles/images/4/40/18360-doge-doge-simple.jpg/revision/latest?cb=20151209161638" alt="doge" />


nice use of factories!


@dhleong You can use `parseKeys("<Esc>")` here to make it more compact.


Which I already pushed in case you missed it ;-)


TeamCity pull requests :: netty [Build 1185](https://garage.netty.io/teamcity/viewLog.html?buildId=5352&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 6397, ignored: 23 Build time: 00:44:36


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


@dhleong I believe this import is unused. Could you please remove it?


much scale
<img src="https://lh3.googleusercontent.com/E6EO3XO6zP7NtBq2L9SDF1DbBoYamUWc8QTRvOFuQg_Gka2Vw_RIv-AjU5Ysu4XgwHU=w170" alt="doge again" />


It was a bad version of checking ability1. I think the intent was the same. It was to check if the Pokemon has an additional ability, by checking if the ability was released after the gen of the event.


Makes sense to me


Oh! Accidental commit!


Clears up some errors I made while copy + pasting, looks good.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14274](https://teamcity.mesosphere.io/viewLog.html?buildId=122120&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 220 Build time: 00:02:28
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14275](https://teamcity.mesosphere.io/viewLog.html?buildId=122125&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1 (1 new), passed: 0, ignored: 219 Build time: 00:02:36
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


TestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTestTest


ok!


Teacher Emails and Faculties are both links to webpages on MHS Links, so that's why I put them in the same section. You could probably remove the faculties page altogether: as far as I know, not many people are using it.


>My code didn't crash ever.

http://d.pr/i/19dHw/5NrfCykO

We got these emails once a month or so for like half a year.

No, we're no longer talking about just this commit, because you're no longer talking about just this commit; _you_ brought up my recent commits that crashed.


test


It's working great on LP. Have a look at my initramfs changes for alucard when you have time.  (You probably got the other message anyway) There were some things that needed to be changed :)


Nit: This condition is bit convoluted.  You may want split as following:

//Current scope is a parameter scope
bool isEnclosedInParamScope = (this->m_currentScope->GetScopeType() == ScopeType_Parameter);

//Or Enclosed scope is parameter scope in case of function expr
if (this->m_currentScope->GetScopeType() == ScopeType_FuncExpr && this->m_currentScope->GetEnclosingScope() && this->m_currentScope->GetEnclosingScope()->GetScopeType() == ScopeType_Parameter)
{
  isEnclosedInParamScope = true;
}


Isn't "which vagrant" simpler?

Honestly, I've never used "type".


Kinda makes sense, good enough for me :D


why?


Cosmetic change: can you clean up the headers? It seems only `cstring` is used. Also remove the added new line.


Please add a comment on the reasoning.


Why?


LoadComponentRefactor (amirroth) - x86_64-MacOS-10.9-clang: OK (2051 of 2051 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)


畫面遷移時，除了第一個contorlller外，其他的controller每次都會做新的（沒有特別處理的話）。所以viewLoad會每次被呼叫。比較好的解決方法是按照MVC（Model View Controller）的概念，資料不要放在viewController，而是放在一個Singleton的model裡集中管理。


If I recall correctly, I did correct that bug myself. That crash was not part of this commit. You may take a quote out of context, but that does not erase the fact that crash was from a specific context in a specific commit that happened on a very, very specific and unexpected setting and it was fixed anyway (by me, I think?).

And we are not talking about this commit since I asked the point about talking about a year old commit. I also never got a reply to that question.

Once again: what is your point?


done.


Treehouse challenge - js basics


*cough* Log


It's one of those terribly common but terribly bad habits that people have.

> which(1) is an external program used to search PATH for an executable. It behaves differently on different systems and you can't rely on a useful exit code


*cough* commented out code


This is confusing. Should be in its own method, with a description on top explaining what it does/how it works.


不過這設計的概念一開始比較難理解，所以替代方案是把資料放在第一個controller，然後遷移時將資料傳給下個controller。


具體的方法有空再再寫。


The docker image hosted on docker hub is called `seegno/bitcoind` so I wouldn't mind keeping this as-is.


For the tables you should use a CSS class rather than an ID.  Because a CSS ID should only apply to one element.  I assume we want to have the option for multiple tables.


On re-reading this, the first half of the sentence seems a little unnecessary. Maybe it's sufficient to simply point out that the committed offset should be the offset of the next message the consumer will consume.


Changed instances to `seegno/bitcoind`.


Is this a particular magic number?


Same question.


J'ai regardé test commit et il me semble bon.


There are some redundant `getcastledata` command usages in this `treasure_TE` NPC.


awesomeeeee :+1:  thank you


Edit 3: Final solution has been pushed already. I've tested everything and it works well.


`.@guild_id = getcastledata(.@map$,1);`


а если передадут рейтинг `-1`? а если `"wtf"`?


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


可以參考 https://developer.apple.com/library/prerelease/ios/documentation/UIKit/Reference/UIStoryboardSegue_Class/index.html。
從destinationViewController取得下個controller的參照。


а этот тест срабатывает? я в коде не вижу, почему бы


а, потому что ты его сравниваешь с 10... Ну это скорее побочный эффект, но ок, согласен, можно и так :)


@rpappalax By default it seems that mozprofile just creates profiles in random directories. For example, this gem:
```sh
/var/folders/qc/g_f0szh95k1fzph34rhmf5jw0000gp/T/tmphQDnAQ.mozrunner/user.js
```

But it seems that by passing a `--profile=rpapa` flag, it will create a "./rpapa/" directory in the current folder and create the following two files:
- ./rpapa/prefs.js
- ./rpapa/user.js

I guess the secret would be to check and see if we can launch a Firefox instance with a relative/absolute file profile path. Then probably best to use `--profile=%(FF_PROFILE_DIR)s/{random_string}` and let our nightly refresh job just remove that folder entirely. That doesn't take into account the profiles.ini file, if we need to somehow manage an entry in there or not.


if u don't like passing `context`, you could just throw an error made by this: https://www.npmjs.com/package/http-errors


Perhaps instead of <h2>'s an <p>'s for different sections nest unordered lists.


Très bonne idée d'utiliser reselect!


If `(require 'subr-x)` is missing then `string-remove-prefix` and `string-remove-suffix` are undefined functions.


What does this "live console" feature do?


I changed it to make the teacher emails link larger, and I grouped the faculty page with the others as that is a link to things like connect and portal. Apparently (speaking to people) lot of people still use it, I could embed a tracking image on an external site to measure the usage.

Peter

> On 3 Feb 2016, at 12:01 PM, Michael <notifications@github.com> wrote:
>
> Teacher Emails and Faculties are both links to webpages on MHS Links, so that's why I put them in the same section. You could probably remove the faculties page altogether: as far as I know, not many people are using it.
>
> —
> Reply to this email directly or view it on GitHub.
>


>```
            foreach (NetworkInterface nic in Interfaces)
            {
                if (nic.GetIPProperties().GetIPv4Properties() != null)
                    list.Add(nic);
            }
            return list;
```

if there exists a machine has not an ipv4 address, will `First()` throw a `NullReferenceException` ?


Can you break this condition into multiple lines? Something like an if\else combo. This is not readable.


This should have already been squareArr


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


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


This also loads the plugins before the siad loading screen is done. Just as an fyi if that wasn't intended, it makes for a funky text overlap at the very least:
![sia-ui_008](https://cloud.githubusercontent.com/assets/4606838/12770040/f862b1d0-ca57-11e5-9cb4-51fb11c06b9b.png)


@Nadahar it's more robust if we don't intentionally leave in gaps/pitfalls for subclasses, but complete the circle ourselves.  Plugins can override/workaround as needed (and suffer the consequences of any bad choices they may make). Plus this isn't simply a jumpy issue, we farm out url-resolving to any plugin that's willing to do the job for us, so we shouldn't make unnecessary requirements that may or may not be satisfiable, depending on the context.


LGTM


定下来了？


try it, I cannot explain. go to gameserver.ini and change liveConsole to 1 (in the console section) and start the server


Make your own world!


There are two typographic errors here:
"every constructs" → "every construct"
"Those constructs supports" → "Those constructs support"

I also wonder if fusionning  the first two sentences would not be better: in the original sentence the enumeration was quite long so splitting the sentences made sense, but this is not true anymore. Similarly, without the enumeration
the "those constructs" feels quite undefined; maybe "This infix syntax" would be more straightforward after fusioning
the first two sentences? I am also not too fond of "Every construct" compared to "any construct" or "all constructs";
it feels too positively defined, but this is up to personal taste.


thx


111411352_ATDeprecateFields (Nigusse) - i386-Windows-7-VisualStudio-12: OK (2061 of 2061 tests passed, 0 test warnings)

 * 549 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)


Line 613 / 675 are correct. string values


I too prefer INI over JSON for this. I think having a shared `_shared/prefs/global.ini` with our basic product-non-specific settings is good, plus maybe just a `autopush/e2e-test/prefs/prefs.ini` with the shared+inherited configs in a single place.


Yep, it was to be "icewm" :(


<%= @order_items.each do |order_item| %> 多了= ，使用 <% @order_items.each do |order_item| %> 就好


Returns `true` if [s] is neither null nor the empty string.


Why did you eliminate this?


One small nit, other than that, lgtm.


so whats the status?


I'm not sure what's going on here. You didn't edit from the most current file in in-progress, so there are merge conflicts. You also created a second branch, and this is where the pull request exists. NOT in in-progress.


Nice, thanks


Done


good work, man.

INI it is!  i like the --profile=mydir, but I'm thinkin that storing the profiles in a randomized dir feels somewhat dirty.  might also be problematic for troubleshooting stuff.  i'm sure if we play with this, we'll figure out how best to use that temp dir more as a cache, but then (if need be), copy the output prefs.js file to the desired profile_path


On a snowy day, like today, I'd want to stay home and play! Make snow angels, build a snowman, have a bonfire and play in the snow.


Oh, nice! I'll get right on it


If we have two methods that do the same thing, I think we should just remove this one and use the "getYaw" version.


Odd, these were already in our tree; they must have gotten lost somehow.


@DougGregor Is this supposed to be `~InObjCSelectorExprRAII() ...` ?


Okay


Can UIProp be removed? It doesn't seem to exist anymore.


I started with this (to mimick the isEmpty), but I think current version is accurate and somewhat easier to read - it returns true only if passed a string that is not empty.

You version would read, that the method return true if I pass it an number, empty list, or whatever else, right?


I heard Linux kernel will randomly kill process if the memory is not enough. https://plumbr.eu/blog/memory-leaks/out-of-memory-kill-process-or-sacrifice-child


@skeptical You seem to miss the point - this isn't some trap we make for plugins, it's information we must have to deliver the content correctly. The only thing it's floating on at the moment is that most of the content probably happens to match the default, but as the default is user configurable this is highly random. The warnings are legitimate as this WILL lead to problems unless the default happens to match that of the content.

There is no other consequence than that it is logged, and when the content later fails to play I'd say it's a good thing that there was some kind of a warning. If we're going to stand any chance of following the DLNA standard better (and need less hacks and tricks to get things working in each and every case) we have to have basic information like this. A plugin's job can't just be to get the media, it must get the necessary information as well.


lose this space


Autorun


all goooood!


I'm going to leave this as "it" could also be read as referring to the resource fetch algorithm.


When reading the description and example, it is not clear to me what happens to
`let[@foo] x= 1 and y =2`? Is the attribute duplicated on each binding? Or does it apply only to
the first binding `x`?


Hmmmm I'm not getting a 404.

Could this have something to do with how the wayback machine works?

https://web.archive.org/web/20150917030556/http://zoerooney.com/learn-web-fonts/


,Autorunwizard


Haha, apparently, it did!


Loop? Why would someone want a loop?


You can monitor GC by print out the GC log. If there are a lot of full GC frequently, it is a problem. You should increase your Heap size. What is the GC method GH using now?


Hmmm thanks this fixes that annoying toast

And bhavik here too?!!


HTML5 uses the term "stop playback" (actually "stopping playback" due to the context), so I suggest we follow that.


Why is this needed? Since this is a library project that references net451 and dotnet5.6 I think it is not necessary here.


It took me over an hour to debug one of my packages today before I found the change in the capitalization.  I had to change my code to fix the case.
````
StatusChk <- http_status(GET(APIString))
if(StatusChk$category %>% stringr::str_to_lower() =="client error"){
````
Now I am completely immune from future changes/reversion to the case.
I'm sure that the intended and cleaner usage (from some of my newer code) is:
````
h <- httr::HEAD(target)
 if(h$status_code!=200){
````
but I was dealing with an old piece of code that was from my early R days.  An undocumented change like this just to pretty up the response seems unnecessary.

Sorry about whining about a great package that I use 100 times a week.


rename this flag `loadTpchData`


The reason for throws on `err` is that `err` is only set when the exec system call failed, not that the command failed, and so continuing with testing is pointless. If you _are_ going to change these I'd ask that you change all of them though.


s/Clinet/Client/


here too


Elsewhere (in this file) we're still using `is` and it seems to me that if we should be consistent at least within a particular test.


better do a search/replace :)


TeamCity pull requests :: netty [Build 1186](https://garage.netty.io/teamcity/viewLog.html?buildId=5353&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 6412, ignored: 23 Build time: 00:43:23


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


Looks good


same comments as previous test apply here


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


alrighty.


I will do it, but you can do it if you find some np :p


YOU SHALL BE IMPRESSED!!


There may or may not be a subtle race condition here. I can't really tell.


I just got back xD


did you do it?


Hey why can't I install ws normally ffs


@devincoughlin, @slavapestov, possibly of interest.


Other than the `mz` dep issue I think this looks great. One other thing i'd add (or you can add if you want) is a pre commit hook that runs the linter.

Thanks @martinheidegger for your work.


Some consistency comments apply.


I am trying to install it without having to run the installws everytime but I get this:

C:\WINDOWS\system32>npm install ws
C:\WINDOWS\system32
└── ws@1.0.1

npm WARN ENOENT ENOENT: no such file or directory, open 'C:\WINDOWS\system32\package.json'
npm WARN EPACKAGEJSON system32 No description
npm WARN EPACKAGEJSON system32 No repository field.
npm WARN EPACKAGEJSON system32 No README data
npm WARN EPACKAGEJSON system32 No license field.

C:\WINDOWS\system32>


you have to cd to the directory


How about a .travis.yml?


nit: I think we tend to leave single package import statements still on multi lines with (). I saw another instance, too.


how do I do that? xPP


I want to be a programmer,software developer,I wanna learn coding kindly put me through.


Indeed, Thanks for catching that.

IIRC, 24.3 (which we support) doesn't include subr-x.
@bbatsov guess you'll have to use other functions.


`cd [yourdirectorypathtosrc]` example: `cd ~/users/example/desktop/Ogar-unlimited/src`


nit, extra blank line...


@martinheidegger I'd hold off on travis integration for now. The lib still needs unit tests anyway.


I use Windows


This looks much cleaner.

FYI.

```res.status(400).send(err);```

Should be:

```res.status(400).send(err.message);```

I think the the previous example will work but err is an object, not a string.


Travis would run the standard tests on every PR ;)


it is universal


and now with have no comments left at all, when the idea was to preserve the ones with @license or @preserve. Not sure why suddenly this option went berzerk :(


bye now though


It doesn't seem to do anything, the console isn't anything different..


maybe revert these import changes, since you don't even modify the files otherwise?


No promises to anyone following along about the *rest* of the things necessary for binary frameworks not tied to an OS. (There are a lot.)


Добавил индикатор прокрутки сбоку, если размер окошка меньше, чем кол-во элементов.
Добавил саму прокрутку элементов.
Добавил проверку на "влезание" в экран.
Осталось доделать цвет и работу с осью X.
Вроде всё...


Ahh, was wondering on the use. Yeah it kinda showed everything.

could potentially use a concat task to put the license in.


@jkgrain yes @nathangoulding was right -- there are several commits that are fixing it in dev version. Since I am using my own fork I just cherry-picked them for now. You need these:
* [update to use status_code](https://github.com/rstats-db/bigrquery/commit/9e1b0b3d900812934249047834ec70f0f2823e87)
* [import status_code](https://github.com/rstats-db/bigrquery/commit/8dd1e7800a6444186eb09a7af81b33dacbcb6eaa)
* [use status_code consistently](https://github.com/rstats-db/bigrquery/commit/d3b30eac2bac11a22a90e28c807c75e8f3c924ca)


Show me your console


It is done. but I have to use $scope in the controller.


(If you dont know how,  right click and click mark, press enter and paste here)


it's regular, it has only the starting things ( and yes I know how to do that, I taught you remember ^-^ )


what about that one, once the URL is correct : (http://melonjs.github.io/melonJS/docs/me.pool.html)[http://melonjs.github.io/melonJS/docs/me.pool.html]


True enough, might as well.
If you want to add the .travis.yml to this PR I'll setup travis and get this merged.


C:\Users\\Downloads\Ogar-unlimited-master\Ogar-unlimited-master\src>node index.js
                                        _ _       _              _
                                       | (_)     (_)_           | |
  ___   ____  ____  ____    _   _ ____ | |_ ____  _| |_  ____ _ | |
 / _ \ / _  |/ _  |/ ___)  | | | |  _ \| | |    \| |  _)/ _  ) || |
| |_| ( ( | ( ( | | |      | |_| | | | | | | | | | | |_( (/ ( (_| |
 \___/ \_|| |\_||_|_|       \____|_| |_|_|_|_|_|_|_|\___)____)____|
      (_____|
[Game] Ogar Unlimited - An open source Agar.io server implementation
[Game] By The AJS development team
[Game] Loaded stats server on port 88
[Game] Listening on port 443
[Game] Current game mode is Free For All
[Autopause] The Game Was Paused to save memory. Join the game to resume!
>[Autopause] Game Resumed!

Here you go if you insist


[http://melonjs.github.io/docs/me.pool.html] (http://melonjs.github.io/docs/me.pool.html) should be automatically redirected to [http://melonjs.github.io/melonJS/docs/me.pool.html] (http://melonjs.github.io/melonJS/docs/me.pool.html),


Sounds reasonable. No reason to want the other really.


In that case, that sounds fine to me!


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14280](https://teamcity.mesosphere.io/viewLog.html?buildId=122152&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 219 Build time: 00:02:32
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Updated the PR


Also you can use require as `require('./parser/product);` rather than `require('./parser/product.js');`

I think the code would be cleaner if you created instances of the parsing function.

You can look at how encycle is structured to see an example of this.

I would expect that each route would look something like this.

```
var max = 20;
var productParser = new ProductParser(max);
var reviewParser = new ReviewParser(max);

app.get('/reviews/:id', function(req, res) {
   var offset = req.query.offset ? req.query.offset >= 1 ? parseInt(req.query.offset) : 1 : 1;
   var limit = req.query.limit ? parseInt(req.query.limit) : maxLimit;

   productParser.getReviews(req.params.id, offset, lastPage)
   .then(function(reviews, count){
    res.send({ pagination: {fromPage: offset, toPage: lastPage, lastPage: count}, reviews: reviews });
   })
   .catch(function(err){
    res.status(400).send(err.message);
   })
});
```

Both classes can require the validator method you've written or you can write a base class and extend it.


The first link gives you a 404 because we don't have a file in this repo named `me.pool.html`. But if we did, it could use a common javascript to replace `/docs` with `/melonJS/docs`.


Can we have the butler get this?  The other correction algorithms have their data passed in, but there is a readIsrData method to get all the necessary ISR data.


@coyote240: We'll probably need to reinstate this to provide a CSRF-protected form for the alarms delete operation.  Sorry I didn't catch this earlier.


https://github.com/CyanogenMod/android_device_samsung_qcom-common/blob/cm-12.1/BoardConfigCommon.mk#L21-L24

already there ???????????????????????????????


看了下描述 貌似cost弃置的是红色牌  我之前写错了，汗。
另外 triggerable这里的检测可以更详尽点？  用candiscard之外，
从减少询问的角度讲，若空城+装备区仅有黑色牌，也可以不触发。


If you want live console, change the value in gameserver.ini to 1


ignore this change , I used these lines to the local server running on my machine.


AHHHHHHHHHH that was a hell of an update


@coyote240: We'll probably need to reinstate this to provide a CSRF protection for the alarms delete operation.  Sorry I didn't catch this earlier.


@coyote240: We'll probably need to reinstate this to provide a CSRF protection for the alarms delete operation. Sorry I didn't catch this earlier.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14281](https://teamcity.mesosphere.io/viewLog.html?buildId=122168&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 219 Build time: 00:07:44
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


OK no conflict


[View.php](https://github.com/OXID-eSales/oxideshop_ce/blob/b-dev-ce/source/Core/View.php#L556)

```php
            // page parameters is the part which goes after '?'
            $aParams = explode('?', $sNewAction);

            // action parameters is the part before '?'
            $sPageParams = isset($aParams[1]) ? $aParams[1] : null;
```

Thanks!


When many messages are awaiting for reply iterating over the whole list is going to be quite expensive


If you added namespace `smart_objects`, why did you leave smart_objects here?


Just dropped you an email @dkulyk


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 14352](https://teamcity.mesosphere.io/viewLog.html?buildId=122506&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 0, ignored: 219 Build time: 00:02:29
### Failed tests
```
null: Kubernetes e2e suite.Kubectl client Guestbook application should create and stop a working application [Conformance]: <no details avaliable>

```


Thanks for the mention <3


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 143](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=741&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:38:53


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 240](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=742&buildTypeId=XbimEssentials_XbimEssentials) is now running


Maybe these numbers should be replaced by the constants in StringSupport?


@kgbvax naja was in den letzten Commits rund um die extra Seite gemacht wurde war plain JavaScript mit deutschem Naming ist halt kaum noch wartbar. Und was ich mit dem letzten Kommentar meinte war, dass es zwar löblich ist, dass Leute sich die Arbeit machen, aber das macht auf Dauer wohl eher mehr Probleme als es welche behebt. Meine Meinung.


@JacquesLucke
 Thanks Jacques, that helps. I'm afraid You will see a lot of odd stuff  like this, because I simply don't understand it nor I  know exactly  what to do lol

That description has to change haha

I will revisit it after work,  but whenever You see something that is really bad and You want to change it, just do it right away. We will adjust to it. It never should be the opposite way.


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


not sure this is following the Eclipse release process, Matteo ;-)


also here: use the explicit one parameter for the Vm id and require empty signature on the rest


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 240](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=742&buildTypeId=XbimEssentials_XbimEssentials) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:02:27


Why *always* copy the static stuff into the default output?


config-repo is a new feature being developed which would let you configure your pipelines in an external repository of your choice. This checkout happens under a (flyweight) folder on the server machine, so I think it would be alright to perform a shallow clone there too, but @tomzo would be the best person to answer that.


It's labeled HACK for a reason ;)


i don't think we need to deprecate it if SocketFactory.getDefault() is a sane default


okay. to get the db connection back to a single process: can I pass objects through Queues or must i convert them to elementary data types? I can just forward the parsing part to the workers, let them create the objects and pass them back to the main process (which writes them to the database). Here we can do the commit batching.

Is this more ``python''?


Thank you!


Thumbs up for actually benchmarking this. Actually, I think the improvement is not bad at all. Using Visual Studio, even a simple `.cpp` file containing just

    #include <windows.h>
    #include <list>
    #include <vector>
    #include <stdio.h>

Already generates 3.6MB of code for me.

I think if the optimisation can be implemented without too much sweat, it might still be a nice improvement. Maybe reading line-by-line isn't even the most efficient idea but we should rather read chunks of a couple kB or so (but the line-by-line approach has the benefit of being very easy to understand and hard to get wrong).


Why would you not use jenkins::sysconfig for this?


Salut,

Je n’ai pas de préférence particulière à vrai dire ;). Le plus simple est probablement de rendre ce champ facultatif.

Olivier;


We always take the first occurance for date and amounts, so I was very surprised to see your code that took the last occurance for the other fields ! I found it because it broke one of my invoices (and probably several). Feel free to make it an option, which defaults to the first occurance.


@capisce Can you make this 1.1.0 since it adds a new API function? kthxbye


copyWith ? (it's just that newCallbackClient looks like a factory method, but it's more akin to copy/clone)


+1, I like this.


Aww yeah redactor 2 <3 <3 <3


Most repo does have `.php_cs` or `.php_cs.dist` file :(


thanks for this and the other small but helpful refactorings


What is plugin for?

Maybe we need a ReleaseNode and Version Control.


Ah, is this why I get:
Warning in <UnknownClass::SetDisplay>: DISPLAY not set, setting it to lxplus011.cern.ch:0.0
when running ;-)  Sorry, will fix in a downstream PR.


Thanks, it's great that we can capture ctrl_c! However I wonder if it's still OK to use the script without specifying a context?


not sure if it comes from my old code but that can be removed


Back then `nt2` required a newer version of Boost, that is why we built a custom deb.


I think the version should be 2.2.0 then, since the last num is for fixes of the current state. Upgrading libs change that.


comment on a line


why not use a connection per process? What's the problem with multiple connections? That's what a database is buit for. Of course you can do it in the main (calling) thread but it will slow things down because you have a bootleneck and use a lot of memory. So doing it in the workers would be the best


@theintz are you running ``composer install`` (from a lock file) or ``composer update`` ?


How about just falling back to configs in the CWD?


that's likely to be something important to document


fixed this in PR https://github.com/dotnet/corefx/pull/5773 .. Will take care of this while rebasing,


On a meta level, I would say that depends on what changes the upgraded libs introduce, but okay.


I think for date, etc you are right. First is best. For amount the last is better. I have a case that has several "Totals" until arriving at the correct "Total" last.


opkkii


@romanblanco maybe? (let's play with deMorgan rules:) ):
```
objects = objects.select { |obj| !obj.archived? && !obj.orphaned? }
objects = objects.select { |obj| !(obj.archived? || !obj.orphaned)? }
objects = objects.reject { |obj| obj.archived? || obj.orphaned? }
```


Would picking the last amount and first everything else solve your issues? @alexis-via


¿Sólo una regresión de dos dimensiones?


In this case, after "clear cache", we have an error: "mkdir failed: EBUSY (Device or resource busy)".
So folder isn't created.


Hi Oleg, please review the use of similar strings and combine them, using text-transform to change case rather than having the same string in different cases. For example, you have both the strings:

New Books
New books

This is double the work for translators.


See 4c9013a79189a79fbaf2d99f74b49896e9ec88b1


you can also refer to the Python test you wrote and the Java example application (the path would be enough, e.g., You can see a full example in the test file py4j-python/src/tests/java_tls_test.py)


:shipit:


We should respect the user's choice of theme and icons by using system theme and icons. **In the future** we may add **optional** theming (opt-in) but never by default.


Removed, not needed.


@TsudaKageyu  that is really awesome,thank you very much.
But I still doubt if the other tag parser will have the same problem?
Since some of the String class constructors still have the characteristic(waste of memory).
Thanks again.
With kind regards!


Remove pg in this case.


OK


Yes, refactored


Right


Hmm, let's try to remove the trigger that `sharedLibrary` should be `false` on Darwin. I see it's been there for many years 97a65f81b2572, so it's likely there's no  reason to keep it anymore.


OK, change on GetMessagesRequest.ids method


@AByzhynar see https://github.com/LuxoftSDL/sdl_core/commit/50aa34d1a88ff2eb6ac2d0abe24f9275388f22cd


I didn't see any reason for creating `choice_set` when you've already had `new_choice_set_array`


@jaapp
It's broken.....doesn't compile with the cube LED_STRIP settings. Someone needs to look at it.


Not sure myself. Eclipse release process only references downloads from the Eclipse website (last time I checked).


For `mono_threads_wait_pending_operations` there is no pending operations to wait for, out of `mono_threads_core_abort_syscall`
For `mono_thread_info_check_suspend_result`: in the case of the syscall abort, we do not set `suspend_can_continue` in `suspend_signal_handler`, so `mono_thread_info_check_suspend_result` would always return FALSE, leading to returning NULL from this function.


Yes, it makes sense to do only shallow clone on server. I doubt that configuration plugin would need deep git history to get configuration.


@AByzhynar see https://github.com/LuxoftSDL/sdl_core/commit/ef7a082f02cf01959beb34c826b59f967b1a2ac6 and https://github.com/LuxoftSDL/sdl_core/commit/41a2eb5203838c0498f7a46cd4042fe4c59c5c09


Rename this file `iaas.go`


I tried that and it didn't work, something related to the `-Wl,soname=...` not being supported on Darwin (Understandable as AFAIK that's an ELF-only concept).


I don't have this problem on my machine but I guess that's cause my SQL thing isn't configured in the first place.

BTW, the test ARGS=-j4 works, so wicked!!!


please consider using `StringUtils.isEmpty()` here


@AByzhynar see https://github.com/LuxoftSDL/sdl_core/commit/ef7a082f02cf01959beb34c826b59f967b1a2ac6


Maybe we could try to always use the autoconfiscation patch (for even Linux) and see if that fixes it...


BTW, I can't merge my last PR because of that, so if you could disable parallel test till its fixed, that would be cool.


@nikolai-b Great work!


Thank


Updated **buildings** solar pv.


@lpichler could be better :blush:, thanks :+1:


@tonio Je supprime la deuxième </a>non ?


Because there is no more [enzyme](ftp://ftp.mi.fu-berlin.de/pub/OpenMS/documentation/html/structOpenMS_1_1ProteinIdentification_1_1SearchParameters.html)


yep


It looks like you renamed 'Sum' as 'SampleRunList', but have not removed 'Sum' from the work flow chart.


removed


stylish-moz


:+1: Thanks!


Would this change resolve dita-ot/dita-ot#2136?


That I would prefer unique (on a db-level) Sources, Destinations and IncidentCatalogEntries. If I'm using four concurrent processes with separate transactions and I came across the same Source in those four in parallel, each of them will try to create one -> this violates the (not yet existing) unique constraint. If you commit after each [source, destination, incidentcatalogentry] update, other parallel transactions still have a race condition until the next commit point.

If you move the write process to a single process this would not happen anymore. In addition I would expect way better cache (OS as well as db connection) utilization. Trade-off: context-switches. How is the ratio of I/O wait and CPU processing time for the python process? How many cores does you computer have? I would assume that for a 2 core machine a multi-threading solution (parsing in multiple threads so that there's no I/O wait on the db) would lead to two fully utilized cores (python + postgres).


I was too dumb to forget that, the proper commit name have to be "Added option to set maximum timeout between taps for doubletap2wake", but shot was fired and I cannot change it... I will make sure it will not happen in future commits.
Peace


:-) autoconfiscation. Perhaps not on Linux, as it might lengthen bootstrapping nontrivially.


Le malloc est à 400 mais il faudrait récupérer la taille réelle sur la première ligne du fichier .txt lue


fixed


Commits related to this issue:

* c8dfb59b873d68cc0e252e87d2f23ec8354d8890
* 281dd1c3f3abe2befc69c4c9660766010df105ac
* 9c084fb3990d2ddc352eecb7fda8cd00d0efe86c
* c9164a6feb8dfa948125b7719446472d3d02ce24


# [clip-path](https://github.com/postcss/autoprefixer)


TeamCity pull requests :: netty [Build 1196](https://garage.netty.io/teamcity/viewLog.html?buildId=5373&buildTypeId=pulls_netty&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 6405, ignored: 23 Build time: 00:43:36


gayyyyyyyyyyyyyyy


@OmgImAlexis that wasn't the only problem... e was undefined too
the exceptions need to be
```python
except Exception as e:
```


Don't seem to work properly for plain text, for instance `-k 150`. `-k 3` works fine, but not when in 256 color mode.


@VVeremjova see https://github.com/LuxoftSDL/sdl_core/commit/ef7a082f02cf01959beb34c826b59f967b1a2ac6


You're discussing a log printout? Don't you think there are more important stuff to address? I'm with @skeptical on this. Web based content will not ever have any mediainfo data so UMS must do a qualified guess. If plugins can't get the mediainfo data why should they guess? So if my guess is that the sample rate is 192 kbps then that guess is somehow more valid the UMS guess? Why? If I as a plugin developer knows (I'm doing a spotify plugin for example) I can of course set this value correctly but if I make a generic plugin that handles random media my guess will be as good or bad as UMS. Should I still make the guess or should I let UMS do it instead. My vote is on UMS as that is how it has worked in the past. Reducing a log in that situation is also good since it is a legal case.


On 03-02-2016 06:28, Leandro A. F. Pereira wrote:
> Will this work while cross-compiling to 32-bit from a 64-bit machine?
>

Do you mean something like 'CFLAGS=-m32 -ffloat-store'?
If so, yes, it does work.

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/solettaproject/soletta/commit/a158685409e3f4000bae0d6d94fcb8aae2490d95#commitcomment-15850160>.
>


Thank's Tzachi! I will test it this weekend.

As the logic was different for quite some time, should we have this optional?
Something like "Extend snooze of higher priority alerts to lower priority alerts." (There may be better/more concise version.)


`nt-2` required >= 1.57 version, while 15.10 features 1.58 already.