This commit implements multi-measure rests in the Humdrum to MEI converter.

Example input:

```
**kern	**kern
*M4/4	*M4/4
=1-	=1-
1c	1d
=2	=2
1d	1g
=3	=3
1r	1e
=4	=4
1r	1r
=5	=5
1r	1r
=6	=6
1r	1r
=7	=7
1r	1r
=8	=8
1r	1r
=9	=9
1r	1r
=10	=10
1f	1r
=11	=11
1g	1g
=12	=12
1a	1g
==	==
*-	*-
```

Rendering in verovio:

MEI output

```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>
                <date>2016-12-24 08:04:10</date>
            </pubStmt>
        </fileDesc>
        <encodingDesc>
            <projectDesc>
                <p>Transcoded from Humdrum with Verovio version 0.9.13-dev-768df72</p>
            </projectDesc>
        </encodingDesc>
    </meiHead>
    <music>
        <body>
            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-000000157111119">
                        <staffGrp xml:id="m-000000203279374" symbol="brace" barthru="true">
                            <staffDef xml:id="staffdef-000000084719932" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="1" lines="5" />
                            <staffDef xml:id="staffdef-000000054517807" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="2" lines="5" />
                        </staffGrp>
                    </scoreDef>
                    <section xml:id="section-000000082834662">
                        <measure xml:id="measure-L3" n="1">
                            <staff xml:id="staff-L3F2" n="1">
                                <layer xml:id="layer-L3F2" n="1">
                                    <note xml:id="note-L4F2" dur="1" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L3F1" n="2">
                                <layer xml:id="layer-L3F1" n="1">
                                    <note xml:id="note-L4F1" dur="1" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L5" n="2">
                            <staff xml:id="staff-L5F2" n="1">
                                <layer xml:id="layer-L5F2" n="1">
                                    <note xml:id="note-L6F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L5F1" n="2">
                                <layer xml:id="layer-L5F1" n="1">
                                    <note xml:id="note-L6F1" dur="1" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L7" n="3">
                            <staff xml:id="staff-L7F2" n="1">
                                <layer xml:id="layer-L7F2" n="1">
                                    <note xml:id="note-L8F2" dur="1" oct="4" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L7F1" n="2">
                                <layer xml:id="layer-L7F1" n="1">
                                    <mRest xml:id="mrest-000000074391174" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L9" n="4">
                            <staff xml:id="staff-L9F2" n="1">
                                <layer xml:id="layer-L9F2" n="1">
                                    <multiRest xml:id="multirest-000000128903378" num="6" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L9F1" n="2">
                                <layer xml:id="layer-L9F1" n="1">
                                    <multiRest xml:id="multirest-000000112979187" num="6" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L21" n="10">
                            <staff xml:id="staff-L21F2" n="1">
                                <layer xml:id="layer-L21F2" n="1">
                                    <mRest xml:id="mrest-000000075507802" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L21F1" n="2">
                                <layer xml:id="layer-L21F1" n="1">
                                    <note xml:id="note-L22F1" dur="1" oct="4" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L23" n="11">
                            <staff xml:id="staff-L23F2" n="1">
                                <layer xml:id="layer-L23F2" n="1">
                                    <note xml:id="note-L24F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L23F1" n="2">
                                <layer xml:id="layer-L23F1" n="1">
                                    <note xml:id="note-L24F1" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L25" n="12" right="end">
                            <staff xml:id="staff-L25F2" n="1">
                                <layer xml:id="layer-L25F2" n="1">
                                    <note xml:id="note-L26F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L25F1" n="2">
                                <layer xml:id="layer-L25F1" n="1">
                                    <note xml:id="note-L26F1" dur="1" oct="4" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```

----------------------

Styling of barlines will break the multi-rests (but still need to figure out how to stylize the barline):

```
**kern	**kern
*M4/4	*M4/4
=1-	=1-
1c	1d
=2	=2
1d	1g
=3	=3
1r	1e
=4	=4
1r	1r
=5	=5
1r	1r
=6	=6
1r	1r
=7:|!	=7:|!
1r	1r
=8	=8
1r	1r
=9	=9
1r	1r
=10	=10
1f	1r
=11	=11
1g	1g
=12	=12
1a	1g
==	==
*-	*-
```

Rendered as:

converted MEI data:

```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>
                <date>2016-12-24 08:07:19</date>
            </pubStmt>
        </fileDesc>
        <encodingDesc>
            <projectDesc>
                <p>Transcoded from Humdrum with Verovio version 0.9.13-dev-768df72</p>
            </projectDesc>
        </encodingDesc>
    </meiHead>
    <music>
        <body>
            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-000000089438526">
                        <staffGrp xml:id="m-000000179964674" symbol="brace" barthru="true">
                            <staffDef xml:id="staffdef-000000150310844" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="1" lines="5" />
                            <staffDef xml:id="staffdef-000000065781448" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="2" lines="5" />
                        </staffGrp>
                    </scoreDef>
                    <section xml:id="section-000000165144751">
                        <measure xml:id="measure-L3" n="1">
                            <staff xml:id="staff-L3F2" n="1">
                                <layer xml:id="layer-L3F2" n="1">
                                    <note xml:id="note-L4F2" dur="1" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L3F1" n="2">
                                <layer xml:id="layer-L3F1" n="1">
                                    <note xml:id="note-L4F1" dur="1" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L5" n="2">
                            <staff xml:id="staff-L5F2" n="1">
                                <layer xml:id="layer-L5F2" n="1">
                                    <note xml:id="note-L6F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L5F1" n="2">
                                <layer xml:id="layer-L5F1" n="1">
                                    <note xml:id="note-L6F1" dur="1" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L7" n="3">
                            <staff xml:id="staff-L7F2" n="1">
                                <layer xml:id="layer-L7F2" n="1">
                                    <note xml:id="note-L8F2" dur="1" oct="4" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L7F1" n="2">
                                <layer xml:id="layer-L7F1" n="1">
                                    <mRest xml:id="mrest-000000177847416" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L9" n="4">
                            <staff xml:id="staff-L9F2" n="1">
                                <layer xml:id="layer-L9F2" n="1">
                                    <multiRest xml:id="multirest-000000094614766" num="3" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L9F1" n="2">
                                <layer xml:id="layer-L9F1" n="1">
                                    <multiRest xml:id="multirest-000000108562769" num="3" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L15" n="7">
                            <staff xml:id="staff-L15F2" n="1">
                                <layer xml:id="layer-L15F2" n="1">
                                    <multiRest xml:id="multirest-000000062316930" num="3" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L15F1" n="2">
                                <layer xml:id="layer-L15F1" n="1">
                                    <multiRest xml:id="multirest-000000088696982" num="3" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L21" n="10">
                            <staff xml:id="staff-L21F2" n="1">
                                <layer xml:id="layer-L21F2" n="1">
                                    <mRest xml:id="mrest-000000052810509" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L21F1" n="2">
                                <layer xml:id="layer-L21F1" n="1">
                                    <note xml:id="note-L22F1" dur="1" oct="4" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L23" n="11">
                            <staff xml:id="staff-L23F2" n="1">
                                <layer xml:id="layer-L23F2" n="1">
                                    <note xml:id="note-L24F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L23F1" n="2">
                                <layer xml:id="layer-L23F1" n="1">
                                    <note xml:id="note-L24F1" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L25" n="12" right="end">
                            <staff xml:id="staff-L25F2" n="1">
                                <layer xml:id="layer-L25F2" n="1">
                                    <note xml:id="note-L26F2" dur="1" oct="4" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L25F1" n="2">
                                <layer xml:id="layer-L25F1" n="1">
                                    <note xml:id="note-L26F1" dur="1" oct="4" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```


ah I haven't pushed the latest changes out yet to Clojars, just committed the version bump for the defaults repo though


@victorlevasseur I think that a few other actions could benefit from this :)
Also I've flagged a few refactoring that I'll be doing in a next commit


Are unofficial IBANs used in Iran?


It seems like std::free is missing (either a stand-alone call or a parameter to MemoryInputStream::add_data()).

It's also possible to avoid unnecessary copying by using Gdk::PixbufLoader instead of MemoryInputStream::add_data: check my old draft of #114 : https://github.com/danpla/gImageReader/commit/f2b44ef9bb498c33eb69c3594400b7f176aa7084


should this be "Still"?


Please add comment from now on


Yea, revert this already.


The SNP format is pretty much a recognized STANDARD now for naming program icons, as it has been in use for some time now and the coding for the SNP icon format has been adopted by many image teams. So we cannot now pick an choose which bits of the SNP format to use and which bits we don't use.


Maybe an artifact of a change in code layout?

Let's see what happens if we run it again. Note that this will execute two runs, one after the other, and compare their results, as opposed to executing a single run then comparing against the previous day's results.

@nanosoldier `runbenchmarks(ALL, vs = "@f27c6f3ae50b45e0e6ff2305dd5031d07c8665a7")`


Why did this get changed to default to false? This is more dangerous and can be disabled as any other user preference if the user doesn't want this to get in the way.


Mind the spelling.


Using 1 seconds of delay? It only comes on the screen


see above comment


I wouldn't encourage you putting suggestions into commit message


Great point.  Thanks!


Thanks a lot for the review, issues should be addressed in
c47b1ebe22bb888d63293093e0c0bf74dcbc6bb1
9cf200cc553f163f881f3f5def56215725174735


Ok, I will try to find a minute this week.

Thanks!


I had to disable it for testing sakes and forgot to re-enable it.


That's fine, just put it on the TODO list for the next release.


Since this is a rooted query, won't it potentially provoke a forced layout if the table doesn't have its own ID and we have to put a temporary one there to make `qSA` work right? I suppose for this context it may not matter since we're already manipulating the DOM.

Could we go back to `elem.gEBTN("tbody")` and check whether the first result (if any) is a child of `elem`? That's probably a few more bytes though.


Jon Snow


[09:45:18 PM]  Loaded Build: v0.1-15-Dec-16
[09:45:27 PM]  Initializing AI...
[09:45:31 PM]  Changing objective to: Hero Management
[09:45:34 PM]  Scene: Lobby
[09:45:39 PM]  Scene: Heroes
[09:45:39 PM]  Start managing heroes
[09:45:40 PM]  Checking each position for level 30...
[09:45:42 PM]  - Got position: 2
[09:45:48 PM]  ERROR: Only one image can be processed at once. Please make sure you dispose of the page once your finished with it.
[09:45:48 PM]  ERROR: System.InvalidOperationException: Only one image can be processed at once. Please make sure you dispose of the page once your finished with it.
   at Tesseract.TesseractEngine.Process(Pix image, String inputName, Rect region, Nullable`1 pageSegMode)
   at SevenKnightsAI.Classes.SevenKnightsCore.IsHeroLevel30(Boolean retrying)
   at SevenKnightsAI.Classes.SevenKnightsCore.IsHeroLevel30(Boolean retrying)
   at SevenKnightsAI.Classes.SevenKnightsCore.ManageHeroes()
   at SevenKnightsAI.Classes.SevenKnightsCore.MainLoop(Object sender, DoWorkEventArgs e)
[09:45:53 PM]  Checking each position for level 30...
[09:45:54 PM]  - Got position: 2
[09:46:00 PM]  ERROR: Only one image can be processed at once. Please make sure you dispose of the page once your finished with it.
[09:46:00 PM]  ERROR: System.InvalidOperationException: Only one image can be processed at once. Please make sure you dispose of the page once your finished with it.
   at Tesseract.TesseractEngine.Process(Pix image, String inputName, Rect region, Nullable`1 pageSegMode)
   at SevenKnightsAI.Classes.SevenKnightsCore.IsHeroLevel30(Boolean retrying)
   at SevenKnightsAI.Classes.SevenKnightsCore.IsHeroLevel30(Boolean retrying)
   at SevenKnightsAI.Classes.SevenKnightsCore.ManageHeroes()
   at SevenKnightsAI.Classes.SevenKnightsCore.MainLoop(Object sender, DoWorkEventArgs e)
[09:46:05 PM]  Checking each position for level 30...
[09:46:08 PM]  - Got position: 2


Das die kompletten Postfachdaten im Klartext gespeichert werden darf imho nicht sein.
Wenn ein unbedarfter User ein Log, oder seine settings Datei irgendwo postet, hat er ein Problem.


Wow


Wooooow


I no


Dobro je :D haha


addresses latest issue in #100


99% of texts are -- copy and paste from known source... i dont know how this happen :(...
Corrected:
https://github.com/cmangos/wotlk-db/commit/c1a053284e5927c25ad92c5ca1b28f21da874459


This is the first change


WOW! How you do it MAN ? HATS OFF!
TEACH ME TOO. 👍 :D


SESE is a very old concept. I did not even hear about it in the last decade or so. Good that you reminded me. :)  It was very useful in the early days to debug the programs. With the modern IDE and the debugging capabilities, I don't think you need to bother about it. If your function does one thing and can be exited with a single return statement, great.  Go ahead.

But the method below - by implementing SESE, the code is hard to read. Any code should read like a prose. Simple to understand by anyone. What do you think?


Nice commit name.


delete commented out code


Move all custom javascript files to the bottom of the page.


Does the new defconfig have changes I made like HZ ?


Redundant whitespace


This is the first commit for my hello-world file


understood - Merry Christmas to you and yours, LraiZer! ATB- AL :)


Move the whole script to a separate file


@tk-hendrik @JustinAzoff just a heads up. about 50% of the way there. i started by just abstracting out some of the funny parts for readability. converting things to generators back to the store, next looking at the tokens and upsert bits... feedback welcome, just didn't wanna trounce on you if you end up poking around more... prob not doing more till late next week..


Add JSDoc


Thanks, Daniel, I've fixed this in efe2ec83fbc.


Rename to displayCurrentDate


First Commit


@napernik hows that a reason for not using whatever means are available now? Or are you saying that registering Services in a StartupHandler is completely broken and can't be used by anyone in the current state?


This and below methods have almost the same functionality. I'm suggesting to extract common functionality to a new function.


Add JSDoc instead of comments


I removed all options that you can adjust yourself in the game's provided options.

And, I was wrong about some memory stuff, so that has been adjusted.


<!-- PMABOT:SOB -->
This commit is missing Signed-Off-By line to indicate that you agree with phpMyAdmin Developer's Certificate of Origin. Please check [contributing documentation](https://github.com/phpmyadmin/phpmyadmin/blob/master/CONTRIBUTING.md) for more information.


[2nd Attempt.zip](https://github.com/angelolanaza/portfolio/files/671856/2nd.Attempt.zip)


Antibirth keeps crashing when I run it. It crashes right away and says that isaac_ng has stopped working. I have the .exe version of the file. windows 10, no afterbirth, have rebirth.


bhaiya ye X_train_images iska size mai R ki badle , max of R over the complete file hona chahiye na ??


This reminds me Henry Ford's phrase: "You can order T-model of any color, but only if this color is black.")


consider declaring params as `const char*`.


url : "/advanced/scholars"


I am not able to compile the WIN64 configuration on Windows 10, Visual Studio 2012 and Visual Studio 2013 with this patch. I get compiler errors in line number 206. Is "0x00'0D'8B'4C" valid in C/C++?


Use HostingEnvironment.MapPath instead of accessing HttpContext.Current


@greut cette partie me fait très peur sans transaction. C'est du bon vieux bricolage bien douteux. Y aurait un moyen plus simple et plus sécurisé de mettre à jour `$orderElement` et `$lens`?


ありがとうございます


![](https://github.trello.services/images/mini-trello-icon.png) [הורדת הgenrator](https://trello.com/c/lvLbRj30/1-genrator)


Bien vu !


![](https://github.trello.services/images/mini-trello-icon.png) [ürünlerin listelenmesi(servis-android)](https://trello.com/c/uu8hNb9N/7-urunlerin-listelenmesi-servis-android)


Merci, à vous aussi ! (En passant est-ce que vous avez reçu ma convention pédagogique par mail ?)


Apparently, not all languages use AM/PM. Such as EN-US


Failed nightly build. Add 7.1 and allow nightly to fail.


This commit makes it easier to generate multi-bar rests from part extraction by ignoring null-token data lines.

Example input:

```bash
    extractx -s 1 jrp://Jos2701
```

```
**kern
*staff3
*Ivox
*I"Contra
*I'C
*clefF4
*k[]
*M2/1
*met(C|)
=1-
!LO:TX:Y=24:t=Monstra te esse matrem
0r
.
=2
0r
.
=3
0r
.
=4
0r
.
=5
0r
.
.
.
=6
0D
.
.
.
=7
0A
.
.
.
.
.
.
=8
1.A
.
.
.
4G\
4A\
=9
[0B
.
=10
0B]
.
=11
0r
.
=12
0r
.
=13
0r
.
=14
0G
.
.
=15
0A
.
.
.
.
=16
0c
.
.
.
.
=17
0r
.
.
.
.
.
.
.
=18
0B
.
.
.
.
=19
0c
.
.
.
.
=20
0d
.
.
.
=21
1c
1A
.
=22
0B
.
.
.
=23
0A
=24
0r
.
.
=25
0r
.
=26
0r
.
.
.
=27
0r
.
.
.
=28
0r
.
=29
0r
.
.
.
.
=30
0AA
.
.
.
=31
0E
.
.
.
.
.
=32
1.E
.
.
.
4D\
4E\
=33
[0F
.
=34
0F]
.
=35
0r
.
=36
0r
.
.
.
.
=37
0r
.
.
.
.
.
.
=38
0D
.
.
.
.
=39
0E
.
.
=40
0G
.
.
=41
0r
.
.
.
=42
0F
.
.
.
.
.
=43
0G
.
.
.
.
=44
0A
.
=45
1G
.
.
1E
.
.
.
=46
0F
.
.
.
.
.
.
=47
0E
.
.
.
.
.
=48
0r
.
.
.
.
=49
0AAl
==
*-
```

Verovio rendering:

<img width="707" alt="screen shot 2016-12-24 at 09 19 23" src="https://cloud.githubusercontent.com/assets/3487289/21468165/d46a94d8-c9ba-11e6-8ce4-a48ff6deb5e8.png">

MEI output:

```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>
                <date>2016-12-24 09:25:21</date>
            </pubStmt>
        </fileDesc>
        <encodingDesc>
            <projectDesc>
                <p>Transcoded from Humdrum with Verovio version 0.9.13-dev-ef09430</p>
            </projectDesc>
        </encodingDesc>
    </meiHead>
    <music>
        <body>
            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-000000175320191">
                        <staffGrp xml:id="m-000000021672176">
                            <staffDef xml:id="staffdef-000000031040542" clef.shape="F" clef.line="4" key.sig="0" meter.count="2" meter.unit="1" meter.sym="cut" n="1" label.abbr="C" lines="5" />
                        </staffGrp>
                    </scoreDef>
                    <section xml:id="section-000000200988483">
                        <measure xml:id="measure-L10" n="1">
                            <staff xml:id="staff-L10F1" n="1">
                                <layer xml:id="layer-L10F1" n="1">
                                    <multiRest xml:id="multirest-000000172094411" num="5" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L28" n="6">
                            <staff xml:id="staff-L28F1" n="1">
                                <layer xml:id="layer-L28F1" n="1">
                                    <note xml:id="note-L29F1" dur="breve" oct="3" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L33" n="7">
                            <staff xml:id="staff-L33F1" n="1">
                                <layer xml:id="layer-L33F1" n="1">
                                    <note xml:id="note-L34F1" dur="breve" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L41" n="8">
                            <staff xml:id="staff-L41F1" n="1">
                                <layer xml:id="layer-L41F1" n="1">
                                    <note xml:id="note-L42F1" dots="1" dur="1" oct="3" pname="a" accid.ges="n" />
                                    <note xml:id="note-L46F1" dur="4" oct="3" pname="g" accid.ges="n" stem.dir="down" />
                                    <note xml:id="note-L47F1" dur="4" oct="3" pname="a" accid.ges="n" stem.dir="down" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L48" n="9">
                            <staff xml:id="staff-L48F1" n="1">
                                <layer xml:id="layer-L48F1" n="1">
                                    <note xml:id="note-L49F1" dur="breve" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                            <tie xml:id="tie-000000005634497" startid="#note-L49F1" endid="#note-L52F1" />
                        </measure>
                        <measure xml:id="measure-L51" n="10">
                            <staff xml:id="staff-L51F1" n="1">
                                <layer xml:id="layer-L51F1" n="1">
                                    <note xml:id="note-L52F1" dur="breve" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L54" n="11">
                            <staff xml:id="staff-L54F1" n="1">
                                <layer xml:id="layer-L54F1" n="1">
                                    <multiRest xml:id="multirest-000000099585980" num="3" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L63" n="14">
                            <staff xml:id="staff-L63F1" n="1">
                                <layer xml:id="layer-L63F1" n="1">
                                    <note xml:id="note-L64F1" dur="breve" oct="3" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L67" n="15">
                            <staff xml:id="staff-L67F1" n="1">
                                <layer xml:id="layer-L67F1" n="1">
                                    <note xml:id="note-L68F1" dur="breve" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L73" n="16">
                            <staff xml:id="staff-L73F1" n="1">
                                <layer xml:id="layer-L73F1" n="1">
                                    <note xml:id="note-L74F1" dur="breve" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L79" n="17">
                            <staff xml:id="staff-L79F1" n="1">
                                <layer xml:id="layer-L79F1" n="1">
                                    <mRest xml:id="mrest-000000037055395" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L88" n="18">
                            <staff xml:id="staff-L88F1" n="1">
                                <layer xml:id="layer-L88F1" n="1">
                                    <note xml:id="note-L89F1" dur="breve" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L94" n="19">
                            <staff xml:id="staff-L94F1" n="1">
                                <layer xml:id="layer-L94F1" n="1">
                                    <note xml:id="note-L95F1" dur="breve" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L100" n="20">
                            <staff xml:id="staff-L100F1" n="1">
                                <layer xml:id="layer-L100F1" n="1">
                                    <note xml:id="note-L101F1" dur="breve" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L105" n="21">
                            <staff xml:id="staff-L105F1" n="1">
                                <layer xml:id="layer-L105F1" n="1">
                                    <note xml:id="note-L106F1" dur="1" oct="4" pname="c" accid.ges="n" />
                                    <note xml:id="note-L107F1" dur="1" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L109" n="22">
                            <staff xml:id="staff-L109F1" n="1">
                                <layer xml:id="layer-L109F1" n="1">
                                    <note xml:id="note-L110F1" dur="breve" oct="3" pname="b" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L114" n="23">
                            <staff xml:id="staff-L114F1" n="1">
                                <layer xml:id="layer-L114F1" n="1">
                                    <note xml:id="note-L115F1" dur="breve" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L116" n="24">
                            <staff xml:id="staff-L116F1" n="1">
                                <layer xml:id="layer-L116F1" n="1">
                                    <multiRest xml:id="multirest-000000102734963" num="6" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L142" n="30">
                            <staff xml:id="staff-L142F1" n="1">
                                <layer xml:id="layer-L142F1" n="1">
                                    <note xml:id="note-L143F1" dur="breve" oct="2" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L147" n="31">
                            <staff xml:id="staff-L147F1" n="1">
                                <layer xml:id="layer-L147F1" n="1">
                                    <note xml:id="note-L148F1" dur="breve" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L154" n="32">
                            <staff xml:id="staff-L154F1" n="1">
                                <layer xml:id="layer-L154F1" n="1">
                                    <note xml:id="note-L155F1" dots="1" dur="1" oct="3" pname="e" accid.ges="n" />
                                    <note xml:id="note-L159F1" dur="4" oct="3" pname="d" accid.ges="n" stem.dir="down" />
                                    <note xml:id="note-L160F1" dur="4" oct="3" pname="e" accid.ges="n" stem.dir="down" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L161" n="33">
                            <staff xml:id="staff-L161F1" n="1">
                                <layer xml:id="layer-L161F1" n="1">
                                    <note xml:id="note-L162F1" dur="breve" oct="3" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                            <tie xml:id="tie-000000183905318" startid="#note-L162F1" endid="#note-L165F1" />
                        </measure>
                        <measure xml:id="measure-L164" n="34">
                            <staff xml:id="staff-L164F1" n="1">
                                <layer xml:id="layer-L164F1" n="1">
                                    <note xml:id="note-L165F1" dur="breve" oct="3" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L167" n="35">
                            <staff xml:id="staff-L167F1" n="1">
                                <layer xml:id="layer-L167F1" n="1">
                                    <multiRest xml:id="multirest-000000074406358" num="3" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L184" n="38">
                            <staff xml:id="staff-L184F1" n="1">
                                <layer xml:id="layer-L184F1" n="1">
                                    <note xml:id="note-L185F1" dur="breve" oct="3" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L190" n="39">
                            <staff xml:id="staff-L190F1" n="1">
                                <layer xml:id="layer-L190F1" n="1">
                                    <note xml:id="note-L191F1" dur="breve" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L194" n="40">
                            <staff xml:id="staff-L194F1" n="1">
                                <layer xml:id="layer-L194F1" n="1">
                                    <note xml:id="note-L195F1" dur="breve" oct="3" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L198" n="41">
                            <staff xml:id="staff-L198F1" n="1">
                                <layer xml:id="layer-L198F1" n="1">
                                    <mRest xml:id="mrest-000000037567191" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L203" n="42">
                            <staff xml:id="staff-L203F1" n="1">
                                <layer xml:id="layer-L203F1" n="1">
                                    <note xml:id="note-L204F1" dur="breve" oct="3" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L210" n="43">
                            <staff xml:id="staff-L210F1" n="1">
                                <layer xml:id="layer-L210F1" n="1">
                                    <note xml:id="note-L211F1" dur="breve" oct="3" pname="g" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L216" n="44">
                            <staff xml:id="staff-L216F1" n="1">
                                <layer xml:id="layer-L216F1" n="1">
                                    <note xml:id="note-L217F1" dur="breve" oct="3" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L219" n="45">
                            <staff xml:id="staff-L219F1" n="1">
                                <layer xml:id="layer-L219F1" n="1">
                                    <note xml:id="note-L220F1" dur="1" oct="3" pname="g" accid.ges="n" />
                                    <note xml:id="note-L223F1" dur="1" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L227" n="46">
                            <staff xml:id="staff-L227F1" n="1">
                                <layer xml:id="layer-L227F1" n="1">
                                    <note xml:id="note-L228F1" dur="breve" oct="3" pname="f" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L235" n="47">
                            <staff xml:id="staff-L235F1" n="1">
                                <layer xml:id="layer-L235F1" n="1">
                                    <note xml:id="note-L236F1" dur="breve" oct="3" pname="e" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L242" n="48">
                            <staff xml:id="staff-L242F1" n="1">
                                <layer xml:id="layer-L242F1" n="1">
                                    <mRest xml:id="mrest-000000106824608" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L248" n="49" right="end">
                            <staff xml:id="staff-L248F1" n="1">
                                <layer xml:id="layer-L248F1" n="1">
                                    <note xml:id="note-L249F1" dur="breve" oct="2" pname="a" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```


`penalty_buff` is not initialized.


Test


Test, project(Test)


Nayyingkapolo


Don't worry about it @Grz3s, things like this can happen. I was just skimming over the TBC-DB changes committed recently and I was lucky enough to spot this one. One small step closer to perfection for the databases! :smile:

And thanks for the all the efforts!


Convert indentation to spaces for better code viewing


Merci Thomas,
oui, j'ai même répondu par mail...


Thanks god.


n^2 complexity (nested loop). Can you do better?


consider using modulo operation for index rotating.


isso aqui deveria ser um objeto tipo  InvestimentoForm. Outro detalhe, aqui é mais frescura.. mas deixa os nomes dos métodos no imperativo, tipo investe. Não que faça uma grande diferença, é mais pq você manda o método executar..


I think now scope is node should be greater than 4.


vou fingir que não li esse nome de interface :P


Pls needsmoredocs


isso aqui é lógica de negócio, não pode deixar vazar para a página. E se a lógica para investir for diferente de verificar o saldo > 0? vc vai ter que vai mudar na página!


Consider either `'z' - 'a'` or `toupper` (better).


essas duas coisas aqui representam uma ação do sistema, a ação de investir. Deveria ter um local isolado só para ela, até para facilitar os testes. E uma outra coisa, e se a conta não tiver saldo? Como que o investimento ta sendo feito?


now ip is located in /usr/sbin, atleast ip-full (LEDE) and the status of interfaces are always offline
regards


será que em vez de rolar uma herança, não podia rolar uma composição?


Trial


Blue Grey*


Done


Done in 4606c34e1


SPFBL-2.5.0-TESTING - release 2016-12-23


my apologies, but what about .none?


> I suppose for this context it may not matter since we're already manipulating the DOM.

Exactly, and this code immediately precedes said manipulation.

> Could we go back to `elem.gEBTN("tbody")` and check whether the first result (if any) is a child of elem? That's probably a few more bytes though.

Worse, because the correct tbody is not necessarily first in DOM order. I actually tried out two flavors of breakable loop to address the situation, but both were far too big for the value. Our choice is basically between the before and after here, and of the two the new one really is better AFAICT.


I want to revisit this in 5.4 because I feel like currently MailFake is doing too much. We should only be asserting that a Mailable was sent to the mailer with the proper arguments. Testing the build method should be an entirely different test that simply news up the mailable and calls build() manually.


Добрый день, это мое домашнее задание в программе R-studio


uHunt was down when this problem was uploaded. That's the reason of the title.


![](https://github.trello.services/images/mini-trello-icon.png) [[2] JS scripts for filters not recognized on mobile](https://trello.com/c/B8MnKcoY/106-2-js-scripts-for-filters-not-recognized-on-mobile)


No worries:)


first comment


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b1](https://ci.tsr.me/viewLog.html?buildId=7006&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


@ar-maged `zero` in the documentation means no parameters :D


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b1](https://ci.tsr.me/viewLog.html?buildId=7006&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **FAILURE**
Summary: Compilation error: :compileJava (new) Build time: 00:01:01


@ban-masa ハイライト問題を解決しました。
roseus立ち上げなおして`:AnsiEsc`読んでも大丈夫になったはずなので、`Open_roseus`の内部で`AnsiEsc`呼ぶといいと思います。ただし、今までは`:AnsiEsc`を2回呼ぶとエスケープシーケンスが元に戻っていたと思いますが、これはできなくなって、一度`:AnsiEsc`を呼んだらバッファを閉じない限りは色はそのままです。

おまけで、roseusインタプリタ上でlispの構文ハイライトが行えるようになりました。lisp rainbowは機能するし、グローバル変数に色はつくしで、とりあえずそれなりな環境になったのかなと思います。


k


@larsjohnsen can you please send me your email address? mine can be found from my github profile, you can send it that way if you don't want to post it publicly, thanks!


Looks like there's some issues with this change. https://github.com/leethomason/tinyxml2/pull/509


There are gonna be quite a few shit commits before full release :D Thx for errorchecking @evil-at-wow .


I have no idea as to why, but for whatever reason this causes a kernel panic for me on Onyx. I was wondering if it did the same for you. Very unfortunate


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b2](https://ci.tsr.me/viewLog.html?buildId=7007&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


dsasadsadsa


You could do that. I wasn't aware of variable R.

However, note that the image pixel values have only 2 values, and hence it
would be optimized to store it in a 1 bit representation format. However,
you could also eliminate this issue by instead extracting only a few
features from the image instead of choosing all the pixel values. You could
choose this way if you have a scarcity of computational power.

Since the R varies over all the images, a more robust technique could be to
extract/engineer some specific features for all the images.

Fifth Year Undergraduate Student,
Electrical Engineering Department
IIT Kharagpur.
anirudt@iitkgp.ac.in

On Sat, Dec 24, 2016 at 10:39 PM, amanpurwar <notifications@github.com>
wrote:

> bhaiya ye X_train_images iska size mai R ki badle , max of R over the
> complete file hona chahiye na ??
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/amanpurwar/kaggle/commit/3ae57bb5e1c1d325bfdea67696a1cd7f610b4833#commitcomment-20290675>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFpF9YregBSrAZLxxZvb8dewHviwvd-nks5rLVHEgaJpZM4LVJM2>
> .
>


Need to add `logError`


xD


If you want this to be automagically rebuilt on a nightly basis, then you also need to fork https://github.com/zbeekman/nightly-docker-rebuild and follow the instructions there. If you have questions on setup, you can always ping me at @zbeekman on twitter or here on github. Good luck! 😄


Good catches :)


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b2](https://ci.tsr.me/viewLog.html?buildId=7007&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **FAILURE**
Summary: Compilation error: :compileJava (new) Build time: 00:03:25


# Learn Git and to make and deploy a Website with Node.js


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b3](https://ci.tsr.me/viewLog.html?buildId=7008&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


@EladKeyshawn Was there a reason why we didn't just restore `tempForUndo`, but constructed a new web view from `tempForUndo`?


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build b3](https://ci.tsr.me/viewLog.html?buildId=7008&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 20 Build time: 00:01:23


Done


any idea how to implement the KNN based image retival


Just found out that this commit also breaks `FABProgressCircle` finishing animation. Maybe we should replace this library or remove it for now. What do you think? @madeye


There is already a JSDoc, because the function doesn't have any parameters


test


So it is now returning objects? :thinking:


url : "/advanced/moutounes"


@mpakus - this fork of leather is not the one on rubygems. I did just release new versions of storytime (v2.1.2) and storytime-admin (v0.2.2) that point directly to this fork though, so if you're using those, you should be good to go.


there's no need to insert brackets around references. xml2rfc is doing that.


forgot to mention that a few more channels were also nuked
in this update, as name changes no longer required...
LraiZer now IGNORES any characters in the picon name
other than A to Z and 0 to 9 - how cool is that?


No, I realized decoding the JSON to arrays instead of objects was a lot easier to work with, so I included the call to `json_decode()` in the `get()` and `post()` methods. That's why the tests don't have to call it now.


so far i used a local version of the DTD for local editing (most XML tools are happier to find the DTD locally). was there a difference in DTDs, or did you just want to conform to a general guideline that recommends to reference the DTD on the xml2rfc server?


@nathanchance could not reproduce 2% drop on bullhead


Breaks when not DateTime (ex. when simple Date object is passed)


Thanks for adding this, it looks very nice.


Oh ok. :smile:


Oxygen was happier to validate the XML when it had the DTD at a URL. I
happily complied ;-)

H

On Sat, Dec 24, 2016 at 7:38 PM, Erik Wilde <notifications@github.com>
wrote:

> so far i used a local version of the DTD for local editing (most XML tools
> are happier to find the DTD locally). was there a difference in DTDs, or
> did you just want to conform to a general guideline that recommends to
> reference the DTD on the xml2rfc server?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/dret/I-D/commit/4f8b928f9b331298c9f7428f8652bab66a2dcff5#commitcomment-20290859>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADojA_ti4HMr_v4oN2QVOEC_6lrtVooPks5rLWatgaJpZM4LVRm1>
> .
>

--
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library
http://public.lanl.gov/herbertv/
http://orcid.org/0000-0002-0715-6126

==


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b4](https://ci.tsr.me/viewLog.html?buildId=7009&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b4](https://ci.tsr.me/viewLog.html?buildId=7009&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **FAILURE**
Summary: Exit code 127 (new) Build time: 00:00:04


But pylint and autopep8 will change it. Importing a project module before the gtk modules is not pep8


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b5](https://ci.tsr.me/viewLog.html?buildId=7010&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b5](https://ci.tsr.me/viewLog.html?buildId=7010&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:09


I'm working on something in my API library for this, but it's still only a duct tape on top of the real problem + will still break your system if not installed:

```
from oca import import_guard
with import_guard():
    from whatever import something
```
What would be real nice is an import guard in core. I'm not so sure where this is taking place though, so I just keep getting lost in the module loader code 😖


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b6](https://ci.tsr.me/viewLog.html?buildId=7011&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b6](https://ci.tsr.me/viewLog.html?buildId=7011&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:04


Need change this line to:
`n -= 64 - **dst_idx**;`


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b7](https://ci.tsr.me/viewLog.html?buildId=7012&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) is now running


First proposition of structure


cool


TeamCity FlatStone Tech :: Applied Logistics :: Development Build [Build develop-b7](https://ci.tsr.me/viewLog.html?buildId=7012&buildTypeId=FlatStoneTech_AppliedLogisticsMc189_DevelopmentBuild&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 20 Build time: 00:01:33


Почему вы удалили мой комментарий, а не ответили на него?


Consider solution with one loop and without extra array: generate 2 random numbers within array size limits and swap the corresponding elements.


This is wrong "commit" There is "next" with re-fix for this commit.
Sorry. :(


MySQL permet de mettre un verrou via `SELECT ... FOR UPDATE`. Une transaction seule ne suffira pas dans le cadre d'un conflit RW.

https://laravel.com/docs/5.3/queries#pessimistic-locking


doesn't `keccak-tiny` belong there also?


is it freed finally?


Need add missing bracket:
+                       }


is it freed?


nazi Rules on commits ))))


Good catch man. I just included it.

Btw, here are the reasons i made changes to your code.

1) I have left this logic in tact. It was much clearer than what I had originally. The only thing I removed was the switch. I did this because the if has less lines of code to it.
```swift
if leftContainsPathBoolean == rightContainsPathBoolean {
   position = leftContainsPathBoolean == false ? .full : .middle
} else {
   position = leftContainsPathBoolean == false ? .left : .right
}
```

2) I removed the `[onowned self]` because in that case, referring to `.self` inside that closure would not have led to a retain cycle, because it would not be strongly captured.

3) I removed the 2nd closure because it is easier for me to read if i just renamed the variable to something clearer than 'left' and 'right'
```swift
let indexPathContains: (_ step: Int) -> Bool = { (step: Int) -> Bool in
   return self.theSelectedIndexPaths.contains(IndexPath(item: indexPath.item + step, section: indexPath.section))
}


I just commited the new code fixing the error you just spotted. it now looks like this
```swift
        let rangePosition = { () -> SelectionRangePosition in
            if !self.theSelectedIndexPaths.contains(indexPath) { return .none }
            if self.selectedDates.count == 1 { return .full }
            let selectedIndicesContainsPreviousPath = self.theSelectedIndexPaths.contains(IndexPath(item: indexPath.item - 1, section: indexPath.section))
            let selectedIndicesContainsFollowingPath = self.theSelectedIndexPaths.contains(IndexPath(item: indexPath.item + 1, section: indexPath.section))
            let position: SelectionRangePosition
            if selectedIndicesContainsPreviousPath == selectedIndicesContainsFollowingPath {
                position = selectedIndicesContainsPreviousPath == false ? .full : .middle
            } else {
                position = selectedIndicesContainsPreviousPath == false ? .left : .right
            }
            return position
        }
```


hey, @anonydog! are you receiving this?


The problem here is in ExtUtilts::MakeMaker, (make manifest doesn't work).


One last thing to note, this code will have to be revisited.
This logic
```swift
IndexPath(item: indexPath.item - 1, section: indexPath.section)
IndexPath(item: indexPath.item + 1, section: indexPath.section)
```
will have to be revisited. It will work for regular calendars. But if a user's layout is different (eg. if they used a flowing calendar layout) it will break.

The ideal fix here will be to: Instead of using +1 and -1, i should do calculation to see if the `following` and the `previous` indexPath is right after or before the current indexPath being looked at. Currently +1 and -1 does not do this


This will stop the entire process. what if your function is just a 3rd-party library functionality that is used in different applications? Exit on error is not what a user expected.
You can return error code and pass array by reference. In this case you will report about error on upper level and will be able assign result pointer to passed-by-ref param. This is, however, C-style. Modern approach is to throw exceptions.


This is now implemented:
https://github.com/Whonix/qubes-whonix/commit/170fe0941c9c287d0a1c28e5cc9ab32844c728e5

sleep / wait / trap can probably be avoided when using systemd`KillSignal=sigkill`.


I had to comment out with #CMAKE_USE_DIR=${S}/project/cmake/
to get the ebuild for kodi working. I do not know if the CMakefile.txt has changed its position or what is going on; but I thought you would like to know


Consider passing you password components as array of 3 const strings.
This way you will express your idea more explicitly and avoid these magic numbers.


Set your body/html height to 100%. This is a standard practice I employ to ensure the entire page is being utilized/filled by children elements.


Added a "wrapper" element to handle the flexing of your two major blocks: the grid and the hero-image. Also a pretty standard practice, so the `body` element can stay clean and serve as a solid foundation.


Make sure you watch the video that Tim posted regarding how `flex-grow`, `flex-shrink`, and `flex-basis` work. `flex` is simply shorthand for all three of those individual properties.


I used `stretch` for the `align-items` value so that I wouldn't have to keep hard-coding `min-height` on all your `article` elements. Without it, you would have to set the article height's to a minimum of 150px or 200px to avoid white-space between the rows at certain screen widths. Using `align-items: stretch` was easier/cleaner.


The code below was developed to operate a four motor Rover-Robot with an Arduino 101 and
 Adafruit Motor-Servo Controller Shield using the Blynk iPhone app using the Blynk "Joystick" and Blynk
 "Long Slider" over a BLE Bluetooth connection. This code should work for a 2 motor Rover. You will have to
 designate the motors appropriately in the Define Motor Port Section ~line 43.

 Note: This code generates an error "Blynk.begin(auth, blePeripheral);"
                                                                    ^
 during compliation. It doesn't seem to be an issue.

 Use this code at your own risk!


Depending on screen width, I am just changing the `flex-basis` value on the first block and last block in your grid, in conjunction with changing the `flex` values on your articles. This what allows the blocks to move and shift their spots based on screen width.


wow, thanks for such a huge reply )
actually I'm not too good with UI (I preferably write either logics or SpriteKit related stuff), so I don't know what's the right way to work with indexPath;
for now, as promised before, I try to write tests validating rangePosition values - and so will make a pull request as soon as they are ready


Here a lot of copies happen implicitly.
To be precise: 2 per iterations.
Unnecessary overhead.


awesome.


Oups c'est ma faute, à la base j'avais seulement fait une redirection sur ce mail mais récemment je l'ai passé en tant qu'adresse email utilisable et j'ai oublié de l'ajouter à mes adresses à synchroniser...


Nothing changed other than the indentation (tabs to spaces).


If you know smth by compile time, there is no need to allocate on heap:
```
    char* f_names[] = {
        "Bob",
        "Bill",
        "Javier",
        ...
    };
```


**body!**


![calendar_example](https://cloud.githubusercontent.com/assets/3949304/21468561/e4111d7e-ca20-11e6-9706-c6505db4eabd.PNG)

btw here is how the calendar I work on looks like - so, as you said, it is a flowing calendar (I guess) and thus rangePosition does not work as expected


@yangweichen we should not have our DB credentials on GH. we should be using environment variables for these and inject them at runtime. if you've never done something like that before, check out [dotenv](https://www.npmjs.com/package/dotenv) or similar libraries

Since you already posted these, I'd consider them compromised. GH crawlers regularly go thru public repos and scrape username/pws. Please provision another Cloudant account and use those instead, making sure not to upload them


closes #2


test commit.


[Your benchmark job](https://github.com/JuliaLang/julia/commit/c428a5f7ad0d724b7c549dcc007485413591f704#commitcomment-20290596) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/2aa795e7758883c2705b02ce86ba04cfd4115cb7/c428a5f_vs_f27c6f3/report.md). cc @jrevels


Very inefficient!
You don't need to shift array literally, you can do it virtually. What you actually need is to increase index of the next element to be added to the 1st one.


🎉🎉🎉
On Thu, Dec 22, 2016 at 6:11 PM Adam Rothman <notifications@github.com>
wrote:

> Yassssss
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/other-xyz/other.js/commit/fbac8e1ff4d86f8272ace2aaf48155c371cee50a#commitcomment-20281232>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAE1iPu8NIvAb-rdRGKxNV3sywEtwJ74ks5rKy3DgaJpZM4LUhyf>
> .
>


Just an idea. What about supporting redirections for domain names without requiring the scheme too?
i.e. For now, it must be `go.php?url=http(s)://pod.url`
Would be sufficient (and not require any urlencoding) if it could be just `go.php?url=pod.url`

Found a simple little function [here](https://stackoverflow.com/a/1974047).


> (mean)


Well, at least it's consistent.


is it a Christmas present? :D


Button tanımlama


animasyon nesnelerini tanımladık


ve Ani nesnelerini button tıklanmasına ekledik


Inconsistent formatting within a file drives me nuts. Please use an autoformatter and configure it to match the existing style.


Лишний div


This comment is not necessary, as the case is self-evident.


Case is self-evident; comment not necessary.


Remove.


Oh. let me clarify.

Sorry. I did not mean to say `flowing calendar`
I mean that it might break if the user has `generatingOutDates` set to false && (the calendar has no headers || or the `setStrictBoundaries` is set to false.

I have not tested it yet, but i believe it will fail (it will display incorrectly)
And why? Because the index paths will be different on the same screen.
I use `indexPaths.item` and `indexPath.section` to know if it should be `.full, .none, .left, .right`.

The calendar you just posted here is not that kind of calendar. I do not think any user of this library has created that kind of calendar yet. And the library already has over 40,000 downloads :)
So I am not worried about it yet.


![](https://github.trello.services/images/mini-trello-icon.png) [After backing out of the team selection menu, a player still existed and had control. They were able to move around the menu scene.](https://trello.com/c/FcNPEm5C/144-after-backing-out-of-the-team-selection-menu-a-player-still-existed-and-had-control-they-were-able-to-move-around-the-menu-scene)


I care


yeah that was pretty dumb


also pretty dumb


差别阈限


so is it a good place to do ScheduleGenerateAll? why wasn't this already done?


@tiagosiebler .  I totally understand what you're saying about sprites but the images were going to be high quality.  Sprites are great for low resolution, things like thumbs, but a request for a large image is going to be too much of a burden for most people's internet connection to receive one giant image. However, if @Timtam77 wants to resize them to be smaller, I don't see why not use a sprite.

I like the idea of giving each of the images a coordinate but I'm still thinking that using a database would be easier to maintain and use.  However, if you are willing to handle the js I'm more than happy to see what you come up with!


The FreeBSD ports version of the HPN patch was simplified like this:

                /* Allocate a channel number for the socket. */
#ifdef HPN_ENABLED
                /*
                 * explicitly test for hpn disabled option. if true use smaller
                 * window size.
                 */
                if (!hpn_disabled)
                        c = channel_new("port listener", type, sock, sock, -1,
                            hpn_buffer_size, CHAN_TCP_PACKET_DEFAULT,
                            0, "port listener", 1);
                else
#endif
                c = channel_new("port listener", type, sock, sock, -1,
                    CHAN_TCP_WINDOW_DEFAULT, CHAN_TCP_PACKET_DEFAULT,
                    0, "port listener", 1);

to make it apply cleanly against newer version of OpenSSH more easily. It may be worth considering such a style.


missing a new line here


Because it is  three large-scale industrial projects, and the FSC can only suitable for the large-scale, if the project is small or not large-scale, we still need to find some other method.


position:fixedでウィンドウに固定。
左上を基準位置に
top:25px;
left:30px;


position:fixedでウィンドウに固定。
今度は右下を基準位置に
bottom: 25px;
right: 30px;


Better ea976ebb2f86efe323a9f32627569f8154532512 ?


Another long comment to check trimming: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque luctus eleifend est sed vulputate. Proin iaculis mauris est, vitae rhoncus turpis tincidunt at. Ut ex eros, commodo ac nunc nec, porta facilisis massa. Proin pellentesque maximus nisl id condimentum. Donec vulputate pharetra mauris, ultrices vestibulum augue. Donec porta fermentum justo, nec sollicitudin quam aliquet in. Maecenas sollicitudin quis leo eu pharetra. Nam egestas gravida sem quis molestie. Pellentesque ac congue.


It seems simpler to use dimension ID but that should be ok


It is my playground for expiriments with modern GL and optimizations. I found no benefits for end users yet.


n requer pratica nem habilidade


The empirical study is based on human beings. in the process, it cannot be very accuracy. So the more research I mentioned is the author should investigate more respondents form more countries, so that we can get some convincing results. And because of the human factors, the author must consider about the 	deviation and some possible risks.


@itzsaga ah, it looks like a person has to be in the organization (or something like that) to be able to see that list. We may need to make a collaborators.md file in the repo and link to that instead.


this is shit!


stop writing useless code!


@alena


Hello! You we're totally right, I just forgot to push my master to upstream... which I just did! Thanks


This is to remove non-fundamental solutions


Only continue if solution is better


@jim-p @sbeaver-netgate Note that currently 'text' is not an expected value here. IpAddress.class.php expects "BOTH", "V4" or "v6".
After https://github.com/pfsense/pfsense/pull/3248 then 'HOSTV4' will be an expected parameter value.

Nothing gets broken by using 'text' - it just avoids putting any special hover 'help' text.


Forgot to add in the commit.
Spell.cpp Credit
https://github.com/mangosR2/mangos/commit/6b791f5

All others Credit:
https://github.com/mangosR2/mangos/commit/6b791f5


Note the above comment, and try to assess the reasons, and what we can do now.


Did this fix get put into 2.1.3?


Why `B` and not `/Beta` here and in the equation?


Is the calendar you are working on displayed correctly to your liking?


Do you want to describe as the "location parameter" rather than "mean" to maintain consistency with README?


Description? Mean or location?


Can roll up into the previous `if`.


this commit has a spelling mistake


url : "/advanced/explanations/{matne_id}"
example : "/advanced/explanations/493"


Makes sense. Also makes sense to drop http now, no pods are without TLS
unless they are broken.

On December 24, 2016 2:47:56 PM Armando Lüscher <notifications@github.com>
wrote:

> Just an idea. What about supporting redirections for domain names without
> requiring the scheme too?
> i.e. For now, it must be `go.php?url=http(s)://pod.url`
> Would be sufficient (and not require any urlencoding) if it could be just
> `go.php?url=pod.url`
>
> Found a simple little function [here](https://stackoverflow.com/a/1974047).
>
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/diasporg/Poduptime/commit/c55772b45cb4169e510b35c161ed4fb39e1bc042#commitcomment-20290984


I know this won't hurt to keep but it's oriented towards non-OMS ROMs, OMS capable firmwares don't need to prove innocence.


added "This is a test..."


These middleware routers need to come _before_ the front end request handler, otherwise all GET requests will get swallowed up by the proceeding request handler


Спрайт лучше добавлять в конец страницы
перед закрывающимся тегом боди.

Строки 190, 222, 238 тег р внутри ul быть не может, это не валидно


Строка 167 лишний div


the calendar is displayed pretty correct until I select another set (range) of dates (e.g. if I tap on the 6th of feb, I programmaticaly de-select the 9th and the 6th, and then select a range of 6th-9th, and here is what I get
![img_3482](https://cloud.githubusercontent.com/assets/3949304/21468646/bb611802-ca25-11e6-9e91-4a194ec3a1ad.PNG)
):


My 🎄 gift lol


Have a merry Christmas :bell:
Maybe Santa brings me a new formatter.


OK, i am seeing an issue with range select. Looking more into it


Tentando


I have to admit though if I select, say, 14th of Feb instead of 9th, everything works just fine


So you want to force TLS for all pods?
I'd totally agree with that! Especially with Let's Encrypt, there is just no more excuse for it.

That will also cut away a nice chunk of redundant code 😉


Фотки не отображаются так как не верное разрешение, не png а jpg


Can you show me your `configureCalendar` function code?


Can you show me your configureCalendar function code?
And also, can you tell me what calendar version are you using?


http://pastebin.com/te4TGj1y

lines 69 - 77
also
lines 158 - 162


version 5.0.1 (as the project is on Swift 2)


+Copyright (c) 2016 Mohammad Hussein Tavakoli Bina , Pooya Khandel


Кнопки должны быть внутри тега форм


algo para comentar


Hehe OK then. I was just surprised with the number of quite different benchmarks that exactly got 2x faster.


A binary search or hash table might be faster than this sequential search, especially when the number of ranges increases.


It's probably wise to add a comment to this if the order of start addresses must stay incremental.


Thanks for this, it's good to have a start


Yup. I did that years ago when some pods ran unencrypted, that's been gone
a while now and they won't federate so let's call http dead (to the world
if possible)

On December 24, 2016 3:15:30 PM Armando Lüscher <notifications@github.com>
wrote:

> So you want to force TLS for all pods?
> I'd totally agree with that! Especially with Let's Encrypt, there is just
> no more excuse for it.
>
> That will also cut away a nice chunk of redundant code 😉
>
> --
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/diasporg/Poduptime/commit/c55772b45cb4169e510b35c161ed4fb39e1bc042#commitcomment-20291044


На этом этапе вылетает эксепшн:
java.lang.NullPointerException
	at ru.stqa.pft.rest.RestHelper.getIssueStatus(RestHelper.java:43)
	at ru.stqa.pft.rest.TestBase.isIssueOpen(TestBase.java:13)
	at ru.stqa.pft.rest.TestBase.skipIfNotFixed(TestBase.java:21)
	at ru.stqa.pft.rest.RestTests.testCreateIssue(RestTests.java:24)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:100)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:646)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:811)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1137)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:753)
	at org.testng.TestRunner.run(TestRunner.java:607)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:368)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:363)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:321)
	at org.testng.SuiteRunner.run(SuiteRunner.java:270)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1284)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1209)
	at org.testng.TestNG.runSuites(TestNG.java:1124)
	at org.testng.TestNG.run(TestNG.java:1096)
	at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
	at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:127)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)


If the issue is with the virtual environments, could we use the --system-site-packages flag instead?


@madara134 already patch ?


is this commit related to yielding? :)


CON ESTA INFORMACIÓN ENTENDERÁS MEJOR QUÉ ES EL BLOGGING Y EN QUÉ ASPECTO ES BLOGGER LO QUE SE ENTIENDE


aa


Thx, fixed in bd13c28ba81a32551cf16f71c0c7f4aa08976ad7


`monitor->name` could already have been allocated, better `free()` it before.


[barbs html 2 push.txt](https://github.com/bpatrin/Westie-resume/files/671952/barbs.html.2.push.txt)


@shlevy I think I can best make that PR as a follow up to https://github.com/NixOS/nixpkgs/pull/21268. I need the `buildPackages` in there to do it right, along the lines of:
```nix
let bootPkgs = if stdenv ? cross then selfPkgs else prevPkgs;
```
for every compiler


Where are you getting this value (7,587,000)?

In my own testing, the Cheytac .408 yields a stability factor of ~0.15668, where this calculation yields 2.13e-08.  I would recommend more unit testing on this function.


Very coool.


Possibly; it's just that it's a bit brute-force. (TBH I added it to this
PR because I'm switching between Windows & Linux machines and this was
the easiest way to get things moving).

Perhaps I should extend the question earlier in the thread. Should we
say: "Use virtualenv with --system-site-packages" and just go from there?


Look, @Avaq! The first release is v1.0.0! :smile:


Yeah, the surveillance pod is useless to players (except for the FW mission).

The new scanning attributes do not have tooltips yet.


M


Yes, I'll reply back on the PR, sorry, I just saw this on my phone when the appveyor build failed earlier before.


Yes, perhaps. I extracted all of these from the `tests_requires` and the previous setup. I do agree it should all be consolidated.


Wasn't meowth52 this time either :(((((


тестовый коммент


I didn't use `json_decode` because the source is a `repr` not a `json.encode`, though it happens to be proper JSON currently. I'm hoping to get away from the helper methods like `assertDictEqual` because with pytest, it handles rewriting of simple asserts to provide better context.


I'm said panda. @ChShersh on this line you: (1) made action which is useless (2) created serious security vulnerability


Here I'm sad panda as well


groups


See https://github.com/serokell/kademlia/blob/master/src/Network/Kademlia/Instance.hs#L243


Contents retrieved from https://github.com/reactjs/redux/tree/master/examples/shopping-cart


@pranavkm why the Travis failed, after this commit?!!


@FantasyIsBae Done


Build the initial home page


Usually the guards are indented on the next line:

```haskell
function x y
  | x == y    = 5
  | otherwise = 4
```


@LegitSoulja Its alright i only just came back , and thanks for doing it :)


> And besides: he commit text was rather misleading, as it suggested to be for EN only.

Yes, just the EN file is updated.


Hmm yeah it looks like you're right. I likely didn't test this scenario back then, since I didn't envision my users resizing their windows. If you wanted to make a pull request to handle this case I'd definitely be happy to take a look.


Hi there,

I was just looking through the WWW logs of the web server hosting nuxi.nl and was amazed by the relatively large number of requests going to this specific file.

The reason why I'm providing a copy of this and other tarballs is because I distribute binary packages based on them. The copies are there as a service to our users. They are not there because we're operating a mirror service for everybody to use.

If you had gone to nuxi.nl, you could have found our email address clearly stated at the bottom of the page and contacted us to ask for approval to list this site as a mirror. I would have likely said yes, but because of this situation I'm pretty much tempted to say no.

Please remove this mirror from this formula.


Contains:
  MNIST_train.txt
  MNIST_test.txt


I see. Thought it might be mandatory to pick it as DU had it too, hehe.
Will revert it, so its not cluttering up things.


Тесты


Testing server side validation using classes.


Добавил стоп, чтоб не стакался таймер при новой игре.


исправил проверку на собираемость


Сортировка массива с результатами


`this.letters` is undefined. Explanation?


Заработал вывод массива втаблицу


F405 - this one that you suggested me doesn't work in my case.


In which way?


KO Myung-Hun dixit:

>Yes, please...

OK. What’s the actual default `$PATH` on OS/2?
I’d then add that with `.;` prepended as an example,
so users can copy/paste it right from the manpage.

Thanks,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence.		-- Coywolf Qi Hunt


Finally someone did it!


Hi,

ich habe eine Mail im Postfach, bekomme aber "TV-Planer: falsches Datumsformat"


maybe have [This Line ](https://github.com/LegitSoulja/jsGen-phpGen/blob/master/unminified/jsGen.js#L11) be defined outside the constructor so all functions can access it


realised my mistake


###### Gen.genSerials("LlEeGgIiTtSsOoUULlJjLlAa", 5, 5, 2)
```
jjLaT-otsLg-GLSLE-IGSIA-GgLIG-alsaI
lUiSe-UlJjT-LlTjO-lsLeT-llOEt-LlatI
```
###### Gen.genSerials("LlEeGgIiTtSsOoUULlJjLlAa", 5, 5, 2)
```
jjLaT-otsLg-GLSLE-IGSIA-GgLIG-alsaI
lUiSe-UlJjT-LlTjO-lsLeT-llOEt-LlatI
```
###### Gen.shuffle(["a","b","c","d", "e", "f"]);
```["a", "e", "d", "c", "f", "b"]```


@FantasyIsBae not needed, besides, a function can return it if really needed.


Is it fixed or not


@FantasyIsBae it's public to all classes in the constructor.


Coming soon!


Ok , i understand


getSerials work, but not that :/


@FantasyIsBae line #34


Not enough flags.


wat


I complete you.


The dll was moved to a sub-folder to avoid conflicts. Makes sense from a build perspective, but the xmltest.exe and .dll end up in different folders, so they don't find each other on "Run".


ты убил падежи!


Opened issue assigned to you:
Spartinizer new feture: remove redundant code from c'tors #1008

please change the relevant information (labels/assignee/milestone) as you wish.

regarding our project code: i still didn't refactor the code (just opened an aissue for that). this issue will be closed by the end of the weekend (31.12).


great plan +!


Done for the chunk system or more things are coming ? @Muqsit


Thanks!


unexpected behavior expected?


I'd should wrap this with brackets


Hi,

ich habe bei den Einstellungen 00:00 als Startzeit bei wunschliste angegeben. Dann scheint die Uhrzeit nicht in der Mail zu stehen. Kann das der Grund sein?


In short: I added additional parameter to `RETURN_NODES` which holds number of messages to which `RETURN_NODES` response is split


Ref pre-commit/pre-commit-hooks#159


Here begins an "ol" short for ordnened list!


The following may be helpful in this case:

merge_unifications(Us1, Us2, Us) :-
        append(Us1, Us2, Us3),
        maplist(eq_pair, Us3, Pairs0),
        keysort(Pairs0, Pairs),
        group_pairs_by_key(Pairs, Groups),
        maplist(vars_all_equal, Groups, Us).

eq_pair(A=B, A-B).

vars_all_equal(Label-[Var|Vars], Label=Var) :-
        maplist(=(Var), Vars).

Sample query and answer:

?- merge_unifications([a=A,b=B,d=D], [a=X,b=Y,c=C], Us).
A = X,
B = Y,
Us = [a=X, b=Y, c=C, d=D].


Is there any reason to move these lines below its initial position (LOC 253-255)?


uh oops


Code would work in same way, only now I shouldn't think if we won't overwrite `known` with outdated value


oh cmon github


Is it okay that `defaultChan rq` is used here twice instead of variable `dChan = defaultChan rq`? Was it so neccessary?


While they pass chan they use 3-4 names for it in the stack. I feel myself a data flow algorithm. One name less is better


@georgeee  I didn't not notice after review where this number of messages is used :(
Could you point out?


Fucking house style man. How fucking hard is it?


Here # of messages is set


No fucking really, this needs to say what size that is.


What exactly can this be used for? Examples?


And here # of messages is checked


need to remove this line


@FantasyIsBae there's nothing wrong with Gen.each,

Gen.each(Gen.genRandomNumbers, "", 5, 5)
```
67522
62304
74431
60668
21447
```


@Pranayyadav Hi it's already implemented in the `ImageRetrieval`.  When you choose from the drop down menu one of the many distance functions then what it actually executes is the kNN method of retrieving images. In section 3.1 of the [paper](http://arxiv.org/abs/1608.03811)  it describes in more detail how it works.


Gen.getRandomUTF8 still isn't working though, trying to figure out the cause.


@FantasyIsBae wait, it is working xDD

Gen.genRandomUTF8("", 5)
```8zrjh```

Gen.genRandomUTF8("ASFGG", 50)
```ASFGASGSSGGFGGSSAAFAAAGFGSGSAGFGAFGFSSAAGGGSGAAAGA```


hello world


I'll see if i can find something


天哪！太感动了，谢谢五月！我这两天逐条测试了一下，等下把反馈贴上来，仅供参考哈（之前鸽了太久，做点啥证明自己还认真着…），这个update已经很帮忙了~~！
by 兔子


I guess .toString() fixed it.


Rejected & Reasons
2-1，靡颜佚貌，低分物品。
2-7，卷边少女，本关tag重、无tag极低分。
3-2，居家短裤·黑，低分物品。
4-6，万圣夜之舞，低分物品。
5-12，印花短裙·粉格，较低分、无tag、此关F太多（改过关提示：无中式tag的衣服外套容易F）。
6-6，旋律悠扬，妙尘，复古蓝宝石，白雪喵星人，过关提示：此关F太多、避开裙子。
6-7，少女心事·蓝，分数较低，而且是第七章才能获取、不收入F表应该不太影响新手过关。
6-9，采茶曲·裙，较低分（上下装易F!）。
6-9，上海烟云梦，少女公主亲测均可用。
7-5，水手少女·白，少女公主亲测均可用。
7-6，萌兔侍童·下装，低分物品、过关提示已注明容易F。
7-8，无畏，已收录（白名单关卡）。
8-4，贵公子，连衣裙基本都F，改为连衣裙白名单关卡。
9-1，樱桃汽水，少女公主亲测均可用。
11-4，桔梗，少女公主亲测均可用（下装搭配：粉色青春）。
11-5，牛仔小妞，少女公主亲测均可用（本关要求亚尼拉海盗，外套无要求，可能是保暖分数太低被误认为F了）。
14-支1，花香，远低于有tag的顶配，过关提示：没波西米亚tag的容易F。
14-支1，束腰蓝裙，分低、可用。
16-1，蝶舞翩跹·珍稀，极低分。
16-1，印花短裙·粉格，同系列均为低分、有很多更高的易获取物品，可用。
16-5，错觉隧道，少女公主亲测均可用（是原色容易F）。
16-支1，蒸汽时代，低分物品。
联盟6-6，粉翼·华丽，这件我开联盟第六章的时候亲手测过的，可用，会再测一遍确认。
联盟7-3，采撷草莓·珍稀、冰蓝蔷薇，已收录（白名单关卡）。


teste


This is fine with me


Thanks @triska! Added this in 8729ade. I had a cruder fix, that just unified the variables while leaving the duplicates in place. This is more elegant, and has taught me about key-value lists! (yes I am a Prolog n00b)


Lel *presses that was easy button*


Have you seen the picture of your PC : http://i.imgur.com/LZVaLpV.png


gonna add the rgb gen xD


and yes


I'll work on binary


Dissapointed ?


xd


No, it's the truth, but it's sad


天哪，太感动了！很有帮助，谢谢五月QAQ！我这两天逐条测试了一下，没收录的贴在上面了，仅供参考哈（之前鸽了太久，做点啥证明自己还认真着…也是想说明一下没收录的都是为啥，其实不用看哈…）。另外也增加了很多，就没有一一列出。
by 兔子


I know , its just about as sad as my life xD


fixed in https://github.com/NixOS/nixpkgs/commit/585c642bf8adf495d66e1f4ea6d96bc767730347


yaosdifaskldjfa


Не повредит ограничение целостности на уровне базы данных `null: false` для названия станций и номера поездов.


asdfasdf


Arial is a property of Microsoft. Although MS allows downloading Arial for free, we may not redistribute it. It's not open source.


I formatted it wrong set_prop does work, I might re-commit it with the correct formatting or i'll just revert it. It makes no difference at all apart from cleaning up warnings at build time.


What the fuck, why? ![DansGame](https://cdn.betterttv.net/emotes/twitch_fixed/33_1x.png)

That was not a demand on the C&D, and I don't think the people in charge of music on TPP were even targeted by it. (I know some of the game's devs are involved with TPP as well, which is why I'm not sure.)


What about showing snackbar on the top?


There's probably a lot of errors in this , but its an attempt at binary @LegitSoulja

		genRandomBinary(length) {
			var chars = 1 + 0, response
			for(var i = 0; i < length; i++){
				response += chars[Math.floor(Math.random())];
			}
			return response;
		}


ffffffffffffffffffffffffffffffffff


nhhhhhhhhhhh


@FantasyIsBae In binary, you just don't write random numbers lol


I know , i was aiming for the 0's and 1's idea


There's a bit more to it i know


Thanks milo.... ;)


Не особенно хорошо что мы можем задать тип поезда в аргументе. По идее, за тип поезда отвечает непосредственно дочерний класс.


```
function genBinary(custom = "", resp = "") {
    custom = (custom)?custom:(this.letters + this.numbers).toString();
    resp = "";
    for (var i = 0; i < custom.length; i++) {
        resp+= custom[i].charCodeAt(0).toString(2) + " ";
    }
    return resp;
}
```


Oh ok  i get it  , also you did a better job than me xD


@FantasyIsBae updated it


Ok , so whats next ?


Also what time is it currently for you ?


![](https://github.trello.services/images/mini-trello-icon.png) [Create and list all characteristics of a profile page. (Show.html.erb)](https://trello.com/c/YZPuNXEE/16-create-and-list-all-characteristics-of-a-profile-page-show-html-erb)


@FantasyIsBae 6:26pm,

and look at the binary code, its not right.


Нет особого смысла в такой архитектуре: мы кидаем исключение и тут же его отлавливаем чтобы вывести текст. Того же эффекта можно добиться с помощью условного выражения, или `return`.


genBinary("", 5);

Supposed to generate 5 random letters


ok just let me update localy


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


wait


As far as i can tell, current stable hyperion [Version   : V1.03.2 (brindosch-99d9396/d3713a8-1469452981
Build Time: Jul 25 2016 06:54:40] does not support IPv6 as it uses `QHostAddress::Any` which means any IPv4 address in versions < 5. See http://blog.qt.io/blog/2011/07/05/ipv6-changes-in-qt5/

[Hyperion.ng](https://github.com/hyperion-project/hyperion.ng) links agains QT5 and will support IPv6 I guess ...


ok


ui


Стоит вызвать этот метод до того как объект добавляется в `@@stations` иначе может быть добавлен не валидный объект.


пропустили закрывающую треугольную скобку)


not updated


Здесь стоит возвращать `true`.


Why was this done?

See https://github.com/torch/torch7/issues/879


@mrjbq7: let me fix that for you: #1765.


Ok i've got to go as it is 23:30 PM in the UK , what time will you be back tomorrow  (We have like a 6 hour time difference)  @LegitSoulja


note to self, never spend so much time on small details again


![](https://github.trello.services/images/mini-trello-icon.png) [As client I want to have a video model.](https://trello.com/c/ft5QQTMs/6-as-client-i-want-to-have-a-video-model)


remote: minor change to index.html file