i applied the above code using snippet code plugin, and i activated the code, but it didn't work, non administrator users can still see the "cost of good" line when they view orders


U. Me. N


use_eigen_HeatBalanceIntRadExchange (drewyh) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2304 of 2304 tests passed, 0 test warnings)

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


Perhaps should have checked if this was callable as well.


Created multidev environment [lawhelp#ci-994](https://dashboard.pantheon.io/sites/9ec12d94-c804-44b7-968e-166a0b49fdc0#ci-994).

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


Is this a required dependency unless Lambda has the new version of `aws-sdk`?


Here you are assuming that `ugi` instance field is the same as `UserGroupInformation.getCurrentUser` : that is, some piece of code (either in current livy, a future evolution of livy or some other plugin/extension/spi/etc code) has not done a `UGI.login` and modified the current user in `UserGroupInformation` from underneath you.

If it has changed, then the code snippet is going to keep updating ticket cache for a ugi instance which is no longer in user - while the 'actual' ugi instance (currentUser in UGI) will go out of date.

We have two cases here:
* UGI.currentUser must not change - there is an expectation that login happens only once in this caller.
  * If this is the case, an `assert ugi == UserGroupInformation.getCurrrentUser` will formalize the requirement and help catch bugs in future.
* UGI.login can be invoked - in this case, the code should be `UserGroupInformation.getCurrentUser.reloginFromTicketCache()' instead.
  * Note that this scenario will have other issues in hadoop apps btw - particularly with DT renewal and hadoop ipc; but that is orthogonal to the current bug.
  * Ideally, this option should not happen.


oo_boiler_refactor (drewyh) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


Copy of this build can be found at https://www.mewbuilds.com/build/956578738e41447092c8c9082185d90b6475a9cf/index.html


Train your brain, like you train your muscles.

You have to practice if you want to be a better programmer. This is my workout.


At this point I would be happy with it if only web team were using it. If subs, ads, edit or clients were using it I would do more work on it so it was more forgiving with incorrectly inputted urls


done in 4cb423d85eb711dfd97186fdd5f3d075e452c99a


Created multidev environment [lawhelp#ci-996](https://dashboard.pantheon.io/sites/9ec12d94-c804-44b7-968e-166a0b49fdc0#ci-996).

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


@nnposter Thanks! I suspected some of these other key exchange methods offer forward secrecy, but I didn't take the time to check.


sweet


all tests pass:
success: https://travis-ci.org/stellar/stellar-core/builds/421797486?utm_source=github_status&utm_medium=notification


IBM Cloud [toolchain](https://console.eu-gb.bluemix.net/devops/toolchains/59f9787c-1dfe-4e0b-afc0-5ee805c176f8?env_id=ibm%3Ayp%3Aeu-gb "MovieInfo"): [Delivery Pipeline](https://console.eu-gb.bluemix.net/devops/pipelines/30546d66-1ba1-4baa-a2f8-f0236718732b?env_id=ibm%3Ayp%3Aeu-gb "MovieInfo") deployed [MovieInfo](https://github.com/arnabmn/MovieInfo/releases/tag/deploy-ibm-yp-eu-gb-CF1_ARNABHAT-DEV-20180828-225041 "deploy-ibm-yp-eu-gb-CF1_ARNABHAT-DEV-20180828-225041") to [DEV](https://console.bluemix.net/apps/8ca265d5-608c-47ee-939d-c82949a15bef?env_id=ibm:yp:eu-gb "ibm:yp:eu-gb:CF1_ARNABHAT:DEV"), including this commit


I think he was referring to the `mbgl::attributes::*` types and how `gl::Attributes` is templated on those and not the `gl::Attibute{Type}`


And fixed leaving the variable for a light true when destroying the light.


No worries about the license. I see that my own repo has the same confused state. 😊 Will have to clear that up.


This commit adds the basic logic of the `attack` function: first, it creates `max` and `min` variables, to determine the range in which the random generated numbers should fall. Then is uses a series of Javascript `Math()' functions to generate a random number between this min and max, to calculate the damage done to the opponent in the attack (L19). The min/max are reset, in order to then calculate the damage that the opponent does to the player. Finally, if the player's health drops below 0, an alert message is shown indicating the loss.
This code will be refactored but this initial setup tests correctly.


You caught me, real commit follows


fast-forwarding master to auto = 81446c66


I'm sorry for being super sloppy with the commits and formatting and such :-(


Maybe outdated comment? The method does not return anything.


nice


/sys looks good, also regarding to the networking namespace, so I'm going to silence this warning


🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/master/52/display/redirect) (on internal Jenkins) failed in stage 'Test run' 🔥 : hudson.AbortException: script returned exit code 2

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/master/52//console)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/master/41c719d2ab1d8eff6dd5466ebc2c86060332bfb9/52/jenkins-results/api-diff/index.html)
ℹ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/master/41c719d2ab1d8eff6dd5466ebc2c86060332bfb9/52/jenkins-results/apicomparison/index.html) (please review changes)
ℹ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/master/41c719d2ab1d8eff6dd5466ebc2c86060332bfb9/52/jenkins-results/generator-diff/index.html) (please review changes)
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/master/41c719d2ab1d8eff6dd5466ebc2c86060332bfb9/52/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>11 tests failed, 0 tests skipped, 214 tests passed.</summary>

## Failed tests

 * apitest/Mac Classic/All: TimedOut (Execution timed out after 1200 seconds.)
 * xammac tests/Mac/Debug: Failed (Test run failed.)
 * xammac tests/Mac/Debug (all optimizations): Failed (Test run failed.)
 * xammac tests/Mac/Release: Failed (Test run failed.)
 * xammac tests/Mac/Release (all optimizations): Failed (Test run failed.)
 * framework-test/iOS Unified 32-bits - simulator/Debug: TimedOut
 * framework-test/iOS Unified 64-bits - simulator/Debug: TimedOut
 * monotouch-test/watchOS - simulator/Debug: Failed
 * System.Json/watchOS - simulator/Debug: Failed
 * MSBuild tests/iOS: Failed (Execution failed with exit code 27)
 * MTouch tests/NUnit: TimedOut (Execution timed out after 120 minutes.)
</details>


The command isn't called "isNotNSFW" so this might cause some confusion.


Totally fine :) Just got excited over the feature in the commit message and wanted to make sure you do not forgot to share it :D


Do you have an example where we need this and just calling eraseVariable above is not sufficient?


IBM Cloud [toolchain](https://console.eu-gb.bluemix.net/devops/toolchains/59f9787c-1dfe-4e0b-afc0-5ee805c176f8?env_id=ibm%3Ayp%3Aeu-gb "MovieInfo"): [Delivery Pipeline](https://console.eu-gb.bluemix.net/devops/pipelines/30546d66-1ba1-4baa-a2f8-f0236718732b?env_id=ibm%3Ayp%3Aeu-gb "MovieInfo") deployed [MovieInfo](https://github.com/arnabmn/MovieInfo/releases/tag/deploy-ibm-yp-eu-gb-CF1_ARNABHAT-PROD-20180828-230113 "deploy-ibm-yp-eu-gb-CF1_ARNABHAT-PROD-20180828-230113") to [PROD](https://console.bluemix.net/apps/30527a1a-8edc-4258-8a91-c138f61bc64b?env_id=ibm:yp:eu-gb "ibm:yp:eu-gb:CF1_ARNABHAT:PROD"), including this commit


Regarding the black formatting, I understand the such workflows are beneficial. But I was hoping that your work at porting would be something you'd contribute back as PRs for a v11 branch. And I would like other eyes on care_center code because I'm very much a self-taught Odoo developer.

In an earlier post you said you were going to have to fork and self-maintain.  It's a project in daily use, and I have every reason to expect that I'll be maintaining features for years to come. As far as I'm concerned I'd like collaborate more closely on a v11 branch? Is there anything I can do toward that goal?


Never mind, eraseVariable does remove from PMap but does not do the invalidation. I wonder if it would make sense to move the invalidation there too. We never want to remove a variable without invalidating the pointers pointing to that variable right? What do you think?


remove three method


1. I think the `scipy.misc` import is deprecated, switching to `from scipy.special import logsumexp`
2. The original utility function accepted a dictionary, but `scipy`'s function requires an array -- I think only the return statement of the original function should be replaced


i got error

Traceback (most recent call last):
  File "C:/Users/HMS/Desktop/ogredump-master/ogredump/ogre.py", line 3, in <module>
    import urllib2
ModuleNotFoundError: No module named 'urllib2'

any help ?


Fui digitar arquivo e esqueci de digitar ele inteiro, peço perdão pelo vacilo.


i use python 3


LOL


Legal. Próximo passo: acabar com os `any`


oo_boiler_refactor (drewyh) - Win64-Windows-7-VisualStudio-14: Tests Failed (2341 of 2935 tests passed, 29 test warnings)

Messages:

 * 623 tests had: AUD diffs.
 * 623 tests had: EIO diffs.
 * 339 tests had: ESO big diffs.
 * 193 tests had: ESO small diffs.
 * 566 tests had: Table big diffs.
 * 124 tests had: SSZ small diffs.
 * 85 tests had: ZSZ small diffs.
 * 158 tests had: BND diffs.
 * 153 tests had: MDD diffs.
 * 158 tests had: MTD diffs.
 * 157 tests had: RDD diffs.
 * 86 tests had: MTR big diffs.
 * 83 tests had: MTR small diffs.
 * 102 tests had: ZSZ big diffs.
 * 50 tests had: ERR diffs.
 * 16 tests had: SSZ big diffs.
 * 14 tests had: Table small diffs.
 * 1 test had: DXF diffs.
 * 1 test had: SHD diffs.

Failures:

regression Test Summary
 * Passed: 29
 * Failed: 594

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


hello, those are the instructions:
1. server-side:
in files: UsersDbService, FormsDbService
please enter the path of the database in the path field  as follows:
"data source={your path}  ; version=3;"

2.


oo_boiler_refactor (drewyh) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1687 of 1687 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.01%25-green.png)


Added communication functionality between 2 clients


@gerhard done, links updated in the following repos:

```
(19.3)lbakken@shostakovich ~/development/rabbitmq/umbrella (master %=)
$ for C in $(find . -type f -name CONTRIBUTING.md -exec fgrep -l git-commit-msgs {} +); do D="$(dirname "$C")"; echo "$D"; done
./deps/rabbitmq_stomp
./deps/rabbitmq_federation_management
./deps/rabbitmq_consistent_hash_exchange
./deps/rabbitmq_auth_mechanism_ssl
./deps/rabbit
./deps/rabbitmq_shovel_management
./deps/rabbitmq_shovel
./deps/rabbitmq_java_client
./deps/rabbitmq_auth_backend_ldap
./deps/rabbitmq_federation
./deps/rabbitmq_dotnet_client
./deps/rabbitmq_management
./deps/rabbitmq_mqtt
```


I give this commit a grade of B+


@frederickfogerty Do you mind if I cut a 1.1.0 release with this ^ included?


@Duder-onomy of course 😄 please follow the release guidelines in `CONTRIBUTING.md`


今天开始重新学习Vue


This commit refactors the `attack()` method:
* it consolidates the random generation of damage into a new method, `calculateDamage(min, max)`, then calls this method for each player/opponent.
* it creates a method `checkWin()` to determine if the player won or lost, then depending upon the result of the player's response to a confirmation alert will either start a new game or present the Start Game button.


Temporarily disabled '`setkeyv(new_x, c("school.id", "school.year", "gtid")`' (_line#77_) to isolate other bugs in _**`Rach()`**_'s functionality. However, this line now needs to be re-enabled, after adding arg(s) to specify variable names of _`data.table` `keys`_.


Yes ...


Yes, make sense. It's also pretty awkward that we have to look into each Pset to find the MaterializedTemporaryExpr Variables...


Merged


Copy of this build can be found at https://www.mewbuilds.com/build/8c01c43456d2d0baee27e7bd59c0af2fe75e4a27/index.html


@thinkwelltwd
Hi Dave,

Very recently black has introduced a -S option into their codestyle which ignores the quotes.  Too recently for me, I haven't got it installed yet.

The use case we have is an internal helpdesk in odoo, mostly for odoo issues, in a large multicompany environment - with external MSP's for some areas.  So on one hand the scope is smaller, on the other, things like automatically raising cases for tracebacks, security rules for users to raise cross company cases etc.  (I haven't fully scoped yet)

The day of your email about this, just happened to be the day I was evaluating Odoo offerings in this area.  This was mostly a PoC to determine a direction to replace Atlassian suite of apps, of which issue management is the least important.  So I got it to a point to prove it would do the job for signoff, but haven't done anything meaningful since then.

In any case I can roll back the blackened commits sometime this week, they happened late in the piece, but given the mountain of other work I have, I would say further dev work on this by me will be late November.  That was the reason for the codestyle, so I could pass it off to a junior dev to complete without them complaining about the code.  Something I have a meeting scheduled for next Thursday.

Any chance you are going to the Odoo days?  That would be a good chance to discuss collaboration.  Plus I would have had a chance to look more closely.  Otherwise we can connect outside of gh issues.  I'm all for working together.


Could be useful putting a toString of the State enum (USERNAME/STATUS) at end of msg to help server admins differentiate what type of request was made


works only with python2


ninja?


This file is autogen


<!DOCTYPE html>
<html>
<head>
	<title></title>
</head>
<body>

</body>
</html>

<h1> </h1>


Initial commit


node


This is absolutely crucial. Binding in position of expression is sorely lacking.


This "you must know" suggests it isn't possible to train directly with learn.py anymore, and that isn't the case. Instead we've just given a new option for training.


This, on the other hand?
Ternaries are already if-as-expression, and without the awkward parenthesis on the predicate.


nested ternaries are awkward.


lol


you don't have any check to define this HAVE_, right?


网站主题风格


develop (mjwitte) - i386-Windows-7-VisualStudio-14: OK (2368 of 2368 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)


This file should be edited in MM


made*
yay me


Copy of this build can be found at https://www.mewbuilds.com/build/7a8a0cfc1e612bbdf171c8adb84aeee72aff758c/index.html


Copy of this build can be found at https://www.mewbuilds.com/build/cd7c060fe4d573b03f9991b8c18f4194eaefada1/index.html


Merton and BS


Two updates from master in quick succession, I know, but deleting the Github addon was pretty major, so it should be applied ASAP.


Hi!

My name is Jen from Appen. We are currently looking for Burmese speakers in Myanmar for an online and part time job. The task involves giving us feedback about your social media experience. You will be paid per hour.

Benefits:

    Work at home
    Flexible working hours
    Payment details will be provided upon acceptance.

To learn more about the project, click the link below:
https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob

Regards,
Jen


I just noticed that `base` has a trailing slash at the end of it, so when you concatenate `base + "/about"` you end up with `localhost:3000//about` (notice the double slash). So instead just do `base + "about"` or take off the trailing slash in `base`


Trabalho


Лучше использовать макрос HAVE_EXECINFO и хидер execinfo.h оставить.


Lucas Costa da Silva, Mateus Rodrigues Costa e Thiago Aparecido da Silva


已修改，麻烦审核，谢谢


Note this does not affect any other USB sound device, unless one is unlucky enough to have an ALC4040 in it...


Gradle `processResources` task fails if the property file (yml in this case) contains `${..}`. Gradle's [property expansion mechanism](https://www.baeldung.com/spring-boot-auto-property-expansion) uses default dollar-sign placeholders ${…} to [populate](https://github.com/spring-projects/spring-boot/issues/1540) gradle properties, thus conflicting with the standard Spring placeholders. Also it does not support properties with dots which can be avoided. The escape slash before dollar placeholder does not work due to [Issue 8061](https://github.com/spring-projects/spring-boot/issues/8061). To overcome this issue, we have both bootstrap.yml and application.yml for spring placeholders only, while application.properties for gradle project properties which is read by spring. With this fix the gradle `processResources` task is successful populating gradle project properties namely `project.version` for logback.


#6750-Crash-when-no-control-zone-name-is-specified-for-Load-control-in-AirloopHVACUnitarySystem (mjwitte) - i386-Windows-7-VisualStudio-14: OK (2995 of 2995 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)


@StadenElysium
Https://github.com/lh-server/core/commit/abea66098cd68c609a3b7c8fdcb2f61da3af968f
After this commit is restored, the world database still uses the latest World_full_26_august_2018.7z?
Very confused now


✅ [Jenkins job](https://jenkins.internalx.com/job/macios/job/master/50/display/redirect) (on internal Jenkins) succeeded

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/master/50//console)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/master/9f0d2f52f5b701bd3177c40e900f9682dab0ac7b/50/jenkins-results/api-diff/index.html)
ℹ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/master/9f0d2f52f5b701bd3177c40e900f9682dab0ac7b/50/jenkins-results/apicomparison/index.html) (please review changes)
ℹ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/master/9f0d2f52f5b701bd3177c40e900f9682dab0ac7b/50/jenkins-results/generator-diff/index.html) (please review changes)
✅ [Test run succeeded](http://xamarin-storage/jenkins/xamarin-macios/master/9f0d2f52f5b701bd3177c40e900f9682dab0ac7b/50/jenkins-results/tests/index.html)


3.1.4 plz


obfhelper maybe?


159313706_Issue#6796 (Myoldmopar) - x86_64-MacOS-10.9-clang: Tests Failed (2027 of 2995 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-67.68%25-red.png)


This confused me also, but that's what the "f_block_json" returns (see attached image)
![blockjson](https://user-images.githubusercontent.com/38456463/44699171-3d426800-aa83-11e8-9f47-297856608edf.PNG)


Indentation


No need of extra CR


@javer what's the reason for dropping support for 3.2 and 3.3 ?


last


This PR is to resolve the timeout in this test:
https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-win-ws2016-cuda9-cudnn7-py3-build/18033/console

It happened because we start to build caffe2 and aten in this test.


I don't think Storage and Transactions are used on the landing page.
Translations depends on whether you want that landing page to be multi lingual.
Also, with Storage, I'm going to replace it with "IndexedDB" instead of LocalStorage as IndexedDB we can store up to 50MB but LocalStorage has a HardLimit of 5MB. I'm working on trimming down the Json output and will then update the Storage Wrappers.


I had already pushed a fix for this earlier onto the branch, so we could skip cherry picking this one?


sqs


Why don't you try to inject it directly in action?


Hi!

My name is Jen from Appen. We are currently looking for Burmese speakers in Myanmar for an online and part time job. The task involves giving us feedback about your social media experience. You will be paid per hour.

Benefits:

Work at home
Flexible working hours
Payment details will be provided upon acceptance.

To learn more about the project, click the link below:
https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob

Regards,
Jen


Hi @yurchor

Thanks for your contribution!

I am building KF5 components[1] manually for mips64el. So there might be some workaround for QTBUG[2]
Then I will fix K3B bugs[3] as soon as possible.

Regards,
Leslie Zhai

[1] https://github.com/KDE-China
[2] https://bugreports.qt.io/browse/QTBUG-2597
[3] https://mail.kde.org/pipermail/k3b/


用 `dbus list ss|grep group|cut -d "=" -f2|sort -u`获取到的订阅商名字，在某些情况下可能会导致得到的结果没有提行，导致获取到的多个机场商家名字混在一起，而最终导致这些机场的订阅被删掉，所以改用`dbus list ssconf_basic_group_|cut -d "=" -f2|sort -u`应该可以避免触发skipd的这个bug

`"$NO_DEL" == "0"`的时候，会尝试删除已经不再订阅的节点，如果用户成功订阅有3个机场，再一次更新节点的时候，前两个订阅更新失败了，第三个订阅更新成功了，也会使得`"$NO_DEL" == "0"`成立，这种情况下脚本会删除前两个订阅，这显示是不行的，所以更换为DEL_SUBSCRIBE，如果有订阅失败发生DEL_SUBSCRIBE的值就会大于0，这样检测更科学一点。


test


add tons of tokens


#6750-Crash-when-no-control-zone-name-is-specified-for-Load-control-in-AirloopHVACUnitarySystem (mjwitte) - Win64-Windows-7-VisualStudio-14: OK (2995 of 2995 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)


@javer thanks for pointing this out. I want to keep support for 3.2+. Let me check if the latest changes are backwards compatible with those versions


Pass


bonus2 bHpDrainRate and bonus2 bSpDrainRate is not working on misc skill like traps


g


Yea


fix for #1


I wonder if this could have been issue #887


good


Hola!


*hide* my gemset


сalloc -> first 'c' is Cyrillic so it fails to compile.


методы `verify`, `lose`, `win` и `draw` не имеют отношения к классу  Рука
не очень ясно зачем ты их сюда дописал
им место в одном из классов, контролирующих рантайм программы (МайГейм или Раунд)


Executing the daily benchmark build, I will reply here when finished:

@nanosoldier `runbenchmarks(ALL, isdaily = true)`


oh just check the return code? good idea


well idk it's a good reminder no matter what


совсем не ясно что этот метод делает здесь
он был в классе Рука, там ему самое место


and printing it is instantaneous


Wrong link, should be this [link](https://www.facebook.com/events/1111676722316372/) instead.


## Jenkins Build Summary

Built from [this commit](https://github.com/scottschurr/rippled/commit/19ec4b6412128506bf6701c22d9d8a020048e033)

Built at __20180828 - 03:57:42__

### Test Results

Build Type | Log | Result | Status
---------- | --- | ------ | ------
rpm | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/rpm.txt) | 1035 cases, 0 failed, t: n/a | PASS :white_check_mark:
msvc.Debug | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/msvc.Debug.txt) | 1033 cases, 0 failed, t: 781s | PASS :white_check_mark:
msvc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/msvc.Debug_NINJA_BUILD_true.txt) | 1033 cases, 0 failed, t: 648s | PASS :white_check_mark:
msvc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/msvc.Debug_Dunity_OFF.txt) | 1033 cases, 0 failed, t: 1206s | PASS :white_check_mark:
msvc.Release | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/msvc.Release.txt) | 1032 cases, 0 failed, t: 414s | PASS :white_check_mark:
gcc.Release
-Dassert=ON,
MANUAL_TESTS=true | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Release_Dassert_ON_MANUAL_TESTS_true.txt) | 1101 cases, 0 failed, t: 935s | PASS :white_check_mark:
docs | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/docs.txt) | 1 cases, 0 failed, t: 2s | PASS :white_check_mark:
gcc.Debug
-Dcoverage=ON | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug_Dcoverage_ON.txt) | 1036 cases, 0 failed, t: 1036s | PASS :white_check_mark:
clang.Debug | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/clang.Debug.txt) | 1036 cases, 0 failed, t: 282s | PASS :white_check_mark:
gcc.Debug | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug.txt) | 1036 cases, 0 failed, t: 290s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/clang.Debug_Dunity_OFF.txt) | 1036 cases, 0 failed, t: 617s | PASS :white_check_mark:
clang.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/clang.Release_Dassert_ON.txt) | 1035 cases, 0 failed, t: 400s | PASS :white_check_mark:
gcc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug_Dunity_OFF.txt) | 1036 cases, 0 failed, t: 725s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug_Dstatic_OFF.txt) | 1036 cases, 0 failed, t: 291s | PASS :white_check_mark:
gcc.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Release_Dassert_ON.txt) | 1035 cases, 0 failed, t: 426s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF -DBUILD_SHARED_LIBS=ON | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug_Dstatic_OFF_DBUILD_SHARED_LIBS_ON.txt) | 1036 cases, 0 failed, t: 296s | PASS :white_check_mark:
gcc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/gcc.Debug_NINJA_BUILD_true.txt) | 1036 cases, 0 failed, t: 274s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=address,
PARALLEL_TESTS=false,
DEBUGGER=false | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/clang.Debug_Dunity_OFF_Dsan_address_PARALLEL_TESTS_false_DEBUGGER_false.txt) | 1036 cases, 0 failed, t: 996s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=undefined,
PARALLEL_TESTS=false | [logfile](http://ci.ops.ripple.com/job/scott-schurr-rippled/job/fix1578/5//artifact/clang.Debug_Dunity_OFF_Dsan_undefined_PARALLEL_TESTS_false.txt) | 1036 cases, 0 failed, t: 1062s | PASS :white_check_mark:


Does this mean `null` is not a valid `overrideContext`


Yes, I'll put together a release right now


странный набор аттрибутов для класса Рука
больше похоже на аттрибуты класса МайГейм или Раунд


Hi!

My name is Jen from Appen. We are currently looking for Burmese speakers in Myanmar for an online and part time job. The task involves giving us feedback about your social media experience. You will be paid per hour.

Benefits:

Work at home
Flexible working hours
Payment details will be provided upon acceptance.

To learn more about the project, click the link below:
https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob

Regards,
Jen


This is causing 'SyntaxError: Invalid regular expression: /^.*([^.]{5}|.html)(?<!(\?|&)no-cache=1)$/: Invalid group'


структура должна быть примерно следующая:
1. **файл запускающий программу** ("мэйн" или "старт" к примеру)
    - в этом файле логики нет вообще
    - в нем есть "реквайер" всех остальных необходимых файлов
    - в нем создается объект класса Интерфейс
    - затем создается объект контроллера (см. пункт 2)
      можно назвать по другому, по сути это класс, который управляет рантаймом программы, направляет ход ее выполения в зависимости от вводов пользователя и результатов работы самого приложения
      когда происходит  инстанциация этого класса (к примеру Гейм, Казино, Тейбл),  который будет "вести игру", то ему в качестве аргумента передается объект интерфейса
2. **класс КОНТРОЛЛЕР**, т.е. класс "несущий поток исполнения программы"... его функции:
    - вызывать методы интерфейса для общения с игроком
    - вызывать методы других классов (на объектах этих классов), которые будут содержать состояние сущностей программы (Игрок, Дилер, Колода и т.д.)
    - возможно создавать другие контроллеры и вызывать методы этих других контроллеров (если ты решишь выделить часть "потока выполнения приложения" в отдельный "подпоток" ("подпотоки")
    - возможно вызывать методы классов или модулей, в которых будут содержаться "правила" или "логика", ну к примеру из контроллера в такие классы (модули) можно вынести методы ведущие рассчет очков, определение победителя и т.п... здесь идея заключается в том, что если эти методы собрать в одном месте, то поменять их будет легко и просто (ну например вместо игры до 21 сделать игру до 23), при этом никиких вмешательств в другие части программы не понадобится
3. **ИНТЕРФЕЙС** дожен быть полностью вынесен из всех классов!!!
    - лучше всего реализовать это с помощью отдельного класса, к примеру `class Interface` (возможно нескольких классов)
    - все методы "общения с пользователем" (вывод и ввод) должны быть только в этом классе
    - вызов методов интерфейса должен происходить ТОЛЬКО ИЗ класса (классов) КОНТРОЛЛЕРА (методы вызываться на инстансе класса `Interface`)
    - интерфейс не должен ничего знать о приложении вообще, он не должен хранить переменные приложение (только свои служебные), он не должен знать о классах и методах приложения

    **главный плюс такого подхода** и одновременно ориентир, для правильного понимания того, как нужно писать интерфейс и его взаимодействие с контроллером:
    *вместо интерфейса командной строки можно в любой момент написать другой интерфейс, который будет к примеру работать не в командной строке, а отправлять запросы посредством  http протокола... (лишь бы названия методов, т.е. интерфейс класса совпадал), а  логика должна спокойно продолжить работу не обращая внимания на смену интерфейса...*
4. **классы хранящие состояния сущностей приложения**... Игрок, Дилер, Колода, Рука... может быть что-то добавишь, может быть убавишь... основная функция этих классов должна быть в хранении состояния, т.е. объекты этих классов должны хранить аттрибуты, уметь их возвращать, если нужно - вычислять какие-то значения на основе своих аттрибутов (ну и должны принимать значения этих аттрибутов, либо в момент инициализации, либо в течении жизни объектов, посредством методов соотвествующих классов)


[OCA  OCP Practice Tests Exam 1Z0-808 and Exam 1Z0-809.pdf](https://github.com/Abhilasha3000/AB/files/2326446/OCA.OCP.Practice.Tests.Exam.1Z0-808.and.Exam.1Z0-809.pdf)


Hello Jen,

Thank you for the offer. I'm interested in this job and have read the
project page.
But, may I know more in details like project duration, tasks and
responsibilities, and approximate hourly pay rate for me.
I would love to work for this project.

Best,
Nyi

On Tue, 28 Aug 2018 at 10:12, Jacobappen <notifications@github.com> wrote:

> Hi!
>
> My name is Jen from Appen. We are currently looking for Burmese speakers
> in Myanmar for an online and part time job. The task involves giving us
> feedback about your social media experience. You will be paid per hour.
>
> Benefits:
>
> Work at home
> Flexible working hours
> Payment details will be provided upon acceptance.
>
> To learn more about the project, click the link below:
>
> https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob
>
> Regards,
> Jen
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/nyinyinyanlin/wherebikes/commit/52a67634588310d554d6e5b81101b1bcfea4cf93#commitcomment-30307342>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/APVoUv8ERKe3HsfFf4UNQBnWSsqVWIY5ks5uVLwQgaJpZM4WO3JF>
> .
>


oca


Hmm. I can't remember how this works in vCurrent. I'd need to look back at the `get` function and see. You may be right and this should be something like `overrideContext || null` instead of creating one.


Created multidev environment [d8-atsnj#ci-221](https://dashboard.pantheon.io/sites/e5e4f786-50c0-497c-819e-36c05121e231#ci-221).

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


Checkmarx scan results 28 Aug 2018 07:02 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

a23cad998261c81bf63aa21ac681a2e8b5303e7c	@web-flow


这里为什么是 never 呢，如果是 never 就无法传值了，会被检测为 `Type 'string' is not assignable to type 'undefined'`。
[never 类型](https://www.tslang.cn/docs/handbook/basic-types.html)
不能对 children 进行任何操作，这个就 readOnly 应该就可以了呀。


added licence


Created multidev environment [rif-org#ci-18](https://dashboard.pantheon.io/sites/76dc10bc-108e-4982-a0b6-acb53887cbb4#ci-18).

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


@javer thanks so much, that would be very helpful. I updated to 3.2 and 3.3 and both failed your tests... not sure if it is an easy fix for those - I hope so!


Hi Nyinyi,

Thank you for your interest in joining in this project. Complete details including pay rate will be send by the recruiter through project invite after registration using in this link.

https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob

Best regards,

Jenelyn S. Acob
Staffing Specialist | Appen
join.appen.com<https://join.appen.com/>

Facebook<https://www.facebook.com/lifeatappen> | LinkedIn<https://www.linkedin.com/company/appen> | Twitter<https://twitter.com/lifeatappen> | Blog
<https://appen.com/blog/life-at-appen/>See<https://youtu.be/u6xQ7BOcibI> how Appen can help you do what you love

From: Nyi Nyi Nyan Lin <notifications@github.com>
Sent: Tuesday, August 28, 2018 12:01 PM
To: nyinyinyanlin/wherebikes <wherebikes@noreply.github.com>
Cc: Jenelyn Acob <jacob@appen.com>; Comment <comment@noreply.github.com>
Subject: Re: [nyinyinyanlin/wherebikes] Test Myanmar font (52a6763)

Hello Jen,

Thank you for the offer. I'm interested in this job and have read the
project page.
But, may I know more in details like project duration, tasks and
responsibilities, and approximate hourly pay rate for me.
I would love to work for this project.

Best,
Nyi

On Tue, 28 Aug 2018 at 10:12, Jacobappen <notifications@github.com<mailto:notifications@github.com>> wrote:

> Hi!
>
> My name is Jen from Appen. We are currently looking for Burmese speakers
> in Myanmar for an online and part time job. The task involves giving us
> feedback about your social media experience. You will be paid per hour.
>
> Benefits:
>
> Work at home
> Flexible working hours
> Payment details will be provided upon acceptance.
>
> To learn more about the project, click the link below:
>
> https://talent-appen.icims.com/jobs/3171/job?mode=job&iis=jobsite&iisn=Github_Jacob
>
> Regards,
> Jen
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/nyinyinyanlin/wherebikes/commit/52a67634588310d554d6e5b81101b1bcfea4cf93#commitcomment-30307342>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/APVoUv8ERKe3HsfFf4UNQBnWSsqVWIY5ks5uVLwQgaJpZM4WO3JF>
> .
>

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/nyinyinyanlin/wherebikes/commit/52a67634588310d554d6e5b81101b1bcfea4cf93#commitcomment-30307519>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AZP0SrAavI6gT5LdRL3RTWnTrB-uvg1Rks5uVMBzgaJpZM4WO3JF>.

DISCLAIMER: The information and the attachments in this email may be confidential and legally privileged. Access to the contents of this message by anyone other than the intended recipient is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. If you have received this email message in error, please notify the sender immediately by email, facsimile, or telephone, and then delete/destroy the original message and all copies of it from your systems.


Created multidev environment [d8-atsnj#ci-223](https://dashboard.pantheon.io/sites/e5e4f786-50c0-497c-819e-36c05121e231#ci-223).

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


@zahitz I don't think current condition always holds. Those rename operations are also used for broader scope, like rename  a/b/c/d/foo.txt to a/b/m/n/o/p/q/r/s/t/newfoo.txt


I added an issue to track this: https://github.com/rollbar/rollbar-php-symfony3-bundle/issues/35

It might take me until next week before I'm able to test and resolve this though. Do you have a work around in meantime?


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2366 of 2366 tests passed, 0 test warnings)

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


develop (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-passing-green.png)


Thanks, my editor messed up something there. Fixed it.


@zahitz Ohh....I got it, they both Path... thanks, will fix it


I just download the repo how to run this on my local machine?


would it be okay to use ES6 syntax spread operator here?
`contacts: [...state.contacts, ...[contacts]]`


Ok


победитель кажется определен верно, но очки все равно отражаются с ошибкой
у игрока 21, а не 31
при этом что для игрока, что для дилера информация зачем-то выводится дважды (и сгруппировано не самым удачным образом)

```
Bank amount: $ 0
~~~~~~~~~~~~~~~~~~~~~~~~~
User name: MUMU
User bank amount: $ 110
User cards:

🃑, 🂾, 🂭, User score is now: 31
~~~~~~~~~~~~~~~~~~~~~~~~~
__________________________________________________
__________________________________________________
*******************
* MUMU has won! *
*******************
__________________________________________________
User name: MUMU
User bank amount: $ 110
User cards:

🃑, 🂾, 🂭, User score is now: 31
Dealer name: Dealer
Dealer bank amount: $ 90
Dealer cards:

🂽, 🂭, Dealer score is now: 20
Dealer name: Dealer
Dealer bank amount: $ 90
Dealer cards:

🂽, 🂭, Dealer score is now: 20
~~~~~~~~~~~~~~~~~~~~~~~~~
Would you like to (s)kip,  or (o)pen the cards?
```


Small one but I would extract the logic here into a method probably in `FileHelper`. Otherwise, we're duplicating this in `OptimizedImage` and `Upload.`


This doesn't actually work - you called `resolve_safe` at start, so `isnull` will always return `false` and you'll never get to the `return m_io_buffer` path.


oh my gosh


Similar to above, this check is pointless when you called `resolve_safe` above.


I don't sorry, haven't got time today to look at it. Will let you know if I make any progress.


I think this breaks Pokemon Puzzle, start the ROM and try to press start.


159313706_Issue#6796 (Myoldmopar) - i386-Windows-7-VisualStudio-14: OK (2995 of 2995 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)


starcarft 64 logos crazy flashin!


Hola, revise tu código del laboratorio 5 y me pareció un buen manejo de de html y css.  En mi opinion usaria un poco menos de divs. Utilizaria tablas para un mejor ordenamiento o secciones. En lo general estuvo genial lo de usar bootstrap


Хотелось бы узнать что тут делает Startswith. Вы считаете это подходящим способом проверки типа объекта?


What issue was this addressing specifically? clock-drift attacks? How did miners take to the PoW lockdown against PoS blocks?


159474491_Issue#6814 (Myoldmopar) - x86_64-MacOS-10.9-clang: Tests Failed (1393 of 2995 tests passed, 0 test warnings)

Failures:

integration Test Summary
 * Passed: 1
 * Failed: 632

regression Test Summary
 * Passed: 629
 * Failed: 2

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


You can install from Github:

npm:

```bash
npm install JosephusPaye/Keen-UI#024f6836f9517a036a36d07f17b74af0d8629481
```

yarn:

```bash
yarn add JosephusPaye/Keen-UI#024f6836f9517a036a36d07f17b74af0d8629481
```

Then import:

```js
import KeenUI from 'keen-ui/src/index';
```


不知道为什么，这远程代码库上传不上去~


@asuleymanov поправил, спасибо https://github.com/VIZ-World/viz-js/commit/89ce6f69d6683319c131456e2a167cc840521f90


此处有几个问题：
1、gAjaxPost.receiveChatData()、gAjaxPost.chatRecord()等这几个方法跟gAjaxPost类相关性很小，考虑一下是否必须挂到gAjaxPost这个类上；此处建议把这几个方法独立出来；这种情况的一般原则是，方法之间执行上下文（context）如果不是十分相关，要尽量独立，减少耦合；
2. 往与别人相关的类上添加方法时，要格外小心：
a. 尽量避免添加不必要的内容；
b. 要注意方法重名的问题；
c. 特别是往有继承关系的类添加属性/方法时，需要格外注意原型链上的方法被覆盖/重写的问题；


add  a menu to copy class name.


![alt text](promo/feature.png "Secure online Bitcoin wallet")
 Our <b>Bitcoin Wallet</b> is easy-to-use secured bitcoin wallet with all the necessary and modern functionality. You can recieve and send payments, import addresses, view transaction details, etc. App works as client-server application. All data transfer is encoded, and secured via ssh.


Modified.


New-Feature---Account-for-fan-heat-is-zone-cooling-coils (rraustad) - x86_64-MacOS-10.9-clang: Tests Failed (1393 of 2995 tests passed, 0 test warnings)

Failures:

integration Test Summary
 * Passed: 1
 * Failed: 632

regression Test Summary
 * Passed: 629
 * Failed: 2

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


line.139和line140 都使用`$("#" + b)`，是否可以考虑只query一次dom，用一个变量去接query出来的对象？
因为jquery对dom对象的选择也是一笔不小的时间开销（视选择器和dom结构复杂度情况不同而不同）一般来说，对同一个jquery对象操作时，除非两次操作中间这个jquery对象被改变了，否则，只需要更新一次！
下面144行和152行等对`$('.Friend')`的处理也参照这条评论修改！
另外，希望功能实现之后，可以**对整个代码进行检查，尽量避免这种情况**，优先级放到此次deadline之后


Windows CoreWallet


在gAjaxPost.friendList()这个方法里面，有三次循环遍历，但是每一次的遍历变量都是以i来作为遍历指针的，这会导致：1.执行完第一次遍历，i是第一次遍历的长度，如10， 下一次遍历的遍历指针依然是10，i这就导致i这个变量一直被这三个循环更改，然而，在实际业务逻辑中，**这三次循环的变量指针必须是毫无关联、不能相互影响的**！虽然最后实现的效果是一样的，但是**代码可读性差，变量管理混乱**


Rpc??? o


>SGD alters all weights on all nodes. I don't have any weights, filter is a
single value per variable type per level, for all of its inputs.

"Weights" are their and graph theory's  term for "variables" or "values"
(one type of them). Yes, too much interdependence and too many variables
for each pattern.

>>>"My algorithm is supposed to do what NN do far more efficiently, one of
the two is redundant. It's either-or, on all levels." (emails)

>>If you can clarify or give some mapping, suggestions which are easier for
the ANN-people how your
>>filter-update is different and why it's better, why it converges faster
and without the faults of the
>>SGD which require manual corrections.

>I think I explained it:
>Core operation in cogalg is input-to-input comp(), bit-filtering inputs,
integer-filtering matches,
>  higher-order filters for higher-power comps.

FILTERS

IMO these "filters-filtering filters" would benefit from semantic
adjustments and an "essay" on filters, because ANN had also the term with
different meaning and different application, and weights are also called
"filter values" :
https://adeshpande3.github.io/A-Beginner%27s-Guide-To-Understanding-Convolutional-Neural-Networks/
The ANN filters also do "filter", allowing the previous values to pass, or
be amplified or zeroed.

For an image-processing aware persons to/a "filter"  generally means
"Convolution", e.g. Gaussian blur,  which explains why they call the
matrices multiplication and the respective matrices "filters".

>Core operation in ANN is input matrix * weight matrix, which is a dirty
and coarse mix of last-layer
>"error" with every weight in the network.
>Mine is comparison-first, ANN is comparison-last, and even that comparison
is not done right.
>How do you compare a clean theory with a bunch of hacks?

FEEDBACK

Well, maybe with some material and common substrate - output, feedback on
particular input, trajectory of some of the system (model)'s values and
similar or different changes of the success of the models.

BTW, one advantage of ANN is how simple their algorithms are.

With current computing that makes them a factory for a measurable feedback,
allowing to adjust them. That's one reason why there are "hacks", the
feedback allows them.

Also, I noticed that it has become a fashion recently the researchers to
publish their contributions in a kit with the code and the dataset they
used. A  few months or an year ago the gurus were still suggesting the
students to read bunch of papers, "try to reproduce the results" by
implementing them yourself.

CgA still doesn't have any executable practical code and no material
feedback, that is one reason why it's harder to compare it...

HACKS

As of the hacks, it's assumed that humans and their brain in particular are
a product of "hacks".
In the domain of the biggest and more complex systems - the social ones,
including the techno-sphere as a part: the most technologically successful
system up to date is also about system-level "chaos".

The system progresses at large scale through states of reaching to a stall,
declining, crisis,  ad-hoc solutions, and not through a long term
well-planned and smooth transformations.

This is an overgeneralization, of course, there are particular more
specific reasons and there is planning everywhere where intelligene
operate, however there's "planned" (expected) mismatch to reality (not just
in the socialist countries) and the system has to make decisions at the
moment, without controlling all the aspects and often ad-hoc.

Overall, there are evidences that the ad-hoc methods with shorter feedback
are more successful than the over-planned ones in this Universe, they also
converge to higher structures even without the higher level of
cognition/government being aware of all of the details.

The same could go for the ANN and AGI, if we or somebody else doesn't
change the course.

With so many practitioners and ad-hoc and "glue-code" solutions, published
every day with immediate feedback, the progress is amazing.

Even if it's not encompassed with a general theory yet of CogAlg type, from
the pixel to the concepts*,  it could be made up ad-hoc using the NN as
subsystems-elements of another general model which just uses their output.

* BTW, in fact there is a theory for some domain, it's just "too simple":
just find and compute or apply the mutual probabilities of the input
variables, given a data set and selected constraints. "Training" is mapping
different probabilities to labels (higher level patterns), which allows for
selective access of the lower patterns (the distributions over the input
domain). When applied at pixel-level, it produces similar images to the
experienced ones or modifies them in an interesting way (auto-encoders,
GANs).

With segmentation and more supervised approach, these models produces
segmented images with known parts, areas, which could be adjusted
selectively - the user/"higher level" could interactively paint in the
symbolic domain (labels, concepts). Well, I foresaw/wanted such tools in
the early 2010s, when saying that everything would be synthesized and
claiming that art is "exhausted" (I did many years earlier) - it's going on
already. A bit more of a structure and hierarchy, 3D and longer
spatio-temporal spaces and it would generate stories, movies.

https://web.cs.hacettepe.edu.tr/~karacan/projects/attribute_hallucination/

>>When processing new input, especially if recognition fails or is poor,
the input would be tested
>>through various older/different configurations and states.
>>I assume that in CgA the freezing is related to the so called "strong
patterns"?

>I don't have any separate testing, everything is done by the same comp().
>If by freezing you mean extended / recursive search, yes, that's done
within above-average vPs or dPs.
>But I don't consider that a failure.

"Tested" ~ compared/matched. Freezing - I mean some filters being harder to
change than others.

I've forgotten to comment that:

PERFORMANCE

>"My algorithm is supposed to do what NN do far more efficiently, one of
the two is redundant. It's either-or, on all levels." (emails)

MEMORY

I'm not sure about the efficiency yet, e.g. memory-wise. Besides, once
trained, the NN are not that inefficient. The training is pain, but IMO
recognition is pretty fast - well, like with human.

The early test with CogAlg and the first level suggested a huge memory
footprint even there for one image 1024x768 or something.
That's partly due to Python, but it can be estimated roughly - if each
pixel color channel is mapped to, say, patterns with 30 variables, that's:

30 * number_of_channels * size_of_var x number_of_pixels per each image

 Where each var is at least 4 or 8 bytes (or more likely more, Py is
dynamic) and that doesn't include the temporary run-time structures.

I don't know how many such patterns (images) CgA is supposed to remember
before performing "meaningful"  recognition, how many images if has to
"chew" before starting and how many have to be in RAM.

As of the amount of input, that could be estimated with proper analysis of
the types of possible patterns, it's combinatorially and probabilistically
related to the degree of coverage of the underlying patterns (according to
the algorithm view of them) and how easily and with how many redundant
cycles the algorithm could enumerate them.

In the "main-stays", they use coarse probabilities.

IMO many patterns could be learned from even a few "beautiful" images (art
photography with wide spectrum of optical effects, wide histogram, ...).

The beautiful pieces encompass a wide spectrum of the possible patterns
within a domain.

TIME-SPEED

Speed-wise it would be as bad or worse, especially in Python with so many
low-level accesses and alterations of lists and the million dynamically
allocated and deallocated variables.

SCALING

That's another issue with current implementation and algorithm, compared to
ANN, which are coarse, but computationally scale very well.


I don't quite get it why users would expect 16x or 32x downsampling. The architecture is the author's legacy and it could be anything. What would happen when there is a new competitive architecture and it doesn't follow that number?

I do think that breaking changes should be at least warned or in the release notes


IBM Cloud [toolchain](https://dev-console.stage1.ng.bluemix.net/devops/toolchains/4d730d2d-b866-4c66-a991-601058aa8d73?env_id=ibm%3Ays1%3Aus-south "debug-jenkins-plugin"): [Delivery Pipeline](https://dev-console.stage1.ng.bluemix.net/devops/pipelines/ed2cdd95-d5f6-4775-a85e-ec0805a92c7f?env_id=ibm%3Ays1%3Aus-south "Pipeline") deployed [debug-jenkins-plugin](https://github.com/ejodet/debug-jenkins-plugin/releases/tag/deploy-ibm-ys1-us-south-eric_jodet-fr.ibm.com-dev-20180828-050757 "deploy-ibm-ys1-us-south-eric_jodet-fr.ibm.com-dev-20180828-050757") to [dev](https://console.stage1.bluemix.net/apps/fbc15336-cc73-4efc-ab2a-18c69509f5d3?env_id=ibm:ys1:us-south "ibm:ys1:us-south:eric_jodet@fr.ibm.com:dev"), including this commit


git rm [file]


@kcr, there is a DEUNA driver on this branch.


调整了包的结构, 在文件中添加了许可证


This is a lower bound (see REQUIRE on Julia 0.6 docs).

On Mon, Aug 27, 2018 at 8:59 PM Ekin Akyürek <notifications@github.com>
wrote:

> why do we restrict to FileIO 0.5.0 version which is pretty old ?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/denizyuret/Knet.jl/commit/c97a30e6256691d411ffdc5910cd5a91e41a8299#commitcomment-30305652>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABvNpr0szdLlcUq1iIs7wsLXkE1_lbmsks5uVJXygaJpZM4WOu-v>
> .
>


@bitprophet I need to learn Python. 👍


@DarkmoonRabbit I have left this project and will work on my own repo from now on.


Could also be a typo. What version are we compatible with?

On Tue, Aug 28, 2018 at 1:12 AM Deniz Yuret <denizyuret@gmail.com> wrote:

> This is a lower bound (see REQUIRE on Julia 0.6 docs).
>
> On Mon, Aug 27, 2018 at 8:59 PM Ekin Akyürek <notifications@github.com>
> wrote:
>
>> why do we restrict to FileIO 0.5.0 version which is pretty old ?
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/denizyuret/Knet.jl/commit/c97a30e6256691d411ffdc5910cd5a91e41a8299#commitcomment-30305652>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ABvNpr0szdLlcUq1iIs7wsLXkE1_lbmsks5uVJXygaJpZM4WOu-v>
>> .
>>
>


runperiod-bug-fixes (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (3035 of 3035 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)


Cannot is one word.


Thank you for the contribution @aitari ! Merged in.


This is overall more clear and concise. I think the disconnect will be loosened up as you continue to just explain things better you can keep all the information there just go into depth a bit more than usual.


Hi,I don't know that what point_3d , point_t3d , image_u and image_v mean? What's the principle?
Can you help me? Thank you.


Checkmarx scan results 28 Aug 2018 08:30 UTC +03:00

High
Medium
Low
Info

New
0
0
0
0

Recurrent
0
0
0
0

Fixed
0
0
0
0

 Open Viewer
Included commits

Commit ID	Owner

a23cad998261c81bf63aa21ac681a2e8b5303e7c	@web-flow


Just saying hi


This commit and the two others that follow implement instrument name/abbreviation placement at the staff-group level in the conversion from Humdrum to MEI.  Example:

```
**kern	**kern
*I"Piano	*
*I'Pno.	*
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
=	=
0C	0cc
==	==
*-	*-
```

Rendering with verovio:

Conversion to MEI:

```
<?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-08-27T22:33:51" version="2.0.0-dev-9db3cfc-dirty">
                    <name>Verovio</name>

Transcoded from Humdrum

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

            <mdiv xml:id="mdiv-0000000067422310">
                <score xml:id="score-0000001442882201">
                    <scoreDef xml:id="scoredef-0000000725755610" midi.bpm="400">
                        <staffGrp xml:id="staffgrp-0000001855529504" symbol="brace" barthru="true">
                            Piano
                            <labelAbbr xml:id="labelAbbr-0000001377445070">Pno.</labelAbbr>
                            <staffDef xml:id="staffdef-0000000581288198" clef.shape="G" clef.line="2" n="1" lines="5" />
                            <staffDef xml:id="staffdef-0000000397113152" clef.shape="F" clef.line="4" n="2" lines="5" />
                        </staffGrp>
                    </scoreDef>

                        <measure xml:id="measure-L4">
                            <staff xml:id="staff-L4F2N1" n="1">
                                <layer xml:id="layer-L4F2N1" n="1">
                                    <note xml:id="note-L5F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L4F1N1" n="2">
                                <layer xml:id="layer-L4F1N1" n="1">
                                    <note xml:id="note-L5F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L6">
                            <staff xml:id="staff-L6F2N1" n="1">
                                <layer xml:id="layer-L6F2N1" n="1">
                                    <note xml:id="note-L7F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L6F1N1" n="2">
                                <layer xml:id="layer-L6F1N1" n="1">
                                    <note xml:id="note-L7F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L8">
                            <staff xml:id="staff-L8F2N1" n="1">
                                <layer xml:id="layer-L8F2N1" n="1">
                                    <note xml:id="note-L9F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L8F1N1" n="2">
                                <layer xml:id="layer-L8F1N1" n="1">
                                    <note xml:id="note-L9F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L10">
                            <staff xml:id="staff-L10F2N1" n="1">
                                <layer xml:id="layer-L10F2N1" n="1">
                                    <note xml:id="note-L11F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L10F1N1" n="2">
                                <layer xml:id="layer-L10F1N1" n="1">
                                    <note xml:id="note-L11F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L12">
                            <staff xml:id="staff-L12F2N1" n="1">
                                <layer xml:id="layer-L12F2N1" n="1">
                                    <note xml:id="note-L13F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L12F1N1" n="2">
                                <layer xml:id="layer-L12F1N1" n="1">
                                    <note xml:id="note-L13F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L14">
                            <staff xml:id="staff-L14F2N1" n="1">
                                <layer xml:id="layer-L14F2N1" n="1">
                                    <note xml:id="note-L15F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L14F1N1" n="2">
                                <layer xml:id="layer-L14F1N1" n="1">
                                    <note xml:id="note-L15F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L16">
                            <staff xml:id="staff-L16F2N1" n="1">
                                <layer xml:id="layer-L16F2N1" n="1">
                                    <note xml:id="note-L17F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L16F1N1" n="2">
                                <layer xml:id="layer-L16F1N1" n="1">
                                    <note xml:id="note-L17F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L18">
                            <staff xml:id="staff-L18F2N1" n="1">
                                <layer xml:id="layer-L18F2N1" n="1">
                                    <note xml:id="note-L19F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L18F1N1" n="2">
                                <layer xml:id="layer-L18F1N1" n="1">
                                    <note xml:id="note-L19F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L20">
                            <staff xml:id="staff-L20F2N1" n="1">
                                <layer xml:id="layer-L20F2N1" n="1">
                                    <note xml:id="note-L21F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L20F1N1" n="2">
                                <layer xml:id="layer-L20F1N1" n="1">
                                    <note xml:id="note-L21F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L22">
                            <staff xml:id="staff-L22F2N1" n="1">
                                <layer xml:id="layer-L22F2N1" n="1">
                                    <note xml:id="note-L23F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L22F1N1" n="2">
                                <layer xml:id="layer-L22F1N1" n="1">
                                    <note xml:id="note-L23F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L24">
                            <staff xml:id="staff-L24F2N1" n="1">
                                <layer xml:id="layer-L24F2N1" n="1">
                                    <note xml:id="note-L25F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L24F1N1" n="2">
                                <layer xml:id="layer-L24F1N1" n="1">
                                    <note xml:id="note-L25F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L26">
                            <staff xml:id="staff-L26F2N1" n="1">
                                <layer xml:id="layer-L26F2N1" n="1">
                                    <note xml:id="note-L27F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L26F1N1" n="2">
                                <layer xml:id="layer-L26F1N1" n="1">
                                    <note xml:id="note-L27F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L28">
                            <staff xml:id="staff-L28F2N1" n="1">
                                <layer xml:id="layer-L28F2N1" n="1">
                                    <note xml:id="note-L29F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L28F1N1" n="2">
                                <layer xml:id="layer-L28F1N1" n="1">
                                    <note xml:id="note-L29F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L30">
                            <staff xml:id="staff-L30F2N1" n="1">
                                <layer xml:id="layer-L30F2N1" n="1">
                                    <note xml:id="note-L31F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L30F1N1" n="2">
                                <layer xml:id="layer-L30F1N1" n="1">
                                    <note xml:id="note-L31F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L32">
                            <staff xml:id="staff-L32F2N1" n="1">
                                <layer xml:id="layer-L32F2N1" n="1">
                                    <note xml:id="note-L33F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L32F1N1" n="2">
                                <layer xml:id="layer-L32F1N1" n="1">
                                    <note xml:id="note-L33F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L34">
                            <staff xml:id="staff-L34F2N1" n="1">
                                <layer xml:id="layer-L34F2N1" n="1">
                                    <note xml:id="note-L35F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L34F1N1" n="2">
                                <layer xml:id="layer-L34F1N1" n="1">
                                    <note xml:id="note-L35F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L36">
                            <staff xml:id="staff-L36F2N1" n="1">
                                <layer xml:id="layer-L36F2N1" n="1">
                                    <note xml:id="note-L37F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L36F1N1" n="2">
                                <layer xml:id="layer-L36F1N1" n="1">
                                    <note xml:id="note-L37F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L38">
                            <staff xml:id="staff-L38F2N1" n="1">
                                <layer xml:id="layer-L38F2N1" n="1">
                                    <note xml:id="note-L39F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L38F1N1" n="2">
                                <layer xml:id="layer-L38F1N1" n="1">
                                    <note xml:id="note-L39F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L40">
                            <staff xml:id="staff-L40F2N1" n="1">
                                <layer xml:id="layer-L40F2N1" n="1">
                                    <note xml:id="note-L41F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L40F1N1" n="2">
                                <layer xml:id="layer-L40F1N1" n="1">
                                    <note xml:id="note-L41F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L42">
                            <staff xml:id="staff-L42F2N1" n="1">
                                <layer xml:id="layer-L42F2N1" n="1">
                                    <note xml:id="note-L43F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L42F1N1" n="2">
                                <layer xml:id="layer-L42F1N1" n="1">
                                    <note xml:id="note-L43F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L44">
                            <staff xml:id="staff-L44F2N1" n="1">
                                <layer xml:id="layer-L44F2N1" n="1">
                                    <note xml:id="note-L45F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L44F1N1" n="2">
                                <layer xml:id="layer-L44F1N1" n="1">
                                    <note xml:id="note-L45F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L46">
                            <staff xml:id="staff-L46F2N1" n="1">
                                <layer xml:id="layer-L46F2N1" n="1">
                                    <note xml:id="note-L47F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L46F1N1" n="2">
                                <layer xml:id="layer-L46F1N1" n="1">
                                    <note xml:id="note-L47F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L48">
                            <staff xml:id="staff-L48F2N1" n="1">
                                <layer xml:id="layer-L48F2N1" n="1">
                                    <note xml:id="note-L49F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L48F1N1" n="2">
                                <layer xml:id="layer-L48F1N1" n="1">
                                    <note xml:id="note-L49F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L50">
                            <staff xml:id="staff-L50F2N1" n="1">
                                <layer xml:id="layer-L50F2N1" n="1">
                                    <note xml:id="note-L51F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L50F1N1" n="2">
                                <layer xml:id="layer-L50F1N1" n="1">
                                    <note xml:id="note-L51F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L52">
                            <staff xml:id="staff-L52F2N1" n="1">
                                <layer xml:id="layer-L52F2N1" n="1">
                                    <note xml:id="note-L53F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L52F1N1" n="2">
                                <layer xml:id="layer-L52F1N1" n="1">
                                    <note xml:id="note-L53F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L54">
                            <staff xml:id="staff-L54F2N1" n="1">
                                <layer xml:id="layer-L54F2N1" n="1">
                                    <note xml:id="note-L55F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L54F1N1" n="2">
                                <layer xml:id="layer-L54F1N1" n="1">
                                    <note xml:id="note-L55F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L56">
                            <staff xml:id="staff-L56F2N1" n="1">
                                <layer xml:id="layer-L56F2N1" n="1">
                                    <note xml:id="note-L57F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L56F1N1" n="2">
                                <layer xml:id="layer-L56F1N1" n="1">
                                    <note xml:id="note-L57F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>
                        <measure xml:id="measure-L58" right="end">
                            <staff xml:id="staff-L58F2N1" n="1">
                                <layer xml:id="layer-L58F2N1" n="1">
                                    <note xml:id="note-L59F2" dur="breve" oct="5" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                            <staff xml:id="staff-L58F1N1" n="2">
                                <layer xml:id="layer-L58F1N1" n="1">
                                    <note xml:id="note-L59F1" dur="breve" oct="3" pname="c" accid.ges="n" />
                                </layer>
                            </staff>
                        </measure>

                </score>
            </mdiv>

    </music>
</mei>
```


Tests timed out (filed as https://github.com/xamarin/maccore/issues/965).


shouldn't we add `//chrome/browser/extensions/api:api_registration` to the public_deps of our `brave/browser/extensions`?


@vincentdass I'm getting

```
2018-08-28T05:24:14.8377758Z Offset to Central Directory cannot be held in an Int64.
2018-08-28T05:24:14.8405664Z ##[error]Failed to deploy web package to App Service.
2018-08-28T05:24:14.8487164Z ##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
```

After this change


This removed the error that the key does not exist, however, when a new ptype is made it does not appear on the index page


159313706_Issue#6796 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


This is how the resource ID appears on the portal for VMSS. I was told it is common for all the instances.


:tada:


Kod przestanie działać poprawnie jeśli zmieni się rok. Filtrowanie powinno być niezależne od obecnej daty


2018-08-27 22:52 GMT+02:00 Dmitri Goutnik <notifications@github.com>:

> src/pspg.c:1254:28: warning: if statement has empty body [-Wempty-body]
> if (opts->less_status_bar);
>
>
should be fixed now

thank you for report

Regards

Pavel

> On Mon, Aug 27, 2018 at 3:37 PM, Pavel Stehule <notifications@github.com>
> wrote:
>
> > ?
> >
> > Pavel
> >
> > Dne po 27. 8. 2018 22:33 uživatel Dmitri Goutnik <
> notifications@github.com
> > >
> > napsal:
> >
> > > Is trailing semicolon intentional?
> > >
> > > —
> > > You are receiving this because you authored the thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/okbob/pspg/commit/4447c9b880621acbd0414c09cc4dc6
> > 422b3d7a09#commitcomment-30303387>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/
> > AAhXcxck5H3ptgztqDTzmlF4SKncdFR2ks5uVFexgaJpZM4WOdLO>
> > > .
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/okbob/pspg/commit/4447c9b880621acbd0414c09cc4dc6
> 422b3d7a09#commitcomment-30303441>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AFFe0Id-
> BWLYQbSgcgFjOp09S4AYEa23ks5uVFiUgaJpZM4WOdLO>
> > .
>
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/okbob/pspg/commit/4447c9b880621acbd0414c09cc4dc6422b3d7a09#commitcomment-30303580>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAhXc9A2GCspaG2hJTwMYYjS86ZYPnW4ks5uVFwqgaJpZM4WOdLO>
> .
>


Is this actually me that wrote this?


I'm getting a bit confused now as to why this removed the build errors


159313706_Issue#6796 (Myoldmopar) - Win64-Windows-7-VisualStudio-14: OK (2995 of 2995 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)


Ideally we should guard it, but the idea was that resource move itself is a rare event and in that short period when ID is getting updated, we are okay to have few records with incomplete/wrong res ID (which we are not even sure that it could be read wrong/incomplete). So avoided mutex locks while reading altogether to save the cost as reads on it are very frequent.


ok


@samanthajayasinghe : I assumed registration will be part of this, and that in future phases,  we will have an interface to generate reports. Therefore decided to go with 'registerAcceptor.php'... But yeah, Have now changed it to index.php


@MadhukaHarith92 : Please update the URL as index.php


yup, that makes sense. but ill wait for approval of this change, maybe ill have to revert it. :)


Several misspellings are fixed in `tx_journal.go`


Initial commit


Yes, aware of that and that is why mutex lock while updating res id. Although it should be minimal (I have noticed one) as this should happen first time when ConfigLoaded is false.


Awesome! Is this ready for a PR into OpenPDF?


runperiod-bug-fixes (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1731 of 1731 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.84%25-green.png)


@pwasilewski-netcode, commit do warsztatów nr 5 - The ChatApp


Так точно! Имитация движения между станциями, если текущая станция не является последней.


阿萨德


hi


great 👍


中级，逻辑：
这个页面存在两个错误，
1. 没有blog这个layout；
2. 页面经常会在开发态，代码修改保存后页面莫名其妙跳到这个异常页，可能是热部署方面导致会出现一些异常码，后续需要对异常码进行更加详细的判断，并做一些页面拦截


@nzav , Is the Zip Deploy working before this change? Are you using Linux Agent for deployment?


TY


haha


ok


I didn't know if you wanted to remove the change log and the thanks. So I left it in there, since Lua errors don't show up to the generic user due to not having display errors turned on.


merged from readme-edits


是否与背包插件cargBags Nivaya发生冲突。
插件无法加载。
=============translate.google.com=================
Whether there is a conflict with the backpack plugin cargBags Nivaya.
The plugin could not be loaded.


Updated in new PR: https://github.com/orangehrm/orangehrm/pull/304


Did the escape key not work for you to close the add-on? I know there was a warning but it still worked for me.


i enjoy the lil things, like this guys sense of humor!


sfs


I'm not a fan of this one. Involves a lot of code duplication and is a non-discoverable API feature. @pzhokhov I'd recommend reverting.


@jrsquared I'm sure you've answered this somewhere else. Why did Netflix stop using this?


@vincentdass it was working before - I'm using windows agents for builds and releases. Zip package is created via MsBuild


ууу


@nzav , Can you please send the debug logs (set variable `system.debug` to `true` and rerun the release) to `RM_CUSTOMER_QUERIES@Microsoft.com`?


Ясно. Исправил.


There is an export to excel function already. It works very well.

Why would you break the default CSV format ?
CSV stands for "COMMA Separated values" Not Semicolon Separated Values


159313706_Issue#6796 (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1731 of 1731 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.84%25-green.png)


Doesn't fix the issue


And the dmg too?


Did it work like that?


a a a


Undefined name: __logging__ is used but it is never imported.


### This section discusses how to activate the Mobile Check-In and Check-Out.

- □	Turn on online check-in
- □	CALL HILOADC - Option 35 Online Setup
- □	Set 'Allow Online check' flag to Y
- □	Update the Current day check-in allowed time.


;) Just a default qemu target, so that I can twiddle without hardware.


@tillrohrmann What is the purpose to change access level here?


@bboyNishiken Hello, it seems that you are using an older version of Python. This script requires **Python 3.6** at least.
We will add that in our documentation.


Depende, yo siempre escribo `Belt.List` porque es más claro.
Hay otros modules que tienen un `List` module, como el stdlib de Ocaml mismo.
`Belt` es el stdlib de bucklescript que funciona mejor en un javscript backend.
Para evitar confusión siempre escribo `Belt.List`.
Tambíen uso "module aliasing", si el nombre es demasiado largo:
```
module B = Belt;
B.List.map(..)
```

Podemos añadir un compiler flag, que `open Belt` en todos files sin escribirlo.


@kazu-yamamoto @eborden  there is no need to release 2.7.0.3 if it's only for the metadata bound; it would serve no purpose and only cause overhead for the Hackage ecosystem!


我记得有个CRC32 SIZE的宏


We still have to implement the part to update the search bar haha.
(You mean the url, right?)
I'll send a PR this evening


![](https://github.trello.services/images/mini-trello-icon.png) [Add #6 - Add Insurance in Pay slip.](https://trello.com/c/yYYo0lHW/219-add-6-add-insurance-in-pay-slip)


q


dynamic-config.h


dynamic


@ratkosrb I follow you :-)


Update copyrights


startDynamic


函数int()、str()的应用


Dynamic is shutting down. Remove Core.


高级：
多余的v-else


single Dynamic process


SZ_8M SZ_16K SZ_128K


Dynamic is probably...... Remove Core.


Dynamic. Remove Core.


@trotsiuk I got an error installing the package. I think you should remove
useDynLib(threePGNmix1Site)
the only library created is threePGN.


GenerateDynamics


dynamicd.js


Dynamicd


dynamicdjs


Always happy to inspire ;)

Wouldn't it be nice to also print the last summary line over this progress line?


dynamicjs.cc


159474491_Issue#6814 (Myoldmopar) - Win64-Windows-7-VisualStudio-14: Build Failed

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


你好~请问model.txt是怎么得到的？求解答~~谢谢


Change all Bitcoin/bitcoin to Dynamic/dynamic within this file.


See https://github.com/LimeSurvey/LimeSurvey/commit/2a9d8c4fdb3cc9e5e78c4b1096a5fb70e4ce068a , not linked with this commit …


低级：
连续的长作用域链查询，可以考虑先将数据取出赋值一个常量


LGTM


Esa opción me gustaría mucho! Porque creo que al final lo importo en todos los ficheros de reason 😅


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

I updated the Github team because of this commit.

- @dhirschfeld was 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)


That's right! You are so quick hahaha thanks! 👍


Thank you for looking into it. I can live with it. This was the only thing that  really "had to change" when migrating to ClassGraph.

By the way: It seems github thinks the issues you are creating regarding the migration to ClassGraph are spam. At leas I currently get a 404 when trying to open #1.


![](https://github.trello.services/images/mini-trello-icon.png) [Add #5 - In All reports excel total must be Bold.](https://trello.com/c/g210a3er/218-add-5-in-all-reports-excel-total-must-be-bold)


Убрал 'неопределенный' тип вагона.
Не могу разобраться, буду признателен если объяснишь как работает эта магия 😃 — {cargo: CarCargo, passanger: CarPassanger}[self.type.to_sym] || Car


Buena pregunta.
`Belt.List.length(post.comments) == 0` can be put inside the pattern match.
![image](https://user-images.githubusercontent.com/10634678/44706016-97055b00-aaa0-11e8-9a28-4d543dce3d08.png)
Pattern matching on `[]` is actually more performant, because `List.length` walks the whole list if there's more than one item.


Going to think about a way to simplify the 3 matches.


低级：
分行书写


newly added


加点注释  256bits for sha256?
像
/* four bytes for CRC32 */                                                    |
static const int btrfs_csum_sizes[] = { 4 };


It's a bit simple to say that replacing the comma with a semicolon will make Excel read the CSV properly now.

Excel will read the CSV and use the column delimiter depending on your regional settings. Some regions use semicolon, some use comma. By replacing one with the other you will fix it by default for some regions and break it for the others.

A logical way to solve this wold be to have the delimiter choice as a setting as many systems have it.

Choosing one over the other is never a "correct" option - it just depends what most of your user's location settings are.


上記、対応いたしました。
また、issue登録いただければ随時対応していこうと考えております。


sad


struct btrfs_dedupe_info **ret_info
感觉这样返回会被喷...


charactersList is private


使用技术，vue+vuex+axios+mint-ui


note should also be modified *15 minitues not 5 minites*


playerList is private


Please move this string names to class constants


@gregdek, could you give some clarification, why this happened? Is this due to lack of resources/interest or some architecture reasons lead to switch technology? How do you see the future of this project? Are you going to review PRs occasionally or you are looking for some leader from the community?


Maybe if i change Characters by ICharacters in the hashtable is possible to stocke the different job class in the map and access to the methode useSpecialSkill(target)


少了句 free fs_info->dedupe_info


You're awesome! thank you! 🎉 Me cuesta darme cuenta de lo poderoso que es el **pattern matching** jajaja reason es mi primer lenguaje con esta _feature_ 😄


runperiod-bug-fixes (jasondegraw) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2367 of 2367 tests passed, 0 test warnings)

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


讨论：
这里是否可以用map来写


Hi Louzaf

Two perpendicular vectors are used o calculate how the scale factor for a face (or plane really). In SketchUp groups and components can be stretched and skewed, which affects the area.


runperiod-bug-fixes (jasondegraw) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


先写个kfree 吧..


Yay :smiley_cat:


你好大侠，

不知道怎么联系你，就冒昧在这留言了，
看了你的多机搭建fabric1.2环境的文章：
[https://jicki.me/fabric/2018/08/07/hyperledger-fabric-1.2.html](url)
有问题想请教下，这里不好截图，就写到了这里
[http://www.blockchainbrother.com/question/1345](url)
有时间请大侠看一下，谢谢，
(邮箱或者qq：1804582861@qq.com)

谢谢


Shouldn't these changes be made in a different PR?


Changes 08-28-18


Main truffle file


多了个空格


Not handling "Singleton Pattern"? Refer to LoginPage.java and fix


It's nice to remove default unnecessary comments right away ;)


Let me know if the condition is correct.


That doesn't work because `UserGroupInformation.loginUserFromKeytab` has 2 problems:

 - since the Livy keytab may not be renewable, in this case the renew fails and after 24H Livy stops working;
 - it sets the UGI for the whole JVM, so also the REST API would be affected by the change (so basically after 24H also the REST API would not work anymore).

Thanks.


@mrobaczyk

`if (!(attackedBy[Us][KING] & ~pos.pieces() & ~attackedBy[Them][ALL_PIECES]))](url)`

should do the same thing (bench numbers should remain same) and is remarkable faster on certain old cpu's,
than

`if (popcount(attackedBy[Us][KING] & ~pos.pieces() & ~attackedBy[Them][ALL_PIECES]) == 0)`

;-)


Is MyDashboardPage the same with DashboardPage? If yes, merge into 1 class only, or else, remove 1 of them


Finding flux surface from a point using skimage function causses the surface no to go through the point. Im afraid this has reached its limits and skimage function should be replaced.


dd


No I'm sorry I pushed here by mistake. All my work is on my fork but I still have a 401 when publishing to GH


It would be nice if we could have the same line fix in the main theme where the top is not closed either 😉

> On 27. Aug 2018, at 20:49, Martin Wasley <notifications@github.com> wrote:
>
> Thanks Ad, that's fine.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.


Name of element should has prefix
Ex: txtFirstName, btnSubmit, lblWelcomeMessage