Are we really still discussing the issue of full member variable initialization? REALLY?

This is one of the simplest commits, and we are wasting hours discussing if we are burning CPU cycles with variable initialization, or if we should initialize all member variables. Honestly, if that's so important, we should start reviewing all commits up to now for similar reasons. And we should start optimizing ScummVM's performance to be on par with Unity. Or whatever.

This is really so not worth wasting our time on. Could we please move along to something more important or interesting?


:+1: :3


Yes, so please revert this commit and move on.


Thx


maybe now a kernel gets updated instead of installed. the "dnf system-upgrade" from fedora 23 to fedora 24 failes definitely. i had to disable this option and restore the defaults. or dnf system-upgrade fails with

> The operation would result in removing the booted kernel

with "#installonlypkgs=electron" in /etc/dnf/dnf.conf

`$ dnf config-manager --dump | grep installonlypkgs`

> installonlypkgs = ('kernel', 'installonlypkg(kernel)', 'installonlypkg(kernel-module)', 'installonlypkg(vm)')

with "installonlypkgs=electron" in /etc/dnf/dnf.conf

`$ dnf config-manager --dump | grep installonlypkgs`

> installonlypkgs = electron


this doesnt work


Обычно каталог `.idea` добавляется в [файл .gitignore](https://git-scm.com/docs/gitignore).


Some errors found


merged


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


added ko_KR


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 395](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1090&buildTypeId=XbimEssentials_XbimEssentials) outcome was **SUCCESS**
Summary: Running Build time: 00:02:06


Did you had any problems with the new version?

Thanks for the PR. Sorry I didn't see it before.


修正はfoo.texi.poにしていただくほうがよいです。
(foo.texi.origと翻訳されたfoo.texi.poを入力としてpo4a-translateを実行し、その出力が翻訳されたfoo.texiになるため、このファイルを訂正しても上書きされてしまうため）
あと、このバグはxrefの後にピリオドをつけ忘れたのではなく、xrefをrefに修正し忘れたバグです、すいませんm(__)m


I've started a project (https://github.com/birkett/Vertex-K8400-Firmware) to collect end-user patches, and provide updated Vertex firmware - based on newer versions of Marlin.

Can I include this patch in the project? (with full credit of course).


thanks


You all are missing the point. Your in-app gradle files will be included in any code checked in - where in fact you should have your API key completely hidden and never checked in.

Let's say my USER_HOME is this: "C:\Users\Heather\". In this USER_HOME is my AndroidStudioProject folder, containing the current project folder which contains some gradle files (C:\Users\Heather\AndroidStudioProjects\Sunshine-Version-2\.gradle\, or [USER_HOME]\AndroidStudioProjects\[CURRENT_PROJECT]\.gradle for other projects). However, the point is to NOT have the private API key stored anywhere in there. Instead, under C:\Users\Heather\, or whatever your USER_HOME is, there should be a .gradle folder. Open that folder. If this folder does not already contain a gradle.properties file, create a gradle.properties file or copy from C:\Users\Heather\AndroidStudioProjects\Sunshine-Version-2\gradle.properties (if it does already contain a gradle.properties file just use that one.) Open the gradle.properties file and add:

MyOpenWeatherMapApiKey="xxxxx"

-where xxxxx is your API key.

Note that you will have to turn on hidden files probably to get to [USER_HOME].gradle/ - and you will have to use the file system instead of the IDE to get there. And that that folder may be missing the gradle.properties file - if so, just create one by coping over or creating a new file called gradle.properties as stated above.

If you do this with every private API key you have and just add the variable name in the in-app gradle files, your API keys will remain secure and you no longer have to worry about checking them in by mistake.

Hope this makes sense.


private void validate() throws IllegalArgumentException {
+ for (int i=0; i<100; i++) {
+ System.out.print('.');
+ try {
+ Thread.currentThread().sleep(1);
+ } catch (InterruptedException e) {
+ break;
+ }
+ }


I fixed some stuff about notifications after this. There will be a new push tomorrow.


yay backgrounds


I like the UserData.TryGetValue("upgraded", out isupgraded);  pattern :)
Also, I have found that when I use ".SetBotPerUserInConversationData" it will remember the value in all conversations in Facebook if I set the value each time I send a response back to the user.


素晴らしい


Ah, OK.  For SMM 3.0.0 you can search for `:Error:` .


Are there any problems using the Materializer from the current RequestContext


Actually we are modifying the file to add py33-lint and py35-lint, just because some of us also do not have 3.4. I think this is fine as long only one lint and one unit is run on Travis.


\o/


This may be a comment on commit, whatever that means


Blocking Callback


Got all functions in script.js to work


added a quick <p> in index.html


Fixes #108


`ReverseProxyDirective` should read `ReverseProxyDirectives`


By the way, you can upgrade to Triple Twin from either Twin or Flank Guard.


Seems good!


It broke the tests (fixture loading, to be precise) lol, see b293900 for the fix.


I changed things further because "curl ... | sh" is just *asking* for trouble security-wise.  But it is a pain.  Travis doesn't directly support multiple languages, which is terrible, because lots of programs use many languages.  I'll try telling it "language: rust" and use cargo install; that seems plausible.


Thank you! :)


Please read https://sandstorm.io/news/2015-09-24-is-curl-bash-insecure-pgp-verified-install , then tell me what security problems:

1. exist when fetching a shell script from a HTTPS URL and immediately running it
2. do not exist when fetching a tarball from a HTTPS URL, unpacking it, and then running a rust binary contained inside it

This persistent misconception is very tiring.


You WORX realy fast-..... SIR!!!! thank you


This does fix the issue 👍  thanks!


Additionally, keep in mind that Travis runs in a dedicated virtual machine, precisely for sandboxing reasons, so the damage that can be done is basically nil (and anyway damage protection is the responsibility of the Travis team, since it's their hardware).


Okay, I got the main stuff working.  Now I'll add the grep for :Error: .


Absolutely no clue what happened to this commit message


Nangmao


Apparently this didn't work after all! How awesome! :no_mouth:

See commit f2200b9 where I realized this, and 835f3fd where I actually solved the problem.


Changed the formatting of B-squared.


This makes conda-build look for a C compiler to build plain Python packages. I had to downgrade to 1.20.3 to be able to continue building my packages. I doubt it was intended.


Offline usage is better in my opinion (we might add support for chrome
extensions later)
On Jun 24, 2016 9:50 PM, "legoboy0215" <notifications@github.com> wrote:

> Also, why not use a CDN instead of hosting Bootstrap yourself
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/thunderboltstudios/thunderboltstudios.github.io/commit/a35c0a75726026c985cff105706dbaa8894f092b#commitcomment-18011994>,
> or mute the thread
> <https://github.com/notifications/unsubscribe/AJc85y-DV2rLcvSBlsGQHe3p57c3ATJsks5qPJdjgaJpZM4I9VGb>
> .
>


afa dasfasd


This commit implements tuplet groupings for the Humdrum importer.  The implementation is fairly well generalized, but will not yet allow for nested tuplets.

Sample Humdrum data:

```
**kern
*clefG2
*M4/4
=1-
24cLL
24d
24e
24f
24g
24fJJ
28eLL
28d
28c
28d
28e
28f
28gJJ
18fLL
18e
18d
18c
18d
18e
18f
18g
18fJJ
=2
12eL
48dKK
12..cJ
12d
12eL
12fJ
12gL
12fJ
12e
4d
=3
16cLL
16c
48dL
48d
48dJ
16cJJ
2c
24dLL
24e
12f
48.g
96f
24eJJ
=4
12.dL
24ck
12dJ
4e
20fLL
20g
20f
20eJJ
20d
4c
=5
3d
6.e
12f
3g
=6
40%3fLL
40%3e
40%3d
40%3c
40%3d
40%3e
40%3f
40%3g
40%3f
40%3eJJ
8dL
8cJ
==
*-
```

Verovio rendering:

![screen shot 2016-06-25 at 6 05 21 pm](https://cloud.githubusercontent.com/assets/3487289/16360025/456c3abe-3b00-11e6-83cf-1812ce6525ab.png)

Notes:

* In the first beat of measure 2, the partial beam on the second note is pointing the wrong way.
* other problems put into issues (in m 3 & 6).

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-06-25 18:05:09</date>
            </pubStmt>
        </fileDesc>
        <encodingDesc>
            <projectDesc>
                <p>Encoded with Verovio version 0.9.12-dev-b005b99-dirty</p>
            </projectDesc>
        </encodingDesc>
    </meiHead>
    <music>
        <body>
            <mdiv>
                <score>
                    <scoreDef xml:id="scoredef-000000081216521">
                        <staffGrp xml:id="m-000000003395927">
                            <staffDef xml:id="staffdef-000000167038527" clef.shape="G" clef.line="2" meter.count="4" meter.unit="4" n="1" lines="5" />
                        </staffGrp>
                    </scoreDef>
                    <section>
                        <measure xml:id="measure-000000011163330" n="1">
                            <staff xml:id="staff-000000022836729" n="1">
                                <!-- kern: =1-  24cLL  24d  24e  24f  24g  24fJJ  28eLL  28d  28c  28d  28e  28f  28gJJ  18fLL  18e  18d  18c  18d  18e  18f  18g  18fJJ  =2 -->
                                <layer xml:id="layer-000000061588349" n="1">
                                    <beam xml:id="beam-000000028263789">
                                        <tuplet xml:id="tuplet-000000006119006" num="6" numbase="4" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000192425599" dur="16" oct="4" pname="c" accid.ges="n" />
                                            <note xml:id="note-000000201428459" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000114904408" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000181098277" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000090170326" dur="16" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000013469478" dur="16" oct="4" pname="f" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                    <beam xml:id="beam-000000036745394">
                                        <tuplet xml:id="tuplet-000000178293487" num="7" numbase="4" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000194713434" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000213105620" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000092930554" dur="16" oct="4" pname="c" accid.ges="n" />
                                            <note xml:id="note-000000018966295" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000079956934" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000155678532" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000209775310" dur="16" oct="4" pname="g" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                    <beam xml:id="beam-000000169735251">
                                        <tuplet xml:id="tuplet-000000023095285" num="9" numbase="8" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000112171747" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000209406492" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000198717063" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000071113388" dur="16" oct="4" pname="c" accid.ges="n" />
                                            <note xml:id="note-000000128062560" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000139343300" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000111927727" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000188384643" dur="16" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000145555809" dur="16" oct="4" pname="f" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-000000157869649" n="2">
                            <staff xml:id="staff-000000075897316" n="1">
                                <!-- kern: =2  12eL  48dKK  12..cJ  12d  12eL  12fJ  12gL  12fJ  12e  4d  =3 -->
                                <layer xml:id="layer-000000000903694" n="1">
                                    <beam xml:id="beam-000000155999529">
                                        <tuplet xml:id="tuplet-000000021299280" num="3" numbase="2" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000206235134" dur="8" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000155302644" dur="32" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000119928270" dots="2" dur="8" oct="4" pname="c" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                    <tuplet xml:id="tuplet-000000006291219" num="3" numbase="2" bracket.visible="true" num.format="count">
                                        <note xml:id="note-000000080327342" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <beam xml:id="beam-000000153428254">
                                            <note xml:id="note-000000185061790" dur="8" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000132938579" dur="8" oct="4" pname="f" accid.ges="n" />
                                        </beam>
                                    </tuplet>
                                    <tuplet xml:id="tuplet-000000056726040" num="3" numbase="2" bracket.visible="true" num.format="count">
                                        <beam xml:id="beam-000000126571780">
                                            <note xml:id="note-000000209357467" dur="8" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000019007385" dur="8" oct="4" pname="f" accid.ges="n" />
                                        </beam>
                                        <note xml:id="note-000000126314831" dur="8" oct="4" pname="e" accid.ges="n" />
                                    </tuplet>
                                    <note xml:id="note-000000185791322" dur="4" oct="4" pname="d" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-000000153532838" n="3">
                            <staff xml:id="staff-000000170776287" n="1">
                                <!-- kern: =3  16cLL  16c  48dL  48d  48dJ  16cJJ  2c  24dLL  24e  12f  48.g  96f  24eJJ  =4 -->
                                <layer xml:id="layer-000000125176519" n="1">
                                    <beam xml:id="beam-000000166787677">
                                        <note xml:id="note-000000090089632" dur="16" oct="4" pname="c" accid.ges="n" />
                                        <note xml:id="note-000000160485653" dur="16" oct="4" pname="c" accid.ges="n" />
                                        <tuplet xml:id="tuplet-000000042924465" num="3" numbase="2" bracket.visible="true" num.format="count">
                                            <note xml:id="note-000000091731269" dur="32" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000048941347" dur="32" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000070987270" dur="32" oct="4" pname="d" accid.ges="n" />
                                        </tuplet>
                                        <note xml:id="note-000000155882662" dur="16" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                    <note xml:id="note-000000204602620" dur="2" oct="4" pname="c" accid.ges="n" />
                                    <beam xml:id="beam-000000205420444">
                                        <tuplet xml:id="tuplet-000000206696432" num="3" numbase="2" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000177400363" dur="16" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000001607126" dur="16" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000167436220" dur="8" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000037991956" dots="1" dur="32" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000083929684" dur="64" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000138948041" dur="16" oct="4" pname="e" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-000000126022465" n="4">
                            <staff xml:id="staff-000000206814282" n="1">
                                <!-- kern: =4  12.dL  24ck  12dJ  4e  20fLL  20g  20f  20eJJ  20d  4c  =5 -->
                                <layer xml:id="layer-000000010608220" n="1">
                                    <beam xml:id="beam-000000051219242">
                                        <tuplet xml:id="tuplet-000000130362979" num="3" numbase="2" bracket.visible="false" num.format="count">
                                            <note xml:id="note-000000147786509" dots="1" dur="8" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000068285769" dur="16" oct="4" pname="c" accid.ges="n" />
                                            <note xml:id="note-000000063660306" dur="8" oct="4" pname="d" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                    <note xml:id="note-000000062425132" dur="4" oct="4" pname="e" accid.ges="n" />
                                    <tuplet xml:id="tuplet-000000133447090" num="5" numbase="4" bracket.visible="true" num.format="count">
                                        <beam xml:id="beam-000000013334148">
                                            <note xml:id="note-000000124494499" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000085735824" dur="16" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000000473553" dur="16" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000013329222" dur="16" oct="4" pname="e" accid.ges="n" />
                                        </beam>
                                        <note xml:id="note-000000041701536" dur="16" oct="4" pname="d" accid.ges="n" />
                                    </tuplet>
                                    <note xml:id="note-000000153814981" dur="4" oct="4" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-000000027579811" n="5">
                            <staff xml:id="staff-000000202529762" n="1">
                                <!-- kern: =5  3d  6.e  12f  3g  =6 -->
                                <layer xml:id="layer-000000156134481" n="1">
                                    <tuplet xml:id="tuplet-000000141955578" num="3" numbase="2" bracket.visible="true" num.format="count">
                                        <note xml:id="note-000000207822716" dur="2" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-000000208992734" dots="1" dur="4" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-000000116639069" dur="8" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-000000129771466" dur="2" oct="4" pname="g" accid.ges="n" />
                                    </tuplet>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-000000084642210" n="6" right="end">
                            <staff xml:id="staff-000000149574807" n="1">
                                <!-- kern: =6  40%3fLL  40%3e  40%3d  40%3c  40%3d  40%3e  40%3f  40%3g  40%3f  40%3eJJ  8dL  8cJ  == -->
                                <layer xml:id="layer-000000059430793" n="1">
                                    <beam xml:id="beam-000000058703815">
                                        <tuplet xml:id="tuplet-000000081039676" num="10" numbase="6" bracket.visible="false" num.format="ratio">
                                            <note xml:id="note-000000099717369" dur="8" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000053591067" dur="8" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000050433282" dur="8" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000020376783" dur="8" oct="4" pname="c" accid.ges="n" />
                                            <note xml:id="note-000000163711994" dur="8" oct="4" pname="d" accid.ges="n" />
                                            <note xml:id="note-000000151448067" dur="8" oct="4" pname="e" accid.ges="n" />
                                            <note xml:id="note-000000190047006" dur="8" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000167601658" dur="8" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-000000026781362" dur="8" oct="4" pname="f" accid.ges="n" />
                                            <note xml:id="note-000000001785445" dur="8" oct="4" pname="e" accid.ges="n" />
                                        </tuplet>
                                    </beam>
                                    <beam xml:id="beam-000000157961505">
                                        <note xml:id="note-000000139745239" dur="8" oct="4" pname="d" accid.ges="n" />
                                        <note xml:id="note-000000210130640" dur="8" oct="4" pname="c" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```


Why change it to CTRL+SHIFT?


Why do you need to set it to zero when you are calculating in the next step


CNAME


You do not need return statements. Just a list is fine


Indeed, not intended.  Sorry for the trouble.  https://github.com/conda/conda-build/pull/1049 is intended to fix it.  If you have time, I'd appreciate your feedback.  Otherwise, I'll be testing this on a clean windows VM on Monday, and will tag another bug-fix release.


Removed


removed


this link is broken, no peerage.md


Uh, I think it was to match my mod, but I actually forgot I did this and I could probably change it back (I will probably just throw out the favorites menu in my mod as it is right now because it is extremely glitchy)