@jensens Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.namedfile/92/violations
```
plone/namedfile/testing.py:18:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/namedfile/testing.py:22:36: C812 missing trailing comma
plone/namedfile/file.py:267:9: Q001 Remove bad quotes from multiline string.
plone/namedfile/file.py:308:9: Q001 Remove bad quotes from multiline string.
plone/namedfile/handler.py:11:23: C812 missing trailing comma
plone/namedfile/interfaces.py:17:25: C812 missing trailing comma
plone/namedfile/scaling.py:193:25: C815 missing trailing comma in Python 3.5+
plone/namedfile/scaling.py:196:5: C901 'DefaultImageScalingFactory.__call__' is too complex (15)
plone/namedfile/scaling.py:203:25: C816 missing trailing comma in Python 3.6+
plone/namedfile/scaling.py:243:29: C815 missing trailing comma in Python 3.5+
plone/namedfile/scaling.py:407:21: C816 missing trailing comma in Python 3.6+
plone/namedfile/scaling.py:434:25: C815 missing trailing comma in Python 3.5+
plone/namedfile/scaling.py:446:25: C815 missing trailing comma in Python 3.5+
plone/namedfile/scaling.py:460:21: C816 missing trailing comma in Python 3.6+
plone/namedfile/scaling.py:486:29: C815 missing trailing comma in Python 3.5+
plone/namedfile/scaling.py:500:17: C816 missing trailing comma in Python 3.6+
plone/namedfile/utils/__init__.py:84:66: C812 missing trailing comma
plone/namedfile/utils/__init__.py:151:15: T000 Todo note found.
plone/namedfile/utils/__init__.py:156:73: C812 missing trailing comma
plone/namedfile/utils/__init__.py:176:15: T000 Todo note found.
plone/namedfile/utils/__init__.py:183:18: C812 missing trailing comma
plone/namedfile/utils/__init__.py:188:1: C901 'rotate_image' is too complex (20)
plone/namedfile/utils/__init__.py:219:14: C812 missing trailing comma
plone/namedfile/utils/__init__.py:271:25: F821 undefined name 'StringIO'
plone/namedfile/utils/__init__.py:276:1: E302 expected 2 blank lines, found 1
plone/namedfile/utils/__init__.py:280:1: E302 expected 2 blank lines, found 1
plone/namedfile/utils/tiff_utils.py:11:1: C901 'process_tiff' is too complex (11)
plone/namedfile/utils/tiff_utils.py:20:7: T000 Todo note found.
plone/namedfile/utils/tiff_utils.py:81:7: T000 Todo note found.
plone/namedfile/utils/tiff_utils.py:82:7: T000 Todo note found.
plone/namedfile/tests/test_blobfile.py:40:31: C812 missing trailing comma
plone/namedfile/tests/test_blobfile.py:45:35: C812 missing trailing comma
plone/namedfile/tests/test_blobfile.py:50:46: C812 missing trailing comma
plone/namedfile/tests/test_blobfile.py:55:32: C812 missing trailing comma
plone/namedfile/tests/test_scaling.py:85:80: E501 line too long (86 > 79 characters)
plone/namedfile/tests/test_scaling.py:102:80: E501 line too long (81 > 79 characters)
plone/namedfile/tests/test_scaling.py:133:80: E501 line too long (86 > 79 characters)
plone/namedfile/tests/test_scaling.py:156:80: E501 line too long (86 > 79 characters)
plone/namedfile/tests/test_scaling.py:178:80: E501 line too long (86 > 79 characters)
plone/namedfile/tests/test_scaling.py:200:80: E501 line too long (86 > 79 characters)
plone/namedfile/tests/test_image.py:25:80: E501 line too long (80 > 79 characters)
plone/namedfile/tests/test_doctests.py:27:20: C812 missing trailing comma
plone/namedfile/tests/test_doctests.py:43:51: C812 missing trailing comma
plone/namedfile/tests/test_doctests.py:45:10: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:116:28: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:146:70: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:153:76: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:164:74: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:197:75: C812 missing trailing comma
plone/namedfile/tests/test_scaling_functional.py:202:78: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


comment for hallo text


token又封了


Where is `qpci_set_pc` called? I wouldn't have expected it to be called from these tests (thinking that the constructor for the machine is outside the scope of these unit tests).

However, we could also move the assertion in qpci_init_pc (kind of cheating, but less ugly than `0xffffffff`. :)


No vrod razobralsya...rabotaet)


`bytes32 password` will be just as good.


jenkins produced corrupted (invalid or corrupted package (PGP signature)) package, why? :-(


C++


Voll gut gemacht Frank!


- по-прежнему, выполнен комит лишних файлов!
- нет валидации формальных параметров
- округление полученного результата категорически здесь не приветствуется, поскольку не имеет смысла
- соответственно переменная fractionalPart не нужна


Вынести в блок <properties>


{ENTER}
[f03072018094749_download.txt](https://github.com/githubuserdlp/TEST/files/2158665/f03072018094749_download.txt)


it happens


Code style.


:smile:


Удалить комменты к зависимостям


Perfecto, cambios ok 🍄


有興趣可以電郵我研究 hklcf.github@hkit.club


done


@renwokuang 對T_T


Markdown links support optional titles, e.g. `[an example](http://example.com/ "Title")`, so it probably won't make any difference. But why not keep them consistent (revert this or update other links as well)?


If I've got it correctly, this is how phpunit 7.1 works when testing output like echo and print. Otherwise, a command like $ ../vendor/bin/phpunit HelloWorldTest would give us a failed test response. I think I need a hint to make this in another way.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


Hi, Sure.
![img_20180625_153746](https://user-images.githubusercontent.com/7834974/42212790-7668c338-7eb7-11e8-94b4-9e40c71060aa.jpg)


Test Jenkins


- Валидацию логично было бы поместить  до выполнения каких-либо действий


.destination:hoverh2 {
   transform:rotate(0deg);
}


zabbix percona mysql监控


.destination:hoverh2 {
   transform:rotate(0deg);
}
h2 {
   margin : 0;
   transform : rotate(-45deg);
   transition : transform 0.5s;
   text-shadow : 0 0 5px #01579b;
}


- эта часть логики достойна быть выделенной в отдельный говорящий что он делает метод


We don't have to build the cpp package if we don't use it


add animation


Our default is to test without MKLDNN on CPU. Could you disable it?


> 最近流行のGoogle style

リンク張っておきます。
https://ttsuki.github.io/styleguide/cppguide.ja.html

個人的にはファイル内で一貫されたルールが採られていればどっちでも良いです。

どちらかというと namespace 部のインデントの取り方が気になりました（こういう書き方って見たことないです）。


- вроде уже писала про нецелесообразность этого метода


what you can do is simply change the password right after the database is created using AWS CLI and `provisioner` block, then store the password securely in encrypted form (using KMS). The API server then will need to download this password before startup.

If that's too overkill you can simply change the password manually using the AWS console afterwards.
You can also use something like https://console.aws.amazon.com/secretsmanager/home


Исправлено


@keyonjie
The soft #11 is need to change the cfg->num_hw_configs to not be 1 for ONE DAI.
The https://github.com/thesofproject/linux/issues/11 may need to refine if we want to have more config for one DAI.


Thank you for the review!

You are correct, and the remainder from the delayPrimitive also causes bias to the resulting delays. This might need to be revised and re-implemented in case this implementation leaks enough information to derive some of the key material.


Is this for me?
Video playlist recommended by Yves Muya-Benda helped me start exploring github quickly to decided whether it is for me!
https://www.youtube.com/watch?v=BCQHnlnPusY


What is? The default destructor or the class?


Command line options handled by structopt


These variables are only used locally in the loop; there's no need to declare them here.


These variables only used locally in the loop below; there's no need to declare them here.


Thanks 👍


All parsing code is handled by structopt, these lines don't need to be in main


All of the logic that determined `num` before is now made together in a single expression.


This issue was discovered by Zhouyuan Yang of Fortinet's FortiGuard Labs.


Bug introduced by 98eced015b8ec4b8ee86a87e24ab0dbf94a3a40b


We use the `if let` syntax to explicitly announce that we don't care about the `None` case.


This is for springboard


Bug: `sourceLine` is initialized to `null`, so the conditional test will always fail and you'll never read a line.


Ese print test mmm traten de no subirlo... osea acá ya fue, no pasa nada, pero en un laburo posta el consejo es no lo suban


git init
git add
git commit


Hmm after reading the linked thread i'm not sure i understand. I'm
becoming more dumb

But this commit is just the prelude to something else.. see the
attached petget.zip in the previous comment, unzip it in /usr/local in
a 32 bit pup and see for yourself.

The "packages to install" at the bottom will become the "Pkg Info",
assuming i find the inspiration to continue with this since i don't
really think continuing is something reasonable. But it was just a
"proof of concept" as i call it.

One thing is for sure, most of what zb does, i want to undo it, most
of what bk does, i want to undo it. And basically most of the puppy
stuff, i want to delete it.. This surely reflects a conflict of
interest...

I can certainly revert this if you want..


This case is one of many where accessing an `Option<T>` is used over having a separate `bool` and variable to denote a possible null value.


NO


The `ErrorCode` enum here encodes several `bool`s and their values, allowing a simple `match` statement instead nested `if` statements.


This part doesn't need to be in a loop. Instead of busy-waiting until the next iteration, just sleep the thread.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


if(i >= len || i < 0)
return 0;


Here is where we use structopt to serialize all of the command line options into a struct.


We can just check if `duration_since` succeeds, no need to match on the `Err` case.


Sleep instead of busy-waiting in a loop.


i like it! although i wouldn't waste any time on the legacy meeting format, it'll be cheaper to let that tech debt grow until moving to the new meeting becomes most important issue to address


I think it's easier to do this as follows:
1. Read the first `startLine -1` lines.
2. Read the next `startColumn - 1` characters.
... with appropriate checks for EOF.

No need to read past the column and then back up.


> It makes no sense to “clone” an immutable object by creating a new instance. Clone is only meaningful with a mutable object.

Whether or not that's true (and Joshua Bloch certainly agrees that it's at least "wasteful"—"Effective Java", 3rd ed, Item 13), it's not _prohibited_ in any sense, in which case...

> I guess you could call it an optimization.

I think you could probably argue it's _broken._ Although `Cloneable`/`clone()` is an ugly area of Java (Bloch calls it "fragile, dangerous and _extralinguistic_"), the [Javadocs for `Object.clone()`](https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html#clone--) do provide a "general intent" that, among other things:

    x.clone() != x

An implementation of `clone()` that returns `this` would break that "general intent", though the docs also allow that "The precise meaning of "copy" may depend on the class of the object". Personally, I'd just steer well clear of the `clone()` method here.


ta bien


Shit -- do we have to go back and release 2.6.1 -- that's gonna be a pain...


In the `parse` part of the proc macro we can specify the name of the function we want to handle the parsing. In this case it is `std::time::Duration::parse_duration`


`get_values` is a custom parser declared below that converts a comma/space/newline separated list of items into a `Vec<String>`


Bug: The code doesn't handle the case where the line is longer the endColumn (the usual case).
```
if (sourceLine != null)
{
    endColumn = sourceLine.Length >= v2Region.EndColumn
        ? v2Region.EndColumn
        : sourceLine.Length + 1;
}
```
**NOTE** the "+ 1". If the line is 5 characters long, endColumn is 6 (because regions are "half-open" -- that is, they do _not_ include the character at the endColumn position.


3982683-EIRFormulatedWWHP (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1684 of 1684 tests passed, 0 test warnings)

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


This time out custom parser is doing the job of compiling our regex, an semi-expensive one-time operation that you don't want to do in a loop.


This enum is used to encode what kind of error code we want to watch for. `ErrorCode::Any` if obviously for any failure at all, and `ErrorCode::Code` for a specific code.


"transcoded"


Approved


Yes


Think this entry should be [`Forwarded`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded) as per the ticket?


Ese aporte si que se deja ver papa


@ThomasGaertner RL takes much time, yeah. Got a family, I now what you are talking about. 😄
On some days a week I got a couple of hours to work on code. If I'm in the right mood I'm looking into GPS and/or CP otherwise I'm just farming along.
When I got something ready I'll let you know and make a pull request.


🔥 [Jenkins job](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/xcode10/60/display/redirect) (on internal Jenkins) failed in stage 'Test run' 🔥 : hudson.AbortException: script returned exit code 2

✅ [Build succeeded](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/xcode10/60//console)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/xcode10/8a1db43d70f06902781eb4137c84405b8a8d66a7/60/jenkins-results/api-diff/index.html)
✅ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/xcode10/8a1db43d70f06902781eb4137c84405b8a8d66a7/60/jenkins-results/apicomparison/index.html) (please review changes)
✅ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/xcode10/8a1db43d70f06902781eb4137c84405b8a8d66a7/60/jenkins-results/generator-diff/index.html) (please review changes)
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/xcode10/8a1db43d70f06902781eb4137c84405b8a8d66a7/60/jenkins-results/tests/index.html) 🔥

# Test results

150 tests failed, 11 tests passed.

## Failed tests

 * apitest/Mac Unified: Failed (Test run crashed (exit code: 134).)
 * monotouch-test/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * framework-test/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * mini/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * interdependent-binding-projects/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * fsharp/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * mscorlib/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Core/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Data/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Net.Http/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Numerics/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Runtime.Serialization/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Transactions/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Web.Services/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml.Linq/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Security/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ComponentModel.DataAnnotations/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Json/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel.Web/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Sqlite/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Tds/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression.FileSystem/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.CSharp/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Security/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IdentityModel/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * introspection/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/iOS Unified 32-bits - simulator/Release: Skipped (No applicable devices found.)
 * link all/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * link all/iOS Unified 32-bits - simulator/Release: Skipped (No applicable devices found.)
 * link sdk/iOS Unified 32-bits - simulator/Debug: Skipped (No applicable devices found.)
 * link sdk/iOS Unified 32-bits - simulator/Release: Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 32-bits - simulator/Debug (static registrar): Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 32-bits - simulator/Release (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 32-bits - simulator/Debug (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * framework-test/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * mini/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * interdependent-binding-projects/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * fsharp/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * mscorlib/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Core/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Data/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Net.Http/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Numerics/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Runtime.Serialization/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Transactions/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Web.Services/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml.Linq/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Security/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ComponentModel.DataAnnotations/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Json/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel.Web/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Sqlite/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Tds/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression.FileSystem/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.CSharp/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.Security/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * System.IdentityModel/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * introspection/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/iOS Unified 64-bits - simulator/Release: Skipped (No applicable devices found.)
 * link all/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * link all/iOS Unified 64-bits - simulator/Release: Skipped (No applicable devices found.)
 * link sdk/iOS Unified 64-bits - simulator/Debug: Skipped (No applicable devices found.)
 * link sdk/iOS Unified 64-bits - simulator/Release: Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 64-bits - simulator/Debug (static registrar): Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 64-bits - simulator/Release (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/iOS Unified 64-bits - simulator/Debug (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * framework-test/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * mini/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * interdependent-binding-projects/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * fsharp/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * mscorlib/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Core/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Data/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Net.Http/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Numerics/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Runtime.Serialization/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Transactions/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Web.Services/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml.Linq/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Security/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ComponentModel.DataAnnotations/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Json/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel.Web/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Sqlite/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Tds/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression.FileSystem/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.CSharp/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Security/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IdentityModel/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * introspection/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/tvOS - simulator/Release: Skipped (No applicable devices found.)
 * link all/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * link all/tvOS - simulator/Release: Skipped (No applicable devices found.)
 * link sdk/tvOS - simulator/Debug: Skipped (No applicable devices found.)
 * link sdk/tvOS - simulator/Release: Skipped (No applicable devices found.)
 * monotouch-test/tvOS - simulator/Debug (static registrar): Skipped (No applicable devices found.)
 * monotouch-test/tvOS - simulator/Release (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/tvOS - simulator/Debug (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * framework-test/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * mini/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * interdependent-binding-projects/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * fsharp/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * mscorlib/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Core/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Data/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Net.Http/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Numerics/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Runtime.Serialization/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Transactions/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Web.Services/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Xml.Linq/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ComponentModel.DataAnnotations/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Json/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel.Web/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * Mono.Data.Sqlite/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IO.Compression.FileSystem/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.Security/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.ServiceModel/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * System.IdentityModel/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * introspection/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * dont link/watchOS - simulator/Release: Skipped (No applicable devices found.)
 * link all/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * link all/watchOS - simulator/Release: Skipped (No applicable devices found.)
 * link sdk/watchOS - simulator/Debug: Skipped (No applicable devices found.)
 * link sdk/watchOS - simulator/Release: Skipped (No applicable devices found.)
 * monotouch-test/watchOS - simulator/Debug (static registrar): Skipped (No applicable devices found.)
 * monotouch-test/watchOS - simulator/Release (all optimizations): Skipped (No applicable devices found.)
 * monotouch-test/watchOS - simulator/Debug (all optimizations): Skipped (No applicable devices found.)


@lmoran is this covered by a unit test?


Indeed, Thanks for spotting it.


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


The guidelines are not only to protect our limited computational resources per si. **The guidelines follow some programming principles based on the fact that a patch should walk with its own legs**. This is for simplicity and a clear code that will sum up lately in a better program and maintenance of the project.

If a patch shows it is not good enough to pass the boundaries this means it is not strong enough to spend lines of the code and cycles of the processor. If you commit such patch it will fulfill the space of a better patch in the future and continuously make the program less efficient.


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


Hi Tomas Great Video and I like that Alexa with Kodi Skill a lot!! can I try it I've been looking for something like that please thank you you're the best here's my email kevin_kc200912@yahoo.com


Yes @bencaradocdavies , it is supposed to be covered by {{testProxyBaseURLFlagSetWithTemplateForwarded}}, I will look into it as well.


Done diddly added a run image method


fix this tommorrow morning


add Omnibar tests!

Preview: documentation | landing | table


please how can i work with remix offline?


I don't know if this is important, but I have noticed that Nix 1.11.16 (`nix1`) fails to evaluate derivations with such `sha512` hashes with errors like:
```
error: hash ‘OX8XqP7/1a9cqkxYw2yXss15f26NKWBpDXQd0/uK/KPqdQhxbPa994hnzjcE2VqQpDslf55723cKPUOGSmMY3g==’ has wrong length for hash type ‘sha512’
```


Added so the css file could style the button container


@sectioneight  Why did you changed "response" to "result"?


Created multidev environment [sfgov#ci-691](https://dashboard.pantheon.io/sites/91d50373-c4cf-40e4-a646-cb73e16a140c#ci-691).

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


[0/1] Running tests...
Test project /u/grout2/Programming/SentimentAnalysis/_debug
    Start 1: parse_test
1/2 Test #1: parse_test .......................   Passed    0.01 sec
    Start 2: btree
2/2 Test #2: btree ............................***Exception: SegFault  0.10 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) =   0.13 sec

The following tests FAILED:
	  2 - btree (SEGFAULT)
FAILED: CMakeFiles/test.util
cd /u/grout2/Programming/SentimentAnalysis/_debug && /usr/bin/ctest --force-new-ctest-process
ninja: build stopped: subcommand failed.


The packet Serial is passed into the Clock constructor, this should return a reference to the serial.


thinks!


Added an option to hide the window when a new match is found.
Fixes #4


🔥 [Jenkins job](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/revert-4227-gh4225/1/display/redirect) (on internal Jenkins) failed in stage 'Test run' 🔥 : hudson.AbortException: script returned exit code 143

✅ [Build succeeded](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/revert-4227-gh4225/1//console)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/revert-4227-gh4225/df50f667af86b54f03400de4c53217d4bb1c015e/1/jenkins-results/api-diff/index.html)
⚠ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/revert-4227-gh4225/df50f667af86b54f03400de4c53217d4bb1c015e/1/jenkins-results/apicomparison/index.html) (🔥 breaking changes 🔥)
ℹ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/revert-4227-gh4225/df50f667af86b54f03400de4c53217d4bb1c015e/1/jenkins-results/generator-diff/index.html) (please review changes)
🔥 [Failed to publish results](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/revert-4227-gh4225/1//console) 🔥


Created multidev environment [sfgov#ci-692](https://dashboard.pantheon.io/sites/91d50373-c4cf-40e4-a646-cb73e16a140c#ci-692).

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


The Clock requires a pointer to the seial member of the PacketQueue class (See comment in PacketQueue->get_serial())


Readme update with each dependency install for unit test


그리고 해당 파일들의 추적을 제외시키려면, 아래 코드를 따라한다.

`git rm --cached filename`

예시. `git rm --cached node_modules/`

**주의! --cached 를 붙이지 않으면, 파일 자체가 지워진다.**


tzp tests

Preview: documentation | landing | table


Cleanup of pmo:aggregates and pmo:aggregatedIn definitions. Deletion of pmo:hasAggregatingInstance


This is how Electrum and electrum-server communicated originally.  I've updated the ElectrumX docs for this.


First commit


[R/datadocs.R:147:1:](https://github.com/jackwasey/icd/blob/ebed66ff0752790a2f1b7bc21b6fe702bd3e5f31/R/datadocs.R#L147) *style:* **Lines should not be more than 120 characters.**
```r
#'   \url{https://www.cms.gov/Research-Statistics-Data-and-Systems/Statistics-Trends-and-Reports/Reports/Downloads/Pope_2000_2.pdf}
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```


🔥 [Jenkins job](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/master/24/display/redirect) (on internal Jenkins) failed in stage 'Test run' 🔥 : hudson.AbortException: script returned exit code 143

✅ [Build succeeded](http://xamarin-jenkins.guest.corp.microsoft.com:8080/job/macios/job/master/24//console)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/master/4f0bac51616c6b1b029c81aeec48a5b775ec562e/24/jenkins-results/api-diff/index.html)
⚠ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/master/4f0bac51616c6b1b029c81aeec48a5b775ec562e/24/jenkins-results/apicomparison/index.html) (🔥 breaking changes 🔥)
ℹ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/master/4f0bac51616c6b1b029c81aeec48a5b775ec562e/24/jenkins-results/generator-diff/index.html) (please review changes)


Build version: __`0.10.0-renovate/node-8.11.302`__ :crossed_fingers: [`renovate/node-8.11`](https://github.com/streamich/ci-scripts/tree/renovate/node-8.11) on [*Travis*](https://travis-ci.org/streamich/ci-scripts/builds/399828702) :tada:


Funciona en modo local pero cuando se genera el deploy a Heroku el logfile compila con éxito pero la aplicación no puede ser servida.


Nah, I forgot to unlink.


@joshfraser I was wondering if that column should be renamed to "Resources" or something since "Docs" is one of the list items.


Las imagenes suben con exito pero luego de 15-20 minutos son removidas y retorna un estado 404, en modo local son persistentes y funciona a la perfección.


Are the internal stack entries helpful in debugging test errors?


In Cumulus switches, bridge port membership is explicit, so if you want a new port to be a part of an existing broadcasts domain (bridge), the configuration of the bridge needs to be updated to add the new port. See [this configuration](https://github.com/ceftb/prototypes/blob/dcomp/portal/switch/interfaces)


Is this not being used anymore?


个人建议这个 .binding 的颜色进一步变浅，目前貌似和 .label 的色差较小难以发觉。


I'm fine with "Resources".

Was curious about the breakout between Social and Community. The categories aren't very clear to me. Maybe we just use "Community" for both columns?

Also wondering if we should change the treatment of the office address and email address. They were valuable in the beginning to communicate that we're a real project, but it's possible we remove them going forward to cut down on spam & prevent folks from stopping by our offices uninvited.


This fix should now be available in the 1.13.2 release of AsyncSSH.


水电费


我觉得不OK，高光分量是图形学的术语，如果翻译成镜像反射太过直译；漫射是漫反射的简称，原文翻译为漫射可以使文章读起来比较紧凑。


a


别把高光直译成镜面反射


I'm told that Aure blessed the two columns based and Mitch was working from [this request](https://github.com/OriginProtocol/origin-website/issues/212#issue-332209138).


I think I have a better idea of what's going on now.


Did you do any Processing with this project for this code? As in, download the processing program to insert this second code and run it? Or did you only use the first code in Arduino IDE and everything worked fine after that (Blynk/LEDs ect)?


I want two columns, just not clear what counts as community vs social. The distinction is a bit blurry to me. I was suggesting a single "Community" header that covers both columns, but I don't feel strongly one way or other.


It might be clearer if we did:
```
try {
   const tree = mode.apply(expr, settings);
   return tree;
} catch (e) {
    Error.captureStackTrace(e, mode.get);
    throw e;
}
```


3982683-EIRFormulatedWWHP (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2312 of 2313 tests passed, 0 test warnings)

Failures:

integration Test Summary
 * Passed: 628
 * Failed: 1

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


See [this pull request](https://github.com/Microsoft/DirectXTex/pull/83)


Is `expected` the error?


See [this pull request](https://github.com/Microsoft/DirectXTex/pull/81)


3982683-EIRFormulatedWWHP (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


What is `expectFail`?  I thought it might be a boolean since we're passing `this.isNot` or `!this.isNot` for this param.  What am I missing?


This won't be the only class, the builder needs to be added for FsStateBackend as well as thats where the new properties are getting added. For the sake of time, i'll probably leave this out and followup with another PR?


Changes to the tests look good!


business card sample


I've done a first pass of this commit.


1) Genial las ganas que le están metiendo!
2) Ese print... pls...
3)Ojo con los espacios en blanco excesivos.
4)  Para la localización podrían usar un null pattern por ejemplo porque el 0,0 es una valor real... ¿cómo distinguen el valor real del "falso"?
5) Ojo! que inicializan todo cada vez al usar el @BeforeEach. En el caso del user tiene sentido porque así "limpian" la instancia entre tests. Pero hay casos en los que podría ser trabajo sea innecesario. Tengan cuidado, nada más :)
6) Aprovecho este espacio para comentar cosas generales del proyecto:
-armen jerarquía de carpetas para dividir las cosas.
-Eso de exceder al id del objeto públicamente en primera instancia me hace ruido... justificación?
- Podrían usar una interface por ejemplo para el usuario. Cuando el ranking "usa" la clase User... en realidad solo interesa tener "un objeto" que cumpla con cierto protocolo. Bien evitando "violar" objetos y exponer la estructura interna de User.
- Nombres de clases más explícitos: ej Normal debería ser NormalUser o algo así. Normal no me dice nada...
7) Por el nombre del test y leyendo entre "líneas" creo que tienen la intención de hacer un tipo de test e hicieron otro... cuidado.
8) En los tests deberían probar primero el estado inicial (o dan por hecho que arranca bien por otro test que hagan). En este caso les tomo como bien que solo se fijen que cambió la clase, pero para hacerlo completo deberían verificar que las cosas se guardan bien y demás.
9)No entiendo el for del testSecondRanking es un for que inicia en 22 y termina en 42 osea 20...Suponiendo que el usuario se inicializa bien (fijarse punto 5) tienen el mismo caso que en el otro test... (20 comments siendo 20 <22). Hay algo de todo esto que creo que está mal.
9.1) Deduzco por el índice del test segundo que "sería una continuación del primero" lo cual está mal. La idea de los tests es que sean independiente entre ellos y se puedan ejecutar en cualquier orden. NO pueden jamás para pasar de que se ejecuten en un orden determinado.
10) Esas preguntas del índice del for las veo innecesarias. ¿No podría hacer el for hasta el número y directamente una vez finalizado ejetuar el assert?
11) Siguiendo con el punto 10, si no se da la condición del if el test pasa igual y no testean nada...
Entonces o el if siempre es true (sería innecesario entonces) o faltan controlar cosas. Tengan en claro que entonces puede dar un falso positivo el test!!!!!! (Van a ver que pasa, pero en realidad no ejecutó ningún assert).
12) Qué tipo de tests son? porque por el nombre imagino una cosa pero el código me indica otra.
13) Si pueden armar carpetas mínimamente diferenciando el tipo de test (integración, unidad etc) los ayudaría.
14) Recuerden que pueden hacer jerarquías de tests, que pueden llamar métodos privados internos de la clase, etc ;)
15) muy bien agregando en un commit el test particular!


@hippogamesunity why I find your app amazing, and I use FastHub because I'm studying Java, but I find your app amazing with a lot of potential, I wanted a 1000x1000 image for a higher quality and please do not stop updating that app.


ハッシュのkey valueをシンボルで置き換えた。
単位の定義は変わらないものなので定数としてメソッド外に置き直した


Why not make it generic ?
```
*/AdblockDetector/handler.min.js$script,important,redirect=noopjs
```
other examples

https\://digiex.net/
https\://www.antronio.cl/
https\://forum.turkdevs.com/


I support this.


已在 3623a73 中修改


This change don't allow to connect to MongoDB Atlas with Mongoose by default.


Ok


Tests added

Preview: documentation | landing | table


s/separe/separate/

Maybe split in two headers, one for public functions and one for private functions (not used outside the infrastructure and gtest integration patches).


Why is this replacing `nikic/php-parser`?

This is causing me major problems


Care about naming conventions


and missing spaces


If it's a ThreadLocal why would you need synchronized?


No need for these comments, it's more or less self evident.


I know, I know, but I don't like this name particularly. More important, the cast to QOSGraphObject doesn't apply to `get_driver`, only `get_device`.  Do you mind getting rid of the macro and just including it verbatim whenever it is used?


Should this region be configurable?


Hello Jiri,
thanks for your detailed explanation!
This made it clear and I was able to successfully replace the ascii art.
Missing the two spaces  in front of all lines before the characters was the problem I run into.

Best regards
Benjamin


@jensens Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.tiles/16/violations
```
plone/tiles/testing.py:42:45: C812 missing trailing comma
plone/tiles/testing.py:45:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:47:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:58:33: C812 missing trailing comma
plone/tiles/data.py:28:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/data.py:205:1: C901 'map_to_pairs' is too complex (14)
plone/tiles/data.py:239:28: C812 missing trailing comma
plone/tiles/data.py:252:24: C812 missing trailing comma
plone/tiles/data.py:257:1: C901 'encode' is too complex (17)
plone/tiles/data.py:282:36: C812 missing trailing comma
plone/tiles/data.py:283:18: C812 missing trailing comma
plone/tiles/data.py:304:51: C812 missing trailing comma
plone/tiles/data.py:305:22: C812 missing trailing comma
plone/tiles/data.py:312:36: C812 missing trailing comma
plone/tiles/data.py:343:1: C901 'decode' is too complex (14)
plone/tiles/interfaces.py:70:37: C812 missing trailing comma
plone/tiles/type.py:21:20: C812 missing trailing comma
plone/tiles/type.py:41:16: Q000 Remove bad quotes.
plone/tiles/type.py:43:23: C812 missing trailing comma
plone/tiles/tile.py:9:1: I001 isort found an import in the wrong position
plone/tiles/tile.py:57:29: C812 missing trailing comma
plone/tiles/tile.py:89:48: C812 missing trailing comma
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:17:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:18:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:19:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:28:16: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:33:65: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:50:10: C812 missing trailing comma
plone/tiles/esi.py:55:17: C812 missing trailing comma
plone/tiles/esi.py:65:13: Q000 Remove bad quotes.
plone/tiles/esi.py:77:29: C812 missing trailing comma
plone/tiles/__init__.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/meta.py:23:15: Q000 Remove bad quotes.
plone/tiles/meta.py:24:21: Q000 Remove bad quotes.
plone/tiles/meta.py:29:15: Q000 Remove bad quotes.
plone/tiles/meta.py:30:21: Q000 Remove bad quotes.
plone/tiles/meta.py:31:23: C812 missing trailing comma
plone/tiles/meta.py:35:15: Q000 Remove bad quotes.
plone/tiles/meta.py:37:23: C812 missing trailing comma
plone/tiles/meta.py:41:15: Q000 Remove bad quotes.
plone/tiles/meta.py:42:21: Q000 Remove bad quotes.
plone/tiles/meta.py:43:23: C812 missing trailing comma
plone/tiles/meta.py:47:15: Q000 Remove bad quotes.
plone/tiles/meta.py:48:21: Q000 Remove bad quotes.
plone/tiles/meta.py:49:21: Q000 Remove bad quotes.
plone/tiles/meta.py:54:15: Q000 Remove bad quotes.
plone/tiles/meta.py:55:21: Q000 Remove bad quotes.
plone/tiles/meta.py:60:15: Q000 Remove bad quotes.
plone/tiles/meta.py:61:21: Q000 Remove bad quotes.
plone/tiles/meta.py:66:15: Q000 Remove bad quotes.
plone/tiles/meta.py:67:21: Q000 Remove bad quotes.
plone/tiles/meta.py:72:15: Q000 Remove bad quotes.
plone/tiles/meta.py:77:15: Q000 Remove bad quotes.
plone/tiles/meta.py:78:23: C812 missing trailing comma
plone/tiles/meta.py:82:15: Q000 Remove bad quotes.
plone/tiles/meta.py:83:21: Q000 Remove bad quotes.
plone/tiles/meta.py:84:23: C812 missing trailing comma
plone/tiles/meta.py:88:15: Q000 Remove bad quotes.
plone/tiles/meta.py:89:21: Q000 Remove bad quotes.
plone/tiles/meta.py:94:15: Q000 Remove bad quotes.
plone/tiles/meta.py:95:21: Q000 Remove bad quotes.
plone/tiles/meta.py:126:26: C812 missing trailing comma
plone/tiles/meta.py:139:80: C812 missing trailing comma
plone/tiles/tests/test_data.py:19:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:25:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:29:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:38:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:47:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:50:1: E305 expected 2 blank lines after class or function definition, found 1
plone/tiles/tests/test_data.py:62:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:68:78: C812 missing trailing comma
plone/tiles/tests/test_data.py:73:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:77:54: C812 missing trailing comma
plone/tiles/tests/test_data.py:82:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:86:15: C812 missing trailing comma
plone/tiles/tests/test_data.py:96:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:101:40: C812 missing trailing comma
plone/tiles/tests/test_data.py:102:14: C812 missing trailing comma
plone/tiles/tests/test_data.py:107:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:111:15: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:17:45: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:19:50: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


DrillVersionInfo is not found,How to get it


[toptalk.zip](https://github.com/EmptyWalletException/TopTalk/files/2162756/toptalk.zip)
解压后即可,另外我收到了此消息的邮件,但是邮件回复不知道是否能到达你的邮箱,你可以仔细查看项目里的controller来跳转到投稿功能,通过投稿即可向数据库中添加数据


Despite of you sometimes you used not really cool variable namings, it's a nice looking code! Good job! 👍


@jensens Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.tiles/17/violations
```
plone/tiles/testing.py:42:45: C812 missing trailing comma
plone/tiles/testing.py:45:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:47:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:58:33: C812 missing trailing comma
plone/tiles/data.py:28:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/data.py:205:1: C901 'map_to_pairs' is too complex (14)
plone/tiles/data.py:239:28: C812 missing trailing comma
plone/tiles/data.py:252:24: C812 missing trailing comma
plone/tiles/data.py:257:1: C901 'encode' is too complex (17)
plone/tiles/data.py:282:36: C812 missing trailing comma
plone/tiles/data.py:283:18: C812 missing trailing comma
plone/tiles/data.py:304:51: C812 missing trailing comma
plone/tiles/data.py:305:22: C812 missing trailing comma
plone/tiles/data.py:312:36: C812 missing trailing comma
plone/tiles/data.py:343:1: C901 'decode' is too complex (14)
plone/tiles/interfaces.py:70:37: C812 missing trailing comma
plone/tiles/type.py:21:20: C812 missing trailing comma
plone/tiles/type.py:41:16: Q000 Remove bad quotes.
plone/tiles/type.py:43:23: C812 missing trailing comma
plone/tiles/tile.py:9:1: I001 isort found an import in the wrong position
plone/tiles/tile.py:57:29: C812 missing trailing comma
plone/tiles/tile.py:89:48: C812 missing trailing comma
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:12:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/esi.py:17:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:18:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:19:1: I001 isort found an import in the wrong position
plone/tiles/esi.py:28:16: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:33:65: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:50:10: C812 missing trailing comma
plone/tiles/esi.py:55:17: C812 missing trailing comma
plone/tiles/esi.py:65:13: Q000 Remove bad quotes.
plone/tiles/esi.py:77:29: C812 missing trailing comma
plone/tiles/__init__.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/meta.py:23:15: Q000 Remove bad quotes.
plone/tiles/meta.py:24:21: Q000 Remove bad quotes.
plone/tiles/meta.py:29:15: Q000 Remove bad quotes.
plone/tiles/meta.py:30:21: Q000 Remove bad quotes.
plone/tiles/meta.py:31:23: C812 missing trailing comma
plone/tiles/meta.py:35:15: Q000 Remove bad quotes.
plone/tiles/meta.py:37:23: C812 missing trailing comma
plone/tiles/meta.py:41:15: Q000 Remove bad quotes.
plone/tiles/meta.py:42:21: Q000 Remove bad quotes.
plone/tiles/meta.py:43:23: C812 missing trailing comma
plone/tiles/meta.py:47:15: Q000 Remove bad quotes.
plone/tiles/meta.py:48:21: Q000 Remove bad quotes.
plone/tiles/meta.py:49:21: Q000 Remove bad quotes.
plone/tiles/meta.py:54:15: Q000 Remove bad quotes.
plone/tiles/meta.py:55:21: Q000 Remove bad quotes.
plone/tiles/meta.py:60:15: Q000 Remove bad quotes.
plone/tiles/meta.py:61:21: Q000 Remove bad quotes.
plone/tiles/meta.py:66:15: Q000 Remove bad quotes.
plone/tiles/meta.py:67:21: Q000 Remove bad quotes.
plone/tiles/meta.py:72:15: Q000 Remove bad quotes.
plone/tiles/meta.py:77:15: Q000 Remove bad quotes.
plone/tiles/meta.py:78:23: C812 missing trailing comma
plone/tiles/meta.py:82:15: Q000 Remove bad quotes.
plone/tiles/meta.py:83:21: Q000 Remove bad quotes.
plone/tiles/meta.py:84:23: C812 missing trailing comma
plone/tiles/meta.py:88:15: Q000 Remove bad quotes.
plone/tiles/meta.py:89:21: Q000 Remove bad quotes.
plone/tiles/meta.py:94:15: Q000 Remove bad quotes.
plone/tiles/meta.py:95:21: Q000 Remove bad quotes.
plone/tiles/meta.py:126:26: C812 missing trailing comma
plone/tiles/meta.py:139:80: C812 missing trailing comma
plone/tiles/tests/test_data.py:19:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:25:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:29:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:38:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:47:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:50:1: E305 expected 2 blank lines after class or function definition, found 1
plone/tiles/tests/test_data.py:62:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:68:78: C812 missing trailing comma
plone/tiles/tests/test_data.py:73:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:77:54: C812 missing trailing comma
plone/tiles/tests/test_data.py:82:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:86:15: C812 missing trailing comma
plone/tiles/tests/test_data.py:96:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:101:40: C812 missing trailing comma
plone/tiles/tests/test_data.py:102:14: C812 missing trailing comma
plone/tiles/tests/test_data.py:107:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:111:15: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:17:45: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:19:50: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


No problem at all


BRAVO


@jensens Jenkins CI reporting about code analysis
See the full report here: https://jenkins.plone.org/job/package-plone.tiles/18/violations
```
plone/tiles/testing.py:42:45: C812 missing trailing comma
plone/tiles/testing.py:45:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:47:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/tiles/testing.py:58:33: C812 missing trailing comma
plone/tiles/data.py:206:1: C901 'map_to_pairs' is too complex (14)
plone/tiles/data.py:240:28: C812 missing trailing comma
plone/tiles/data.py:253:24: C812 missing trailing comma
plone/tiles/data.py:258:1: C901 'encode' is too complex (17)
plone/tiles/data.py:283:36: C812 missing trailing comma
plone/tiles/data.py:284:18: C812 missing trailing comma
plone/tiles/data.py:305:51: C812 missing trailing comma
plone/tiles/data.py:306:22: C812 missing trailing comma
plone/tiles/data.py:313:36: C812 missing trailing comma
plone/tiles/data.py:344:1: C901 'decode' is too complex (14)
plone/tiles/interfaces.py:70:37: C812 missing trailing comma
plone/tiles/type.py:21:20: C812 missing trailing comma
plone/tiles/type.py:41:16: Q000 Remove bad quotes.
plone/tiles/type.py:43:23: C812 missing trailing comma
plone/tiles/tile.py:57:29: C812 missing trailing comma
plone/tiles/tile.py:89:48: C812 missing trailing comma
plone/tiles/esi.py:31:16: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:36:65: Q001 Remove bad quotes from multiline string.
plone/tiles/esi.py:53:10: C812 missing trailing comma
plone/tiles/esi.py:58:17: C812 missing trailing comma
plone/tiles/esi.py:68:13: Q000 Remove bad quotes.
plone/tiles/esi.py:80:29: C812 missing trailing comma
plone/tiles/__init__.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/tiles/meta.py:23:15: Q000 Remove bad quotes.
plone/tiles/meta.py:24:21: Q000 Remove bad quotes.
plone/tiles/meta.py:29:15: Q000 Remove bad quotes.
plone/tiles/meta.py:30:21: Q000 Remove bad quotes.
plone/tiles/meta.py:31:23: C812 missing trailing comma
plone/tiles/meta.py:35:15: Q000 Remove bad quotes.
plone/tiles/meta.py:37:23: C812 missing trailing comma
plone/tiles/meta.py:41:15: Q000 Remove bad quotes.
plone/tiles/meta.py:42:21: Q000 Remove bad quotes.
plone/tiles/meta.py:43:23: C812 missing trailing comma
plone/tiles/meta.py:47:15: Q000 Remove bad quotes.
plone/tiles/meta.py:48:21: Q000 Remove bad quotes.
plone/tiles/meta.py:49:21: Q000 Remove bad quotes.
plone/tiles/meta.py:54:15: Q000 Remove bad quotes.
plone/tiles/meta.py:55:21: Q000 Remove bad quotes.
plone/tiles/meta.py:60:15: Q000 Remove bad quotes.
plone/tiles/meta.py:61:21: Q000 Remove bad quotes.
plone/tiles/meta.py:66:15: Q000 Remove bad quotes.
plone/tiles/meta.py:67:21: Q000 Remove bad quotes.
plone/tiles/meta.py:72:15: Q000 Remove bad quotes.
plone/tiles/meta.py:77:15: Q000 Remove bad quotes.
plone/tiles/meta.py:78:23: C812 missing trailing comma
plone/tiles/meta.py:82:15: Q000 Remove bad quotes.
plone/tiles/meta.py:83:21: Q000 Remove bad quotes.
plone/tiles/meta.py:84:23: C812 missing trailing comma
plone/tiles/meta.py:88:15: Q000 Remove bad quotes.
plone/tiles/meta.py:89:21: Q000 Remove bad quotes.
plone/tiles/meta.py:94:15: Q000 Remove bad quotes.
plone/tiles/meta.py:95:21: Q000 Remove bad quotes.
plone/tiles/meta.py:126:26: C812 missing trailing comma
plone/tiles/meta.py:139:80: C812 missing trailing comma
plone/tiles/tests/test_data.py:19:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:25:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:29:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:38:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:47:23: C812 missing trailing comma
plone/tiles/tests/test_data.py:50:1: E305 expected 2 blank lines after class or function definition, found 1
plone/tiles/tests/test_data.py:62:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:68:78: C812 missing trailing comma
plone/tiles/tests/test_data.py:73:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:77:54: C812 missing trailing comma
plone/tiles/tests/test_data.py:82:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:86:15: C812 missing trailing comma
plone/tiles/tests/test_data.py:96:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:101:40: C812 missing trailing comma
plone/tiles/tests/test_data.py:102:14: C812 missing trailing comma
plone/tiles/tests/test_data.py:107:36: C812 missing trailing comma
plone/tiles/tests/test_data.py:111:15: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:17:45: C812 missing trailing comma
plone/tiles/tests/test_doctests.py:19:50: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


Try to follow a styleguide of commit messages, for example:

https://gist.github.com/stephenparish/9941e89d80e2bc58a153


This is a crash course by Brad Traversy.


get rid of all of them? Also in qgraph.c ?


@ab14bhardwaj can we remove font-family? is the css same for sidebox and fullview? if yes then we can move it to a common css file.


@ab14bhardwaj same code inside if and else element.classList.add("mck-badge-count");


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @conoria were added to this feedstock maintenance team.
  You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/conda-forge_gotchas.html#using-a-fork-vs-a-branch-when-updating-a-recipe)


@ab14bhardwaj is file preview working with this change?


Puzzle `566-492b5668` disappeared from [`src/main/java/com/zerocracy/pmo/banks/FkBank.java`](https://github.com/zerocracy/farm/blob/master/src/main/java/com/zerocracy/pmo/banks/FkBank.java), that's why I closed #1068. Please, remember that the puzzle was not necessarily removed in this particular commit. Maybe it happened earlier, but we discovered this fact only now.


test


This commit implements `note@breaksec` for breaking sub-beams in the Humdrum-to-MEI converter (both regular beams and grace-note beams, but not for chords or rests).

Example:

<img width="1386" alt="screen shot 2018-07-04 at 12 01 39 pm" src="https://user-images.githubusercontent.com/3487289/42271017-983017a2-7f82-11e8-8760-1ee21bc59bd9.png">

```
**kern
*M3/8
=1
16eLL
16e
16e
32qdLLL<
32qdJ
32qdL
32qdJJJ
16e
16e
16eJJ
=2
16eLL
16e
16eJ
32qfLLL<
32qfJJ
32qfLL
32qfJJJ
16eL
16e
16eJJ
=3
16eLL
16eJ
16eL
16eJ
16eL
16eJJ
=4
32fLLL
32f
32fJ
32fL
32f
32fJJJ
32fLLL
32f
32fJJ
32fLL
32f
32fJJJ
==
*-
!!!RDF**kern: < = below
```

Conversion to MEI:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/4.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="4.0.0">
    <meiHead>
        <fileDesc>
            <titleStmt>
                <title />
            </titleStmt>
            <pubStmt />
        </fileDesc>
        <encodingDesc>
            <appInfo>
                <application isodate="2018-07-04T12:07:23" version="2.0.0-dev-f0e1012">
                    <name>Verovio</name>
                    <p>Transcoded from Humdrum</p>
                </application>
            </appInfo>
        </encodingDesc>
        <workDesc>
            <work>
                <titleStmt>
                    <title />
                </titleStmt>
            </work>
        </workDesc>
        <extMeta>
            <frames xmlns:humxml="http://www.humdrum.org/ns/humxml">
                <metaFrame n="46" token="!!!RDF**kern: < = below" xml:id="loc46">
                    <frameInfo>
                        <startTime float="6" />
                        <frameType>reference</frameType>
                        <referenceKey>RDF**kern</referenceKey>
                        <referenceValue>< = below</referenceValue>
                    </frameInfo>
                </metaFrame>
            </frames>
        </extMeta>
    </meiHead>
    <music>
        <body>
            <mdiv xml:id="mdiv-0000001922242119">
                <score xml:id="score-0000000379308565">
                    <scoreDef xml:id="scoredef-0000000594898472">
                        <staffGrp xml:id="staffgrp-0000001948933727">
                            <staffDef xml:id="staffdef-0000001425625062" clef.shape="G" clef.line="2" meter.count="3" meter.unit="8" n="1" lines="5">
                                <label xml:id="label-0000001862496385" />
                            </staffDef>
                        </staffGrp>
                    </scoreDef>
                    <section xml:id="section-L1F1">
                        <measure xml:id="measure-L3" n="1">
                            <staff xml:id="staff-L3F1N1" n="1">
                                <layer xml:id="layer-L3F1N1" n="1">
                                    <beam xml:id="beam-L4F1-L13F1">
                                        <note xml:id="note-L4F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L5F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L6F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <beam xml:id="beam-L7F1-L8F1">
                                            <note xml:id="note-L7F1" dur="32" oct="4" pname="d" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L8F1" breaksec="2" dur="32" oct="4" pname="d" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L9F1" dur="32" oct="4" pname="d" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L10F1" dur="32" oct="4" pname="d" grace="unacc" stem.dir="down" accid.ges="n" />
                                        </beam>
                                        <note xml:id="note-L11F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L12F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L13F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L14" n="2">
                            <staff xml:id="staff-L14F1N1" n="1">
                                <layer xml:id="layer-L14F1N1" n="1">
                                    <beam xml:id="beam-L15F1-L24F1">
                                        <note xml:id="note-L15F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L16F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L17F1" breaksec="1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <beam xml:id="beam-L18F1-L19F1">
                                            <note xml:id="note-L18F1" dur="32" oct="4" pname="f" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L19F1" breaksec="1" dur="32" oct="4" pname="f" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L20F1" dur="32" oct="4" pname="f" grace="unacc" stem.dir="down" accid.ges="n" />
                                            <note xml:id="note-L21F1" dur="32" oct="4" pname="f" grace="unacc" stem.dir="down" accid.ges="n" />
                                        </beam>
                                        <note xml:id="note-L22F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L23F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L24F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L25" n="3">
                            <staff xml:id="staff-L25F1N1" n="1">
                                <layer xml:id="layer-L25F1N1" n="1">
                                    <beam xml:id="beam-L26F1-L31F1">
                                        <note xml:id="note-L26F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L27F1" breaksec="1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L28F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L29F1" breaksec="1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L30F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                        <note xml:id="note-L31F1" dur="16" oct="4" pname="e" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L32" right="end" n="4">
                            <staff xml:id="staff-L32F1N1" n="1">
                                <layer xml:id="layer-L32F1N1" n="1">
                                    <beam xml:id="beam-L33F1-L38F1">
                                        <note xml:id="note-L33F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L34F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L35F1" breaksec="2" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L36F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L37F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L38F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                    </beam>
                                    <beam xml:id="beam-L39F1-L44F1">
                                        <note xml:id="note-L39F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L40F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L41F1" breaksec="1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L42F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L43F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                        <note xml:id="note-L44F1" dur="32" oct="4" pname="f" accid.ges="n" />
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```


Please test the current dev-master of `phpstan-shim` if it works better.

This PHAR already contains `nikic/php-parser`.


@killerwife can you have a look at this, please? Thanks to this commit, I tried to make NPC 11662 immune to Curse of Tongues and Mind-numbing Poison (Sulfuron Harbinger adds) with:
``` SQL
UPDATE creature_template SET ExtraFlags=4194304 WHERE Entry=11662;
```
But when in-game I have a warlock casting Curse of Tongues (rank 1 or 2) on creature 11662, the spell still applies instead of receiving an 'Immune' message.

I did not check on TBC no WotLK, I no longer have access to these until my PC is fixed/replaced.


@cedriclmenard Could you please open an issue in [opencv_contrib](https://github.com/opencv/opencv_contrib/issues) repository? It is hard to track issues via commit comments.


This struct is unused, so you can put it under `#if 0` too.


You should try to follow a styleguide of commit messages, for example:

https://gist.github.com/stephenparish/9941e89d80e2bc58a153


It crossed my mind as well, but the declaration is at the beginning of a {} block, so it should be no problem.


Can you rename everything from qsdhci to sdhci?


Please rename common_fields to props or something like that.


Po co piszesz w komentarzu co robi ta linijka jak to jest self-documented code


No "#####", just

    /* Memory mapped implementation of QSDHCI.  */


Good namings, nice looking code! :)


this should call `ClearTask`, not `ClearValueReaders`


Hasła trzymane w stringu


W dalszym ciągu brak podsumowania w mailach.


Please place this function in tests/libqos/pci.c, and move it to the patch qgraph-ifies PCI.


You don't use `offhand` variable :smiley:


@zhaojiangbin If you are interested, please let me know what you think of this branch. It is in preparation for eventually adding the pop-up UI.

Also, what do you think of dropping support for ag? It cannot seem to output results in the same format as the other scanners, which complicates the code, and I'm not sure that supporting it adds much value and is worth the trouble. However, if there are any platforms that it's the best choice on, we should probably keep it.

Thanks.


deleted files


Should make most PRs work without having to mess with the makefile.
Windows incompatible, but the makefile has never been tested on CygWin anyways.


Pobranie wszystkich userow i przejscie w petli po ich wszystkich porownujac username i password ?

1. Co w przypadku kiedy mamy 2 userow i takimsamym username i hasle ? Nie ma sprawdzania czy username juz jest zajety.
2.Pomyslales jaki impact na performance bedzie miala apka ktora dla kazdego logowania bedzie przechodzic po wszystkich userach ?


For these tests, let's move them to a separate patch, and not include them in the first submission to qemu-devel. Later, we'll decide what to do about them (the issue being that these are unit tests, not qtests, and should not need `QTEST_QEMU_BINARY`.

To split the patch in `git rebase -i` do something like this:
* mark the patch before this one as `edit`
* copy to the clipboard the SHA1 hash of this patch
* use `git checkout -p` and `git commit` to extract the test to a separate patch
* repeat for other patches that add this kind of test
* at the end, squash together all the patches you have created, and move them at the end of the series


Niepotrzebny komentarz


just added CDC as well, it won't do anything yet. just show up the interface to make sure we got basic right :D


css


Password is not equal to confirm password ?????


Hi Rob, if you look at the commit here [1] you can find the configuration duplicated, this was a mistake and removed by the subsequent (this) commit

[1] https://github.com/NHS-digital-website/hippo/blob/b2a1a0401a792114a63408b3f7a714c8ac2a461a/repository-data/application/src/main/resources/hcm-config/hst/configurations/common/sitemap.yaml


Ah, you're right!


Email is not equals to confirm email. ??
Google translator ->
> E-mail nie jest równoznaczny z potwierdzeniem wiadomości e-mail. ??


Also, this line should be in the qsdhci commit.

Related to this, I wonder if we should name the function `qos_node_consumes`, even though the arguments are reversed compared to the direction of the edge. That's because the argument order becomes more consistent:

    qos_node_create_interface("sdhci");
    qos_node_create_driver("generic-sdhci", NULL);
    qos_node_produces("generic-sdhci", "sdhci");
    qos_node_create_driver("sdhci-pci", sdhci_pci_create);
    qos_node_consumes("sdhci-pci", "pci-bus");
    qos_node_produces("sdhci-pci", "sdhci");


Please move this to tests/qos-test.c.


oo_boiler_refactor (drewyh) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1682 of 1682 tests passed, 0 test warnings)

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


This should be `check-unit-y`, i.e. part of the tests that don't need QEMU to be compiled. Also, please move it to `tests/test/qgraph.c`.


as you like, I decided to use `consumed_by` because it follows the logic of the path, otherwise you have an inverse edge (as you said)


По заданию "_при создании Годзиллы указывается объем желудка_", т.е. у каждого экземпляра свой объем, который задается в `__init__`


По заданию в метод `eat` "_должен передаваться объем съеденного человека_", а не генерироваться внутри.


Endlich der erste Release
Top Papa


s/common/sdhci_props/ or, even better, use a compound literal in qos_create_sdhci_mm:

    qos_create_sdhci_mm(&machine->sdhci, 0x3f300000, &(QSDHCIProperties) {
        .version = 3,
        .baseclock = 52,
        .capab.sdma = false,
        .capab.reg = 0x052134b4
    });


Puzzle `939-6bf607a5` disappeared from [`src/main/java/com/zerocracy/radars/viber/VbEvent.java`](https://github.com/zerocracy/farm/blob/master/src/main/java/com/zerocracy/radars/viber/VbEvent.java), that's why I closed #1072. Please, remember that the puzzle was not necessarily removed in this particular commit. Maybe it happened earlier, but we discovered this fact only now.


No comments here, but there are comments on other commits, about work that has to be done on this one.


OK thanks, confirmed this is fixed in dev-master

Any chance of a stable release?


![](https://github.trello.services/images/mini-trello-icon.png) [009 - Desenvolver Classe EstadoService](https://trello.com/c/FGOgTZ1G/19-009-desenvolver-classe-estadoservice)


@ceastwood isn't `netstandard1.0` means the support for netfx45 and netcoreapp1.0 ?


oo_boiler_refactor (drewyh) - Win64-Windows-7-VisualStudio-14: OK (2806 of 2930 tests passed, 42 test warnings)

Messages:

 * 13 tests had: AUD diffs.
 * 156 tests had: BND diffs.
 * 151 tests had: MDD diffs.
 * 156 tests had: MTD diffs.
 * 151 tests had: RDD diffs.
 * 123 tests had: Table big diffs.
 * 112 tests had: ESO small diffs.
 * 96 tests had: EIO diffs.
 * 99 tests had: MTR small diffs.
 * 2 tests had: ESO big diffs.
 * 6 tests had: ERR diffs.
 * 1 test had: MTR big diffs.

Failures:

regression Test Summary
 * Passed: 499
 * Failed: 124

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


@brentvatne
Why did you commit this?
My header used `<Image />` and I was surprised to get an error.

Is it useless unless it is a string?


good code writing


For beginner, esp tool chain update break my build. So my first move is to check your commit history if you get it fix. For now, it is still OK to browse it from commit history or do a git blame. But in the long run, we have better split it out. That's my 2 cents.


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

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


Once completed, the job reports for Travis CI [build 678](https://travis-ci.org/per1234/arduino-ci-script/builds/399942834) will be found at:
https://gist.github.com/arduino-ci-script-bot/9371a7dedb73a560142ff2ca514b79db#file-travis_ci_job_report_00678-001-tsv


Once completed, the job reports for Travis CI [build 678](https://travis-ci.org/per1234/arduino-ci-script/builds/399942834) will be found at:
https://github.com/per1234/CI-reports/tree/arduino-ci-script/build_00678


This commit adds `chord@breaksec` in the Humdrum-to-MEI converter.

Example:

<img width="1187" alt="screen shot 2018-07-04 at 12 40 55 pm" src="https://user-images.githubusercontent.com/3487289/42272851-bd9408dc-7f87-11e8-923f-e4e762db790f.png">

```
**kern
*M3/8
=1
16b 16g 16eLL
16b 16g 16e
16b 16g 16e
16b 16g 16e
16b 16g 16e
16b 16g 16eJJ
=2
16b 16g 16eLL
16b 16g 16e
16b 16g 16eJ
16b 16g 16eL
16b 16g 16e
16b 16g 16eJJ
=3
16b 16g 16eLL
16b 16g 16eJ
16b 16g 16eL
16b 16g 16eJ
16b 16g 16eL
16b 16g 16eJJ
=4
32cc 32a 32fLLL
32cc 32a 32f
32cc 32a 32fJ
32cc 32a 32fL
32cc 32a 32f
32cc 32a 32fJJJ
32cc 32a 32fLLL
32cc 32a 32f
32cc 32a 32fJJ
32cc 32a 32fLL
32cc 32a 32f
32cc 32a 32fJJJ
==
*-
!!!RDF**kern: < = below
```

MEI conversion:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://music-encoding.org/schema/4.0.0/mei-all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://music-encoding.org/schema/4.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="4.0.0">
    <meiHead>
        <fileDesc>
            <titleStmt>
                <title />
            </titleStmt>
            <pubStmt />
        </fileDesc>
        <encodingDesc>
            <appInfo>
                <application isodate="2018-07-04T12:43:47" version="2.0.0-dev-f0e1012">
                    <name>Verovio</name>
                    <p>Transcoded from Humdrum</p>
                </application>
            </appInfo>
        </encodingDesc>
        <workDesc>
            <work>
                <titleStmt>
                    <title />
                </titleStmt>
            </work>
        </workDesc>
        <extMeta>
            <frames xmlns:humxml="http://www.humdrum.org/ns/humxml">
                <metaFrame n="38" token="!!!RDF**kern: < = below" xml:id="loc38">
                    <frameInfo>
                        <startTime float="6" />
                        <frameType>reference</frameType>
                        <referenceKey>RDF**kern</referenceKey>
                        <referenceValue>< = below</referenceValue>
                    </frameInfo>
                </metaFrame>
            </frames>
        </extMeta>
    </meiHead>
    <music>
        <body>
            <mdiv xml:id="mdiv-0000000985180131">
                <score xml:id="score-0000000823543347">
                    <scoreDef xml:id="scoredef-0000002080716897">
                        <staffGrp xml:id="staffgrp-0000001433990636">
                            <staffDef xml:id="staffdef-0000000653694113" clef.shape="G" clef.line="2" meter.count="3" meter.unit="8" n="1" lines="5">
                                <label xml:id="label-0000001493807608" />
                            </staffDef>
                        </staffGrp>
                    </scoreDef>
                    <section xml:id="section-L1F1">
                        <measure xml:id="measure-L3" n="1">
                            <staff xml:id="staff-L3F1N1" n="1">
                                <layer xml:id="layer-L3F1N1" n="1">
                                    <beam xml:id="beam-L4F1-L9F1">
                                        <chord xml:id="chord-L4F1" dur="16">
                                            <note xml:id="note-L4F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L4F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L4F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L5F1" dur="16">
                                            <note xml:id="note-L5F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L5F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L5F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L6F1" dur="16">
                                            <note xml:id="note-L6F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L6F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L6F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L7F1" dur="16">
                                            <note xml:id="note-L7F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L7F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L7F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L8F1" dur="16">
                                            <note xml:id="note-L8F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L8F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L8F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L9F1" dur="16">
                                            <note xml:id="note-L9F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L9F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L9F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L10" n="2">
                            <staff xml:id="staff-L10F1N1" n="1">
                                <layer xml:id="layer-L10F1N1" n="1">
                                    <beam xml:id="beam-L11F1-L16F1">
                                        <chord xml:id="chord-L11F1" dur="16">
                                            <note xml:id="note-L11F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L11F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L11F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L12F1" dur="16">
                                            <note xml:id="note-L12F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L12F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L12F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L13F1" breaksec="1" dur="16">
                                            <note xml:id="note-L13F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L13F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L13F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L14F1" dur="16">
                                            <note xml:id="note-L14F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L14F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L14F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L15F1" dur="16">
                                            <note xml:id="note-L15F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L15F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L15F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L16F1" dur="16">
                                            <note xml:id="note-L16F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L16F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L16F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L17" n="3">
                            <staff xml:id="staff-L17F1N1" n="1">
                                <layer xml:id="layer-L17F1N1" n="1">
                                    <beam xml:id="beam-L18F1-L23F1">
                                        <chord xml:id="chord-L18F1" dur="16">
                                            <note xml:id="note-L18F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L18F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L18F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L19F1" breaksec="1" dur="16">
                                            <note xml:id="note-L19F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L19F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L19F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L20F1" dur="16">
                                            <note xml:id="note-L20F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L20F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L20F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L21F1" breaksec="1" dur="16">
                                            <note xml:id="note-L21F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L21F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L21F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L22F1" dur="16">
                                            <note xml:id="note-L22F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L22F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L22F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L23F1" dur="16">
                                            <note xml:id="note-L23F1S1" oct="4" pname="b" accid.ges="n" />
                                            <note xml:id="note-L23F1S2" oct="4" pname="g" accid.ges="n" />
                                            <note xml:id="note-L23F1S3" oct="4" pname="e" accid.ges="n" />
                                        </chord>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L24" right="end" n="4">
                            <staff xml:id="staff-L24F1N1" n="1">
                                <layer xml:id="layer-L24F1N1" n="1">
                                    <beam xml:id="beam-L25F1-L30F1">
                                        <chord xml:id="chord-L25F1" dur="32">
                                            <note xml:id="note-L25F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L25F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L25F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L26F1" dur="32">
                                            <note xml:id="note-L26F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L26F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L26F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L27F1" breaksec="2" dur="32">
                                            <note xml:id="note-L27F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L27F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L27F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L28F1" dur="32">
                                            <note xml:id="note-L28F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L28F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L28F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L29F1" dur="32">
                                            <note xml:id="note-L29F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L29F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L29F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L30F1" dur="32">
                                            <note xml:id="note-L30F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L30F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L30F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                    </beam>
                                    <beam xml:id="beam-L31F1-L36F1">
                                        <chord xml:id="chord-L31F1" dur="32">
                                            <note xml:id="note-L31F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L31F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L31F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L32F1" dur="32">
                                            <note xml:id="note-L32F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L32F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L32F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L33F1" breaksec="1" dur="32">
                                            <note xml:id="note-L33F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L33F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L33F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L34F1" dur="32">
                                            <note xml:id="note-L34F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L34F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L34F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L35F1" dur="32">
                                            <note xml:id="note-L35F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L35F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L35F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                        <chord xml:id="chord-L36F1" dur="32">
                                            <note xml:id="note-L36F1S1" oct="5" pname="c" accid.ges="n" />
                                            <note xml:id="note-L36F1S2" oct="4" pname="a" accid.ges="n" />
                                            <note xml:id="note-L36F1S3" oct="4" pname="f" accid.ges="n" />
                                        </chord>
                                    </beam>
                                </layer>
                            </staff>
                        </measure>
                    </section>
                </score>
            </mdiv>
        </body>
    </music>
</mei>
```


Hi! I successfully added new contact, but I found an interesting bug. If I write **Michael**, list is sorted by name - everything is fine. But if I write **michael**, new contact is added to the end of the list. Seems that if name doesn't start with capital letter, it doesn't get sorted by name. How can we fix it?