I don't quite like the fact that it matches the device/channel/attrs to patterns, which might have undesirable effects:

```
<paul@carl> ~/dev/ADI/libiio/build$ tests/iio_attr -a -d ad9361-phy -O -c voltage0 -b rf_port_select B
Using auto-detected IIO context at URI "usb:3.14.5"
dev 'ad9361-phy', channel 'voltage0' (output), attr 'rf_port_select', value 'A'
wrote 2 bytes to rf_port_select
dev 'ad9361-phy', channel 'voltage0' (output), attr 'rf_port_select', value 'B'
dev 'ad9361-phy', channel 'voltage0' (output), attr 'rf_port_select_available', value 'A B'
error Permission denied (-13) while writing 'rf_port_select_available' with 'B'
dev 'ad9361-phy', channel 'voltage0' (output), attr 'rf_port_select_available', value 'A B'
```

Also, the command line is not very intuitive, I end up calling "iio_attr --help" quite often.

My suggestions:

```
iio_attr
```
List all the devices of the context.
With the -u and -a options still present (to specify URI, and automatic context creation).

```
iio_attr <device>
iio_attr <device> <attr>
iio_attr <device> <attr> <value>
```
1. Print the channels and attributes of the device
2. Read the given device attribute. The \<attr\> is a wildcard unless -x is passed.
3. Write the given device attribute. The \<attr\> is not considered to be a wildcard.

```
iio_attr <device> -d
iio_attr <device> -d <attr>
iio_attr <device> -d <attr> <value>
```
Same, for device debug attributes.

```
iio_attr <device> -i <channel>
iio_attr <device> -i <channel> <attr>
iio_attr <device> -i <channel> <attr> <value>
```
The -i option specifies that we want an input channel.
1. Print the attributes of the channel
2. Read the given channel attribute. The \<attr\> is a wildcard unless -x is passed.
3. Write the given channel attribute. The \<attr\> is not considered to be a wildcard.

```
iio_attr <device> -o <channel>
iio_attr <device> -o <channel> <attr>
iio_attr <device> -o <channel> <attr> <value>
```
Same, for output channels.


#6088-User-file-showing-fatal-error-when-sizing-hot-water-coil-UA (rraustad) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1295 of 1295 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-37.66%25-green.png)


Czy trzeba ponownie skompilować i uruchomić komendą run?


@Chayes2017 Drop ในส่วนนี้ด้วยเหตุผลอะไรครับ?
แต่ไม่ควร Drop ครับเนื่องจากมีแผน Utilize ในอนาคตครับ


`try_*` methods usually imply no exceptions being raised.
Any reason to keep it as separate method in public interface at all?


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

org.genivi.sota.core.PackageUploadSpec.Copy package to other users: <no details avaliable>

```


Nie wiem, ciężko mi powiedzieć. Proszę spróbować uruchomić normalnie, nie w
tle.  Komenda z której korzystasz uruchamia program tylko raz. Po restarcie
program trzeba uruchomić ponownie.

05.05.2017 4:52 PM "Wolfman1969" <notifications@github.com> napisał(a):

> Po restarcie systemu po komendzie nohup ./ADS7846-X11 > /dev/null 2>&1 &
> dotyk nie działa.
> Czy powinien działać?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/Tomasz-Mankowski/ADS7846-X11-daemon/commit/c79453e2e1e13c772066e7fd67e777ac304c44d8#commitcomment-22033809>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQXXJzm_HSfWuZIswLD7NqDeyYKLCRjIks5r2zekgaJpZM4NL7qz>
> .
>


sigh, @dominictarr I accidentally pushed master and now I can't pull back these commits to submit as a PR,  apologies.


Fixes #133.


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


because the fieldValues dict is built on sgid roads data, which is in the current schema.  when we go to set_Value in the newFeature fgd it has the new schema - so getting the set field (index/name) for the newFeature from the dict, the indexes/filed names don't match up.


cool


Why does this require the new schema?


Thanks for the feedback.

> ONLY in the startup phase ...
> just add that bad config value to the .rc file and look what happens

Strange, in tmux (using [this config](https://github.com/chros73/rtorrent-ps_setup/blob/master/ubuntu-14.04/home/chros73/.tmux.conf)) I can't see any difference between the original version and when using this removed line version: both are borked.
At least rtorrent doesn't freeze if a wrong value is entered by accident.

I saw you've opened a ticket for it so I leave it with you. :)
Cheers


@clemens I decided to revert the optimization for the time being. See the [pull request](https://github.com/drapergem/draper/pull/801). If you want to look into these issues, I'd be more than happy to take another look.


> Now back to finding out why training isn't working properly...

Please have a look at pull request #883.


<details>

<summary>No TaskCluster jobs started for this pull request</summary>

```js

The `allowPullRequests` configuration for this repository (in `.taskcluster.yml` on the
default branch) does not allow starting tasks for this pull request.
```

</details>


Operations =,-,*,/,== Test


The name is indeed less than ideal. How about ```_multipart_encode_impl```?


Your update didn't work for me.  It looks like the TrimPrefix expression is back to front, swapping it round to: addr := strings.TrimPrefix(url.Path, "/") fixed it.

See: https://golang.org/pkg/strings/#TrimPrefix
func TrimPrefix

func TrimPrefix(s, prefix string) string
TrimPrefix returns s without the provided leading prefix string. If s doesn't start with prefix, s is returned unchanged.


Drop out เยอะมาก :-(
@Chayes2017 คือถ้าไม่ใช้ Inherit หรือ Announce ดีกว่ามั้ยอ่ะครับ
เพราะ POSAssist ถือเป็น Master Class / Super Class


@mewmew done, thanks. https://review.gerrithub.io/#/c/359830/


@ruslanvaliullin please take a look


At first glance, the rules for a number field felt too specific here,  but I suppose a default of some sort is ok. We'll see.


I would put all on one line:
```
elif [[ $OSTYPE = linux-gnu ]] ; then
```
(Sorry!)


This doesn't seem to work anymore... :c


Created #7


Issue #102  related fix


>Most tests pass.

Sry. That's a bit vague. ... I can run them and create an issue, if you want to. Because I don't know what should pass and what not, everything is just guesswork for me.

eg: I'm unable to reach any external `dat://` URL. ... So I'm not sure if they are just offline or the program doesn't work.

>We're down to our last 0.7 todos.

Cool.


The help divider rule just feels wrong to me here, I sense this is specific to the success page.


fixed via 6f478cbc578c7e821c9e913a91b7bdafab7e026e


The altnames and geocode data?  It doesn't - it can use the current schema but i'm in the process of moving all the roads data into the new schema.  I just thought you may as well have the this data in the new schema so you don't have to recreate the locators, etc when I move the sde roads into that schema - you will already be using it.  One of the next things I want to do is rewrite code to get the roads in the new schema.  but i have to rebuild our custom tools, scripts, etc too.  so it might take me some time.  and.... i want to build the new tools in Pro.  anyway, we can chat more about this.


test


It seems like you could use the offsetof macro and __attribute__((aligned(x))) to simply this.


Missed one stage of functionality
see following commit for final Stage 4


hahaha oh christ - I don't know why experimenting with new editors makes me incapable of focusing on basic style, but apparently it does!


Daniel Havlik your emails are not known to GithHb and thus it is impossible to know if you have signed the Plone Contributor Agreement, which is required to merge this pull request.

Learn about the Plone Contributor Agreement: http://docs.plone.org/develop/coredev/docs/contributors_agreement_explained.html How to add more emails to your GitHub account: https://help.github.com/articles/adding-an-email-address-to-your-github-account/


This "resize tmpfs" code should not overide the default size of the tmpfs set by the code that created it.
So, it should only be executed if some swap was found.


Thanks; not a concern for HHVM, will call the C lib instead.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/0cc42106-ce45-4c59-ad14-b983d2afbdff "JansIoT"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/273ddf74-56a1-435e-96a7-9e869bd67418 "JansIoT") deployed [JansIoT](https://github.com/ekstrom-ibm/JansIoT/releases/tag/deploy-ibm-yp-us-south-jan.ekstrom-dk.ibm.com-dev-20170505-150730 "deploy-ibm-yp-us-south-jan.ekstrom-dk.ibm.com-dev-20170505-150730") to [dev](https://console.ng.bluemix.net/apps/c346e9df-efa0-4d9d-aa04-f8a857c7a1e1 "ibm:yp:us-south:jan.ekstrom@dk.ibm.com:dev"), including this commit


Take at look at this file right?


144488793-Correct-surface-convection-calculation-6037 (lgu1234) - x86_64-MacOS-10.9-clang: OK (2489 of 2489 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)


<details>

<summary>No TaskCluster jobs started for this pull request</summary>

```js

The `allowPullRequests` configuration for this repository (in `.taskcluster.yml` on the
default branch) does not allow starting tasks for this pull request.
```

</details>


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


This commit implements figured bass conversion from Humdrum to MEI.

Example Humdrum score with the second spine `**fb` representing the figured bass content:

```
**kern	**fb	**kern
*clefF4	*	*clefG2
*k[]	*	*k[]
*M3/4	*	*M3/4
=1-	=1-	=1-
2.D	.	4dd
.	.	4.dd
.	.	8ee
=2	=2	=2
2.AA	#	2cc#
.	.	4cc#
=3	=3	=3
2.D	5	4dd
.	.	(4.dd
.	6n	.
.	.	16ccLL
.	.	16ddJJ)
=4	=4	=4
2.C	.	2ee
.	.	4ee
=5	=5	=5
2.F	.	4ff
.	.	4.ff
.	.	8gg
=6	=6	=6
2C	.	2ee
4C#	6	4ee
=7	=7	=7
4D	.	(8ddL
.	.	8cc#J)
2BB-	7	4.dd
.	6	8ee
=8	=8	=8
2.AA	#	2cc#
.	.	4cc#
=9	=9	=9
2.D	.	4dd
.	.	4.dd
.	.	8ee
=10	=10	=10
2.AA	#	2cc#
.	.	4cc#
=11	=11	=11
2.D	5	4dd
.	.	(4.dd
.	6n	.
.	.	16ccLL
.	.	16ddJJ)
=12	=12	=12
2.C	.	2ee
.	.	4ee
=13	=13	=13
2.F	.	4ff
.	.	4.ff
.	.	8gg
=14	=14	=14
4.C	.	4.ee
8C#	6	8ee
4D	.	4ff
=15	=15	=15
4GG	7 5	4dd
2AA	5 4	4.dd
.	3#	.
.	.	8cc#
=16	=16	=16
2.D	.	2.dd
=||	=||	=||
*-	*-	*-
```

Rendering with verovio (`develop-humdrum` branch):

```bash
verovio input.krn
```

MEI conversion:

```bash
verovio input.krn --all-pages --no-layout -t mei
```

```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/3.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/3.0.0/mei-all.rng" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
<mei xmlns="http://www.music-encoding.org/ns/mei" meiversion="3.0.0">
    <meiHead>
        <fileDesc>
            <titleStmt>
                <title />
            </titleStmt>
            <pubStmt />
        </fileDesc>
        <encodingDesc>
            <appInfo>
                <application isodate="2017-05-05T08:06:46" version="0.9.14-dev-0bdeb65">
                    <name>Verovio</name>

Transcoded from Humdrum

                </application>
            </appInfo>
        </encodingDesc>
        <workDesc>
            <work>
                <titleStmt>
                    <title />
                </titleStmt>
            </work>
        </workDesc>
    </meiHead>
    <music>

            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-0000000354575044">
                        <staffGrp xml:id="staffgrp-0000000781551082" symbol="brace" barthru="true">
                            <staffDef xml:id="staffdef-0000001519050122" n="1" clef.shape="G" clef.line="2" key.sig="0" meter.count="3" meter.unit="4" lines="5" />
                            <staffDef xml:id="staffdef-0000002122913468" n="2" clef.shape="F" clef.line="4" key.sig="0" meter.count="3" meter.unit="4" lines="5" />
                        </staffGrp>
                    </scoreDef>

                        <measure xml:id="measure-L7" n="1">
                            <staff xml:id="staff-L7F3N1" n="1">
                                <layer xml:id="layer-L7F3N1" n="1">
                                    <note xml:id="note-L8F3" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L8F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L9F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L9F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L10F3" dur="8" oct="5" pname="e">
                                        <accid xml:id="accid-L10F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L7F1N1" n="2">
                                <layer xml:id="layer-L7F1N1" n="1">
                                    <note xml:id="note-L8F1" dots="1" dur="2" oct="3" pname="d">
                                        <accid xml:id="accid-L8F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L11" n="2">
                            <staff xml:id="staff-L11F3N1" n="1">
                                <layer xml:id="layer-L11F3N1" n="1">
                                    <note xml:id="note-L12F3" dur="2" oct="5" pname="c">
                                        <accid xml:id="accid-L12F3" accid="s" />
                                    </note>
                                    <note xml:id="note-L13F3" dur="4" oct="5" pname="c">
                                        <accid xml:id="accid-L13F3" accid.ges="s" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L11F1N1" n="2">
                                <layer xml:id="layer-L11F1N1" n="1">
                                    <note xml:id="note-L12F1" dots="1" dur="2" oct="2" pname="a">
                                        <accid xml:id="accid-L12F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L12F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000001815006827">
                                    <f xml:id="f-0000001962019401">♯</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L14" n="3">
                            <staff xml:id="staff-L14F3N1" n="1">
                                <layer xml:id="layer-L14F3N1" n="1">
                                    <note xml:id="note-L15F3" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L15F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L16F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L16F3" accid.ges="n" />
                                    </note>
                                    <beam xml:id="beam-L18F3-L19F3">
                                        <note xml:id="note-L18F3" dur="16" oct="5" pname="c">
                                            <accid xml:id="accid-L18F3" accid.ges="n" />
                                        </note>
                                        <note xml:id="note-L19F3" dur="16" oct="5" pname="d">
                                            <accid xml:id="accid-L19F3" accid.ges="n" />
                                        </note>
                                    </beam>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L14F1N1" n="2">
                                <layer xml:id="layer-L14F1N1" n="1">
                                    <note xml:id="note-L15F1" dots="1" dur="2" oct="3" pname="d">
                                        <accid xml:id="accid-L15F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <slur xml:id="slur-L16F3-L19F3N1" staff="1" startid="#note-L16F3" endid="#note-L19F3" />
                            <harm xml:id="harm-L15F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000001529310048">
                                    <f xml:id="f-0000002029689440">5</f>
                                </fb>
                            </harm>
                            <harm xml:id="harm-L17F2" place="below" staff="2" tstamp="2.750000">
                                <fb xml:id="fb-0000000573499599">
                                    <f xml:id="f-0000000901152657">6♮</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L20" n="4">
                            <staff xml:id="staff-L20F3N1" n="1">
                                <layer xml:id="layer-L20F3N1" n="1">
                                    <note xml:id="note-L21F3" dur="2" oct="5" pname="e">
                                        <accid xml:id="accid-L21F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L22F3" dur="4" oct="5" pname="e">
                                        <accid xml:id="accid-L22F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L20F1N1" n="2">
                                <layer xml:id="layer-L20F1N1" n="1">
                                    <note xml:id="note-L21F1" dots="1" dur="2" oct="3" pname="c">
                                        <accid xml:id="accid-L21F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L23" n="5">
                            <staff xml:id="staff-L23F3N1" n="1">
                                <layer xml:id="layer-L23F3N1" n="1">
                                    <note xml:id="note-L24F3" dur="4" oct="5" pname="f">
                                        <accid xml:id="accid-L24F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L25F3" dots="1" dur="4" oct="5" pname="f">
                                        <accid xml:id="accid-L25F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L26F3" dur="8" oct="5" pname="g">
                                        <accid xml:id="accid-L26F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L23F1N1" n="2">
                                <layer xml:id="layer-L23F1N1" n="1">
                                    <note xml:id="note-L24F1" dots="1" dur="2" oct="3" pname="f">
                                        <accid xml:id="accid-L24F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L27" n="6">
                            <staff xml:id="staff-L27F3N1" n="1">
                                <layer xml:id="layer-L27F3N1" n="1">
                                    <note xml:id="note-L28F3" dur="2" oct="5" pname="e">
                                        <accid xml:id="accid-L28F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L29F3" dur="4" oct="5" pname="e">
                                        <accid xml:id="accid-L29F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L27F1N1" n="2">
                                <layer xml:id="layer-L27F1N1" n="1">
                                    <note xml:id="note-L28F1" dur="2" oct="3" pname="c">
                                        <accid xml:id="accid-L28F1" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L29F1" dur="4" oct="3" pname="c">
                                        <accid xml:id="accid-L29F1" accid="s" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L29F2" place="below" staff="2" tstamp="3.000000">
                                <fb xml:id="fb-0000001285877614">
                                    <f xml:id="f-0000001617118737">6</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L30" n="7">
                            <staff xml:id="staff-L30F3N1" n="1">
                                <layer xml:id="layer-L30F3N1" n="1">
                                    <beam xml:id="beam-L31F3-L32F3">
                                        <note xml:id="note-L31F3" dur="8" oct="5" pname="d">
                                            <accid xml:id="accid-L31F3" accid.ges="n" />
                                        </note>
                                        <note xml:id="note-L32F3" dur="8" oct="5" pname="c">
                                            <accid xml:id="accid-L32F3" accid="s" />
                                        </note>
                                    </beam>
                                    <note xml:id="note-L33F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L33F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L34F3" dur="8" oct="5" pname="e">
                                        <accid xml:id="accid-L34F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L30F1N1" n="2">
                                <layer xml:id="layer-L30F1N1" n="1">
                                    <note xml:id="note-L31F1" dur="4" oct="3" pname="d">
                                        <accid xml:id="accid-L31F1" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L33F1" dur="2" oct="2" pname="b">
                                        <accid xml:id="accid-L33F1" accid="f" />
                                    </note>
                                </layer>
                            </staff>
                            <slur xml:id="slur-L31F3-L32F3N1" staff="1" startid="#note-L31F3" endid="#note-L32F3" />
                            <harm xml:id="harm-L33F2" place="below" staff="2" tstamp="2.000000">
                                <fb xml:id="fb-0000001040542039">
                                    <f xml:id="f-0000001430711952">7</f>
                                </fb>
                            </harm>
                            <harm xml:id="harm-L34F2" place="below" staff="2" tstamp="3.500000">
                                <fb xml:id="fb-0000000986220941">
                                    <f xml:id="f-0000001136567841">6</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L35" n="8">
                            <staff xml:id="staff-L35F3N1" n="1">
                                <layer xml:id="layer-L35F3N1" n="1">
                                    <note xml:id="note-L36F3" dur="2" oct="5" pname="c">
                                        <accid xml:id="accid-L36F3" accid="s" />
                                    </note>
                                    <note xml:id="note-L37F3" dur="4" oct="5" pname="c">
                                        <accid xml:id="accid-L37F3" accid.ges="s" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L35F1N1" n="2">
                                <layer xml:id="layer-L35F1N1" n="1">
                                    <note xml:id="note-L36F1" dots="1" dur="2" oct="2" pname="a">
                                        <accid xml:id="accid-L36F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L36F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000002029979763">
                                    <f xml:id="f-0000000797176852">♯</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L38" n="9">
                            <staff xml:id="staff-L38F3N1" n="1">
                                <layer xml:id="layer-L38F3N1" n="1">
                                    <note xml:id="note-L39F3" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L39F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L40F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L40F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L41F3" dur="8" oct="5" pname="e">
                                        <accid xml:id="accid-L41F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L38F1N1" n="2">
                                <layer xml:id="layer-L38F1N1" n="1">
                                    <note xml:id="note-L39F1" dots="1" dur="2" oct="3" pname="d">
                                        <accid xml:id="accid-L39F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L42" n="10">
                            <staff xml:id="staff-L42F3N1" n="1">
                                <layer xml:id="layer-L42F3N1" n="1">
                                    <note xml:id="note-L43F3" dur="2" oct="5" pname="c">
                                        <accid xml:id="accid-L43F3" accid="s" />
                                    </note>
                                    <note xml:id="note-L44F3" dur="4" oct="5" pname="c">
                                        <accid xml:id="accid-L44F3" accid.ges="s" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L42F1N1" n="2">
                                <layer xml:id="layer-L42F1N1" n="1">
                                    <note xml:id="note-L43F1" dots="1" dur="2" oct="2" pname="a">
                                        <accid xml:id="accid-L43F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L43F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000000763057315">
                                    <f xml:id="f-0000002079436968">♯</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L45" n="11">
                            <staff xml:id="staff-L45F3N1" n="1">
                                <layer xml:id="layer-L45F3N1" n="1">
                                    <note xml:id="note-L46F3" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L46F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L47F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L47F3" accid.ges="n" />
                                    </note>
                                    <beam xml:id="beam-L49F3-L50F3">
                                        <note xml:id="note-L49F3" dur="16" oct="5" pname="c">
                                            <accid xml:id="accid-L49F3" accid.ges="n" />
                                        </note>
                                        <note xml:id="note-L50F3" dur="16" oct="5" pname="d">
                                            <accid xml:id="accid-L50F3" accid.ges="n" />
                                        </note>
                                    </beam>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L45F1N1" n="2">
                                <layer xml:id="layer-L45F1N1" n="1">
                                    <note xml:id="note-L46F1" dots="1" dur="2" oct="3" pname="d">
                                        <accid xml:id="accid-L46F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <slur xml:id="slur-L47F3-L50F3N1" staff="1" startid="#note-L47F3" endid="#note-L50F3" />
                            <harm xml:id="harm-L46F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000000602233296">
                                    <f xml:id="f-0000000644577561">5</f>
                                </fb>
                            </harm>
                            <harm xml:id="harm-L48F2" place="below" staff="2" tstamp="2.750000">
                                <fb xml:id="fb-0000001415392908">
                                    <f xml:id="f-0000000832246937">6♮</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L51" n="12">
                            <staff xml:id="staff-L51F3N1" n="1">
                                <layer xml:id="layer-L51F3N1" n="1">
                                    <note xml:id="note-L52F3" dur="2" oct="5" pname="e">
                                        <accid xml:id="accid-L52F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L53F3" dur="4" oct="5" pname="e">
                                        <accid xml:id="accid-L53F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L51F1N1" n="2">
                                <layer xml:id="layer-L51F1N1" n="1">
                                    <note xml:id="note-L52F1" dots="1" dur="2" oct="3" pname="c">
                                        <accid xml:id="accid-L52F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L54" n="13">
                            <staff xml:id="staff-L54F3N1" n="1">
                                <layer xml:id="layer-L54F3N1" n="1">
                                    <note xml:id="note-L55F3" dur="4" oct="5" pname="f">
                                        <accid xml:id="accid-L55F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L56F3" dots="1" dur="4" oct="5" pname="f">
                                        <accid xml:id="accid-L56F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L57F3" dur="8" oct="5" pname="g">
                                        <accid xml:id="accid-L57F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L54F1N1" n="2">
                                <layer xml:id="layer-L54F1N1" n="1">
                                    <note xml:id="note-L55F1" dots="1" dur="2" oct="3" pname="f">
                                        <accid xml:id="accid-L55F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L58" n="14">
                            <staff xml:id="staff-L58F3N1" n="1">
                                <layer xml:id="layer-L58F3N1" n="1">
                                    <note xml:id="note-L59F3" dots="1" dur="4" oct="5" pname="e">
                                        <accid xml:id="accid-L59F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L60F3" dur="8" oct="5" pname="e">
                                        <accid xml:id="accid-L60F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L61F3" dur="4" oct="5" pname="f">
                                        <accid xml:id="accid-L61F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L58F1N1" n="2">
                                <layer xml:id="layer-L58F1N1" n="1">
                                    <note xml:id="note-L59F1" dots="1" dur="4" oct="3" pname="c">
                                        <accid xml:id="accid-L59F1" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L60F1" dur="8" oct="3" pname="c">
                                        <accid xml:id="accid-L60F1" accid="s" />
                                    </note>
                                    <note xml:id="note-L61F1" dur="4" oct="3" pname="d">
                                        <accid xml:id="accid-L61F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L60F2" place="below" staff="2" tstamp="2.500000">
                                <fb xml:id="fb-0000001823454365">
                                    <f xml:id="f-0000000058386218">6</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L62" n="15">
                            <staff xml:id="staff-L62F3N1" n="1">
                                <layer xml:id="layer-L62F3N1" n="1">
                                    <note xml:id="note-L63F3" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L63F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L64F3" dots="1" dur="4" oct="5" pname="d">
                                        <accid xml:id="accid-L64F3" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L66F3" dur="8" oct="5" pname="c">
                                        <accid xml:id="accid-L66F3" accid="s" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L62F1N1" n="2">
                                <layer xml:id="layer-L62F1N1" n="1">
                                    <note xml:id="note-L63F1" dur="4" oct="2" pname="g">
                                        <accid xml:id="accid-L63F1" accid.ges="n" />
                                    </note>
                                    <note xml:id="note-L64F1" dur="2" oct="2" pname="a">
                                        <accid xml:id="accid-L64F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <harm xml:id="harm-L63F2" place="below" staff="2" tstamp="1.000000">
                                <fb xml:id="fb-0000001027827828">
                                    <f xml:id="f-0000000343848728">7</f>
                                    <f xml:id="f-0000000294121925">5</f>
                                </fb>
                            </harm>
                            <harm xml:id="harm-L64F2" place="below" staff="2" tstamp="2.000000">
                                <fb xml:id="fb-0000001941858648">
                                    <f xml:id="f-0000001509313477">5</f>
                                    <f xml:id="f-0000000814436641">4</f>
                                </fb>
                            </harm>
                            <harm xml:id="harm-L65F2" place="below" staff="2" tstamp="2.750000">
                                <fb xml:id="fb-0000001138693773">
                                    <f xml:id="f-0000001799464394">3♯</f>
                                </fb>
                            </harm>
                        </measure>
                        <measure xml:id="measure-L67" n="16" right="dbl">
                            <staff xml:id="staff-L67F3N1" n="1">
                                <layer xml:id="layer-L67F3N1" n="1">
                                    <note xml:id="note-L68F3" dots="1" dur="2" oct="5" pname="d">
                                        <accid xml:id="accid-L68F3" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                            <staff xml:id="staff-L67F1N1" n="2">
                                <layer xml:id="layer-L67F1N1" n="1">
                                    <note xml:id="note-L68F1" dots="1" dur="2" oct="3" pname="d">
                                        <accid xml:id="accid-L68F1" accid.ges="n" />
                                    </note>
                                </layer>
                            </staff>
                        </measure>

                </score>
            </mdiv>

    </music>
</mei>
```


Thanks!


I realise I used the wrong 'to'


#6088-User-file-showing-fatal-error-when-sizing-hot-water-coil-UA (rraustad) - i386-Windows-7-VisualStudio-14: OK (2493 of 2495 tests passed, 0 test warnings)

Messages:

 * 2 tests had: EIO diffs.
 * 2 tests had: ESO big diffs.
 * 2 tests had: MTR big diffs.
 * 2 tests had: Table big diffs.

Failures:

regression Test Summary
 * Passed: 597
 * Failed: 2

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


merken? :P


Created functionality as requested in Stage 4. In addition to requested classes I also created a marina management class, so that this could keep a record of all people, boats and marinas added to the system, to facilitate some of the requested functionality. References to the objects created in these arraylists can then be passed to the arraylists in classes such as marina and boat, such that associations are created.


Yeah sorry, I hadn't pushed this yet @joeferraro


hasMaterialProperty will return _false_ in the constructor of the material that provides to property comes _later_ in the input file (hence the _construction order_ comment). We absolutely want to avoid this behavior in moose, as we want to support input file generators that may not offer the option of ordering blocks (like peacock).
It also introduces to possibility of very subtle and hard to find user errors (if the ordering is wrong).


@bear101 Yes, I downloaded it and will test.


Nope! Made it possible to handle virtual inheritance cases. Decreases overall performance.


hi


zwraca prawdę jeżeli użytkownik jest null?


Done in https://github.com/xwiki/xwiki-platform/commit/9a8111e7d406d6e48ac752fdb94eadf189547abe. Thanks!


TeamCity WeSay1.5 :: wesay1.6-win32-continuous [Build 1.6.24.3840e21696bad6ce2d203d019a0b60b7ba2cf4a1](http://build.palaso.org/viewLog.html?buildId=90150&buildTypeId=bt170) outcome was **FAILURE**
Summary: Execution timeout (new); tests failed: 1 (1 new), passed: 1423, ignored: 31 Build time: 01:15:35
### Failed tests
```
Addin.Transform.Tests.dll: Addin.Transform.Tests.PdfMakerTests.CreatePDF: <no details avaliable>

```


Is it just me or does that feel better lol?


I've just had a weird idea. Since scripts, movetypes, and units are (almost) 1:1:1, Instead of a pool, it may be possible to reserve the space inside CUnit. This should help wrt cache misses.


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


That's what I thought, too.


Is vectorcall still relevant? :D


does his have units?


```python
def enter(self, player):
  # any decision the play makes you store it here
  # example player choose weapon
  player.weapon = weapon he chose
```


Seeing if the email would send, hopefully I can build a interval over the weekend instead of 20==20 or random numbers


Could've inline'd it for faster code.


Hey - just FYI - in Eagle 8 a library search for "WS2812" yields "Sorry, no match!". For some reason the component names you have entered require an asterisk at the end to be found. A search on "WS2812B*" works. For other components that is not necessary.


Nice Reverse Inspect!
Is there a way to switch it off ?


[R/RLearner_oneclass_ksvm.R:8:75:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/R/RLearner_oneclass_ksvm.R#L8) *warning:* **Unneded concatenation of a constant. Remove the "c" call.**
```r
      makeDiscreteLearnerParam(id = "type", default = "one-svc", values = c("one-svc")),
                                                                          ^
```
[R/RLearner_oneclass_ksvm.R:43:32:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/R/RLearner_oneclass_ksvm.R#L43) *style:* **Commas should always have a space after.**
```r
    sv = d[kernlab::SVindex(m),]
                               ^
```
[R/RLearner_oneclass_ksvm.R:49:32:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/R/RLearner_oneclass_ksvm.R#L49) *style:* **Commas should always have a space after.**
```r
    sv = d[kernlab::SVindex(m),]
                               ^
```
[R/RLearner_oneclass_ksvm.R:58:3:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/R/RLearner_oneclass_ksvm.R#L58) *style:* **Variable or function name should be dotted.case.**
```r
  Ktest = kernlab::as.kernelMatrix(crossprod(t(.newdata), t(.model$learner.model$sv)))
  ^~~~~
```
[R/StackedLearner.R:556:50:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/R/StackedLearner.R#L556) *style:* **Do not place spaces around code in parentheses or square brackets.**
```r
      m = makeLearner("regr.nnet", predict.type = )
                                                 ^
```
[tests/testthat/test_base_learnerArgsToControl.R:15:21:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/tests/testthat/test_base_learnerArgsToControl.R#L15) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  arg1 = quote(expr =)
                    ^~
```
[tests/testthat/test_base_learnerArgsToControl.R:16:21:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/tests/testthat/test_base_learnerArgsToControl.R#L16) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  arg2 = quote(expr =)
                    ^~
```
[tests/testthat/test_base_learnerArgsToControl.R:41:23:](https://github.com/mlr-org/mlr/blob/86fe97c6ff76782d45bdc7eb00f46513740b6900/tests/testthat/test_base_learnerArgsToControl.R#L41) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  devmax = quote(expr =)
                      ^~
```


I'm not surprised. I've not used ProofGeneral much since this was authored. (I moved to coquille in Vim)


You can check for yorself: create a directory with decent amount of files (the fastest way to do so is by writing a shell script and running it somewhere on SD card). Now trigger deletion of the directory and look at it's contents before they are gone.

On May 5, 2017 8:21:50 PM GMT+07:00, Vishal Nehra <notifications@github.com> wrote:
>But I'm returning from onEvent on anything except when the events are
>create/delete or modify. I also saw the logs and onEvent had lots of
>callbacks for reads. But as I'm filtering for these events, do you
>think debouncing will still be that relevant? I'm yet to see logs for
>#registerContentObserver though, but events should still remain the
>same.
>
>--
>You are receiving this because you were mentioned.
>Reply to this email directly or view it on GitHub:
>https://github.com/arpitkh96/AmazeFileManager/commit/7c293a63630596fdfc84468e889c986a7d73f723#commitcomment-22032528

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Turns the checkbox into an animated processing icon.


Since you are now using ExecutionContext I don't think it really make sense to keep going trough ModelBridge. IMO you should get rid of the setContextProperty/getContextProperty methods you introduced.


I've squashed the 4 commits into one commit: https://github.com/graphhopper/graphhopper/commit/4d442076c63c38b651c5cd64b3c157695164d3b8

Have tested a few things and seems to work for those and feels also faster - thanks!

I will update the command here to use the graphhopper.sh script (?) https://github.com/graphhopper/graphhopper/tree/pt/reader-gtfs#quick-start


Turns the animated processing icon back into the checkbox.


np


ToDo: make 100% sure it returns the same numbers


True. Fixed in repo.


I doubt it, but still


Mas java e outras linguagens que eu conheço também tem OO, pra ser expressivo não tem que ser algo que tem em uma linguagem e não tem na outra?


I'll inline it.


#sign-off


I'll check it out, thanks. I've only had problems with PG.


@dkluin Neat.


Oh shit! ❤ @jasonlally.


Ok, will do. How do we match them? Like, file trees inside the archives should be the same?


Smalltalk é mais radical no significado de OO.
Tente descobrir exemplos de coisas que são objetos em Smalltalk e não são objetos em outras linguagens (C++,Java,etc).
Depois mostre, com mais exemplos, porque essas diferenças podem ser interessantes.


@rexim 🐐


Thanks ;-) fixed "my" issue.


Hello ! What you mean commas ','. (individual codes with commas). To run multiple codes in a sequence, separate the individual codes with commas make configuration.yaml file error. what is right way like 565874,233555,149874 or '565874,'233555,'149874.


@julianlam the code that uses it is here: https://github.com/boomzillawtf/tdwtf/blob/e7dc6f378401c3b61f4230b04b51b800a36dbae0/plugins/nodebb-plugin-tdwtf-customizations/custom.js#L123-L140

I remember fixing it at some point to always make the time difference count as the past.


And blink haven't href at all.  Isn't it?

5 мая 2017 г. 21:18 пользователь "Pooya Parsa" <notifications@github.com>
написал:

> @mosinve <https://github.com/mosinve> dropdown-item.vue is extending bLink
> ;)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/bootstrap-vue/bootstrap-vue/commit/31876063ee2ec7184991427459294d0ea52c8ba0#commitcomment-22033364>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AUA6xggqGPqmOoOdsTPxxbFKSWODawSnks5r2y_EgaJpZM4NR7xr>
> .
>


Ok. I didn't want to get ahead of ourselves and accomplish one thing at a time but it sounds like you are close to switching everything to the new schema. If that's the case, shouldn't the other grinder do that work. It seems like you're mixing the responsibility of the two.


This doesn't make it easier to understand - we first run `if new in new_labels` and then `if new in all_labels` - why? `all_labels` includes `new_labels`

It either has to be `new not in base_labels` or rewored completely


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


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/ed6bf748-aad5-4dae-8ce8-51f06e59f0a7 "Victoria-Mobile-App-Backend"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/c99112a8-1124-4c5c-870a-989bccd45dd8 "Victoria-Mobile-App-Backend") deployed [Victoria-Mobile-App-Backend](https://github.com/cvilla31/Victoria-Mobile-App-Backend/releases/tag/deploy-ibm-yp-us-south-Victoria-Seguros-dev-20170505-153306 "deploy-ibm-yp-us-south-Victoria-Seguros-dev-20170505-153306") to [dev](https://console.ng.bluemix.net/apps/e1a6b4d9-f165-4620-82db-c8d362164dbe "ibm:yp:us-south:Victoria Seguros:dev"), including this commit


We're checking for this twice. Why won't we do:
```
if all_labels[old] != all_labels[new]:
    if new in new_labels:
        self.log.warning("labels %r=%r and %r=%r should probably have same value",
old, all_labels[old], new, all_labels[new])
    else:
         add_as_an_alias(old, new)
```
for clarity?


![](https://github.trello.services/images/mini-trello-icon.png) [initializer list to string conversion for configuring list](https://trello.com/c/Go54PXJ9/11-initializer-list-to-string-conversion-for-configuring-list)


yes you right.


我用的就是你的这个主题 最近也想加个评论的功能呢


can we get this list dynamically from https://github.com/raccoongang/xblock-video/blob/3d210477e14ebea73900bcb8181e16fad8133b43/setup.py#L53-L58 ?


add score statistics


[dpkg](open)


#open


Tole datoteko pobriši, saj pravi, naj se datoteka `uvoz.r` v mapi `uvoz` ne dodaja v git. Trenutno tako datoteko sicer že imaš, tako da to zaenkrat nima vpliva - če pa bi jo kdaj pobrisal, pa bi s tem preprečil ponovno dodajanje.


все же запутался как тут правильно сделать. Третий вариант разве что заюзать if(msg.gas < tx.gasprice), но это не правильно ж вроде?!
Вариант, что каждый сам забирает сам свои деньги, если выиграл. Думаю можно сделать как тут -https://github.com/ConsenSys/smart-contract-best-practices#favor-pull-over-push-payments . Но правильная ли это реализация будет? потому что в условиях задачи оно вроде само должно разруливать


update


Was it holding back a lot of water?


Why isn't this just a [Fisher-Yates shuffle](https://en.wikipedia.org/wiki/Fisher%E2%80%93Yates_shuffle)?

E.g. Something like https://bitbucket.org/snippets/dchapes/MK7xe


ever heard of forking the repo? because if you're not smart enough to do that there's no way you're smart enough to make a device tree


@vondele Nah, I think it's a functional patch because it changes lazy eval.


What about builds that don't have configs?


JAJAJAJA, ni me di cuenta que se me paso eso, la mala costumbre de Yapo


Why do you duplicate this line ?


![](https://github.trello.services/images/mini-trello-icon.png) [OAUTH instead of email.](https://trello.com/c/qiQDYJoZ/73-oauth-instead-of-email)


Pero Pq nerken, me intriga jaja

On Fri, May 5, 2017, 12:43 PM Adrián Salgado <notifications@github.com>
wrote:

> JAJAJAJA, ni me di cuenta que se me paso eso, la mala costumbre de Yapo
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/LasagnaAndroid/Weather/commit/62deaddce2faef290479ee452636fbcfd6757af0#commitcomment-22034502>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAyV5giyVR1tjnsMnBHGZlkd5ZUopxIAks5r20OQgaJpZM4NSDE7>
> .
>


Why not use the RelaxedX509ExtendedTrustManager ?


sure it is functional, but simplifications can be functional, and in that case they are tested [-3,1] at both STC and LTC. Remains open if this is a simplification.


Не обязательно что б они сами именно забирали. Главное добиться того что б выплату можно было разбить на куски стоящие константное количество газа. Можно например что б любой желающий потратить газ заказівал выплату поочередно для каждого победившего.


Es el nombre del proyecto de rediseño, y la costumbre es colocar en los commits el nombre de la rama/feature en la que estas trabajando.


This line seems to have been left here as a mistake :)


Bluemix [toolchain](https://dev-console.stage1.ng.bluemix.net/devops/toolchains/382868a9-b26f-4d3b-9cff-6ff649bbd4e7 "simple-toolchain-20170428071916785"): [Delivery Pipeline](https://dev-console.stage1.ng.bluemix.net/devops/pipelines/8a97d6dd-fd1c-4d6e-8e48-3c7903ffecbf "simple-toolchain-20170428071916785") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154514 "deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154514") to [dev](https://console.stage1.ng.bluemix.net/apps/e43a052b-ddfa-4fad-9014-8bcc352d78e2 "ibm:ys1:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/05660c97-90f6-4fc9-8228-73793dc2ff09 "yp-03-28"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/009464cd-9c4d-41e0-b935-12e8ad454123 "pipeline_03-28") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-yp-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154514 "deploy-ibm-yp-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154514") to [dev](https://console.ng.bluemix.net/apps/8282e2ff-c4ec-48fd-9d74-6647e440a4e5 "ibm:yp:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Bluemix [toolchain](https://dev-console.stage1.ng.bluemix.net/devops/toolchains/7e05faa7-0ce6-4eb4-95c4-48372d15c85d "simple-toolchain-20170505153750634"): [Delivery Pipeline](https://dev-console.stage1.ng.bluemix.net/devops/pipelines/dd12b740-5289-4cd6-b6e5-5daef1b76238 "simple-toolchain-20170505153750634") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154519 "deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-154519") to [dev](https://console.stage1.ng.bluemix.net/apps/9bdab6e0-e43f-48f3-9c20-0fc3264e039f "ibm:ys1:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Pra nada, hehe. Já corrigi.


`if(msg.gas < tx.gasprice)` тут ты мешаешь бензин с ценой на бензин.


I don't think it makes sense to change this: that code is already wrong anyway


Yeah I saw the NextGenGrinder class in there and thought that would work
for me as a code base for that project. Though i only forsee needing that
code/functionality for 6 months or so as we duel publish both schemas. If
that's too temporary for you I can create a new project.  Either way. It
will probably be a forklift project (?).  I have a python project that
pushes the schema now but I want rewrite it in c#.

On May 5, 2017 9:31 AM, "steveoh" <notifications@github.com> wrote:

> Ok. I didn't want to get ahead of ourselves and accomplish one thing at a
> time but it sounds like you are close to switching everything to the new
> schema. If that's the case, shouldn't the other grinder do that work. It
> seems like you're mixing the responsibility of the two.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/gregbunce/RoadGrinder/commit/2cc39ebccce91ef70734cb0bf7bb4266160e77b9#commitcomment-22034331>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQH4TDIt_ZBaahXPk8wQKMUeAJKGLcTsks5r20DmgaJpZM4NRXpM>
> .
>


I'll submit a variation of this idea soon. Tested a bit locally and it seems more promising.


That setq is a no-op (I added the FIXME when making unrelated changes)


Great start :D


I think yes, but that's way beyond current scope.


I'll experiment with that approach for CommandAI's, which are next up.


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


ref_ground_temp_obj_type (nmerket) - x86_64-MacOS-10.10-clang: Build Failed

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


I believe that the most important thing here is the addition of & tegra_i2s_device0,


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/e0756d5f-6fd0-4aa4-afaa-8dcc9a050af0 "sodashboard"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d99cd32f-a498-4ed1-bd35-5538ef4b6265 "sodashboard") deployed [sodashboard](https://github.com/ibm-cds-labs/sodashboard/releases/tag/deploy-ibm-yp-us-south-Dev-Advocates-cds-demo-20170505-154958 "deploy-ibm-yp-us-south-Dev-Advocates-cds-demo-20170505-154958") to [cds-demo](https://console.ng.bluemix.net/apps/b1a83962-c2c2-4fa9-9fb3-a841d4e8f1b4 "ibm:yp:us-south:Dev-Advocates:cds-demo"), including this commit


Looks like we should remove that, plus the two identical ones in the block
below. Want to PR it? Not at my PC right now

On 5 May 2017 at 15:38, SquidDev <notifications@github.com> wrote:

> When equipping a peripheral, the redstone status will get cleared due to
> these lines
> <https://github.com/dan200/ComputerCraft/blob/master/src/main/java/dan200/computercraft/shared/turtle/core/TurtleBrain.java#L980-L981>.
> I don't know if that is still the intended behaviour after this change or
> not.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/dan200/ComputerCraft/commit/8abff95441b87df733df839eca6c373513e0487b#commitcomment-22033607>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AB3bbKZadawPeb-Hjlk2juP2CNNSx4lAks5r2zRygaJpZM4NSASG>
> .
>


@Tratcher FYI: If you add `<LangVersion>5</LangVersion>` to a property group in your `Common.targets` file, it should make Visual Studio limit you to using syntax supported in C# 5.0 or below.  Once your build infrastructure supports C# 6, you just bump the number up. This solution has worked quite well for me.


I would suggest displaying this as `block` as well...just like you did with the `#posts`


A local 4+0.04 test started off this way:
Score of dev vs base: 464 - 410 - 1207  [0.513] 2081
ELO difference: 9.02 +/- 9.66
SPRT: llr 1.34, lbound -2.2, ubound 2.2


It was a debug trace ; will fix it now.


like seeing the `width:100%` here...nice work!


Great catch...setting the image to `width:100%!`


I'll just remove that line, and put the underscores back in the variable
names; that was what was in PG/xml before merging 157.

On Fri, May 5, 2017 at 11:46 AM, Clément Pit-Claudel <
notifications@github.com> wrote:

> That setq is a no-op (I added the FIXME when making unrelated changes)
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/ProofGeneral/PG/commit/2e65d37c12e9378db479c2db782c38b4b6ba16e3#commitcomment-22034573>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACJAKN7h8Avz4MG-POX0n9BWmtOYQqG7ks5r20Q_gaJpZM4NSFwJ>
> .
>


And then I even tried to be nice and tell him I would help with Github and got nothing but attitude , fuck it. Let him be known as kang banger


Next version will be interactive and add options to filters by OU, rather than full ad domain. May add option to import computers from txt or csv file


My PR https://github.com/crystal-lang/crystal/pull/3595 is obviously out of date but I was wondering if/when we are considering adding IO select actions to crystal.


#6088-User-file-showing-fatal-error-when-sizing-hot-water-coil-UA (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.49%25-green.png)


144935867-User-file-with-RoomAirSettingsAirflowNetwork-is-failing-with-fatal-error-#6086 (EnergyArchmage) - x86_64-MacOS-10.9-clang: OK (2488 of 2488 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)


> what is the breaking change(s) in this release?

It was this commit: https://github.com/mafintosh/hypercore/commit/b90871badcf0de9ae3e94fcb6c70a13b225a13f2

The change broke old hashes, so they couldn't be properly verified/created/something.


Awww yisss.


These classes had been removed when I figured out the built-in margin classes... can you remove please?


The values are untuned.


#6088-User-file-showing-fatal-error-when-sizing-hot-water-coil-UA (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)


Np! Sorry about that


Don't think you've added the favicon image itself have you?


this is check if the new even exists and is more clearer to search it in all_labels, than only in base_labels (and keeping in mind that we already searched new_labels before)


Can't fix stupid. I figure'd you knew this by now Dustin LMAO


Is there performance difference?


Wasn't my fault.  It was GitHubs.


Weird, I did a `git add -A` but yeah it didn't get added, doing that now.


Also we should use PNG rather than ico files now that they're widely supported


we are checking twice because it depends if where is it, as if it is new_labels it takes precedence


["b'/home/rakan/newstore/operations/flakesbot/src/hello.py", '1', '11', ' E999 SyntaxError']


This seems dangerous. We shouldn't be using malloc haphazardly. Why do you need to do this?


https://media.giphy.com/media/3ohzdLBkaClIHc7cSk/giphy.gif  oooh it's not working today


ref_ground_temp_obj_type (nmerket) - x86_64-Linux-Ubuntu-14.04-clang-3.5: Build Failed

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


Porque tá tudo errado mano.. só da commit no que tá pelo menos compilando. Faz o que você quiser ai na tua máquina, compila. Compilou sem problemas!? Comita. @danirlcr10


سلام تلگرام پیام بده

2017-04-23 14:28 GMT+04:30 javad <notifications@github.com>:

> سلام سینا جان من بوت لوا رباتو میخوام میفروشی یابرام میتونی تو هیلپ ایدی
> بزاری هزینشو بدم
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/SinaXhpm/SinChi/commit/18b3ef6ed0842c40d027aa280db56b98a0dd329d#commitcomment-21870271>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ANFUQk5dfR7kZAfYPGD0g9DsVU_aDjOCks5ryyDLgaJpZM4NFXDW>
> .
>


These are very helpful clarifications-- thanks!


My opinion is to use the roads data schema now for the locators since its what we have and are currently using. I would rather the grinder for the new schema be done before we make a grinder that depends on its output. We can create a new  grinder to use the new schema at any time and it shouldn't be too different or difficult. i don't  think we need another project. A forklift pallet can execute c# code so it could be this project. These are all just Friday morning thoughts so lets chat so we have all the details on the table.


invalid syntax\n'


If you dereference random garbage (say memcpy leftovers) it will attempt to slap a tag on them.

It's quite important we not put vulnerabilities in CheriBSD unless there's a well labeled compile time knob to turn them on and off.  This should have stayed in a branch until it proved useful.


Corrigindo: é bem interessante evitar de fazer commit com erro de compilação. Mas você fazer PUSH dos commits com erro de compilação é foda. @danirlcr10


@Tratcher, @RobSiklos Or just add `Microsoft.Net.Compilers 2.1.0` NuGet package as a developmentDependency and get C#7 even on old build infrastructure as it includes the latest Roslyn, csc.exe etc.


@ahmedtd This commit breaks Firefox! Firefox crashes when opening an `Open` or `Save As` dialog, complaining that GSettings schemas are not installed.


Please don't push stuff that breaks all the tests. I don't have time to fix everything for you! You should get an email notification right away nowadays from Travis if you broke the build, so it's easy to figure out what you broke:
https://travis-ci.org/salilab/pmi

As a reminder, HEAD is supposed to work. If it's broken for more than ~3 days, generally I'll revert the offending commit(s) so that people can get work done.


ref_ground_temp_obj_type (nmerket) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: Build Failed

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


Entendi. @rodrigovcortezi


This comment was very helpful! Without it, it's mysterious why the code here manipulates the "user.dir" system property, which seems like a very strange thing to do. I wish the comment hadn't been deleted.


@SeanFeldman What can I say, the email notification came into my Inbox last night, with your comment.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/e0756d5f-6fd0-4aa4-afaa-8dcc9a050af0 "sodashboard"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/d99cd32f-a498-4ed1-bd35-5538ef4b6265 "sodashboard") deployed [sodashboard](https://github.com/ibm-cds-labs/sodashboard/releases/tag/deploy-ibm-yp-us-south-Dev-Advocates-cds-demo-20170505-160405 "deploy-ibm-yp-us-south-Dev-Advocates-cds-demo-20170505-160405") to [cds-demo](https://console.ng.bluemix.net/apps/b1a83962-c2c2-4fa9-9fb3-a841d4e8f1b4 "ibm:yp:us-south:Dev-Advocates:cds-demo"), including this commit


That doesn't help us.  It'll detect the reference type, and then output garbage or crash during the switch statement.  Maybe I'm missing something though.


I'm with you. Looks good!


I think it should be %1$S %2$S instead of %S %S, no?


I love the idea of enabling other participants to the `select` statement and IO is of course a good candidate. However, I don't know exactly how to use that feature in real apps. Only `read` and `write` operations seems to be "selectable". If we want to make a call to `IO#gets` for example, that method makes a buffer that fills with the content read from the stream until it reaches a newline. If the operation need to be cancelled, the buffer must be unread somehow which makes the implementation really complicated.

On the other hand, the IO in Crystal is already event based and it gives a much simpler programming model where different streams are handled in separate fibers and the scheduler will `select` all the running IOs.

It's not my final word on the subject or anything like that. I just need to see more convincing examples of how to use such feature and why I would use it over the programming model we already have.


@rudjdev maybe it's in a different commit?


Dots are unnecessary here for each string


In this instance, the new user does see previous users **once they move or rotate** (update their position).

All previous users that are **static**, with no position update, appear as a clump in the center of the map, with only their rotation showing up.


![](https://github.trello.services/images/mini-trello-icon.png) [Create github repository](https://trello.com/c/E0oXChtn/1-create-github-repository)


how can you some all the logic below into a constructor function?


What did I say about ico files? ;)


BTW, I committed this in a branch because I was playing around the idea of how to implement timeouts without relaying in extra fibers and channels. The implementation is actually suboptimal (I'd like to remove calls to `Time.now` and figure out if the event actually raised or not) and incorrect (if two timeouts are scheduled the same event is reused). But I just didn't want to loose the experiment :)


I saw it after!! :) Changing it now lol


Documentation needs to be updated


No, I was hoping for a separate directory with higher precedence. Overwriting the versioned archive name is brittle, and probably already broken for our EAP build.

The precedence is at the bottom of this doc: https://developer.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization


Graphics have changed


Came here from http://blog.keycloak.org/2015/04/running-keycloak-cluster-with-docker.html . This is exactly what I needed to get two keycloak server instances running in the same cluster. Works like a charm, well done and thanks!


Ah yeah we already had action hooks ihih


Formatting :)


Looks like there was some missing parenthesis in the PR, will fix now!


yes. I think that this should be done as well for the pro slider of posts. We'll do it later.
Enjoy your week end


如果使用最新版本的centos镜像，xs.jar运行时会出现找不到service命令的错误


@alldotmarketing should be fixed with #29


The subscribers/listeners that will now run immediately below have a dependency on this global configuration being already initialized.


Why is this not applied to RCBugfix?


Typo, depulicated block.


Docker image: 496870459963.dkr.ecr.eu-west-1.amazonaws.com/photobox/jenkins-tests:testing_13
Endpoint: http://jenkins-tests-jenkins-testing.k8s-test.photobox.com


elaaa


Good, but which?
You could move the file to internal and include in keyguard and systemui


I'd rather keep that line — it was there before 157, IIRC, and there is a legit bug there that needs fixing


Helll


It causes double I/O options on OP2.


Wow, that's bad.  I will try to reproduce locally and track down the cause.

On May 5, 2017 11:01, "Thomas Tuegel" <notifications@github.com> wrote:

> @ahmedtd <https://github.com/ahmedtd> This commit breaks Firefox! Firefox
> crashes when opening an Open or Save As dialog, complaining that
> GSettings schemas are not installed.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/NixOS/nixpkgs/commit/2cd342cfb361cfa6413e6612028997079c2fa9ed#commitcomment-22034819>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA-FcgDuZzAPkIO5UIw0jwIr4JojLOKiks5r20fvgaJpZM4NSG_x>
> .
>


Ignore me, I am a noob.


The changes you recommend to the material cutoff would be a clearer way to represent the condition. But it is the same actual decision rule, isn’t that right?

I want to make sure I understand: are you recommending that we reduce king moves in R+P? The current implementation says no; but I could see that going either way.

From: Stefan Geschwentner [mailto:notifications@github.com]
Sent: Friday, May 5, 2017 9:24 AM
To: SapphireBrand/Stockfish <Stockfish@noreply.github.com>
Cc: SapphireBrand <sheppardco@aol.com>; Author <author@noreply.github.com>
Subject: Re: [SapphireBrand/Stockfish] Reduce king moves near the leafs except in simplified endgames. (e81d86a)

You want not reduce K+R but you should check with non_pawn_material(..) > RookValueMg

1.	use need > instead of >=
2.	non_pawn_material counts the material total always in middelgame values so use RookValueMg instead of RookValueEg

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <https://github.com/SapphireBrand/Stockfish/commit/e81d86ac4c2a31c49ebd82cf00e430f1ad0ddfae#commitcomment-22032558> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AOcZXRv2-n8s-7ElZF8mw9fSojCpMw0Cks5r2yLagaJpZM4NR6Sh> .


@TheDiamondYT1 i cant compile pls fix it


Yeah thanks forgot about that. Will fix.


OK, back we go!

On Fri, May 5, 2017 at 12:19 PM, Clément Pit-Claudel <
notifications@github.com> wrote:

> I'd rather keep that line — it was there before 157, IIRC, and there is a
> legit bug there that needs fixing
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/ProofGeneral/PG/commit/2e65d37c12e9378db479c2db782c38b4b6ba16e3#commitcomment-22035036>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACJAKIFLMGT4_VJYF9RdMae_sFqnnKcvks5r20wvgaJpZM4NSFwJ>
> .
>


[R/StackedLearner.R:556:50:](https://github.com/mlr-org/mlr/blob/cf226fafa68a817806e5e9b259063b6270fabc6c/R/StackedLearner.R#L556) *style:* **Do not place spaces around code in parentheses or square brackets.**
```r
      m = makeLearner("regr.nnet", predict.type = )
                                                 ^
```
[tests/testthat/test_base_learnerArgsToControl.R:15:21:](https://github.com/mlr-org/mlr/blob/cf226fafa68a817806e5e9b259063b6270fabc6c/tests/testthat/test_base_learnerArgsToControl.R#L15) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  arg1 = quote(expr =)
                    ^~
```
[tests/testthat/test_base_learnerArgsToControl.R:16:21:](https://github.com/mlr-org/mlr/blob/cf226fafa68a817806e5e9b259063b6270fabc6c/tests/testthat/test_base_learnerArgsToControl.R#L16) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  arg2 = quote(expr =)
                    ^~
```
[tests/testthat/test_base_learnerArgsToControl.R:41:23:](https://github.com/mlr-org/mlr/blob/cf226fafa68a817806e5e9b259063b6270fabc6c/tests/testthat/test_base_learnerArgsToControl.R#L41) *style:* **Put spaces around all infix operators (except exponentiation).**
```r
  devmax = quote(expr =)
                      ^~
```


What do you mean?
The slider ' it's the same so...
Am I missing anything?


Is `self.` missing here?
```
                self.skip_string(f)
                self.skip_binary_double(f) if enc_type == REDIS_RDB_TYPE_ZSET_2 else self.skip_float(f)
```

```
rdb -c json --db 2 /data/redis/dump.rdb
Traceback (most recent call last):
  File "/usr/local/bin/rdb", line 9, in <module>
    load_entry_point('rdbtools==0.1.10', 'console_scripts', 'rdb')()
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/cli/rdb.py", line 86, in main
    parser.parse(dump_file)
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 326, in parse
    self.parse_fd(open(filename, "rb"))
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 383, in parse_fd
    self.skip_key_and_object(f, data_type)
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 508, in skip_key_and_object
    self.skip_object(f, data_type)
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 550, in skip_object
    skip_string(f)
```


s


@MackValentine :
Normalement, on a ajouté toutes les méthodes qu'il te manquait :
* `getOpponentPlayerHandSize()`
* `isATargetableCase()`
* `getPlayableCards()`
* `getRoundWinner()`
* `getGameWinner()`
Si on a oublié autre chose, fais-nous signe.


Greet job 💪


@sunnydeng
@v-jacard
I'm not sure why this revision was made. The currently published article is correct. The note shows "three"
and then names all three. The next step also lists the three. I think there was a change for this issue previously, where "two" was changed to "three". This PR should be cancelled.


规范化


Thanks for raising the issue, I've always been slightly puzzled by the EXPOSE model, since of course we could omit this and `docker run -p 3838:3838` would none-the-less expose the port; it seems the main functionality of EXPOSE is so that the `-P` flag works.  Maybe I'm missing something.

Nevertheless, I am not entirely sure that I follow why this should create a problem under proper usage.  No doubt I'm not following what you are doing, but it seems like this would be something of a bug in your nginx configuration -- surely mapping containers by exposed port is something of a hack that could be better done based on container names or labels than relying on port alone.  Technically there's no guarantee that the service (say RStudio) even runs on it's default port; though we don't make it easy to alter that. When I run this behind nginx, I usually use nginx from another container and connect to the rstudio instance via `--link` anyway, which maps the image to the container name.

Note that we do have `rocker/shiny`, but are constantly getting the request to have images that support both (e.g. rocker/issues#200)


这里乱码了


path


@dbaeumer @michelkaporin fyi


<?php


Code is obfuscation enough... This codestyle...


If we add this back, new replies show a timeago in the future(usually one minute). If we add it back we need to add a hack to subtract ~60 seconds from timestamps client side.


It definatly needs to be updated


Why?


Closes #3


aldfaslfjlfasjsa;lfas;'f


akfaksfalskflkawfnba;dbfvKSW


@kichalla sure, you should be able to cherry-pick this commit. dev and rel/2.0.0-preview1 are very similar.


@lucasdemarchi Is there any dependency that we need to take care ?


I guess that happens when you switch from tab to spaces, but don't convert your existing file.


@lucasdemarchi other than above comment i don't see any issue. Is there any way to test this?


@SunnyDeng
@v-jacard
I looked at the source for this. For the first loc comment, the source is good and the text displays "*This text*" on the published page. For the second commend, the source is also good and the text displays Name and Severity correctly on the published page.

I think this was an issue that was fixed previously.
This PR should be cancelled.


I think it should be %1$S %2$S instead of %S %S, no?


Well, the question could also be "How long until systemd learns that
it's a pure freakshow"

It might be easier to teach systemd to behave like it was ever before
and write logs into simple textfiles which could be read very easy with
tail/less/more/grep etc..

Sorry, had to say that 5ct, for me the answer is: "it will take at least
5yrs" until I ask journalctl --freakshow --someother
--totallyunknownparameter for logs.. Fact..
instead of "grep knxd /var/log/*"

regards, please read it with a smiley :)

Michael


Teste de comentário


The comment above took the asterisk out of the comment and formatted it as italic. Yes, the asterisks are intended and the backslashes in the source are correct.


The CSRF cookie changes, so we have to set it again.


This should be included in the monterail theme too.

Best regards
Wanderlei


Hmm I didn't think about that problem, I can't think of a good solution either.


this endpoint no longer supports approvals. It may have been a fluke that there were no approvals for the user, and reordering tests creates approvals for another client. (the filter attempted to filter by client_id)


the old code was updating the the wrong config. we modified `spZone.getConfig()` but sent `config` to the server


Sorry, I'm not the right person for reviewing this. I'll ping this commit internally to see if any RN Android people want to jump on it - but your best bet is probably taking this through the normal PR process.


y u no jest snapshot tests?


@vjeux debugging tests in jest is a pain


Sounds familiar. LGTM


@sascala for future reference, please don't push changes directly to other peoples working branches. it can cause problems and is not a best practice.


TeamCity Market :: INFRA :: Graphouse :: Graphouse on change [Build 95](https://teamcity.yandex-team.ru/viewLog.html?buildId=8689196&buildTypeId=MarketInfra_Graphouse_GraphouseOnChangeOpensource) outcome was **SUCCESS**
Summary: Tests passed: 14 Build time: 00:00:25


TeamCity Market :: INFRA :: Graphouse :: Graphouse on change [Build 96](https://teamcity.yandex-team.ru/viewLog.html?buildId=8689195&buildTypeId=MarketInfra_Graphouse_GraphouseOnChangeOpensource) outcome was **SUCCESS**
Summary: Tests passed: 14 Build time: 00:00:25


TeamCity Market :: INFRA :: Graphouse :: Graphouse on change [Build 94](https://teamcity.yandex-team.ru/viewLog.html?buildId=8689197&buildTypeId=MarketInfra_Graphouse_GraphouseOnChangeOpensource) outcome was **FAILURE**
Summary: Tests failed: 1, passed: 13 Build time: 00:00:25
### Failed tests
```
ru.yandex.market.graphouse.MetricUtilTest.getLastLevelName: <no details avaliable>

```


cc @cpojer


Here, it is not necessary to standardize the data, for it was already whitened.


I don't really know what I was looking for either, though I was probably looking for a more radical overhaul/reprioritization, I think the docs still hail from the days when we tended to direct people to what was at the time called the Django admin site. It's not specific to the recent work on the importer, more just a general gradual drift that docs (understandably) haven't quite kept up with.

As an example of something that's a bit weird, "creating tournament" is its own section, but should probably only be a think for the simple importer (which needs to be renamed in the docs).


Right again: https://github.com/xwiki/xwiki-platform/commit/d002f33e30d443235d2c99c6b6bac21ce06a89e4 Thanks!


your face is wtf


debugLog()??


Tiesiog padariau klaseje static kintamaji, kuris laiko visu krepselyje esanciu daiktu kieki. Taip padariau, nes kazkas lygtais ten man neisejo arba tiesiog, kad butu lengviau gauti ta kieki. Neatsimenu.


Or I'm braindead


Just do this.fold(init)(f).run


You could have been using `styles/muiThemeable` to abstract the context.


Bluemix [toolchain](https://dev-console.stage1.ng.bluemix.net/devops/toolchains/7e05faa7-0ce6-4eb4-95c4-48372d15c85d "simple-toolchain-20170505153750634"): [Delivery Pipeline](https://dev-console.stage1.ng.bluemix.net/devops/pipelines/dd12b740-5289-4cd6-b6e5-5daef1b76238 "simple-toolchain-20170505153750634") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165621 "deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165621") to [dev](https://console.stage1.ng.bluemix.net/apps/fdce451f-b918-4385-aa1c-d1cfcccddb3f "ibm:ys1:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Bluemix [toolchain](https://dev-console.stage1.ng.bluemix.net/devops/toolchains/382868a9-b26f-4d3b-9cff-6ff649bbd4e7 "simple-toolchain-20170428071916785"): [Delivery Pipeline](https://dev-console.stage1.ng.bluemix.net/devops/pipelines/8a97d6dd-fd1c-4d6e-8e48-3c7903ffecbf "simple-toolchain-20170428071916785") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165628 "deploy-ibm-ys1-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165628") to [dev](https://console.stage1.ng.bluemix.net/apps/1a476c75-69b3-46f9-87c7-447a2f96889d "ibm:ys1:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/05660c97-90f6-4fc9-8228-73793dc2ff09 "yp-03-28"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/009464cd-9c4d-41e0-b935-12e8ad454123 "pipeline_03-28") deployed [test](https://github.com/jerome-lanneluc/test/releases/tag/deploy-ibm-yp-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165643 "deploy-ibm-yp-us-south-jerome_lanneluc-fr.ibm.com-dev-20170505-165643") to [dev](https://console.ng.bluemix.net/apps/8282e2ff-c4ec-48fd-9d74-6647e440a4e5 "ibm:yp:us-south:jerome_lanneluc@fr.ibm.com:dev"), including this commit


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/e853ffbe-52ed-439d-9392-c41066e542da "acme-freight-20170417192813466"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/18ac427c-dee0-4ff6-b76e-7ccf948e89fe "erp (dev)") deployed [acme-freight-erp](https://github.com/IBM/acme-freight-erp/releases/tag/deploy-ibm-yp-us-south-svennam-us.ibm.com-acme-freight-20170505-165643 "deploy-ibm-yp-us-south-svennam-us.ibm.com-acme-freight-20170505-165643") to [acme-freight](https://console.ng.bluemix.net/apps/57680ba5-1b98-48c3-b627-a68cf4269f2a "ibm:yp:us-south:svennam@us.ibm.com:acme-freight"), including this commit


![](https://github.trello.services/images/mini-trello-icon.png) [initializer list to string conversion for configuring list](https://trello.com/c/Go54PXJ9/11-initializer-list-to-string-conversion-for-configuring-list)


Yes. My thinking was around placement of retain()/release() to avoid confusion in how/where are  the refcount modified. As readV3Response() creates this ByteBuf, releasing if after handleReadResponse() will make it easier code flow to follow.

```
  ByteBuf buffer = Unpooled.EMPTY_BUFFER;
  if (readResponse.hasBody()) {
               buffer = Unpooled.wrappedBuffer(readResponse.getBody().asReadOnlyByteBuffer());
  }
  handleReadResponse(readResponse.getLedgerId(), readResponse.getEntryId(), status, buffer, completionValue);
+ buffer.release();
```


<details>

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

```js

bad indentation of a sequence entry at line 114, column 13:
                - "%BASH% -c 'export PATH=\"$PAT ...
                ^
```

</details>


We had a big storm last night and Internet went down for a while.
I see you have been working! Looks very good indeed. I will merge this and work from there. I will also try to break up the file-chooser into separate objects as you suggested elsewhere. Thank you!


I am not totally sure this is ok. It's weird to invoke a callback outside of the step function.


This closes #8


we will use the journal or whatever the user configured on his machine for the log. This should be changed to:
```
ExecStart=/usr/bin/mavlink-routerd
```


I don't think this is what we usually do. The isPermanent method has been removed for instance.


Ho aggiunto l'interfaccia.
Ho sistemato il timer mettendolo all'interno dello switch facendolo partire prima di richiamare il metodo del sort e lo fermo subito dopo.


I see. That makes sense. I'll change that


Also the user may desire a different prefix... this needs to be a mavlink-router.service.in, that has @prefix@ here


It's a problem with v8. They'll fix it in node 8+.


unitary_system_performance_multi_speed (nmerket) - x86_64-MacOS-10.10-clang: Build Failed

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


MAVLink Router


no, that's all


Paul:

Thanks for playing with things, and the feedback.

>Also, the command line is not very intuitive, I end up calling "iio_attr --help" quite often.

yeah, I agree. I end up doing the same. Your proposal looks great. Thanks for going through it. I have a couple questions.

```
iio-context : -> (0) iio-context-attributes
              -> (1) device
                         -> (a) device-attributes
                         -> (b) channels
                                        -> (i) channel-attributes
                         -> (c) debug-attributes
```

if you have:
```
iio_attr
```
list devices (which is fine), how does it display context-attributes?

does:

```
iio_attr <device> <channel>
```

list the channel attributes? or you have to always specify one of -i or -o for channels?

if not,
```
iio_attr <device> <attr>
iio_attr <device> <channel>
```
how do I tell those apart?

>I don't quite like the fact that it matches the device/channel/attrs to patterns, which might have
>undesirable effects:

How about remove the -x, and use regular expressions?
https://www.gnu.org/software/libc/manual/html_node/POSIX-Regexp-Compilation.html#POSIX-Regexp-Compilation
https://msdn.microsoft.com/en-us/library/bb982382.aspx

I really only used it when I wanted to write to altvoltage[0-3], so expressing it that way might be (a) more precise than just "altvoltage", and (b) would still allow globs "altvoltage*" when necessary.

Thanks again for the feedback.


Wonder if more efficient to do repeated uncons?

I feel like could use a foreachChunk function.


Are you sure we need to release a ref count here? Ref count held by BookieClient is released right after calling pcbc.addEntry() and the ref cnt held by PendingAddOp is released once the Op submits a callback (success/error).


As [this ](http://tests.stockfishchess.org/tests/view/590c23780ebc59035df342ef) has almost finished (currently at LLR: 2.77) I suggest to let it finish (resume it), because:

-  aborted SPRT tests have no value at all.
-  nobody so far stated explicitly, that it is not a valid simplification and that the test should be stopped.
-  it seems like it will finish soon requiring not many games

So at least we finish with having a test result with a clear YES (or NO).

That said, anyhow I think that the most appropriate bounds for this test IMO would have been [0,4], which are the usual bounds we use when we just move code from one place to another without adding complexity ;-)


push any updates, to the todo branch.


Inconsistent tabing


noice


Could you please test if this works with your various shortcut addons, @primaeval ?

In theory, whenever a new directory is created, it will check the availability of inputstream.adaptive, if stream_protocol is set to 0 (DASH). If it isn't available, or the version is too low, it will change the setting back to HLS.

I am not sure about the performance impact this has. It feels extremely slow since I introduced this patch, but this may also just be server load.


Trying my first hand at github


@suborb

In appmake.c you're including "config.h".  Is this the usual "config.h" also included in zcc.c and sccz80.c?  These files are including "../config.h".  The win32 build breaks because of this difference.  Should it be "../config.h" in appmake.c too?


Depends on which exact scripts/spells used, but usually something happening during play between a group of orphans (throwing something) or making something appear to happen without any resulting change for player or other NPCs. Purely visual, as in scripted play, glow/shine effects or anything looking different than normal movement.


@avinash-palleti install it on any board/computer that has systemd as init.  You can easily check what's being installed and if the files are in the correct place:

```
make install DESTDIR=/tmp/inst
tree /tmp/inst
```

You should see mavlink-routerd there and also the service file. Then install it on your computer, i.e. remove  DESTDIR=/tmp/inst from above. You may want to give it additional arguments or edit /etc/mavlink-router/main.conf to create an endpoint.

Then start it with "systemctl start mavlink-router".  You should be able to see the status with "systemctl status mavlink-router" and the log with "journalctl -u mavlink-router"  (with root user)


Hey @sonybansi check the rest of the documentation above, there is an example:
    living_room_light:
      protocol: 5
      code_on: 654321,565874,233555,149874
      code_off: 654320,565873,233554,149873


except without a specific exception might be dangerous, would it be possible to catch specific things instead (e.g., KeyError)?


![](https://github.trello.services/images/mini-trello-icon.png) [Core Java 1](https://trello.com/c/CnftZQAg/1-core-java-1)


Hello, if product name is NULL and/or id_supplier is 0

Search::indexation (function indexation) from searchcron doesn't work or has no effect, full = 0 or full = 1 both.
It seems to stop if these products found.
Please, can you reproduce it?
p.s.: I know that these kind of nulled products should not be on the database, but anyway....


This should go to stderr


:key:他可能很久不会更新了


No I really think it was because it was easier to do something with deleting stuff in cart or smth. It shouldn't cause any trouble.


@loosebazooka @elharo @akerekes


Who uses Eagle 8 now???

On 5/5/2017 10:22 AM, jpagliaccio wrote:
>
> Hey - just FYI - in Eagle 8 a library search for "WS2812" yields
> "Sorry, no match!". For some reason the component names you have
> entered require an asterisk at the end to be found. A search on
> "WS2812B*" works. For other components that is not necessary.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/adafruit/Adafruit-Eagle-Library/commit/4abf84c3856535c0ab6ae96ec4be784d7dcc6b3e#commitcomment-22034187>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AI4Hl5RBXIophRRL0CzpX15I3snx6-uBks5r2z6-gaJpZM4NSD7F>.
>

--
Thanks
David Surgi
Owner
Surgi Mfg. Co., Inc
213 S. Main St.
PO Box 177
Carl Junction, MO 64834
Ph 417 649 7277
fax 417 649 7278


144488793-Correct-surface-convection-calculation-6037 (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2529 of 2529 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)


and/or some of these products AND different products number between ps_product and ps_product_shop....

is it possible in this case? Maybe better some check about this and alert the user? apart from the function indexation to test....

thank you


Charts & Graphs package


:ship: :surfing_man: lgtm


> alreade
qeuque


Nice, thanks. Did you actually verify that it can send via twilio though? I.e. will they automatically break up longer messages? (I would expect them to, but it is something we should manually QA for sure.)


too much effort to manually go through them huh


Check the alignment on line 58. It's indented farther than it's supposed to be. Consistent alignment is important for humans reading your code.


دست نزن به فایل های من!


Indentation issues


Yes it's the same file. Sorry I didn't know how to fix the project file.

> On 5 May 2017, at 18:08, aralbrec <notifications@github.com> wrote:
>
> @suborb
>
> In appmake.c you're including "config.h". Is this the usual "config.h" also included in zcc.c and sccz80.c? These files are including "../config.h". The win32 build breaks because of this difference. Should it be "../config.h" in appmake.c too?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


144488793-Correct-surface-convection-calculation-6037 (lgu1234) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


There's no point leaving behind the old version of the code commented out.  It can always be retrieved from git history.


这文件是干啥用？就是想问问，挺好奇的


I came across a condition during ensemble change, where a pendingAddOp is complete as it received ackq responses + completed the callback and later due to new ensemble resulted in resending write request. This was due to weak consistency in iterating pendingAddOps queue. The above fix will still retain the same problem of referencing a bytebuffer already released. Or am I missing something here?


Should be one space after the first semicolon.

Also, whenever possible do not use hard-coded numbers in your for loops. What does 20 represent here? What if you wanted to change the number of columns or rows on your model? You'd have to go through every single line to check for hard-coded 20's. Use a variable instead.


graphtie?


Nej nej nej, det var jag som inte hade forkat senaste versionen bara ;) stå på er!


Ok I will commit 'include "../config.h" for appmake.c.  This should also work on the other builds since zcc and sccz80 include it that way too.


@ajaybhargav LC2 is the country and LC1 is the language.
I'm happy to help with your website upgrade if you're running into issues.
Feel free to message me anytime here: http://gitter.im/CaMer0n


did you forgot to remove this line?


Oh! Thanks. Will fix that.


Yes, sure. Fixed the test. It runs in Python 2.7, should be easy fix in Python 3.6 (mostly iteritems errors), but I don't have it available right now.


Oops! Should be be "file://"  :)


Jaha oj! jag trodde det stod här vilken rad jag kommenterade på - 112 är det jag syftar på :) och liknande sak på 121, men då ska det väl vara "player.inverntory().contains(chest)" tänker jag?


Pretty good so far. I haven't had a problem since enabling this although I
also haven't been as busy as I was due to conferences, etc.

On Sunday, April 30, 2017, Mario Zigliotto <notifications@github.com> wrote:

> @derekprior <https://github.com/derekprior> How has this worked out for
> you? Heard you talk about this issue on The Bike Shed™ and immediately
> realized i've been dealing with it too but never connected it to Rails.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/derekprior/dotfiles/commit/7f724946b4181ac0e658372c95308d085471d948#commitcomment-21961551>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAJSWKNilToIMq25JVjKle-_myXdsQftks5r1E5GgaJpZM4NMg5A>
> .
>