TeamCity OTA+ :: rvi_sota_server :: ci [Build 2468](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30766&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


앗 그러네요. 익스텐션들이 엉뚱한 곳으로 복사되고 있었어요. 이제 잘 될거에요!


good


This commit requires at least several more sentences of explanation.


#6105-HW-supplemental-heating-coil-in-AirloopHVAC-UnitarySystem-not-controlling-to-set-point (rraustad) - i386-Windows-7-VisualStudio-14: OK (2494 of 2495 tests passed, 2 test warnings)

Messages:

 * 3 tests had: EIO diffs.
 * 2 tests had: ERR diffs.
 * 2 tests had: ESO small diffs.
 * 2 tests had: Table small diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: MTR big diffs.
 * 1 test had: Table big diffs.

Failures:

regression Test Summary
 * Passed: 598
 * Failed: 1

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


GOOD change.


`??` is a code smell.

```zig
test (node.next) |next_node| {
    // Intermediate node.
    new_node.next = next_node;
    next_node.prev = new_node;
} else {
    // Last element of the list.
    new_node.next = null;
    self.last = new_node;
}
```


Oh, whoops, I'm used to having to install things (like for [C builds](https://github.com/nic-hartley/concaten)). I've removed it.


Hello @Tapsa. I see. Thanks for informing me.


_,,,^..^,,,_ (phone)

> On May 3, 2017, at 6:10 AM, Tobias Pape <notifications@github.com> wrote:
>
> Just curious, why the * to the name and not the type?
>

That's the style in K & R
http://alvand.basu.ac.ir/~dezfoulian/files/Programming/Prentice%20Hall%20-%20The%20C%20Programming%20Language-%20Brian%20W.%20Kernighan,%20Dennis%20M.%20Ritchie,%202nd%20ed.,%20ISBN%20.pdf#page124

So it's what I learnt and used for many years, it's the style in the VisualWorks VM, and in many other C code based I've seen.  AFAICR it's only in parts of the VMMaker that I've seen star next to the type.  Irritating that my visual system sees star next to the type as "wrong".

If there are two conventions I'd like to see used religiously in the VMMaker and platforms source they are:

1. Put the function name in a function/procedure definition (not declaration) on its own line, so

const char *
getImageName(void)
{
    .....

not
const char *getImageName(void)
{
    .....

Rationale, using search tools it is easy to find definitions by looking for name at beginning of line.

2. tabs = 4 spaces.
Rationale:
- tabs are quick and convenient to use for indenting code
- 8 space wide tabs are way too wide
This might imply e.g. adding the vi tabstop metadata to the beginning of files.  I prefer to set up my .exrc/.vimrc.  I hope others will set up their favourite editors to view/edit source using this appearance.

A couple of things I'm less exercised about, but that I strongly prefer is

1a. Put open curlies at the end of line, so
    if (expr) {
        ...
    }
    else {
        ....
    }

not
    if (expr)
    {
        ...
    } else
    {
        ....
    }

1b. Don't use curlies around thens or elses in if-then-else for single statements

Rationale: vertical real estate is at a premium when landscape is the predominant aspect ratio and code is organized as a scroll.

2. Put con/disjunctions at the beginning of line so
    if (expr1
     && expr2) {
not
    if (expr1 &&
         expr2) {

Rationale, it's much easier to read; all the con/disjunctions line up and are easily read.  At the end of last be they get lost and are ragged

But there are far more important things to be concerned about :-)
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


What is the purpose of this change?


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.91.6f66347250f5e4c8f6da23563304b2570f31b970](http://build.palaso.org/viewLog.html?buildId=89832&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:34


I'm not suggesting to check each range() callsite, rather to leave them alone entirely. That's the least effort you can get ;-) And replacing all xrange occurrences by range, which is a one-character global search&replace (no manual check), very hard to beat too.
= no time wasted trying to predict and work around unlikely theoretical problems. Wait for them to happen.

Ditto with the Python 3 runbot. It will be ready as soon as we have a codebase that can remotely "run" under Python 3. It would be useless until then. The bulk of the conversion work is not based on test results, but on code analysis, right?
Once that's out of the way, the final code will be validated with the help of the test suite...


> It handles changes that occur after the page has been built

I have two events. I guess this is the one you are referring to https://github.com/schomery/stylish-chrome/blob/scheduler/manage.js#L134

> It's not invoked by page-building code.

I am not following then. The event is inside https://github.com/schomery/stylish-chrome/blob/scheduler/manage.js#L393 which seems to be fired once an style is changed, right?


@didi0613 @jchip are these removals really intentional? They seem to be required by a few other gulp tasks downstream. Perhaps I've missed something?


Nice !


@schomery, [test it](https://github.com/schomery/stylish-chrome/tree/embed-digests). Seems okay and has no conflicts with your branch so once you approve I can push it into master and you'll rebase your branch on the new master.


How about `-- | @since 0.3.24`? Does that work?


It could be your network has not been started yet, and Domoticz tries to see if there is an update available


Just to document it: consumption difference in idle based on a quick test was 250mW less with `rtw_power_mgnt=2` compared to `rtw_power_mgnt=0`: https://github.com/ayufan-pine64/linux-build/pull/1

`rtw_power_mgnt=2` leads to noticeable delays when working on the Pinebook via Wi-Fi/SSH (which is a strange use case though). So it needs further investigation how these settings affect normal Pinebook usage (with RPi-Monitor installed and running in the background -- `/usr/local/sbin/install_rpi_monitor.sh` is available from now on)


@alkemist this is what you asked @breskeby to do

I had to exclude `TaskOperationDetails ` because it's causing a StackOverflow when using JsonBuilder


Thanks :)


rename _httpClientFactory


Fixed. thanks


remove comments


Thank you so much Brian. You are right on about JS. I was confused more due to just having a busy mind more than anything. This is why I am talking a JS online course because now I feel that I understand enough to learn more.
I will definitely stay in touch and increase my knowledge and abilities around web development. Funny this is what I've wanted to do as a career but when you are taking care of a family sometime you do what pays the bill, hence my current devops role.
Thank you for being a great teacher, your ability to patiently deal with a group of people who come from various background and get us to produce what I saw.....Amazing!!

TTYL!!

Tracy


Extract repeated code to a function.


HAHAHAHAHAHA. Good one!


Does this imply that solutions submitted for the challenge must contain two agents: one trained for maximum 100k steps, and another trained for 500k?


avoid `??` with `test`, see other comment


Các file báo cáo liên quan


Right now the color maps are at the top of the sirepo-plotting.js file.
Adding a new one should be relatively easy - just compute the 0-255 color
string from matplotlib values and add the entry to COLOR_MAP. I'll add jet
to the list when the software allows selecting a different color map for
the plots.

import matplotlib.pyplot as plt
from matplotlib import colors
import numpy as np

name = 'jet'
cmap = plt.get_cmap(name)
color_list = ''

for v in np.linspace(0, 1, 256):
    color_list += colors.rgb2hex(cmap(v)).replace('#', '')

print("{}: '{}'".format(name, color_list))

On Tue, May 2, 2017 at 7:04 PM, Maksim Rakitin <notifications@github.com>
wrote:

> Is it hard to add a new colormap, e.g. jet?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/radiasoft/sirepo/commit/7a9ce3576b9a830b18775878e683fb8bb6308045#commitcomment-21992476>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGNwrvf9c0Jn1v2HvlHKvszECmg0_ECFks5r19KRgaJpZM4NOi58>
> .
>


Okay. Then I leave it out, as it's not very relevant. And I will add a comment in the `errors` enum regarding this fact.


IC2 defined this value as equal to a nugget


I have a not yet published evolution where I now also log the URL called.... that would probably help answering your question. I initialy had the same idea as Gizmocuz but I think it is wrong. Network down would not produce a 404. 404 is an error sent by the remote server.... which implies it has been reached in the first place.
On my own systems I have once in a while HTTP 522 errors (0 up to 2 per day) when the update server is not available, but never a 404.


DBSCAN Algorithm


Bug da risolvere


Ah, I've missed the first one. Well it's okay then I guess. BTW, don't you need some event in handleDelete as well?


(note your comment is on your fork :)


Strange Naming convention, remove the underscores and give it a better name.
IHttpClientSimpleFactory


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2468](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30766&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Tests failed: 6 (1 new), passed: 273, ignored: 3 Build time: 00:13:32
### Failed tests
```
org.genivi.sota.device_registry.DeviceResourceSpec.First POST request on 'ping' should update 'activatedAt' field for device.: <no details avaliable>

org.genivi.sota.resolver.test.DevicesResourceWordSpec.Vin resource should install a package on a VIN on PUT request to /vehicles/:vin/package/:packageName/:packageVersion: <no details avaliable>

org.genivi.sota.resolver.test.DevicesResourceWordSpec.Vin resource should list installed packages on a VIN on GET request to /vehicles/:vin/package: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should support filtering by installed packages on VIN: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should support filtering by hardware components on VIN: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should return a string that the core server can parse: <no details avaliable>

```


## Units

| Changed                                               | Status   |
|:------------------------------------------------------|:---------|
| `./data/tlg2042/tlg028/tlg2042.tlg028.1st1K-lat1.xml` | New      |
| `./data/tlg2042/tlg028/tlg2042.tlg028.opp-grc1.xml`   | Deleted  |
| `./data/tlg2042/tlg028/tlg2042.tlg028.1st1K-lat1.xml` | Passing  |

*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/257)*


As stated here: http://fontawesome.io/get-started/ ("Using Sass or Less" section)


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/258)*


Could it be something else on the Domoticz side.
I also noticed that the log reports the following:

 2017-05-03 17:45:25.378 WebServer(HTTP) started on address: :: with port 8080
2017-05-03 17:45:25.420 WebServer(SSL) started on address: :: with port 443

This can't be due to your changes.
But previous it showed the ip aswelll but Domoticz doesn't report any ip.
RPi3 has an ip as i can ssh into it.


i am deeply sorry :)


Lol same q


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/259)*


I think this line is not needed anymore as we are not writing any new key and the old ones are already removed in https://github.com/schomery/stylish-chrome/commit/bf04b1136858deb4564552a8b1820eb3fc21411b#diff-f9b12bd72f40c9b8ed144484f0f12a5fR77


This is fixed upstream by https://github.com/NixOS/nix/pull/1366.


@AnthonyKulis Interface lab


TeamCity libpalaso :: palaso-win32-master Continuous [Build 4.0.99.1168095c4cca95e40e57e4982415341591dfde69](http://build.palaso.org/viewLog.html?buildId=89836&buildTypeId=Libpalaso_PalasoWin32masterContinuous) outcome was **SUCCESS**
Summary: Tests passed: 3725, ignored: 128 Build time: 00:04:21


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.92.1168095c4cca95e40e57e4982415341591dfde69](http://build.palaso.org/viewLog.html?buildId=89833&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:43


Seems to work ok.


Oeps a typo and not only [base] but [updates] and [extras] also.

That first line below example should be:
1) Just add line: `proxy=http://<proxy ip-address>:<proxy port>` in `/etc/yum.repos.d/CentOS-Base.repo` below `[base],[updates],[extras]`.

Kind regards,
Herman Bakker


Shouldn't these regexes be like this: `/$If\b`, using the regex `\b` operator rather than `($|[^S])`, etc. which would gobble that 'S' and match (admittedly oddball) stuff like '$IfStored'? Maybe nitpicking, but I'd rather keep this as clean as possible, in the same spirit as commit SHA-1: 68248c6aaab2b20ec8882f57d58951084b5ec967::Make :function matching more precise


return type should be  `%&Node(T)`


para mandar los params como form data, de la otra manera no recuerdo como los manda, pero me daba error en donde uso la gema.


Works ok. It is not possibly to copy a subtree for an empty project, I expected to be able to do that.


docker-image


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/260)*


Okay, thanks.


Looks good to me. Please merge


I agree with 1.

I don't agree with 2, I'd rather say there should be no mixing of tabs/spaces, I'd advocate. I use 3..4 different editors on different platforms and it looks always different.

For 1a./1b. I'd say:
Always do
```
if (a) {
 x;
} else {
 y;
}
```
and never omit braces. Reason? [Apple's gotofail](https://nakedsecurity.sophos.com/2014/02/24/anatomy-of-a-goto-fail-apples-ssl-bug-explained-plus-an-unofficial-patch/) for example.

But we should have this all agreed upon and written down elsewhere.


@bhklein Can I get a post-commit review on this? This plugs an edge case where the probe is an FTE and we'd potentially count it as a hit depending on the order of the gallery templates (since all the comparisons for this probe would be `-std::numeric_limits<float>::max()`. In practice this doesn't show up in our evaluations because we force the enrollment of the probe by picking a face detection bounding box of the whole image, and thus there are no FTEs.


# hi dear  elkayem
your balance robot is really amazing , I am really surprised of your job ...
i really need to your help for my final project
is it possible to you that  explain your code in a video "Please Please"  ???
I really need your help....


This just fixes a compiler warning.


New Youtube with NSFW and just audio

Example:
https://www.youtube.com/playlist?list=PLi5ZVIjP3PTNKJ_kIB9vQBhoPvMmvuUKn

or search google "radio live youtube"


Why were multiple fatal warnings disabled here?

Stuff like:
1) disable_fatal_linker_warnings
2) 'werror%': '',

You will (and we are, right now) run into fatal errors at runtime which are hard to debug because the code was broken at compile time (broken as in - not safe to use).

This needs to be reverted and fixed properly.


This is because it detects IPV6, and it is listning on this IP address for quite some time now, maybe you recently updated?
For the above, it could also be that you are using a hardware plugin that needs to pull data from a HTTP website. If your network was not started yet, this also results in this error.
For most (if not all) hardware plugins i added a delay of 5 seconds before the fist poll.


should be  List.fold_left (fun acc e -> if f e then acc@[e] else acc) [] l


Thank you for reviewing the commit.  Fixed in e61c157c62cfb905ba1e62cb1cf3bd65439c13f0.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f3d5c510-3dd3-427e-80b5-f6d1ea69fef0 "QCRI"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/9abe8827-1d05-4724-974a-616e3313903f "simple-toolchain-20170502141909634") deployed [QCRI-AA](https://github.com/borisonr/QCRI-AA/releases/tag/deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-155633 "deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-155633") to [QCRI](https://console.ng.bluemix.net/apps/2ad6238c-9f03-48f7-bb3f-136654ccd357 "ibm:yp:us-south:BlueMetalAA:QCRI"), including this commit


Idiomatic:

```zig
*node = Node(T) {
    .data = data,
    .prev = undefined,
    .next = undefined,
};
```


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/261)*


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/262)*


docker-image


hmm, this opens a can of worms since this is generally not possible.


Didn't think of that... will try and add a delay to any hardware which poll data from my network or internet.


jalebi hangs on the bootlogo for like 9 seconds without this one. Reduced to 4 now.


Ah, yes, thanks. I forgot about that


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/263)*


y u stalk mah git u weeb


Looks like this commit has gone stale - I'll update it for you.


The convention I've been using is that `init` generally means setting field values and not allocating, and `create` means allocating. I think we could call this function `createNode` and call the other one `allocateNode`.


I am doing this right now: https://github.com/schomery/stylish-chrome/blob/scheduler/schedule/core.js#L87-L93

Basically one first alarm call, existence of an style is checked and then the next scheduling is performed. handleDelete simplifies this function.


puedes poner estas cosas en issues o wiki en lugar de crear commits innecesarios joer


Depending on the system used (like a raspberry pi for instance), i would expect that the network is started quite fast.
It could also be that we need to tweak the domoticz startup script in /etc/init.d


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f3d5c510-3dd3-427e-80b5-f6d1ea69fef0 "QCRI"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/9abe8827-1d05-4724-974a-616e3313903f "simple-toolchain-20170502141909634") deployed [QCRI-AA](https://github.com/borisonr/QCRI-AA/releases/tag/deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-155900 "deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-155900") to [QCRI](https://console.ng.bluemix.net/apps/53b1f808-97af-42dc-b602-07a098851eba "ibm:yp:us-south:BlueMetalAA:QCRI"), including this commit


`data: &const T`


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/264)*


Move `ListIterator` inside `Linkedlist` and rename it to `Iterator`.


Fixes #11


Then you don't need to accept T as a comptime parameter, you can reference T from the outer scope.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f3d5c510-3dd3-427e-80b5-f6d1ea69fef0 "QCRI"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/9abe8827-1d05-4724-974a-616e3313903f "simple-toolchain-20170502141909634") deployed [QCRI-AA](https://github.com/borisonr/QCRI-AA/releases/tag/deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-160145 "deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-160145") to [QCRI](https://console.ng.bluemix.net/apps/288de3f1-245a-46e0-a16f-68367551fc79 "ibm:yp:us-south:BlueMetalAA:QCRI"), including this commit


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/265)*


TeamCity Code :: 1. Development :: DDK :: Feature [Build 278](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=22126&buildTypeId=Code_Development_Ddk_Feature) is now running


Oh, good. I took a wild guess on this, but it seemed to do what I hoped. The previous version was linking in both (SSL and non-SSL) libraries, which I figured might be dangerous.


Sim. Recordar é transitivo indireto quando reflexivo. "Como se se recordasse de..." Vou corrigir.


Ah, indeed. It doesn't hurt though. Or you can remove it now, this is up to you.


If you do this then you don't even need it to be a function. You can do:

```
const Node = struct {
    prev: ?&Node,
    next: ?&Node,
    data: T,
};
```


Stupid me,
No hardware i own is capable of setting a delay and don't have plugins.
My RPi has its network ready before Domoticz is started.
Also check my scripts and all net work ip are set to 127.0.0.1.
Removing scripts doesn't help and no other stuff running which polls data over my network.

Just fired up my second RPi3 with a clean Domoticz installation.
No scripts, hardware and such, but it doesn't report the error.

Will now try to disable all my hardware and see what happens


## Global

| Changed            |   Status |
|:-------------------|---------:|
| `coverage`         |     1.64 |
| `metadata_passing` |    29    |
| `metadata_total`   |    29    |
| `nodes_count`      |   515    |
| `texts_passing`    |    15    |
| `texts_total`      |     1    |

## Words

| Changed   |   Status |
|:----------|---------:|
| `UNK`     |    -4863 |
| `grc`     |   +30048 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg002/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg003/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg004/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg005/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg006/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg007/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg008/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg009/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg010/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg011/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg013/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg016/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg017/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg018/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg019/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg020/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg021/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg022/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg024/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg025/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg026/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg027/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg028/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg029/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg030/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg031/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg032/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg033/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg034/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg003/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg004/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg005/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg006/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg007/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg008/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg009/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg010/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg011/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg013/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg016/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg017/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg018/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg019/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg020/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg021/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg022/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg024/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg025/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg026/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg027/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg028/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg029/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg030/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg031/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg032/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg033/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg034/__cts__.xml`                     | Passing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/266)*


function named "getPwmFromPfmOrJasparFile", while in other files (e.g. NAMESPACE or utility.R) this function is attemp to be called as "getPwmFromPfmOrJasp**e**rFile"


TeamCity Code :: 1. Development :: DDK :: Feature [Build 278](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=22126&buildTypeId=Code_Development_Ddk_Feature) outcome was **SUCCESS**
Summary: Tests passed: 68 Build time: 00:01:13


It's okay. please merge.


#6105-HW-supplemental-heating-coil-in-AirloopHVAC-UnitarySystem-not-controlling-to-set-point (rraustad) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1896 of 1896 tests passed, 0 test warnings)

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


The pinyin.ZeroConsonant is a valid input but undocumented from the command help.

I'd like to keep it that way until https://github.com/go-cc/cc-pinyin/issues/10 is fixed.


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/267)*


Thank you for the explanation, Paul.


Eek, I saw a bug, I'll push an update.


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/268)*


#6105-HW-supplemental-heating-coil-in-AirloopHVAC-UnitarySystem-not-controlling-to-set-point (rraustad) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


@pprice FYI, if you add these to a CHANGELOG.md file -- the marketplace will add a link for it, and vscode will have a new tab on the extensions page for it


I disabled the following hardware which polls data: Weatherunderground, Nest and two Youless devices.
After a full system reboot i don't see any 404 error


Just submitted a pull request with the code I am currently running. As soon as it is merged you can pull the new version and reboot.... you'll see what is called that returns a 404.


I unset that security option in the browser, still had a problem. Moved on to other examples in the book and they are going smoothly. When I goggled that error, seems pretty common in other contexts as well.


This recipe succeeded in travis build - failures were in other recipes. Succeeding travis build (including this recipe) succeeded (commit 37505f48fc68d2a8d68a3877c29c683a30ff82ed).  Also, the comment for this commit is wrong - it's version 0.98.0, not 0.90.0.


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/269)*


What does this means?


Syntax Error. Expected ";".

LocationAudit changes = NewCode;

var is bad.


nice, thanks!


מפגר


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/271)*


![](https://github.trello.services/images/mini-trello-icon.png) [Digital Watch Commit By Jay 2017-05-03](https://trello.com/c/eC4PbTrk/17-digital-watch-commit-by-jay-2017-05-03)


Heu... I could comment a bit before you merge it.
I tried several things like switching some list to dictionaries.
For the moment it works because at the end, I reconvert them as a list.

If you want to do a merge, I will take a last look at it before you do it.
Is it possible?

On 05/03/2017 05:29 PM, Michael Scott Cuthbert wrote:
>
> are these changes things we should incorporate into base music21?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/SonyCSL-Paris/music21/commit/c6c3843686fa21bc0479f574f8d0343a6e02ea5b#commitcomment-22000605>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ALX_xG5CUuW3vARb5NoGUXPmsXvMXwWaks5r2J1FgaJpZM4NPkby>.
>

--
Stéphane Rivaud
PhD Student
Université de Reims Champagne-Ardenne
Sony CSL
6 rue amyot
75005 Paris


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.93.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89839&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:05:00


LOOOL, revent @caspervanneck


Good catch.  The mistake here is that we used the same variable name for the input ("var request") and the parameter passed to the callback.  This would make sense if they had different names.  We will fix it.


Why lowercase writeLog ? All other methods are uppercase


TeamCity Code :: 1. Development :: DDK :: Feature [Build 279](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=22127&buildTypeId=Code_Development_Ddk_Feature) is now running


HostUri needs a better name, MessageBrokerUri maybe.


TeamCity libpalaso :: palaso-win32-master Continuous [Build 4.0.100.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89845&buildTypeId=Libpalaso_PalasoWin32masterContinuous) outcome was **SUCCESS**
Summary: Tests passed: 3611, ignored: 128 Build time: 00:05:48


좋아요~


TeamCity libpalaso :: palaso-precise64-libpalaso-2.6 Continuous [Build 2.6.1346.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89837&buildTypeId=PalasoPrecise64v26Cont) outcome was **SUCCESS**
Summary: Tests passed: 3589, ignored: 111 Build time: 00:06:33


TeamCity libpalaso :: palaso-trusty64-lfmerge Continuous [Build 2.6.337.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89838&buildTypeId=PalasoTrusty64lfmergeContinuous) outcome was **SUCCESS**
Summary: Tests passed: 3589, ignored: 111 Build time: 00:06:26


Note also the subtlety that "toEqual" and "toBe" are different in jasmine.  The request object inside the callback should equal the request object from the caller, but will not necessarily be the same memory address.


TeamCity Code :: 1. Development :: DDK :: Feature [Build 279](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=22127&buildTypeId=Code_Development_Ddk_Feature) outcome was **SUCCESS**
Summary: Tests passed: 68 Build time: 00:01:10


TeamCity libpalaso :: palaso-win32-libpalaso-3.1 Continuous [Build 3.1.356.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89846&buildTypeId=bt223) outcome was **SUCCESS**
Summary: Tests passed: 3611, ignored: 128 Build time: 00:06:40


> Also, maybe it's better to have a javascript event coordinator with subscribe function, not DOM events.

This works. I can add something like `schedule.handleEvent = {}` but my point is if in the future some other modules need these events, they could have access to them without modifying the manage.js which I think is a plus point.

Ideally we could have an `EventEmmiter` module that fires important events. like
```js
var ui = new EvenEmitter();
...
ui.trigger('styles-ready');
...
ui.on('styles-ready', () => {});
```


![](https://github.trello.services/images/mini-trello-icon.png) [??](https://trello.com/c/vQP63YYw/18--)


TOPIC!


Sentido fazia. Mas os dois pontos antecedem: enumerações, explicações, discurso direto, síntese ou resumo, exemplos, citações; ou sucedem ao vocativo. Não se aplica aí.


Hello Again, Many thanks for your answer. I was trying to add some patch for Docker repo. Have you tried some patch in Docker Repo to work with Swarm and --device?
Thanks


+25

On Wed, May 3, 2017 at 10:51 AM, Randy Hodge <notifications@github.com>
wrote:

> @AnthonyKulis <https://github.com/AnthonyKulis> Interface lab
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Hodge-zf/lightbulb/commit/22c7911e0c385bebf559e1a397935b5f6fede365#commitcomment-22001046>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA-8MVtNuTpGLs08xViye-NGRRaGBAySks5r2KKBgaJpZM4NPmWY>
> .
>


почему не локально?


Thank you @avar !!! this is great.


I don't think we should merge this.  It'll work great for anyone using a vanilla install of recap, but if anyone's customized ${OPTS_FDISK} in their recap.conf, this might actually break their existing installation.  For example, fdisk takes a "-b" argument to specify block-size, but parted doesn't support it:
```
root@qwatch[~]# OPTS_FDISK="-l -b 4096"
root@qwatch[~]# FDISK=$( which parted fdisk 2>/dev/null | head -1 )
root@qwatch[~]# ${FDISK} ${OPTS_FDISK}
/sbin/parted: invalid option -- 'b'
Usage: /sbin/parted [-hlmsv] [-a<align>] [DEVICE [COMMAND [PARAMETERS]]...]
root@qwatch[~]#
```
I'd encourage you to undo this specific commit from the existing PR, and we can iron out the best way to integrate parted support in a separate branch/PR.


I thought it might be worth mentioning since someone may not feel comfortable posting on GitHub saying, "Hey Google (and world), this is my number - remove it!" since it's public. Filing an issue through Issue Tracker anonymizes/disambiguates their username to the public.


See broken build https://ci.appveyor.com/project/chcg/scintilluaplusplus/build/1.0.17

should be at least //NPPM_GETCURRENTCOLUMN


might have problem (index different with id) in race condition


Sim. Passou.


Ah do you mind sharing with me the types that are failing the assert? I may not be using precisely the correct assertion to verify what I need.

For information on standard layout types, the CPP website is great: http://en.cppreference.com/w/cpp/concept/StandardLayoutType

`offsetof` is simply a macro which returns the byte offset of the struct member, so I'm just checking to make sure the two pair instantiations have their members in the same byte positions.


Hello,
Thank you for the commit.
But when that commit will be ship into the 40.0.3 version?
Thanx


TeamCity libpalaso :: palaso-linux64-libpalaso-3.1 Continuous [Build 3.1.311.f1ea25564ea515d4f9a3c8309ded1a2697d264b5](http://build.palaso.org/viewLog.html?buildId=89842&buildTypeId=bt322) outcome was **SUCCESS**
Summary: Tests passed: 3589, ignored: 111 Build time: 00:06:03


я бы таргет бланк тоже пихнул сюда


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/272)*


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2469](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30774&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


It's done now. Sorry for the delay!


Oh, yeah.. boost has better containers.


Oh no, so sad.   Q____Q

Jhan-Ying, Liao (廖展瑩)

E-mail: lemon5920@gmail.com

Sent from
https://polymail.io/?utm_source=polymail&utm_medium=referral&utm_campaign=signature

On 2017年5月04日 週四 at 上午12:15 "BlueT - Matthew Lien - 練喆明"

<
mailto:
> wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }

might have problem (index different with id) in race condition

—

You are receiving this because you authored the thread.

Reply to this email directly,
https://github.com/lemon5920/vue-todo-list/commit/2d382ad0ad49fc9ab5556d0c2ca6c2c37e241259#commitcomment-22001538
, or
https://github.com/notifications/unsubscribe-auth/ANUdpsQ21tVGVsOmNY76mOp9INevDoRHks5r2KgEgaJpZM4NPoRB
.


Now I have a vanilla installation of Symphony 2.7.x (as of today, head is at 9c9e088a344d490439b24b7bcd5c3478d59c45d6) plus the default workspace, running on PHP 7.1.4 and MySQL 5.7 (in strict mode).

First bad news: Using the simple test procedure (i.e. manually duplicating one row in an Input field's data table) I managed to break Symphony's backend anyway (trying to access **Content > Articles**):

> Symphony Warning: strip_tags() expects parameter 1 to be string, array given
>
> An error occurred in `/var/www/html/symphony/lib/toolkit/class.field.php` around line `1024`

Here's the relevant part of the backtrace:

    [:0]
        GenericErrorHandler::handler();
    [/var/www/html/symphony/lib/toolkit/class.field.php:1024]
        strip_tags();
    [/var/www/html/symphony/lib/toolkit/class.field.php:993]
        Field->prepareTextValue();
    [/var/www/html/symphony/lib/toolkit/class.field.php:961]
        Field->prepareReadableValue();
    [/var/www/html/symphony/content/content.publish.php:614]
        Field->prepareTableValue();
    [/var/www/html/symphony/content/content.publish.php:359]
        contentPublish->__viewIndex();
    [/var/www/html/symphony/content/content.publish.php:364]
        contentPublish->__switchboard();

So I am afraid that your "fix" does not suffice to overcome the corrupted data issue.

Please don't blame me, I only did [what I was told](https://github.com/symphonycms/symphony-2/commit/58bc57f2a4153ce0d7ad0e47406ab4a9e6b60746#commitcomment-21904878) (last paragraph of this comment).

This stuff feels worse every day.

I would really like to test this systematically. So please verifiy my findings and tell me where to go from here. Here's what I did:

<img width="831" alt="bildschirmfoto 2017-05-03 um 18 14 06" src="https://cloud.githubusercontent.com/assets/40072/25670299/86dabb48-302c-11e7-9d5b-71d170b91e7e.png">

Then go to *Content > Articles*. Boom!


Gooood


Good catch! I missed porting over `self.codingPath = encoder.codingPath` in the initializers of this implementation — will fix. Thanks!


Just enabled my hardware one by one with in between a system reboot.
Looks like Nest is polling data right on when Domoticz starts.
With Nest disabled no 404 error
With Nest enabled i do see a 404 error
While sometimes the same happens for my Youless devices, not always but sometimes


We've been using the code as-is since this commit was made (roughly 10 months now) without issue.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2470](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30777&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


в вебинаре сказали, что так тоже можно


also updated api to v1 as opposed to v1beta


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.94.1168095c4cca95e40e57e4982415341591dfde69](http://build.palaso.org/viewLog.html?buildId=89847&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:35


![](https://github.trello.services/images/mini-trello-icon.png) [bangs v0.12.0 (theme: documentation & alignment)](https://trello.com/c/Qchbepyz/39-bangs-v0-12-0-theme-documentation-alignment)


Created multidev environment [ci-example-d8-composer#ci-557](https://dashboard.pantheon.io/sites/c401fd14-f745-4e51-9af2-f30b45146a0c#ci-557).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-557-ci-example-d8-composer.pantheonsite.io/)


Bkjjh


We need to add also Unity4 directive.


Sorry for dropping the ball, this is now actually updated.


`внутренние отступы`


*[Hook UI build recap](http://ci.perseids.org/repo/OpenGreekAndLatin/First1KGreek/273)*


Right commit message is: "Mongoose Setup on port  --port 27018, builded basic data and seeding it to the data, all things done using mongod and mongo and by creating seed and models folder"


P.S.: I lied, one more test is failing. gotta go now though, see you tomorrow. @tom95


:D I'm ok with that.  A couple months from now I'll forget it all


Я комментирую


@sergiomb2 OK, can you write us when it will finish? o simple add finished in the commit ;)


The title of webpack expert expires after a week, so you're good ;)


Based on what was said before;
while (index < words.size())
would not include the very last item on the list because it would not be less than the total number size.

Should it not be - while (index <= words.size()) ????


@schomery, btw since we communicate a lot, maybe skype is more convenient? my nick is `tophff`


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.95.e39a5f6f755371b46ebcffc6528a86007502ff53](http://build.palaso.org/viewLog.html?buildId=89848&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:04:30


зачем? у тебя на главной курсор меняется и говорит что это интерактивный элемент


везде где есть бг картинка - задает бг цвет который преобладает в картинке - на случай если картинка не прогрузится


@LeonHartley didn't have the problem after adding the table, even without opening the catalog


зачем ргба если альфа какнал равен нулю?


Unfortunately that is not the case here on our hardware.
And I guess I'd argue that GCC warnings exist for a reason (although I prefer LLVM/Clang myself).

I'm looking into dumping all these hacks and upgrading to the Igalia bitbake recipes here:
https://github.com/Igalia/meta-browser, so we can hopefully move to a new base soon.

(I plan to prepare pull requests for that to ease maintenance).


лишнее


![](https://github.trello.services/images/mini-trello-icon.png) [Refactoring v1.0](https://trello.com/c/4NLH5SKz/20-refactoring-v1-0)


![](https://github.trello.services/images/mini-trello-icon.png) [sdsd](https://trello.com/c/jqCoFpWf/1-sdsd)


зачем? мы наоборот хотим показать что по активному нельзя кликнуть


@skriems wouldn't we need the version info?


But this commit doesn't change a single visible character


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2470](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30777&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 293, ignored: 3 Build time: 00:11:56


Is it because of CRLF or what


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2469](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30774&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Tests failed: 5, passed: 274, ignored: 3 Build time: 00:15:15
### Failed tests
```
org.genivi.sota.resolver.test.DevicesResourceWordSpec.Vin resource should install a package on a VIN on PUT request to /vehicles/:vin/package/:packageName/:packageVersion: <no details avaliable>

org.genivi.sota.resolver.test.DevicesResourceWordSpec.Vin resource should list installed packages on a VIN on GET request to /vehicles/:vin/package: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should support filtering by installed packages on VIN: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should support filtering by hardware components on VIN: <no details avaliable>

org.genivi.sota.resolver.test.ResolveResourceSpec.Resolve resource should return a string that the core server can parse: <no details avaliable>

```


I'd perhaps recommend using this instead:

buffer->list = mymalloc(buffer->max * sizeof(*buffer->list));

The advantage of this form is that if the type of buffer->list changes, the allocation is still correct.

(I might also call the structure member 'array' rather than 'list', as the former seems more precise.)


цвет


oh it does


Forgot to scroll :joy:


window.imageBuilder =


Ha, tired of having the test fail output annoyingly not at the end of the build output?


window.imageBuilderApp =


Thanks!

We should also make some reference near the start to the TYPE_FIXED_LINE_OR_MOBILE faq: the difference here is that we don't return that type, we use the mobile prefix (or its absence) to decide whether a number is mobile or fixed line, meaning if the user omits it we get it wrong.


Please provide the patches so we can fix it.


Please have a look on this page, it will show you the capabilities of
all Allwinner CPUs:
https://en.wikipedia.org/wiki/Allwinner_Technology

Am 03.05.2017 um 15:16 schrieb Invictaz:
> Is H265 only on Allwinner A64 or also on A10?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/mosterta/libvdpau-sunxi/commit/3a1002edd716a97c5f782e9bebf2c6994a9c4c23#commitcomment-21998306>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADC2rZ8SQ9y7fDD1cJR1K-U4dDDazJDBks5r2H4lgaJpZM4NPYdR>.
>


## Global

| Changed            |   Status |
|:-------------------|---------:|
| `coverage`         |     1.67 |
| `metadata_passing` |    29    |
| `metadata_total`   |    29    |
| `nodes_count`      |   525    |
| `texts_passing`    |    16    |
| `texts_total`      |     2    |

## Words

| Changed   |   Status |
|:----------|---------:|
| `UNK`     |    -4863 |
| `grc`     |   +30636 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg002/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg003/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg004/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg005/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg006/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg007/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg008/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg009/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg010/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg011/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg013/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg016/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg017/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg018/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg019/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg020/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg021/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg022/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg024/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg025/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg026/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg027/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg028/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg029/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg030/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg031/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg032/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg033/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg034/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg003/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg004/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg005/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg006/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg007/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg008/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg009/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg010/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg011/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg013/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg016/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg017/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg018/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg019/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg020/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg021/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg022/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg024/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg025/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg026/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg027/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg028/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg029/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg030/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg031/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg032/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg033/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg034/__cts__.xml`                     | Passing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/274)*


ужас, вешай классы


Maybe [email](mailto:jeremy.schomery[at]yahoo[dot]com) is a better option. I don't install any messengers on my work PC nor my cell.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2471](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30780&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


RasPi_GPIB driver is currently not part of linux-gpib, so apply the patch here.


Last version was 4.0-rc which did not support linux kernels > 4.0


ваще пиздец


пвторяющиеся стили можно выносить в объединенные селекторы


There is a bug in this commit - unaligned write in writeback mode would be committed to HDD directly (which is OK), but could be later rewritten in clean_thread if those blocks were already marked as DIRTY (which is not OK).


@dairejpwalsh


The file provides details partial work analyzed by Caleb Muinde


Just for reference, the if check isn't required (C standard says 'free(NULL)' is a no-op.)


There should be another log line below this message that displays where it is originated from, like

Nest: error text

checked the class, it should do this

same for youless, but there was one situation where this was not logged, will be there in the next beta


@bolasblack hey! please see https://github.com/NekR/offline-plugin/pull/241 and follow up here https://github.com/NekR/offline-plugin/pull/248


Nah, it's roughly the same as github notifications. Let's continue using them.


It might be useful to have a quick comment here to explain *why* the refcount isn't incremented.


Olá professor,

A ideia era que o programa fizesse os testes enquanto "executava" o seu
estado de espera, mas pensando agora realmente parece desnecessário pois o
fim da execução só depende da 1ª trilha. Posso alterar isso e reenviar? A
propósito, nós também ficamos com uma dúvida sobre a redeclaração da
variável "on", poderíamos declará-la apenas uma vez no começo?

Adrianno Sampaio

2017-05-03 11:49 GMT-03:00 fsantanna-uerj <notifications@github.com>:

> Pra que esse par/or em volta se a 2a trilha é um await FOREVER?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/adrianno3259/reativos/commit/eaf2756bac21c773cce6302de15e783e7cd1356a#commitcomment-21999828>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJh1Cf_iraH7iD7LFMAW8Toos0GEHsVaks5r2JPjgaJpZM4NPgvf>
> .
>


This is my first R project that I helped in analyzing academic work for student research project.


core-setup is going through some transition at the moment.  i'm expecting to have the links working again today though.


For modularity, it may be worth considering putting all the packet_buffer functions into a new .c file. (ffmpeg.c is quite large already, and I believe the packet_buff definition could then be kept private to that .c file.)


Well, it's a debugging feature.  It shouldn't be used _ever_, except when
you want to experiment with something that mysteriously loses the tag bit.
Thus, the description: it breaks the security model.

2017-05-03 16:37 GMT+01:00 Brooks Davis <notifications@github.com>:

> This commit requires at least several more sentences of explanation.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/CTSRD-CHERI/cheribsd/commit/9a2b10323baca14ba6d31ba67174be8e2404b0fe#commitcomment-22000771>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABLmJ8FQEjRVk09xlTxD-Gm0fLG3ZL-oks5r2J8xgaJpZM4NPlI1>
> .
>


fixed in https://github.com/lemon5920/vue-todo-list/commit/0815dbdf4f6c94a18d466edb70fdbc3bfb785e66


But now can i not see the messages in console


If you follow that rule there's no need to fix this. I don't know if it can break well-written code that works.


Fixed c_interface DLL_PUBLIC macro usage from breaking STP's installation and from leaking internal macro definitions to the API.


Please change AlreadyExistsException  -> EntityAlreadyExistsException
You want to be as specific as possible when naming exceptions.


кто ж тебя научил ргба всюду пихать


Type on the first draft


Typo


Should be in state so React can pick up changes properly (and re-render if necessary)


correction


As long as you understand how to make them


<details>

<summary>Submitting the task to TaskCluster failed. Details</summary>

```js

bad indentation of a sequence entry at line 33, column 42:
     ... isionerId": "aws-provisioner-v1",
                                         ^
```

</details>


Partially addresses issue #12.


@MatthewJWalls <3


TeamCity OTA+ :: rvi_sota_server :: ci [Build 2471](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=30780&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 293, ignored: 3 Build time: 00:11:22


Fixed in 22b736acc5a83e3143158f47f33dc75eb2736d17.  Thanks!


это общий стиль для всех социалок


@raymanfx that would be awesome!! (getting rid of the hacks and moving past chromium-54.x.y.z) A person who works for Igalia contacted me privately on Apr 7 to point out their repository, I just haven't had time to come back to it.

It would be great to have recipes to support the latest stable release: https://www.chromium.org/developers/calendar (currently 58.0.3029.96)


Hi! I noticed you already translated the Indonesian files but didn't create a pull request to my repository
Is this ready for merge?


зачем?


movieSelect 함수는 component의 controller에서 다시 $event 파라미터 추가


Looks great to me!

On Wed, May 3, 2017 at 9:54 AM, Josh Klontz <notifications@github.com>
wrote:

> @bhklein <https://github.com/bhklein> Can I get a post-commit review on
> this? This plugs an edge case where the probe is an FTE and we'd
> potentially count it as a hit depending on the order of the gallery
> templates (since all the comparisons for this probe would be
> -std::numeric_limits<float>::max(). In practice this doesn't show up in
> our evaluations because we force the enrollment of the probe by picking a
> face detection bounding box of the whole image, and thus there are no FTEs.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/biometrics/openbr/commit/670ab1c133c091cb4cc633794252e2737358d8fb#commitcomment-22001097>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFi9GWlmGZlMb7Veh3X90j3OEKLavi4cks5r2KMmgaJpZM4NPmk3>
> .
>


This keep things easier no non smtp sysadmins that has access to search tab.


this commit displeases me


Yep... whoops. I will get this fixed asap


Can you please help me . how to set 'port' in package.json. Because i working in local. My point i want to check  'amcharts3-react-master\examples\webpack' that webpack folder in local


Your system clock appears to be off a bit... that or you can time travel.

> netblue30 committed 4 minutes from now


min


ужас


    import string
    r.append(random.choice(string.ascii_lowercase+string.digits))


#6105-HW-supplemental-heating-coil-in-AirloopHVAC-UnitarySystem-not-controlling-to-set-point (rraustad) - x86_64-MacOS-10.9-clang: OK (2489 of 2489 tests passed, 3 test warnings)

Messages:

 * 3 tests had: EIO diffs.
 * 2 tests had: ERR diffs.
 * 3 tests had: ESO small diffs.
 * 3 tests had: Table small diffs.
 * 1 test had: MTR small diffs.

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


You are welcome to fix it if you'd like to use it! :) I'm not really a regexp "expert",
was just trying to add a useful DSL wrapper that worked for most cases.


Ummmm... yeah.... there is no such thing as a `ConcurrentHashSet`. 😱

Thanks for the _correct_ improvement! 👍


лишнее


с какой радости они висят абсолютом?


False remove all new


Fixed and released in 0.10.12


what? "description" is too long???? it should not be


Hell yes!
![](http://savepic.ru/13805187.png)


стиль обертки


This commit introduced a bug, please see https://jira.bikalabs.com/browse/LIMS-2638

<img width="1080" alt="analyseauftrag_hinzufugen_" src="https://cloud.githubusercontent.com/assets/713193/25672086/8d689f2e-3032-11e7-82ad-0881993798bd.png">


I removed ing from Attacking, as it was 'Weapon Attack Centering' before and also it makes 'Horizontal' not fit in the screen.


@HonzaCech
Missing check if parent Item exists in DB


Define a String resource that has this format. Example:
`<string name="test">Repository: %$s<string>`


лично я пропагандирую margin-right'ы, по той же причине что и margin-bottom'ы


ok


Previously IDEA understood "," as a path separator, allowing to share a run configuration defining the idea.additional.classpath property between multiple machines with different OSes. Now you only understand only the OS-dependent path separator. Is that really necessary?


аутлайн в хроме


Jag håller med och ska göra ett försök, men jag är nybörjare på github.


Creo que nos conviene usar lista_t** tabla; por que despues cuando creas a cada elemento del vector tabla le asignas un puntero tipo lista y actualmente esta igualando un void a un lista_t*.


Mirko Buffoni sent them in an old (2007) bug report. I'm forwarding the original message with attachments.


Nice.


лишнее


Me parece que esta bien. Se entiende y es correcto destruir las lista inicializadas en caso de que no se pueda inicializar todas.


TeamCity Chorus :: chorus-linux64-master Continuous [Build 2.6.786.4454b5c977b50368ae674382e36cf9616696657c](http://build.palaso.org/viewLog.html?buildId=89849&buildTypeId=bt323) outcome was **UNKNOWN**
Summary: Canceled (Tests failed: 12 (12 new), passed: 816, ignored: 52) Build time: 00:11:22
### Failed tests
```
Chorus.Tests.dll: Chorus.Tests.ChorusSystemTests.CanMakeNotesBarWithOtherFiles: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.ChorusSystemTests.CanShowNotesBar: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.ChorusSystemUsage.CreateNotesBar: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.After2Syncs_HistoryHas2: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.After2Syncs_WithFilter_OnlyFilteredItemsShown: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.BeforeAnySyncing_EmptyHistory: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_GivesGoodResult: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_NoHgLockWarningWithMultipleWorkers: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_NoPreviousRepoCreation_Throws: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.GetRepositoriesToList_NoRepositoriesKnown_GivesUsb: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.InitiallyHasUsbTarget: <no details avaliable>

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


:laughing:


лишняя обертка


Comments would be great; esp. what the problem with the current code is and how this solves those problems.

Looking forward to seeing DeepBach some day!


Hi @cedricve,

So nice to hear from you!

> In mean time, before aligning with the Etcher upstream again, is there any work a round (manual approach) that may help? E.g. clean the SD card manually before flashing?

The problem is sadly caused by the image you flash, so there is not really a workaround :( I advice you to try to sync your fork as soon as possible, given there are many, many bugs we've fixed since then!


nope. This shaves ~40 seconds off the builds by caching stuff


Possibly should have more descriptive message. This reads like "oh you accidentally have 1.28, let's revert/break something"


@Vachounet  Im trying to compile standalone kernel for potter using your kernel sources and im getting this error:

 " CC      drivers/input/misc/vl53L0/stmvl53l0_module.o
In file included from drivers/input/misc/vl53L0/inc/vl53l0_api_strings.h:33:0,
                 from drivers/input/misc/vl53L0/inc/vl53l0_api.h:32,
                 from drivers/input/misc/vl53L0/stmvl53l0_module.c:40:
drivers/input/misc/vl53L0/inc/vl53l0_platform.h:37:27: fatal error: stmvl53l0-i2c.h: No such file or directory
 #include "stmvl53l0-i2c.h"
                           ^
compilation terminated."

Do you know how to fix this error? Sorry for write you here..


TeamCity Chorus :: chorus-linux64-master Continuous [Build 2.6.787.4454b5c977b50368ae674382e36cf9616696657c](http://build.palaso.org/viewLog.html?buildId=89850&buildTypeId=bt323) outcome was **UNKNOWN**
Summary: Canceled (Tests failed: 12, passed: 665, ignored: 44) Build time: 00:03:07
### Failed tests
```
Chorus.Tests.dll: Chorus.Tests.ChorusSystemTests.CanMakeNotesBarWithOtherFiles: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.ChorusSystemTests.CanShowNotesBar: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.ChorusSystemUsage.CreateNotesBar: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.After2Syncs_HistoryHas2: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.After2Syncs_WithFilter_OnlyFilteredItemsShown: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.HistoryPanelModelTests.BeforeAnySyncing_EmptyHistory: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_GivesGoodResult: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_NoHgLockWarningWithMultipleWorkers: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.AsyncLocalCheckIn_NoPreviousRepoCreation_Throws: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.GetRepositoriesToList_NoRepositoriesKnown_GivesUsb: <no details avaliable>

Chorus.Tests.dll: Chorus.Tests.SyncControlModelTests.InitiallyHasUsbTarget: <no details avaliable>

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


Yes. Thanks for notifying me.

On May 3, 2017 8:56 AM, "zwyuan" <notifications@github.com> wrote:

> should be List.fold_left (fun acc e -> if f e then acc@[e] else acc) [] l
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/pakkaliu/CS131-17S/commit/81551071456a4d0e3f9ff0ba78d73bcb4976dae7#commitcomment-22001129>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHvfBiGCPL7IanAYLIxofEqhcCLOO61zks5r2KObgaJpZM4NPmwW>
> .
>


Please do this with a PR from your fork in the future. Thanks.


@NycuRO no and why revent it?


that should be bug #1215 not #1205


Part 5


Just, to verify website for league of legends riot api.


I'll mostly put comment because i'm sure that there are better python
programmer than I am that would propose better solution.

For DeepBach, it is available on GitHub but I've done lots of modifications.
The Github version is a bit outdated.
I'll tell you if we release a new one!

On 05/03/2017 07:04 PM, Michael Scott Cuthbert wrote:
>
> Comments would be great; esp. what the problem with the current code
> is and how this solves those problems.
>
> Looking forward to seeing DeepBach some day!
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/SonyCSL-Paris/music21/commit/c6c3843686fa21bc0479f574f8d0343a6e02ea5b#commitcomment-22002549>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ALX_xIAnk4qlExKcdmM-sk_ZbvbRmA8rks5r2LO6gaJpZM4NPkby>.
>

--
Stéphane Rivaud
PhD Student
Université de Reims Champagne-Ardenne
Sony CSL
6 rue amyot
75005 Paris


sorry again! im about to copy&paste this, can i add you to my THANKS/package.json files as collaborator? or you want to be as far as possible from me? xD ty'¡ (cos i think this will not be my last copy&paste from you)


this is a major overhaul of the component structure.  the demo-server has always been somewhat difficult to maintain because it lives inside the component.  we want to be able to use a standard electrode app for the demo-server.


In case this will be forgotten, this breaks the current (and awesome) way of ChatAboveHeads in SSC (NSSC?) where the Chat also shows above the player themselves, this was a neat and a long awaited feature/fix.

Would be great if this could be added again.


thx...


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f3d5c510-3dd3-427e-80b5-f6d1ea69fef0 "QCRI"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/9abe8827-1d05-4724-974a-616e3313903f "simple-toolchain-20170502141909634") deployed [QCRI-AA](https://github.com/borisonr/QCRI-AA/releases/tag/deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-171321 "deploy-ibm-yp-us-south-BlueMetalAA-QCRI-20170503-171321") to [QCRI](https://console.ng.bluemix.net/apps/2ee94cb0-f0b3-4ab6-a5d9-3085e247e1bf "ibm:yp:us-south:BlueMetalAA:QCRI"), including this commit


Fixes issue #178
Thank you @swtaylor for the obvious solution that I simply missed.


oui


@aeschli How about a non-negative option name. e.g. showFoldIcons / renderFoldIcons which defaults to true ?


What it's actually for should have been described.  It really seems like a good way to break applications by putting tags on trash data.  It should also have been optional if it was committed (I'm not convinced it should have been.)


## Global

| Changed            |   Status |
|:-------------------|---------:|
| `coverage`         |      1.7 |
| `metadata_passing` |     29   |
| `metadata_total`   |     29   |
| `nodes_count`      |    552   |
| `texts_passing`    |     17   |
| `texts_total`      |      3   |

## Words

| Changed   |   Status |
|:----------|---------:|
| `UNK`     |    -4863 |
| `grc`     |   +31984 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg002/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg003/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg004/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg005/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg006/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg007/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg008/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg009/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg010/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg011/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg013/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg016/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg017/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg018/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-grc2.xml` | New      |
| `./data/tlg0540/tlg019/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg020/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg021/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg022/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg024/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg025/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg026/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg027/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg028/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg029/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg030/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg031/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg032/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg033/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg034/__cts__.xml`                     | New      |
| `./data/tlg0540/tlg002/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg003/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg004/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg005/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg006/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg007/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg008/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg009/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg010/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg011/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg013/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg016/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg017/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg018/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-grc2.xml` | Passing  |
| `./data/tlg0540/tlg019/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg020/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg021/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg022/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg024/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg025/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg026/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg027/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg028/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg029/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg030/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg031/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg032/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg033/__cts__.xml`                     | Passing  |
| `./data/tlg0540/tlg034/__cts__.xml`                     | Passing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/275)*


Make sure to remove the php stuff =)


I don't think we need "type = 'source'". There are binary Win/Mac packages
on CRAN. But I welcome an update to the README as a general matter.

On Tue, May 2, 2017 at 10:35 PM, David LeBauer <notifications@github.com>
wrote:

> this is an old commit, but if you weren't aware you can always edit a file
> directly in GitHub, e.g. https://github.com/nimble-dev/
> nimble/edit/devel/README.md
>
> I went ahead and did it here: #319
> <https://github.com/nimble-dev/nimble/pull/319>
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-21992990>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACYr3hK576To_tPS0284C1acgi0cEaa6ks5r1-f4gaJpZM4NO5YV>
> .
>


<details>

<summary>Submitting the task to TaskCluster failed. Details</summary>

```js

You do not have sufficient scopes. This request requires you
to have one of the following sets of scopes:
[
  [
    "secrets:get:repo:github.com/mozilla-releng/services:branch:staging"
  ]
]

You only have the scopes:
[
  "assume:repo:github.com/mozilla-releng/services:branch:taskcluster-rework",
  "queue:create-task:aws-provisioner-v1/github-worker",
  "queue:route:index.garbage.*",
  "secrets:get:garbage/*",
  "secrets:set:garbage/*"
]

In other words you are missing scopes from one of the options:
 * Option 0:
    - "secrets:get:repo:github.com/mozilla-releng/services:branch:staging"
----
method:     createTask
errorCode:  InsufficientScopes
statusCode: 403
time:       2017-05-03T17:15:38.573Z
```

</details>


Looks good!


Doesn't seem to be working. Running Alfred 3 on macOS 10.12 and I got an error that it couldn't find the Alfred 2 path. Seems like file_exists is coming up false even when the directory exists.


Is there any update on this fix?


Hmm... Having only the pics of fsww and yucu as featured images doesn't make any sense. I also don't see it as an advantage, that the titles are now under the featured picture and not above.
I guess this is some unfinished work..?


<details>

<summary>Submitting the task to TaskCluster failed. Details</summary>

```js

You do not have sufficient scopes. This request requires you
to have one of the following sets of scopes:
[
  [
    "secrets:get:repo:github.com/mozilla-releng/services:branch:taskcluster-rework"
  ]
]

You only have the scopes:
[
  "assume:repo:github.com/mozilla-releng/services:branch:taskcluster-rework",
  "queue:create-task:aws-provisioner-v1/github-worker",
  "queue:route:index.garbage.*",
  "secrets:get:garbage/*",
  "secrets:set:garbage/*"
]

In other words you are missing scopes from one of the options:
 * Option 0:
    - "secrets:get:repo:github.com/mozilla-releng/services:branch:taskcluster-rework"
----
method:     createTask
errorCode:  InsufficientScopes
statusCode: 403
time:       2017-05-03T17:17:08.816Z
```

</details>


@ctubio, absolutely! do you have a gitter? I'm planning on making some pretty sizeable changes. I'd be more than willing and interested on collaborate in a single repo. I'm über comfortable with JS, but lacking in trading knowledge.


Ah I see. Thanks for clarifying.


Yeah, this is not enough. Have you looked at [the example](https://developer.gnome.org/glib/stable/glib-Message-Logging.html#g-log-structured)?

What happens with:

```
g_log_structured (G_LOG_DOMAIN, G_LOG_LEVEL_DEBUG,
                  "MESSAGE", "%s: called",
                  G_STRLOC);


Seems possible.


@paciorek, do we still publish a slightly different version from the r-nimble.org <http://r-nimble.org/> R repository than on CRAN, with a different setting about building libnimble and/or a different tweak for calling jags or stan?  I don’t remember the exact tweaks involved.

> On May 3, 2017, at 10:15 AM, Christopher Paciorek <notifications@github.com> wrote:
>
> I don't think we need "type = 'source'". There are binary Win/Mac packages
> on CRAN. But I welcome an update to the README as a general matter.
>
> On Tue, May 2, 2017 at 10:35 PM, David LeBauer <notifications@github.com>
> wrote:
>
> > this is an old commit, but if you weren't aware you can always edit a file
> > directly in GitHub, e.g. https://github.com/nimble-dev/
> > nimble/edit/devel/README.md
> >
> > I went ahead and did it here: #319
> > <https://github.com/nimble-dev/nimble/pull/319>
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-21992990>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/ACYr3hK576To_tPS0284C1acgi0cEaa6ks5r1-f4gaJpZM4NO5YV>
> > .
> >
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-22002762>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHpCMfIvNV21EjzZxDqFL3I7A11CPvfgks5r2LYwgaJpZM4NO5YV>.
>


Or better yet `Plug 'tpope/vim-commentary`


AllowMultipleSolversToFindARoot (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2527 of 2528 tests passed, 94 test warnings)

Messages:

 * 95 tests had: EIO diffs.
 * 6 tests had: ESO small diffs.
 * 6 tests had: MTR small diffs.
 * 5 tests had: Table small diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: AUD diffs.
 * 1 test had: ERR diffs.

Failures:

regression Test Summary
 * Passed: 615
 * Failed: 1

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


Noooooooo


Hi @takatost. Can I ask you why do you need `/data/www` folder? Dockette default folder is `/srv`, is it complication?


Ping @mattbucci


This changes the response of `/alerts` in a backwards incompatible way but I don't see the corresponding change to public/js/operations.js. Is that a WIP still? If we deploy this then will make it so the "You have new unread messages" never displays?


TeamCity Chorus :: chorus-linux64-master Continuous [Build 2.6.788.4454b5c977b50368ae674382e36cf9616696657c](http://build.palaso.org/viewLog.html?buildId=89851&buildTypeId=bt323) outcome was **SUCCESS**
Summary: Tests passed: 938, ignored: 57 Build time: 00:13:36


Closes issues #157, #156, #96.


Please fix your syntax errors. This is not JavaScript.


I don't remember how we were tweaking building libnimble. At the moment in
terms of what i push up to the website, it has the rstan functionality
enabled while the CRAN version does not. I think that's the only difference
(it's the only difference I made in building 0.6-5...)

On Wed, May 3, 2017 at 1:19 PM, perrydv <notifications@github.com> wrote:

> @paciorek, do we still publish a slightly different version from the
> r-nimble.org <http://r-nimble.org/> R repository than on CRAN, with a
> different setting about building libnimble and/or a different tweak for
> calling jags or stan? I don’t remember the exact tweaks involved.
>
> > On May 3, 2017, at 10:15 AM, Christopher Paciorek <
> notifications@github.com> wrote:
> >
> > I don't think we need "type = 'source'". There are binary Win/Mac
> packages
> > on CRAN. But I welcome an update to the README as a general matter.
> >
> > On Tue, May 2, 2017 at 10:35 PM, David LeBauer <notifications@github.com
> >
> > wrote:
> >
> > > this is an old commit, but if you weren't aware you can always edit a
> file
> > > directly in GitHub, e.g. https://github.com/nimble-dev/
> > > nimble/edit/devel/README.md
> > >
> > > I went ahead and did it here: #319
> > > <https://github.com/nimble-dev/nimble/pull/319>
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/nimble-dev/nimble/commit/
> 2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-21992990>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/ACYr3hK576To_
> tPS0284C1acgi0cEaa6ks5r1-f4gaJpZM4NO5YV>
> > > .
> > >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub <
> https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2
> f979132050#commitcomment-22002762>, or mute the thread <
> https://github.com/notifications/unsubscribe-auth/
> AHpCMfIvNV21EjzZxDqFL3I7A11CPvfgks5r2LYwgaJpZM4NO5YV>.
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-22002846>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACYr3iEDWaZeEK_GZnoRNRnok2uH5LdZks5r2LcxgaJpZM4NO5YV>
> .
>


Witam


Ok, that refreshes me.  If we were tweaking libnimble in the past, apparently we aren’t doing so now.

Is the rstan enough of an issue that it is still worth explaining how someone might want to install directly from our R repo rather than CRAN?

> On May 3, 2017, at 10:22 AM, Christopher Paciorek <notifications@github.com> wrote:
>
> I don't remember how we were tweaking building libnimble. At the moment in
> terms of what i push up to the website, it has the rstan functionality
> enabled while the CRAN version does not. I think that's the only difference
> (it's the only difference I made in building 0.6-5...)
>
>
>
> On Wed, May 3, 2017 at 1:19 PM, perrydv <notifications@github.com> wrote:
>
> > @paciorek, do we still publish a slightly different version from the
> > r-nimble.org <http://r-nimble.org/> R repository than on CRAN, with a
> > different setting about building libnimble and/or a different tweak for
> > calling jags or stan? I don’t remember the exact tweaks involved.
> >
> > > On May 3, 2017, at 10:15 AM, Christopher Paciorek <
> > notifications@github.com> wrote:
> > >
> > > I don't think we need "type = 'source'". There are binary Win/Mac
> > packages
> > > on CRAN. But I welcome an update to the README as a general matter.
> > >
> > > On Tue, May 2, 2017 at 10:35 PM, David LeBauer <notifications@github.com
> > >
> > > wrote:
> > >
> > > > this is an old commit, but if you weren't aware you can always edit a
> > file
> > > > directly in GitHub, e.g. https://github.com/nimble-dev/
> > > > nimble/edit/devel/README.md
> > > >
> > > > I went ahead and did it here: #319
> > > > <https://github.com/nimble-dev/nimble/pull/319>
> > > >
> > > > —
> > > > You are receiving this because you are subscribed to this thread.
> > > > Reply to this email directly, view it on GitHub
> > > > <https://github.com/nimble-dev/nimble/commit/
> > 2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-21992990>,
> > > > or mute the thread
> > > > <https://github.com/notifications/unsubscribe-auth/ACYr3hK576To_
> > tPS0284C1acgi0cEaa6ks5r1-f4gaJpZM4NO5YV>
> > > > .
> > > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub <
> > https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2
> > f979132050#commitcomment-22002762>, or mute the thread <
> > https://github.com/notifications/unsubscribe-auth/
> > AHpCMfIvNV21EjzZxDqFL3I7A11CPvfgks5r2LYwgaJpZM4NO5YV>.
> > >
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-22002846>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/ACYr3iEDWaZeEK_GZnoRNRnok2uH5LdZks5r2LcxgaJpZM4NO5YV>
> > .
> >
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub <https://github.com/nimble-dev/nimble/commit/2d36a0d36c9ccae89036a5bdd7a7b2f979132050#commitcomment-22002898>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHpCMdVJBrv5iutyzxpZy5RCWMeX6soeks5r2LfVgaJpZM4NO5YV>.
>


closes #223


Please use more descriptive variable names


@chelmuth: please add to staging


The tabs!!!!!!


Since this is a comment on a commit itself, it probably will still be
forgotten without an issue.

On Wed, May 3, 2017 at 11:12 AM OFF <notifications@github.com> wrote:

> In case this will be forgotten, this breaks the current (and awesome) way
> of ChatAboveHeads in SSC (NSSC?) where the Chat also shows above the player
> themselves, this was a neat and a long awaited feature/fix.
>
> Would be great if this could be added again.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/NyxStudios/TShock/commit/528d9c642b08584bbeec4d1e84e992e8d0d003f8#commitcomment-22002690>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAggpzUGoBN82hnbhopMVmFSBptbbjjYks5r2LWOgaJpZM4NPkvE>
> .
>


So great!

    root@pinebook:/sys/class/axppower# ls -al
    total 0
    drwxr-xr-x  2 root root    0 May  3 17:21 .
    drwxr-xr-x 51 root root    0 May  3 17:21 ..
    -rw-r--r--  1 root root 4096 May  3 17:21 axpdebug
    -r--r--r--  1 root root 4096 May  3 17:21 bat_current_direction
    -r--r--r--  1 root root 4096 May  3 17:21 bat_temp
    -r--r--r--  1 root root 4096 May  3 17:21 batt_max_cap
    -r--r--r--  1 root root 4096 May  3 17:21 charge_on
    -r--r--r--  1 root root 4096 May  3 17:21 coulumb_counter
    -r--r--r--  1 root root 4096 May  3 17:21 disibat
    -r--r--r--  1 root root 4096 May  3 17:21 disvbat
    -r--r--r--  1 root root 4096 May  3 17:21 ext_valid
    -r--r--r--  1 root root 4096 May  3 17:21 ibat
    -r--r--r--  1 root root 4096 May  3 17:21 ic_temp
    -r--r--r--  1 root root 4096 May  3 17:21 is_on
    -r--r--r--  1 root root 4096 May  3 17:21 ocv
    -rw-r--r--  1 root root 4096 May  3 17:21 out_factory_mode
    -r--r--r--  1 root root 4096 May  3 17:21 power_sply
    -r--r--r--  1 root root 4096 May  3 17:21 rdc_show
    -rw-r--r--  1 root root 4096 May  3 17:21 regdebug
    -r--r--r--  1 root root 4096 May  3 17:21 vbat
    -rw-r--r--  1 root root 4096 May  3 17:21 vbuslimit

Thanks a lot!


fixed the "edge case" where there were only 2 nodes, obviously edges will never be greater than 1, assuming one edge per source and destination node


Your tuning gave {S(-3, -5), S(-4, -3),S(-3,  0),S(-1,  1) };
Should't you update  your KingDisAttSlope accordingly ?


same as above


fetch photo evidence <- I solved it :)


Essentially this serves the same purpose as older versions of Sunset Loader.


Thanks!


First


Second


![](https://github.trello.services/images/mini-trello-icon.png) [Se agrego el estatus a la consulta de acceso a la plataforma por parte del personal. 03/05/2017](https://trello.com/c/754gOl88/37-se-agrego-el-estatus-a-la-consulta-de-acceso-a-la-plataforma-por-parte-del-personal-03-05-2017)


This is something which we might want to instrument and make sure isn't a performance bottleneck -- ideally we could push this work into the database so that we don't incur the serialization/deserialization/data transfer overhead of transferring an entire user's message history when we really just want a couple aggregate statistics.

Especially because this endpoint is certainly the most commonly hit due to every client polling it once a second.


`state 5 times` -> `state 25 times`


I haven't found a way to make real inheritance work :/
Would prefer to make the Godot classes D classes, but they have a lot of issues: virtual methods, certain casts, and RTTI with `typeid` all implicitly access the C++ class's data, causing segfaults or branches to the wrong functions.
Inheritance itself has problems too: the D class will implicitly convert to a Godot base class when passed to a method, keeping the *same* pointer. I don't think either `alias this` or `opCast` will override inheritance in that case; we should always pass `self`, but it's easy to forget and (AFAIK) impossible to disable the implicit conversion.

Maybe there's ways to work around some of those while still using classes? I'll open an Issue tonight and write down the list of problems and potential workarounds I've thought of so far. Suggestions are definitely welcome! The way it is now "works", but isn't necessarily the best way.


Oops. Disregard this. I didn't see the file below. 😳


TeamCity libpalaso :: palaso-precise64-libpalaso-2.6 Continuous [Build 2.6.1347.2075c9f0397b6ea813efd2512b18c5b7dc077fb7](http://build.palaso.org/viewLog.html?buildId=89858&buildTypeId=PalasoPrecise64v26Cont) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:05


Should read
```
initially waiting `sleep_time` seconds, with a 2x linear backoff between each try, up to `max_sleep` seconds.
```