Can you try commenting line 914 in political_great_powers.txt (the one I edited for the last fix) and see if that fixes the Hungary bug? Or, if you prefer, send the save over and I'll try a few things.

It looks like Tanganyika was already a trust territory in 1946. Would it be better to make it a puppet at game start? If so, let me know and I'll do a quick province history edit on all its cores...


New logo (incomplete)


Строка лишняя.


[ 45%] Building CXX object src/server/game/CMakeFiles/game.dir/Handlers/QueryHandler.cpp.o
/home/WoD/source/src/server/game/Handlers/QueryHandler.cpp: In member function ‘void WorldSession::HandleQuestPOIQuery(WorldPackets::Query::QuestPOIQuery&)’:
/home/WoD/source/src/server/game/Handlers/QueryHandler.cpp:375:95: error: no matching function for call to ‘std::vector<WorldPackets::Query::QuestPOIBlobPoint>::push_back(<brace-enclosed initializer list>)’
                         questPOIBlobData.QuestPOIBlobPointStats.push_back({ point.X, point.Y });
                                                                                ^
In file included from /usr/include/c++/6.3.1/vector:64:0,
                 from /usr/include/c++/6.3.1/queue:61,
                 from /home/WoD/source/src/common/Common.h:30,
                 from PrecompiledHeaders/gamePCH.h:3:
/usr/include/c++/6.3.1/bits/stl_vector.h:914:7: note: candidate: void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = WorldPackets::Query::QuestPOIBlobPoint; _Alloc = std::allocator<WorldPackets::Query::QuestPOIBlobPoint>; std::vector<_Tp, _Alloc>::value_type = WorldPackets::Query::QuestPOIBlobPoint]
       push_back(const value_type& __x)
       ^~~~~~~~~
/usr/include/c++/6.3.1/bits/stl_vector.h:914:7: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘const value_type& {aka const WorldPackets::Query::QuestPOIBlobPoint&}’
/usr/include/c++/6.3.1/bits/stl_vector.h:932:7: note: candidate: void std::vector<_Tp, _Alloc>::push_back(std::vector<_Tp, _Alloc>::value_type&&) [with _Tp = WorldPackets::Query::QuestPOIBlobPoint; _Alloc = std::allocator<WorldPackets::Query::QuestPOIBlobPoint>; std::vector<_Tp, _Alloc>::value_type = WorldPackets::Query::QuestPOIBlobPoint]
       push_back(value_type&& __x)
       ^~~~~~~~~
/usr/include/c++/6.3.1/bits/stl_vector.h:932:7: note:   no known conversion for argument 1 from ‘<brace-enclosed initializer list>’ to ‘std::vector<WorldPackets::Query::QuestPOIBlobPoint>::value_type&& {aka WorldPackets::Query::QuestPOIBlobPoint&&}’


I guess you forgot a colon here? i.e: "mobile",


aa


Не верно. Этот код приведет к ошибке и делению на ноль. Я писал тебе код который поможет это избежать. И даже без диапазонов 1..10.


@dedmen Are you sure you wanted to comment this function out?
This doesn't match the commit description and looks like a potential mistake.


"schrijven":["schrijven","schrijven_N"],


I this this value is ignored


Lets roll this back


Where is `'tmp/'`? If it contains random files, won't this code attempt to process them?
Better to create a unique temporary directory (use `tempfile.mkdtemp()`?)
Or use `ZipFile.open()` instead of `extractall()` to read directly from the zip archive.
For debugging, we'll need to examine these files, so we may want to extract them from the zip in `fetch.py`; then `parser.py` should recognize the directory name (same name without `.zip`?) and process the files inside.
I think we should check for extension `.xls` or `.xlsx`, and give an error for an unrecognized extension.


My logic was something like that the Gentoo bug had a ready and confirmed patch that could and should be applied and committed easily, and thought of committing this to for-gentoo as kind of a workaround, not a real solution that was reachable so nearly.

But then, the idea of the for-gentoo overlay is to have ebuilds that can be used by Gentoo users, with new or fixed packages so indeed in the future in cases like this one I'll be committing there.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/15efea59-9a3e-4d68-be51-ce2b3c71f014 "iot-predicative-hypernutrition"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/f98dd5b0-a5c0-47b4-9399-5a64652d2165 "Pipeline") deployed [Bluemix_ChatRoom](https://github.com/ChristophDoerr/Bluemix_ChatRoom/releases/tag/deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-204326 "deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-204326") to [CloudComputing](https://console.ng.bluemix.net/apps/f7c6d33c-da24-4105-8c72-41f91ad0b1ab "ibm:yp:us-south:christoph.doerr@student.reutlingen-university.de:CloudComputing"), including this commit


@wsalesky I made these changes to add our workshop participants to our list of editors. I'm a bit afraid to mess up anything in the app. ;) Could you please merge this into master? Thank you.


Описание задания где???


If you resume then it you should be able to just call `step(resumed_epoch)`, right?


@meowmoo do you think the labels should be localized?


"stuiter":["stuiter_N","stuiteren"],
"stuiterend":["stuiteren"],
"stuiterende":["stuiteren"],


Issue_#6020 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2524 of 2531 tests passed, 0 test warnings)

Messages:

 * 7 tests had: AUD diffs.
 * 7 tests had: EIO diffs.
 * 7 tests had: ESO big diffs.
 * 7 tests had: Table big diffs.
 * 1 test had: MTR big diffs.
 * 3 tests had: ERR diffs.
 * 2 tests had: SSZ big diffs.
 * 2 tests had: ZSZ big diffs.

Failures:

regression Test Summary
 * Passed: 609
 * Failed: 7

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


whyy?


Чтоб совсем было понятно в таких примерах пиши так:
'p 0.3.rationalize   # => (0/3)'

Иначе говоря покажи что в результате консоль вернет. Тогда будетпонятно. Чтобыло до и что будет после. В описании методов ты это должен был видеть.


nah i think he just removed it

________________________________
From: gabc <notifications@github.com>
Sent: Tuesday, May 9, 2017 4:27:07 PM
To: M32Media/redash
Cc: Subscribed
Subject: Re: [M32Media/redash] Put Refresh Token inside an ENV (ddd4412)

Did you put the token somewhere else? So that we can use it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/M32Media/redash/commit/ddd4412e2fd8b9fb9169fee82fe4773d2d66b0c1#commitcomment-22077330>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AV8IC_rtARQavWcDM5BXmuCtwqhXWV87ks5r4MwbgaJpZM4NV1hN>.


Thanks for tackling this!
See my comment on parser.process_file() after it in code view.
Removing duplicate results should be in a separate commit.


Created multidev environment [bad-ass-web-machine#ci-7](https://dashboard.pantheon.io/sites/0ac1a188-6dc8-4087-8c0d-0975eb15e5cc#ci-7).

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


What's the problem with `other.description` if `T : StringProtocol`?


Oh welp, it's not that important anyways

________________________________
From: james-m32-media <notifications@github.com>
Sent: Tuesday, May 9, 2017 4:46:58 PM
To: M32Media/redash
Cc: Gabriel Beauchamp; Comment
Subject: Re: [M32Media/redash] Put Refresh Token inside an ENV (ddd4412)

nah i think he just removed it

________________________________
From: gabc <notifications@github.com>
Sent: Tuesday, May 9, 2017 4:27:07 PM
To: M32Media/redash
Cc: Subscribed
Subject: Re: [M32Media/redash] Put Refresh Token inside an ENV (ddd4412)

Did you put the token somewhere else? So that we can use it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/M32Media/redash/commit/ddd4412e2fd8b9fb9169fee82fe4773d2d66b0c1#commitcomment-22077330>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AV8IC_rtARQavWcDM5BXmuCtwqhXWV87ks5r4MwbgaJpZM4NV1hN>.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/M32Media/redash/commit/ddd4412e2fd8b9fb9169fee82fe4773d2d66b0c1#commitcomment-22077675>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABa13BTwjusLOYbVDuif6y6XLWMQgXUaks5r4NDCgaJpZM4NV1hN>.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/15efea59-9a3e-4d68-be51-ce2b3c71f014 "iot-predicative-hypernutrition"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/f98dd5b0-a5c0-47b4-9399-5a64652d2165 "Pipeline") deployed [Bluemix_ChatRoom](https://github.com/ChristophDoerr/Bluemix_ChatRoom/releases/tag/deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-204855 "deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-204855") to [CloudComputing](https://console.ng.bluemix.net/apps/f7c6d33c-da24-4105-8c72-41f91ad0b1ab "ibm:yp:us-south:christoph.doerr@student.reutlingen-university.de:CloudComputing"), including this commit


"terugblik":["terugblik_N","terugblikken_V"],


"terugblikken":["terugblik_N","terugblikken_V"],
"terugblikt":["terugblikken_V"],
"terugblikte":["terugblikken_V"],
"terugblikkend":["terugblikken_V"],


The issue imo is not compatibility but upgradeability. I know how to change the ciphers in my nginx conf and I follow pretty well news about cryptography and what is the ciper *du jour*. But most admins don't, and whenever the "crypto folks arguing amongst themselves" part of your solution happens and they come to an agreement, well, the doc will be upgraded, and... 90% of the existing instances will keep using the settings from when they installed.

Whereas reporting the choice of the ciphers to the crypto lib by setting it to HIGH:!MEDIUM:!LOW:!aNULL:!NULL:!SHA lets admins do `apt-get update; apt-get dist-upgrade` and be fucking done (okay maybe they'll need to restart nginx once in a while too). Okay, maybe that doesn't give you a 105% score on some internet test, maybe that doesn't give you PFS (right now), but it doesn't expose you to LOGJAM if you have correct DH params and disable DHE_EXPORT ciphers (which we can do easily without losing upgradeability by setting !EXPORT).


Issue_#6020 (Nigusse) - 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)


You could avoid lifetimes here by using `String`.

Generally, think about who should "own" the string to decide whether to use String vs str. In most cases for me, the struct ends up making sense as owning it, so I use String.


No binding- as I said, you should assume it will be `null` at all times.


"terugkeer":["terugkeer_N","terugkeren"],
"terugkeert":["terugkeren"],
"terugkeerde":["terugkeren"],
"terugkeerden":["terugkeren"],
"teruggekeerd":["terugkeren"],
"teruggekeerde":["terugkeren"],


This is the initial commit


If there's no favicon, there's probably not a need for this endpoint


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/15efea59-9a3e-4d68-be51-ce2b3c71f014 "iot-predicative-hypernutrition"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/f98dd5b0-a5c0-47b4-9399-5a64652d2165 "Pipeline") deployed [Bluemix_ChatRoom](https://github.com/ChristophDoerr/Bluemix_ChatRoom/releases/tag/deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-205258 "deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-205258") to [CloudComputing](https://console.ng.bluemix.net/apps/f7c6d33c-da24-4105-8c72-41f91ad0b1ab "ibm:yp:us-south:christoph.doerr@student.reutlingen-university.de:CloudComputing"), including this commit


It is a policy- no binding in utilities, unless you are sure on what you're doing.


I prefer to use `format!()` rather than manipulating strings. Generally it's good form to avoid `mut` unless really convenient / a big performance boost.


I think a better name for `delete_sample` would be `update_sample`, both in the controller and the core class.


`description` is supposed to be a human-readable description and there are intentionally insufficient restrictions to ensure that this actually copies the source.


@wsalesky Sorry Winona. I found a mistake. I should be done now if you could merge to master. Thanks.


TeamCity libpalaso :: palaso-win32-master Continuous [Build 4.0.141.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90530&buildTypeId=Libpalaso_PalasoWin32masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:02:10


TeamCity libpalaso :: fixing-to-fix-palaso-linux64-masterContinuous [Build 4.0.42.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90529&buildTypeId=JasonHatesMono) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:02:43


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     1.11 |
| `nodes_count`   |   827    |
| `texts_passing` |    21    |
| `texts_total`   |     3    |

## Words

| Changed   |   Status |
|:----------|---------:|
| `eng`     |   +59925 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | Failing  |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | Failing  |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | Failing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/364)*


Please update the documentation `bundle exec rake lapis:docs` to update the docs.


Ok, did not think about that. But I have another suggestion:
If you move the code from `Item#onItemUse` (which is interpreted as onPlaceItemIntoWorld by Forge) to `Item#onItemUseFirst`.
This one is called very early when the item is right clicked and the action done here cannot be undone by canceling any event.

This would solve the problem of the chest content being lost if any mod cancels the PlaceEvent.
I think this also affects Protection Plugins for SpongeForge or similar as they also cancel the PlaceEvent (as far as I can tell from SpongeForge's code).
If this code is moved to `#onItemUseFirst` they would not be able to prevent the block change, but it would prevent losing the items. (And if you are the owner of a protected chest on a server, you probably prefer a improved chest over losing your items).

This solution is not perfect, but better than the current one.


I agree. Github wiki is very easy to use and its pages tend to appear in Google searches.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/15efea59-9a3e-4d68-be51-ce2b3c71f014 "iot-predicative-hypernutrition"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/f98dd5b0-a5c0-47b4-9399-5a64652d2165 "Pipeline") deployed [Bluemix_ChatRoom](https://github.com/ChristophDoerr/Bluemix_ChatRoom/releases/tag/deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-205712 "deploy-ibm-yp-us-south-christoph.doerr-student.reutlingen-university.de-CloudComputing-20170509-205712") to [CloudComputing](https://console.ng.bluemix.net/apps/f7c6d33c-da24-4105-8c72-41f91ad0b1ab "ibm:yp:us-south:christoph.doerr@student.reutlingen-university.de:CloudComputing"), including this commit


Ugh, sure.
Would you mind opening an issue with that information? I'll forget otherwise.


TeamCity libpalaso :: palaso-trusty64-lfmerge Continuous [Build 2.6.363.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90531&buildTypeId=PalasoTrusty64lfmergeContinuous) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:05:08


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.138.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90532&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:02:41


Avoid unwrap unless you're 100% sure that an error won't be thrown (even then, some people think `expect()` is better, so you can give a friendly error message when it panics.)

There's a lot of ways to handle errors in rust: https://doc.rust-lang.org/book/error-handling.html

Since this is a smaller app, I'd probably use [map_err](https://doc.rust-lang.org/std/result/enum.Result.html#method.map_err), in combination with using functions to avoid copypasta'ing it.


>@pmario how does publishFilter relates to this topic? May be a solution to what I'm talking about ?

the publishFitler variable [was introduced 2 years ago](https://github.com/Jermolene/TiddlyWiki5/blame/master/core/templates/save-all.tid) after a user request #1800.

This issue got closed even if the solution actually didn't work out well. .. It only works if one introduces a special UI button, [with a wrapper configuration](https://github.com/Jermolene/TiddlyWiki5/issues/1800#issuecomment-113425781).

What we actually want, is something more like this: "SyncFilter should build from certain tags instead of hardcoded" #1746 ... or more specifically like [@tobibeer 's suggestion](https://github.com/Jermolene/TiddlyWiki5/issues/1746#issuecomment-141380520):

I think instead of activating this PR we should aim for a more generic solution, which will also work for /save/all if possible.


As of 2017-05-09, this change in rxjs 5.3.2 breaks Angular 4.1.1 + Angular-CLI 1.0.2 with the following error during a simple ng version call:
RxJS could not find any global context (window, self, global)
Error: RxJS could not find any global context (window, self, global)
    at C:\projects\APM-Routed\node_modules\@angular\cli\node_modules\rxjs\util\root.js:15:11
    at Object.<anonymous> (C:\projects\APM-Routed\node_modules\@angular\cli\node_modules\rxjs\util\root.js:16:3)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\projects\APM-Routed\node_modules\@angular\cli\node_modules\rxjs\Observable.js:2:14)

I look


If you wanted to be REALLY performance-oriented, I think you can programmatically build this MIME type to avoid parsing strings as much as possible. But that would be overkill for this.


"uitstappen":["uitstap_N","uitstappen_V"],
"uitstapt":["uitstappen_V"],
"uitstapte":["uitstappen_V"],
"uitstappend":["uitstappen_V"],
"uitstappende":["uitstappen_V"],
"uitgestapt":["uitstappen_V"],
"uitgestapte":["uitstappen_V"],
"uitstapten":["uitstappen_V"],


Thanks guys!

Awesome support.


Configuracion de facebook


Crypto is a topic in which it is easy to get lost but also to spend time arguing about nuances.

> Every person who submits a PR for it radiates an air of infosec confidence, how are we supposed to decide this without being cryprographic experts ourselves?

You can't, not without spending a long time on this topic. Maybe if there is quasi-consensus then it's possible to proceed, see end of this post.

> The commit that switches to HIGH makes maintenance of this page easier and allows us to make sure every admin automatically switches to better ciphers as they are being released and automatically switches off problematic ciphers as they are deprecated.

You'd think that, but this is **not** correct. In fact, this is a mistake nginx maintaners have also made. nginx defaults to `HIGH:!aNULL:!MD5` which is not that far from what's in the current config for Mastodon.

The trouble with this is that you'd _assume_ that OpenSSL folks would maintain `HIGH` to mean high security, modern ciphersuites when in reality [all it means](https://www.openssl.org/docs/man1.0.2/apps/ciphers.html) is

> key lengths larger than 128 bits, and some cipher suites with 128-bit keys

...and that's unlikely to change much. This results in 72 different ciphersuites with the nginx default config, with 72 ciphers of wildly differing quality and strength. You have to keep in mind that OpenSSL is aimed at an extremely broad audience, coupled with a long historical compatibility to keep in mind. They couldn't change the `HIGH` setting radically even if they wanted to. The `DEFAULT` OpenSSL setting allows 97 different ciphers, which is OpenSSL's way of saying "maximum compatibility".

So what's wrong with the default `HIGH` setting and why can't it be used to let an upstream security library deal with it?
- even without sha1, it includes 36 different ciphers for the latest stable OpenSSL version and connection security depends on the weakest cipher that a server supports (attackers can just force it)
- those 36 ciphers include DHE ciphers where they have no practical use for modern clients, but you absolutely need to generate correct DH parameters and include that with the ssl_dhparam setting, **if** DHE ciphers are used, not just because of logjam but because of weak OpenSSL defaults
- I'll not go into details about Perfect Forward Security but basically it means: can someone who compromises your private key decrypt any previously recorded traffic with it or not? This depends on the ciphersuite.
- HTTP/2 has a cipher blacklist and also a mandatory support list which requires specific ciphers otherwise a HTTP/2 connection won't be established.
- based on past experience the `HIGH` list won't be updated fast enough to avoid problems

So if not upstream and a default list, then what?

Your best bet is probably to set the few cipher suites from this pull request [#231](https://github.com/tootsuite/documentation/pull/231) and then **close** this topic for a few years. Those ciphers cover all modern clients, have no known security issues and they also are being used for most of the world's encrypted traffic. It is less likely that this list would need changing for _security_ reasons than the `HIGH` list, having a few known-good ciphers is the maintainable solution.

The original pull request which changed to `HIGH` was well-intentioned, but unfortunately having the opposite of the intended effect.

cc @wxcafe @Gargron


TeamCity libpalaso :: palaso-linux64-libpalaso-3.1 Continuous [Build 3.1.338.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90535&buildTypeId=bt322) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:35


Travis CI [build 325](https://travis-ci.org/per1234/arduino-ci-script/builds/230495901) has started. Once completed the job reports will be found at:
https://gist.github.com/per1234/2eb6ef47b55f794dd2141a0fd5706219#file-travis_ci_job_report_325-1-tsv


boats keep driving straight into the shore .. no matter the radius on static areas ..I give . just make a  bee line for the first shore line the see


Meant story 10


Travis CI [build 49](https://travis-ci.org/per1234/test/builds/230496776) has started. Once completed the job reports will be found at:
https://gist.github.com/per1234/5c871fa4db91afea5b8f740c6e62377e#file-travis_ci_job_report_49-1-tsv


This is really cool!


"uitstel":["uitstel_N","uitstellen"],
"uitstelt":["uitstellen"],
"uitstelt":["uitstellen"],
"uitstelt":["uitstellen"],


TeamCity libpalaso :: palaso-linux64-libpalaso-2.6 Continuous [Build 2.6.1376.3c0eda180c484baa55120298f66882248c282b58](http://build.palaso.org/viewLog.html?buildId=90538&buildTypeId=PalasoLinux64v26Cont) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:35


@DanaGuo Can it catch all exceptions in the call to router.versionControl()?


I was wondering what the `'a` actually did... I just saw it in the docs for askama


No more:

ls: cannot access '/var/spool/cron/atjobs': No such file or directory


! always succeeds (and fails)
You should check the variables


The changes to most files to have lines which are not-too-long is good.  Except for
code/Data/Drasil/Concepts/Math.hs
which really was much nicer before, because things lined up.  I think this is one case where we should make an exception.  Can you revert that one change please?


It was to get rid of an error log 🤷♂


Will error in IE11


you finally realized


Good to know!


based on this discussion at https://groups.google.com/a/gradle.com/d/msg/cloud-services-engineering/XAFZZHiiVWw/Gsdw7e3XAQAJ


you have realised your true form


It's a lifetime annotation: https://doc.rust-lang.org/book/lifetimes.html

My strategy for learning rust was to avoid lifetimes until it was necessary to learn. That seemed to work for me.


> For durations we should use get_dive_duration_string (we'll need a C wrapper around it that returns a char *). And get_time_string_s() should then be renamed to get_surface_interval() or something like that.

Yes, that idea sounds good. Or maybe we even create only one function with sufficient arguments or even some overloading which can do any format needed. But I have no preference here. What do you think is better?

Regarding the C wrapper I'm even not sure if we are calling the get_time_string_s(); today from any C file. Maybe we even don't need the C wrapper and can easily move everything to qthelper.cpp.


@DanaGuo What's the use case to concat path elements to build a method?


Hm, I would've thought that the router would return a 404 by default


Give me a day or two and I shall take a look at this.


jquery was a mistake


Yes! Absolutely.


"uitverkoop":["uitverkoop_N","uitverkopen"],
"uitverkoopt":["uitverkopen"],
"uitverkocht":["uitverkopen"],
"uitverkochte":["uitverkopen"],
"uitverkochten":["uitverkopen"],


[Tabs2] clicking selected tab again fires onChange (#1069)

Preview: documentation
Coverage: core | datetime


h


[Docs] Navigator scrolls selected item into viewport (#1049)

Preview: documentation
Coverage: core | datetime


Seems like scoth.io changed it back to the first link :/
Sorry for the inconveneince


@DanaGuo Can you please explain the parameters for crypto.randomBytes()? Is this call synchronous or asynchronous?


essay


"uitwassen":["uitwassen_V","uitwas_N"],
"uitgewassen":["uitwassen_V"],
"uitwast":["uitwassen_V"],
"uitwaste":["uitwassen_V"],
"uitwasten":["uitwassen_V"],


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     1.25 |
| `nodes_count`   |   864    |
| `texts_passing` |    23    |
| `texts_total`   |     1    |

## Words

| Changed   |   Status |
|:----------|---------:|
| `eng`     |   +62790 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | Failing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/365)*


@DanaGuo When this server is up will there be multiple threads to handle requests?


I think we should use this https://github.com/babel/babel-preset-env#usebuiltins


Not precisely. load_state_dict would also resume the lr. If the user calls it BEFORE creating LR Scheduler, the base lr would be incorrect.


`return false`? :wink:


Yeah, before making everything, check if its a part of another thing


i was having trouble using %WINDIR% as it wouldn't expand correctly in all cases which is why i had resorted to ENV['windir']. in the resources it cannot expand the windows %WINDIR% style like it did before when just executing commands. Is there perhaps something i missed that makes this work now? in theory the cookbook should be broken when using the default install path.


TeamCity libpalaso :: palaso-linux64-libpalaso-2.6 Continuous [Build 2.6.1377.b9a494217b89dabfeea8c14172d23e11bff77538](http://build.palaso.org/viewLog.html?buildId=90539&buildTypeId=PalasoLinux64v26Cont) outcome was **SUCCESS**
Summary: Running Build time: 00:04:56


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     1.32 |
| `nodes_count`   |   890    |
| `texts_passing` |    24    |

## Words

| Changed   |   Status |
|:----------|---------:|
| `eng`     |   +64889 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng1.xml` | Deleted  |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | New      |
| `./data/tlg0540/tlg001/tlg0540.tlg001.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg002/tlg0540.tlg002.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg003/tlg0540.tlg003.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg004/tlg0540.tlg004.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg005/tlg0540.tlg005.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg006/tlg0540.tlg006.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg007/tlg0540.tlg007.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg008/tlg0540.tlg008.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg009/tlg0540.tlg009.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg010/tlg0540.tlg010.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg011/tlg0540.tlg011.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg012/tlg0540.tlg012.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg013/tlg0540.tlg013.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg014/tlg0540.tlg014.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg015/tlg0540.tlg015.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg016/tlg0540.tlg016.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg017/tlg0540.tlg017.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg018/tlg0540.tlg018.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg019/tlg0540.tlg019.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg020/tlg0540.tlg020.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg021/tlg0540.tlg021.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg022/tlg0540.tlg022.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg023/tlg0540.tlg023.perseus-eng2.xml` | Passing  |
| `./data/tlg0540/tlg024/tlg0540.tlg024.perseus-eng2.xml` | Passing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-greekLit/366)*


"ThroughModel" needs to be "Through**put**Model"


Good catch! I'm doing prototyping in Chrome, where the presence of scroll bars doesn't normally affect page layout, so I hadn't considered that issue.

I've been experimenting, and preventing background page scrolling for modal overlays appears to be a rather complex issue. I've begun a section in the document on [Avoiding background scrolling](https://docs.google.com/document/d/1V87DbueCGaC6Rlr2WrD_t2dKi2urLvIFDh4adLekG8I/edit#heading=h.uo7aporwd8bc) to try to capture the pros and cons of possible solutions. Any thoughts you have on those options would be appreciated.


Let's do it.


Learn to delete.."practice"


I wasn't implementing any one specific idea from talkchess but it did inspire me to rethink my previous efforts.  Here I'm trying to count how many threads have already started searching at the rootDepth OR higher so that is why I increment on lines 376 and 383.  Different ways of counting can be useful as well.


TeamCity libpalaso :: palaso-win32-master Continuous [Build 4.0.142.b9a494217b89dabfeea8c14172d23e11bff77538](http://build.palaso.org/viewLog.html?buildId=90548&buildTypeId=Libpalaso_PalasoWin32masterContinuous) outcome was **SUCCESS**
Summary: Tests passed: 3747, ignored: 128 Build time: 00:05:57


"verbruik":["verbruik_N","verbruiken"],
"verbruikt":["verbruiken"],
"verbruikte":["verbruiken"],
"verbruikten":["verbruiken"],
"verbruikend":["verbruiken"],
"verbruikende":["verbruiken"],


There are exactly 2 things that conform to the `StringProtocol`: `String` and `Substring`. We know exactly what `description` returns for those. But, as `init<T : StringProtocol>` is now allowed, and `characters` is available, I will just do:

```swift
extension protocol StringProtocol {
  public init<T : StringProtocol>(_ other: T) {
    self.init(other.characters)
  }
}
```


This condition is breaking because, at the very least, Powershell 5.1 Build 14393 Revision 1066 (From a latest Windows Server Core Docker container) requires parentheses around the expression being negated when using !


TeamCity libpalaso :: palaso-linux64-libpalaso-3.1 Continuous [Build 3.1.339.b9a494217b89dabfeea8c14172d23e11bff77538](http://build.palaso.org/viewLog.html?buildId=90542&buildTypeId=bt322) outcome was **SUCCESS**
Summary: Running Build time: 00:05:13


kmkk


"verdragen":["verdragen_V","verdrag"],
"verdraagt":["verdragen_V"],
"verdroeg":["verdragen_V"],
"verdroegen":["verdragen_V"],
"verdragend":["verdragen_V"],
"verdragende":["verdragen_V"],


- login op homepage gestyled
- extra parameter toegevoegd aan Materialize.fadeInImage() om de duration van de transitie te kunnen bepalen


Travis CI [build 17](https://travis-ci.org/per1234/MegaCore/builds/230467990) has started. Once completed the job reports will be found at:
https://gist.github.com/per1234/1b005ec33dc8cdbde14dd2dedfb083a5#file-travis_ci_job_report_17-1-tsv


Not Object.raw but String.raw


Re the AtomicInteger....If you mean for the remainingBytes, this class is single threaded so there is no need of it.
Re the reusable callbacks I can allows allocations using an immutable version too, but I was planning to made this one public and usable in other contexts (eg JournalImpl callers)


A te nawiasy to tu muszą być?


It is! Thanks!


Issue_#6020 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1297 of 1297 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-37.67%25-green.png)


change this as
API Documentation :   https://orangehrm.github.io/orangehrm-api-doc


Change this as
 https://github.com/orangehrm/api-sample-app-php


"verschil":["verschil_N","verschillen"],
"verschillen":["verschil_N","verschillen"],
"verschilt":["verschillen"],
"verschilde":["verschillen"],
"verschilden":["verschillen"],


I'm using the "old" ids, and German is already translated, if Spanish is missing sure add it.


128792325-Issue5803 (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (2334 of 2496 tests passed, 10 test warnings)

Messages:

 * 23 tests had: EIO diffs.
 * 6 tests had: ESO big diffs.
 * 10 tests had: Table small diffs.
 * 3 tests had: ERR diffs.
 * 7 tests had: AUD diffs.
 * 17 tests had: ESO small diffs.
 * 9 tests had: MTR big diffs.
 * 8 tests had: Table big diffs.

Failures:

EnergyPlusFixture Test Summary
 * Passed: 470
 * Failed: 3

regression Test Summary
 * Passed: 437
 * Failed: 159

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


ahh .. hard code AUTO_INCREMENT=24 id and not utf-8 tables


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.139.b9a494217b89dabfeea8c14172d23e11bff77538](http://build.palaso.org/viewLog.html?buildId=90544&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **SUCCESS**
Summary: Running Build time: 00:06:12


hard code AUTO_INCREMENT=24


Please what is the version of python that work with it
It can be the problem here
Because the python i installed is 2.7
Is it a problem or no
Please give me in detail
What you install exactly
Python
Open cv
Librairy ......

I am stressed and i can t find solution

Le 9 mai 2017 07:42, "Intissar Khalifa" <khlifaintissar@gmail.com> a écrit :

> The system is windows 8  (64 bits )
> Is this file related to all project in Sl
> Or it is independent ?
> How can you install this library ?
> ________________
>
> import sys
> from PyQt4 import QtGui, QtCore
> from PyQt4.QtGui import *
> import cv2          //instaled
> import numpy     // instaled
> import numpy as np
> import time
> import os
> import glob
> import math
> import pickle
> from numpy import array
> from collections import Counter
> from PIL import Image
> from PIL import ImageFont
> from PIL import ImageDraw
>
> Le 9 mai 2017 07:30, "Pohan Yang" <notifications@github.com> a écrit :
>
>> Sorry, i'm working now.
>> waht's your OS, linux or windows?
>> include library: OpenCV, numpy, python, PIL...
>> You have to install these application complete before running code.
>> You can try to list your error message, i can check if i have time.
>> best wish for you
>>
>> 2017 14:29 in Taiwan.
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/PohanYang/Sign-Language-Estimation-by-Tensorflow/commit/704bcd8de21d52616027e56b8684a3bd7f692088#commitcomment-22066239>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AXIdr-an_DVZH5PyDL95MBgcgHLXAJU8ks5r4AgFgaJpZM4NMaba>
>> .
>>
>


XD


Kindly explain to me what this line of code does


I don't think we even need that init for API, since we get it from RangeReplaceableCollection.  I think maybe what we want is an optimization in the RRC conforming init that downcasts `other` to `String` and/or `Substring` and does something more efficient.


"vervoer":["vervoer_N","vervoeren"],
"vervoerde":["vervoeren"],
"vervoerden":["vervoeren"],
"vervoerend":["vervoeren"],
"vervoerende":["vervoeren"],
"vervoerd":["vervoeren"],
"vervoerde":["vervoeren"],


Haskell Web scraper


As for exactly 2 things conforming to `StringProtocol`, it's true, until some user implements her own.


"voorvallen":["voorvallen_V","voorval_N"],


Is there a way to make it avoid stretching?


let's return 0 on success and non 0 on failure.
There is no point for additional < 0 checks in if. < 0 makes sense for functions that return file descriptors or -1 if error.


But that's `luaL_checkudata`, and this is `lua_touserdata`, though granted I have no idea which is correct. Fell free to change my addition if it's wrong.


See code for parsing indexes:

https://github.com/silverstripe/silverstripe-framework/blob/master/src/ORM/Connect/DBSchemaManager.php#L555-L579


Issue_#6095 (Nigusse) - Win64-Windows-7-VisualStudio-14: OK (2494 of 2494 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)


for a seed


lol ;-)


Good catch! Haven't had a lot of time to properly set this all up.


nice work. Will try to make it run and see results. Thanks


"vouw":["vouw_N","vouwen_V"],
"vouwen":["vouw_N","vouwen_V"],
"gevouwen":["vouwen_V"],


TeamCity libpalaso :: fixing-to-fix-palaso-linux64-masterContinuous [Build 4.0.43.b9a494217b89dabfeea8c14172d23e11bff77538](http://build.palaso.org/viewLog.html?buildId=90546&buildTypeId=JasonHatesMono) outcome was **SUCCESS**
Summary: Running Build time: 00:06:29


@pkyle could you look over and fill in function header information please?


fixes #404


This is javaEE app. I used Spring MVC framework to develop this web-app.
The idea was to create OnlineShoping store. Designe is pretty simple and this is learning project
not a commerical one.
As every spring app, this app is devided in 3 parts:
-Model
-View
-Controller
For ORM (Object-relational mapping) I used Hibernate Framework. In terms of design of pages all is done by :
-Html
-css
and of cours they have been part of JSP (wich I used for view part of app).
Last but not least I used MySQL for data persistence.


Yes, that is actually intended. The function is replaced by the new control_fdr functions. They are more flexible and don't require modification of the bcf.


LOL I got eye cancer


vreemd:
"walm_":["walm__N"],
moet zijn
"walm":["walm_N"],  ?


Apart from that, there was actually a bug in this function (respectively the underlying rust-bio code), that lead to too conservative FDRs. This is now fixed as well.


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1894 of 1894 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)


Alright, all done and did another reset of the Weblate repository. Thanks a lot for your quick work, @urbalazs!


sdsdsda


as tested the final version of the game is working! with generated code by EMF! Ill be uploading the final version soon .


t/m einde gedaan, en soms ook wat vervoegingen toegevoegd die er niet inzaten


60 complete


TeamCity libpalaso :: palaso-win32-master Continuous [Build 4.0.143.cf90575117c73a44607c56882f78517d64d10116](http://build.palaso.org/viewLog.html?buildId=90555&buildTypeId=Libpalaso_PalasoWin32masterContinuous) outcome was **SUCCESS**
Summary: Tests passed: 3747, ignored: 128 Build time: 00:06:27


K


если у тебя нет тестов, то оно не надо


я б советовал вообще вместо jsp/jstl заюзать что-то поактуальнее типа freemarker хотя бы


TeamCity libpalaso :: palaso-linux64-libpalaso-2.6 Continuous [Build 2.6.1378.cf90575117c73a44607c56882f78517d64d10116](http://build.palaso.org/viewLog.html?buildId=90552&buildTypeId=PalasoLinux64v26Cont) outcome was **SUCCESS**
Summary: Running Build time: 00:05:07


отформатируй по человечески помник


Oh I see. Now it make sense. Thank you @nidup


убери кучу пробелов


+@Getter
 +@Setter
 +@EqualsAndHashCode
 +@ToString
вместо этого чудесно работает аннотация @Data


убери пробел


I think I'm fine with either way. It's just how test results are grouped in testgrid and it can be changed very easily.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/5f2b938e-d1dc-48d7-b430-8cd186823952 "moviasconnect"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/e7bd51b1-f252-4413-80db-578feb8b7c42 "moviasconnect") deployed [moviasconnect](https://github.com/efmiranda/moviasconnect/releases/tag/deploy-ibm-yp-us-south-movias-dev-20170509-213518 "deploy-ibm-yp-us-south-movias-dev-20170509-213518") to [dev](https://console.ng.bluemix.net/apps/1079c952-4422-430f-866a-49923506fc68 "ibm:yp:us-south:movias:dev"), including this commit


They both do essentially the same thing; the only difference is that "checkudata" also verifies that it _is_ userdata and also that it has the correct metatable. while "touserdata" returns null if it's not userdata and doesn't check the metatable even when it is.

Mind you, the check is technically superfluous since this function should never be called on something with the wrong metatable; on the other hand, if somehow it was called on something with the wrong metatable (or something that's not userdata), that would be bad.


Conceptually, a single function that is sufficiently configurable has its charm, but often in reality it's easier to have one core function to do the work, and a couple or three wrapper functions that take different types of arguments.


если ты начал юзать паттерны, то size указывай в нем "^[A-Za-zА-Яа-я]{2,20}$")


@tw15egan I think this should be `2rem` instead of `32px`.  What's the reason for using `px` for this?


у тебя ж дата и так лежит в клиенте, нет смысла в префиксе client в названии полей, birthday назвать достаточно


Don't forget to remove this line before putting it to staging :)


Kindly explain what this line of code does


наверное, все таки record_id


@Data


Typescript gives me an error for this line:
```
file: 'src/services/user.service.ts'
severity: 'Error'
message: 'Property 'authState' does not exist on type 'AngularFireAuth'.'
```


:smile: Looks pretty fun though :+1:


append the errors?


Ouch.. committing a token to a public repo is a very big security issue :/
I've unauthorized it for security reason


Closes #11


не обязательно указывать @Table вообще, хибер сам тебе его нормально назовет


The validation file you added looks like a repetition of the other file


There's not separate callbacks for success, error, and done


ditto


может быть null? убер size, внеси в паттерн


surname это одно слово, тут не нужен camelCase


Hey Lars,

What exactly do you mean with I should move this to its own project?

How building with angular 4.x would make any difference?

It is compatible with angular 4.x, I just named it angular2-emoji-picker
because I believed it would clarify it was not built for angularjs

On Tue, May 9, 2017 at 6:23 AM, Lars Støttrup Nielsen <
notifications@github.com> wrote:

> You really should move this entire thing into its own project.
>
> I'm commenting here because there's no issue tracker. :)
> Also, request that you build this project with angular 4.x, possibly
> because of angular/angular#13359
> <https://github.com/angular/angular/issues/13359>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/lsharir/angular2-emoji-picker/commit/879d2a7b51c8e9d57cef065ce27880095a463ccc#commitcomment-22068496>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADMNyA7BW-0lxJ06hnREBlQY0hvOBPbCks5r4D6EgaJpZM4NVHNM>
> .
>


TeamCity libpalaso :: palaso-linux64-master Continuous [Build 4.0.140.cf90575117c73a44607c56882f78517d64d10116](http://build.palaso.org/viewLog.html?buildId=90556&buildTypeId=Libpalaso_PalasoLinux64masterContinuous) outcome was **SUCCESS**
Summary: Running Build time: 00:06:26


From my perspective, the consensus is that the programmer should not ever mess with the code by manually inserting prefetch instructions because they work differently across different CPUs. The safest bet would be reducing the size of your structure to fit as many array elements into a single cache line as possible.


TeamCity libpalaso :: palaso-trusty64-lfmerge Continuous [Build 2.6.364.cf90575117c73a44607c56882f78517d64d10116](http://build.palaso.org/viewLog.html?buildId=90543&buildTypeId=PalasoTrusty64lfmergeContinuous) outcome was **SUCCESS**
Summary: Running Build time: 00:15:15


Now the plural forms are missing in Weblate. See: https://hosted.weblate.org/translate/tiled/translations/hu/?type=allchecks
I can add them from my local translation file, but it seems to be that something is wrong with the syncing process.


есть серия, номер, дата, а это просто паспорт? Чет непонятно


[0] * 12 works :)


это дата выдачи паспорта, наверное, стоит так и назвать


@NotEmpty для дат по-моему не работает


According to @syarra, this broke TRON. It's probably not a good idea to refer to multipliers in a projected method for bound-constrained problems. I would say that `hop()` in `al_model` should take care of using the correct multipliers.

cc: @lambe


sorry, my bad. I forgot to install `4.0.0-rc.0`


зарплату не надо валидировать?


@NotEmpty и @Pattern конфликтуют, замени на @NotNull


@Entitty @Data?


In gravitystorm/openstreetmap-carto/issues/1430 we looked at https://github.com/skywinder/github-changelog-generator for automatic generation of osm-carto changelogs, but decided manually generated changelogs were an important part of our outreach process.


size -> pattern


Hi @ytsvetko , what are these `word_weights` values supposed to be doing?
I think this was something that was half-done on `master` at the time that I branched.


INADDR_LOOPBACK requires wrapping into htonl(). Without it connect() hangs on my little-endian machine.


чего не юзать человеческие @OneToMany и тп. GroupServises_ID имя колонки стремное, придерживайся единого стиля именования


![](https://github.trello.services/images/mini-trello-icon.png) [Cadastro de usuários](https://trello.com/c/jlX0k9Y5/1-cadastro-de-usuarios)


servises нет такого слова


@Data, пробел


Why not gunicorn?


Looking into that now.


@paperlib 👌 Lots of progress :)


I think @dougalm greenlit it (in a chat) because we're eager to get continuous benchmarking going. I'm sure it can be polished (like removing the tutorial comments and example lines from asv.conf.json, possibly removing the RNNSuite old-style class in favor of the function-based interface of asv to better fit with the rest of autograd's style) but it doesn't affect the rest of the code.


убрать size


TeamCity libpalaso :: fixing-to-fix-palaso-linux64-masterContinuous [Build 4.0.44.cf90575117c73a44607c56882f78517d64d10116](http://build.palaso.org/viewLog.html?buildId=90558&buildTypeId=JasonHatesMono) outcome was **SUCCESS**
Summary: Running Build time: 00:06:04


merge remote-tracking branch origin master


в одном месте salary, в другом wage?


> Regarding git log, that's pretty nice, but it does require a git tree (so it wouldn't work with channels).

Maybe nix-channel eventually can learn about fetching directly from git repos?


@Entity @Data?


> Whats the feedback from the JCTools project have you tried to contribute them there? Especially as you've contributed before :)

Very good for the past PRs: Nitsan W. has already merged a fixed message size off heap Ring Buffer I've designed + he is reviewing a new Multicast one too (there is a pending PR with it on JCTools).
I could ask on gitter or speak directly to Nitsan about it, but I suspect that such data structures could became part only of [jctools-experimental](https://github.com/JCTools/JCTools/tree/master/jctools-experimental)....

> I think def wouldn't want an apache project dependant on a single individual's personal project (no offence meant) just from a maintenance/longevity pov, so pulling into artemis maybe an option if jctools don't wish to adopt.

Anyway I was planning (could be a good [DISCUSS] thread on dev list) to cut and paste a shaded version of the only one needed on Artemis, without adding the direct dependency of the project.

> ring buffers works well in non blocking message flows/processing arch, its reason why they became a success story after lmax bounded on the scene with them

Agree, but I can add that there other good reasons too: bounded predictable latency (little law rules), bounded memory footprint, "natural" flow control and batching...

> though if just single producer and single consumer and both are already non blocking parts of the system then the overhead of the ring buffer is negated.

I didn't get the meaning of this sentence!

>  did see though in the code some ByteUtils.copy methods being invoked, surely we'd like to as much as possible pass around a buffer/memory pointer so to be zero-copy.

Agree but I've to match as much as possible the original TimedBuffer API to not break too many things so some copies are unavoidable: I've already tons of changes in this branch :P
I could design a journal that can be appended by multiple threads in parallel with zero-copy semantics  and a background (coalescing with IOPS limiter) flusher threads, but this would mean to break the support for the other type of journals, that simply can't do such things (from the API perspective).


почему Byte?


@Data


нет такого слова Servises


I meant using $LOCALIZE.  This is not needed?