As far as I remember, it improves interoperability of non-blocking pushers and blocking workers.


By the way, I'd suggest you to use `git commit -a --amend` to modify the existing commit instead of creating a new one. In this case, you won't need to do squash the commits later.


![](https://github.trello.services/images/mini-trello-icon.png) [add samples](https://trello.com/c/aE2djPqg/27-add-samples)


Couldn't run policy because this branch has conflicts that must be resolved, the policy will automatically run again after the conflicts are resolved
:point_right: click here to view a full list of the events :point_left:


when i click the save button the listview is not updated??


cv2是什么呀


[bot] 自动构建 [auto-dragalia-f298f42b.zip](https://circleci.com/gh/NateScarlet/auto-dragalia/433/artifacts/0/home/circleci/project/artifacts/auto-dragalia-f298f42b.zip)


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


Ok, thank you for your answer. We're wondering about this because since this change we see a "notify" queue in our metrics. From time to time the size increase fast...

Which part of Laravel use this parallel queue? I think we don't need this at the moment... Could it be optional?


Makes sense. And yes.


@Vizvezdenec
Good luck for LTC.

A hint to github diff. Github shows only commit diffs not code diffs (like in git). So you get on github only clean diffs if one branch contains (commit wise, not code wise, even if the code the same but the commit hashes are different its not the same on github) the other on. The simplest way is to rebase or merge your base branch in the advanced branch (I do this always in this to help the approvers at comparing). Then the diff is showed as expected.


As long as it doesn't already exist, `$!` would be nice to add.


ok


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

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

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

### Deployments updated

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

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


@PetukhovVictor Probably "Non-parenthesized" and "aren't" would be more correct


What is this program for? Is this a test of something for KeitaiWaniKani?


is design for ResultAvatar


Just curious. Have Dan and Sam seen this?


@nkint i've VScode configured to run these 2 formatters on file save:

- https://marketplace.visualstudio.com/items?itemName=nsoult.typescript-imports-sort
- https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode


:hourglass_flowing_sand: Waiting for custom rule data to be resolved
:point_right: click here to view a full list of the events :point_left:


Maybe I should add a wiki page about project / editor config?


Successfully aliased the URL <https://block-demos-ni0wuh9lk.now.sh> to the following aliases:

* https://block-demos.webpipes.now.sh
* https://block-demos-git-master.webpipes.now.sh


maybe you're right, and if there'd be hundreds/thousands of cells, am sure this would be making a difference, but here I doubt it... :)


Tried that too, didn't work. My guess is that  Python `unittest` starts with a clean environment.


The only source that I have seen for that, is here: https://github.com/justinelliotmeyers/INDIA_PINCODES/


There is already an index on SHS for `project_type, date, record_type`.  As long as the query has both columns, it should get used.  Also, indexes don't go on the main SHS table as no data is stored there.  It is partitioned.  See https://github.com/greenriver/hmis-warehouse/blob/master/db/warehouse/migrate/20180127151221_alter_indexes_on_service_history_services.rb#L10 for examples of how to adde indexes.  Though, they should be added very sparingly as the tables are huge and any index added can result in 10-50GB of data.


PR_opened/Fix_7328_CrashAFNZoneInlet (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 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-68.46%25-green.png)


DAFx version


Added.


![](https://github.trello.services/images/mini-trello-icon.png) [add a func to create nodes easily](https://trello.com/c/RLUYocwc/44-add-a-func-to-create-nodes-easily)


@juanpedromoreno could it be :thinking: ?
```
%%("pureconfig-generic", V.pureConfig)
```


What is the reason for not supporting Node.js 11, 12 ? I've been running with 12.4.0 without issues lately.


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


Good catch. :)


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2253-EC-668-SeedQuestionT](https://teamcity.nice.org.uk/viewLog.html?buildId=56006&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **SUCCESS**
Summary: Tests passed: 433 Build time: 00:07:03


잘 푸셨습니다 :) 깔끔한 로직이에요!


Successfully aliased the URL <https://star-staff-5gqu6fym9.now.sh> to the following aliases:

* https://star-staff.hanterokun.now.sh
* https://star-staff-git-master.hanterokun.now.sh


엄청 정리를 잘 하셨네요! 훌륭합니다 ㅎㅎ


Successfully aliased the URL <https://texttv-3-app-nahrtn4b5.now.sh> to the following aliases:

* https://app.texttv.nu
* https://texttv-3-app.bonny.now.sh
* https://texttv-3-app-git-texttv2019.bonny.now.sh


love that


박스를 아주 이쁘게 잘 그리셨네요 ㅎㅎ
마지막 혈액형 로직도 깔끔합니다!


Successfully aliased the URL <https://builder-yzelctksbd.now.sh> to the following alias:

* https://builder-staging.now.sh


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2858707)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/2858707/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>113 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa9abb42070): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff76fd9ef60): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/Debug: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe3811eb680): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ffa84e3ca90): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9590427500): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/Debug: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8d28f90160): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9070766bd0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f988a3a4ec0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f81cc36dc60): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f883860ac00): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Debug: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f85538bf2c0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa8347aa3f0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Debug: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe68b5b1a30): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/Debug: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fea06d29430): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Debug: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8e156967b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fadbc9ce140): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fedeb1d5320): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb9575a1060): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd4be6146d0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcc7419bfd0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fce6e556810): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd6c9e7bf60): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa4de8ec8d0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc64f61c800): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe0e20045c0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff757f99100): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9abada7f00): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa38b817c80): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9d356c5190): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcc9fc99720): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f94a9b30060): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fdfc6da8030): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa714f04a30): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f7f73496eb0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fca9277feb0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb00a8709b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f89080bdfd0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9144be3570): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/Release: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fbf05b68e50): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f836dcae3e0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc9cb621da0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff3bef64950): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa9b01de450): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff123181cb0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8e56e400a0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8402306bf0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa977e20730): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe9ccc4a210): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7facd2e0d180): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7feec045fbf0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fdc65bb4ce0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f96255ecec0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe20c58d790): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ffc16a97ed0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8febaa2160): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f90b15f3880): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/Release: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc407b1e7b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb0f8f454f0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb9d6d36010): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8a03a82850): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb0667f8580): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7febc3cf65b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7faa0ad49600): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8edc2778c0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff92ad01500): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f97c1abf130): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ffbfe4ef2d0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f84068b93a0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f95a41cc490): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff60416f2d0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8592988b30): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa4ad2ec6e0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc4f83f4950): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff2267039e0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe0692e2a60): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff6cdcbbe70): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9510ce3570): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa1c7d6a030): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa15a1f4660): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9cf1587d30): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f83c2e60e20): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f90034cb040): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcca2ad41e0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8b1dd5dd80): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe2859aae40): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc3a6237860): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ffe0554b770): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcabcc76db0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8bef54b470): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fac3a6e46b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa958484fe0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff62b400d70): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f94e5a19940): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc6fc5d59b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7feb343b1b80): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fdd77452f40): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7ff56fc79670): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcf943bf9c0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa3a4e64060): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe7dbc0e8f0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcec2e102f0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd592e4d940): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe628c252a0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb90ff949a0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/iOS Unified 64-bits - device/Debug: SGenConc: TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8a74b59070): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fddbc7f5e20): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fda02fa5470): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): TimedOut (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9e9d485e10): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8efc4a36d0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc7d75638b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd5b7d95160): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
</details>


If you are using redis queues, this notify queue will be used. I don't think we have an opt-out option because the overhead is supposed to be negligible: the number of items in this queue shouldn't be more than the number of actual jobs you have in your queue. Do you see something else?


전체적으로 코드에서 많이 고민한 흔적이 보입니다!
정말 고생하셨습니다 :)


So this works for `VarData`, but I also derive `Eq` for `ValData`, and the only non-`Doc` field I can compare on `ValData` is the type, which is not enough to guarantee equality. `inOutCall` (the function for generating a call to a function defined by inputs and outputs) accepts `Value`s as the inputs, since a parameter in a function call doesn't necessarily need to be a variable. If I changed that function to accept the inputs as `Variable`s, I wouldn't need the `Eq` instance for `ValData` but we would force all input parameters for input/output functions to be variables (I don't think this would break anything we have currently, though). Should I do that @JacquesCarette?


looks like a piece of shit


What about D?


아주 잘 푸셨습니다!
여러가지 풀이방법을 정리해두셨네요 :)


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2254-EC-781-Fix-wdio-test](https://teamcity.nice.org.uk/viewLog.html?buildId=56009&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **SUCCESS**
Summary: Tests passed: 433 Build time: 00:06:51


Make sure you're following Java naming conventions, where all method names and variable/field names are camel case


Shouldn't these use `get_or_create()`?


Does the users.showAll() call work?


Hey folks! Just noticed this. As far as the compiled agent goes, the archives I upload to pip include an agent. So, as this `PKGBUILD` installs from pypi, there is no need to compile the agent too.

> pentoo/pentoo-overlay@92903b5

The build steps here are compiling from source, hence the need to compile an agent as well.

Hope that helps clear it up!


@AimableHonorable D is too!


Thanks! I fixed it. ("isn't" is from the previous wording of this)


Memo for who is searching for complete info list of github flavor emojis

- before: `emoji.json`
- after: `emoji.json` + https://developer.github.com/v3/emojis/


What happens if you manipulate the list multiple times? Are the changes saved?


All are set/reset at the same time and I don't think it is a good idea to reset individual counters at different times. Why bother having all these symbols? Why not just have one "stats_reset_time" or "stats_start_time" ?

These counters were introduced in a different patch but weren't reset then! Looks odd to me.


Successfully aliased the URL <https://jobifymvc-gmtfitws4.now.sh> to the following aliases:

* https://jobifymvc.mandimartins23.now.sh
* https://jobifymvc-git-master.mandimartins23.now.sh


Successfully aliased the URL <https://texttv-3-app-jja1mhyjt.now.sh> to the following aliases:

* https://app.texttv.nu
* https://texttv-3-app.bonny.now.sh
* https://texttv-3-app-git-texttv2019.bonny.now.sh


Okay thank you for your information.


That was done via bundix.


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 2255](https://teamcity.nice.org.uk/viewLog.html?buildId=56015&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Set build number (Command Line)) (new) Build time: 00:00:29


How would the we know the the user does not exist? Should we throw an exception, or return a certain status code for example?


PR_opened/Fix_7151_GeneratorPVAvailSched (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 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-68.46%25-green.png)


Do we really need iter1 as it is same as iter ?


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 2256](https://teamcity.nice.org.uk/viewLog.html?buildId=56016&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Set build number (Command Line)) Build time: 00:00:27


ukral :tophat:


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 2257](https://teamcity.nice.org.uk/viewLog.html?buildId=56017&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Set build number (Command Line)) Build time: 00:00:28


I've admittedly been lazy on the context here. Instead of makeContextAware, changing eventLoop to contextAwareExecutor should be simpler and more idiomatic.


Successfully aliased the URL <https://star-staff-9axm5upu6.now.sh> to the following aliases:

* https://star-staff.hanterokun.now.sh
* https://star-staff-git-master.hanterokun.now.sh


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 2258](https://teamcity.nice.org.uk/viewLog.html?buildId=56018&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Set build number (Command Line)) Build time: 00:00:27


ты че еблан зачем


зачем?)


There's a typo here (% in front of S is missing)


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


Sorry only read the green properly, didn't see the red, which was actually using the context executor. I'll take a closer look tomorrow since at first glance the old code looks ok.


I don't expect this to modify the internal MOI objective function


ты нахуя весь прикол многопоточности убил, додик?


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


Successfully aliased the URL <https://moltin-stripe-paymentintents-dq5dfpdma.now.sh> to the following aliases:

* https://moltin-stripe-paymentintents.moltin.now.sh
* https://moltin-stripe-paymentintents-git-master.moltin.now.sh


Successfully aliased the URL <https://gatsby-theme-moltin-example-nxnienetn.now.sh> to the following aliases:

* https://gatsby-theme-moltin.now.sh
* https://gatsby-theme-moltin-example.moltin.now.sh
* https://gatsby-theme-moltin-example-git-master.moltin.now.sh


Successfully aliased the URL <https://nikoheikkilafi-qdsaa5vuv.now.sh> to the following aliases:

* https://nikoheikkila.fi
* https://nikoheikkilafi.njh.now.sh
* https://nikoheikkilafi-git-master.njh.now.sh


roboware-studio_1.2.0-1524709819_amd64.deb it can not work


le falta esto deletepersona


routes for users added


Successfully aliased the URL <https://qiaokun-web-grtyn9jbs.now.sh> to the following aliases:

* https://qiaokun-web.njzjz.now.sh
* https://qiaokun-web-git-master.njzjz.now.sh


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


`$!` exists in Prelude, though we never use it. Can we hide it from our Prelude import? Or is there another good name for this operator we could use instead?


Successfully aliased the URL <https://voicestoemotions-lzkh237qr.now.sh> to the following aliases:

* https://voices-to-emotions.com
* https://www.voices-to-emotions.com
* https://voices-to-emotions.osoc19.now.sh
* https://voices-to-emotions-git-master.osoc19.now.sh


Could you please add an info how should properties in this class be used? Especially how do we actually plan to user experimental features as framework maintainers.

It makes sense that we want to make something opt-in, but is that permanent or will it eventually become the default? In case the feature gets enabled by default in some future version, can it still be disabled here (then it's strange to call it "experimental"). Or will the property be removed all together (inducing a breaking change)?


Hmmm... better `mode.Equals("stwHeroes")` 🤔


TypeError: can't convert np.ndarray of type numpy.int32. The only supported types are: float64, float32, float16, int64, int32, int16, int8, and uint8.


Hi @bluetech, this seems to break the dynamic fields example in the [documentation](https://www.django-rest-framework.org/api-guide/serializers/#dynamically-modifying-fields).

Do you see a way to still be able to dynamically select fields to display? Thanks.


[bot] 自动构建 [auto-dragalia-2a9ef65d.zip](https://circleci.com/gh/NateScarlet/auto-dragalia/435/artifacts/0/home/circleci/project/artifacts/auto-dragalia-2a9ef65d.zip)


Happy


self.timestamp[1] is in nanoseconds. What are you trying to do? If timestamp[1] is an int, then python2 should give you a ZERO but python3 will give you a fraction (less than 1). Do we need to convert it to float() ?


Same as the other comment


This is not the latest version of the code: https://github.com/JuliaOpt/JuMP.jl/pull/2008/files#diff-e4991d07bfce9eff7cb2d85159526296R183


Thanks for catching and fixing that so quickly (thanks also to @cyrus-and for reporting it).

We should probably use `outline-on-heading-p` instead of manually doing the condition there.  On the other hand, if we do something like this, we could avoid calling `beginning-of-line` twice:
```el
(cond
 (current-prefix-arg
  (prefix-numeric-value current-prefix-arg))
 ((save-excursion
    (beginning-of-line)
    (when (looking-at outline-regexp)
      (max 1 (funcall outline-level)))))
 (t 1))
```
What do you think?


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2259-EC-668-Yes-No-Questi](https://teamcity.nice.org.uk/viewLog.html?buildId=56019&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Run Jest tests (Command Line)) (new) Build time: 00:01:37


Also I was wrong about my remark regarding a test case in my PR. Now, I realize, that at least the formtting of the timestamp should be checked in a test case. That would have prevented this typo from slipping through.
Will create a follow-up PR ...


[bot] 自动构建 [auto-dragalia-35404891.zip](https://circleci.com/gh/NateScarlet/auto-dragalia/437/artifacts/0/home/circleci/project/artifacts/auto-dragalia-35404891.zip)


Do we actually reset inode stats as well?


Should the indentation be removed from `mkEnvArgs` and the function it's based off of `mkEnv`, or is the indentation desired in some specific cases?


Tar


I don't like how this class does nothing to keep itself in a consistent state - what does mean when route is both included and excluded, why should there be anything excluded when it disabled all together, ...


我使用IDE运行出现了FileNotFoundError: [Errno 2] No such file or directory: 'paper_reading/relation2id.txt'
我在终端里运行没有出现这个问题了，但是新的问题出现了Traceback (most recent call last):
  File "train.py", line 101, in <module>
    graph, _ = load_graph(os.path.join(args.data_dir, 'train2id.txt'), num_ent)
  File "C:\Users\stone\Documents\GitHub\PaperRobot\Existing paper reading\utils\utils.py", line 93, in load_graph
    adj = torch.FloatTensor(nx.adjacency_matrix(graph.G, nodelist=range(num_ent)).todense())
TypeError: can't convert np.ndarray of type numpy.int32. The only supported types are: float64, float32, float16, int64, int32, int16, int8, and uint8.


Successfully aliased the URL <https://calendars-jg8n6yta7.now.sh> to the following aliases:

* https://calendars.weaming.now.sh
* https://calendars-git-master.weaming.now.sh


Not sure if we need to send stats reset time to show exports!


Reverted change in f86e8ec35d04d5518187ba52f85de3012640817c and 03d833247f1e5e01ea85a8ee51ec47a42a2eb8ba.


Successfully aliased the URL <https://bworks-wzxlfcvtju.now.sh> to the following alias:

* https://www.b-works.io


<details>

<summary>Submitting the task to Taskcluster failed. Details</summary>

end of the stream or a document separator is expected at line 11, column 1:
    mozilla
    ^

</details>


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2260-EC-668-Yes-No-Questi](https://teamcity.nice.org.uk/viewLog.html?buildId=56020&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Run Jest tests (Command Line)) Build time: 00:01:35


`varVal` renamed to `valueOf` in 0a4f34b6e1621764371f5fd0e8dc563d517b314b.


Derived instance of `Eq` for `VarData` removed in 631fa766252d7829a307289d8e1dca3db75ee3e1.


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2261-EC-668-Yes-No-Questi](https://teamcity.nice.org.uk/viewLog.html?buildId=56021&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Run Jest tests (Command Line)) Build time: 00:01:38


Yes, that works for me


@Demonoid could you try that case and see if the TC_LOG_ERROR is logged ?


Successfully aliased the URL <https://neontribe-www-okjqzt4uc.now.sh> to the following aliases:

* https://www.neontribe.co.uk
* https://neontribe-www.neontribe.now.sh
* https://neontribe-www-git-master.neontribe.now.sh


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2262-EC-668-Yes-No-Questi](https://teamcity.nice.org.uk/viewLog.html?buildId=56022&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **FAILURE**
Summary: Exit code 1 (Step: Run Jest tests (Command Line)) Build time: 00:01:39


@anhive-junior

s00_signage.php 보안 코드


Successfully aliased the URL <https://goldenoldies-hptp4g42p.now.sh> to the following aliases:

* https://golden-oldies.belial.now.sh
* https://golden-oldies-git-master.belial.now.sh


![](https://github.trello.services/images/mini-trello-icon.png) [[4h] Chapter 2. Basics of programming on C# (We, 17.07.19)](https://trello.com/c/UTMRCYz1/22-4h-chapter-2-basics-of-programming-on-c-we-170719)


Successfully aliased the URL <https://todo-app-7n0y05rka.now.sh> to the following aliases:

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


Successfully aliased the URL <https://builder-yxpxbclxxa.now.sh> to the following alias:

* https://builder-staging.now.sh


@yhk1515

JSON_UNESCAPED_UNICODE 이거는 뭔가용?


Hello,

How can followings constructs work ? I mean :

name/value vs. arg0.arg1

/**
	 * Add a date header.
	 *
	 * @param name the header name
	 * @param value the value of the header
	 */
	public void addDateHeader(String name, long value) {
		response.addDateHeader(arg0, arg1);
	}

	/**
	 * Add a header.
	 *
	 * @param name the header name
	 * @param value the value of the header
	 */
	public void addHeader(String name, String value) {
		response.addHeader(arg0, encode(arg1));


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/expose-execute-proxy-auto-configuration-script/3/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/expose-execute-proxy-auto-configuration-script/3/display/redirect) (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/expose-execute-proxy-auto-configuration-script/3//console)
✅ Packages: [xamarin.ios-12.15.0.270.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/3/package/xamarin.ios-12.15.0.270.pkg) [xamarin.mac-5.15.0.270.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/3/package/xamarin.mac-5.15.0.270.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/3/jenkins-results/api-diff/index.html)
🔥 [Failed to compare API and create generator diff](https://jenkins.internalx.com/job/macios/job/expose-execute-proxy-auto-configuration-script/3//console) 🔥
    ** Error: Working directory isn't clean:
    HEAD detached at 5fb8bf4c
    Untracked files:
    (use "git add <file>..." to include in what will be committed)

    tests/bcl-test/BCL tests group 1.csproj
    tests/bcl-test/BCL tests group 2.csproj
    tests/bcl-test/BCL tests group 3.csproj
    tests/bcl-test/BCL tests group 4.csproj
    tests/bcl-test/BCL tests group 6.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-modern.csproj
    tests/bcl-test/generated/
    tests/bcl-test/mscorlib-mac-full.csproj
    tests/bcl-test/mscorlib-mac-modern.csproj
    tests/bcl-test/mscorlib.csproj

    nothing added to commit but untracked files present (use "git add" to track)
    Search for `Comparing API & creating generator diff` in the log to view the complete log.
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/3/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>2 tests failed, 169 tests passed.</summary>

## Failed tests

 * monotouch-test/watchOS 32-bits - simulator/Debug (LinkSdk): Crashed
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
</details>


This is a comment


bad class names


:white_check_mark: All Rules (3 / 3) Passed

      :crown: Good job! this pull request is aligned with your organization's best practices!

      :point_right: You can review your rules settings at smart policy management :point_left:

:point_right: click here to view a full list of the events :point_left:


Is the route "Default" excluded for a reason or just to test that the exclusions work? In that case, could you please enable this feature in the first profile to see if the inclusions also works and that route Default is also ok with that.


Collaborator: Review for this commit was created. [Link to review](http://217.170.125.19:40101/ui#review:id=10)


#### Attempt 2

Forked [another attempt](https://github.com/vindard/RNIndy01/tree/load-attempt-2) based on following some Java wrapper instructions and a forum troubleshooting thread.

**The goal in this fork was to:**
1. Do an import of the wrapper from a sovrin maven repo (see `android/app/build.gradle`)
2. Get the appropriate `libjnidispatch.so` (JNA req't) & `libgnustl_shared.so` (NDK16 req't) files from appropriate repos (see [commit message](https://github.com/vindard/RNIndy01/commit/34fb54e4952a87eab1d55d95c138bd6dcfb04fcd)).
3. Write a Java function to create and return a wallet based on these imports (see [commit message](https://github.com/vindard/RNIndy01/commit/432930d1ab9d29d52542f7a68576c6386398b84f))

**Results:**
The code now gets as far as trying to execute `LibIndy.createWallet` before failing seemingly because of a mismatched `libjnidispatch.so` JNA library file. Success points:
- It successfully does the maven repo imports and line imports in the Java module file, and
- if both new `.so` files are removed it instead gets stuck at not being able to properly call `LibIndy$API.indy_create_wallet`
  _Note: There is an entire LibIndy API class with an `indy_create_wallet` method implemented [at this point](https://github.com/AxelNennker/DroidLibIndy/blob/9481099e66906786328dfccf86f77656064bf83f/app/src/main/java/org/hyperledger/indy/sdk/LibIndy.java#L21) in the DroidLibIndy Java implementation I referenced in the [load-attempt-1 branch](https://github.com/vindard/RNIndy01/tree/load-attempt-1).


Successfully aliased the URL <https://effector-hoa3h6b56.now.sh> to the following aliases:

* https://effector.now.sh
* https://effector.zerobias.now.sh
* https://effector-git-master.zerobias.now.sh


Remove the space


Successfully aliased the URL <https://calendars-mywvvjkf1.now.sh> to the following aliases:

* https://calendars.weaming.now.sh
* https://calendars-git-master.weaming.now.sh


Drop "from the file"


Successfully aliased the URL <https://todo-app-cwpkx6nke.now.sh> to the following aliases:

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


Successfully aliased the URL <https://glo-copy-board-hsljnyrpqt.now.sh> to the following alias:

* https://glo-copy-board.now.sh


Successfully aliased the URL <https://voicestoemotions-dkr0c7lwh.now.sh> to the following aliases:

* https://voices-to-emotions.com
* https://www.voices-to-emotions.com
* https://voices-to-emotions.osoc19.now.sh
* https://voices-to-emotions-git-master.osoc19.now.sh


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - x86_64-MacOS-10.13-clang: OK (2449 of 2449 tests passed, 2 test warnings)

Messages:\n
 * 2 tests had: ERR diffs.

![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)


As I mentioned in https://github.com/elastic/apm-agent-dotnet/pull/374#discussion_r304429633 - this logging statement should be Critical not Error and the message is incorrect since `ArgumentException` is not related to `value`.


Successfully aliased the URL <https://chronica-ncpm8e84z.now.sh> to the following aliases:

* https://chronica.xyz
* https://www.chronica.xyz
* https://chronica.ckipp01.now.sh
* https://chronica-git-master.ckipp01.now.sh


Hello
Welcome


Successfully aliased the URL <https://effector-k6w0kd9zh.now.sh> to the following aliases:

* https://effector.now.sh
* https://effector.zerobias.now.sh
* https://effector-git-master.zerobias.now.sh


The same as above.


#8 test script add


Successfully aliased the URL <https://nikoheikkilafi-6vncftm08.now.sh> to the following aliases:

* https://nikoheikkila.fi
* https://nikoheikkilafi.njh.now.sh
* https://nikoheikkilafi-git-master.njh.now.sh


🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2858709)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/expose-execute-proxy-auto-configuration-script/5fb8bf4c493fc78dbc878fd8da55731e38e87db3/2858709/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>11 tests failed, 102 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * monotouch-test/tvOS - device/Release: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * monotouch-test/tvOS - device/Debug (dynamic registrar): Failed
 * monotouch-test/tvOS - device/Release (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug: SGenConc: Failed
</details>


In what way does it break? (I'll only be able to try it myself later).


Now read again the code you changed and cry


Ok
Thank you


반가워요


See [this forum post](https://forum.sovrin.org/t/using-sdk-and-javawrapper-in-android-studio/1130) for inspiration for this attempt.

1. `libjnidispatch.so` was gotten from [this JNA Native repo folder](https://github.com/java-native-access/jna/tree/5.3.1/lib/native) (by choosing the appropriate tag version)

2. `libgnustl_shared.so` was gotten from NDK16b in [the NDK archives](https://developer.android.com/ndk/downloads/older_releases)

I ran `$ jar xf <filename>.jar` where appropriate to extract the `.so` files


Example taken from internet. Not my own code. It got copied with everything else.


1.1.0 changed libeay and ssleay names......
Fix in Cmake:
LIB_EAY_DEBUG: C:/OpenSSL-Win64/lib/VC/libcrypto64MDd.lib
LIB_EAY_RELEASE: C:/OpenSSL-Win64/lib/VC/libcrypto64MD.lib
SSL_EAY_DEBUG: C:/OpenSSL-Win64/lib/VC/libssl64MDd.lib
SSL_EAY_RELEASE: C:/OpenSSL-Win64/lib/VC/libssl64MD.lib


저두요
감사해요


Knew something was broken lmao


Seems like a CamelCase typo? See the capital N


Thanks again, @noseglasses. I do get an error when compiling, probably regarding the final change.

```
In file included from /Users/jdlien/kaleidoscope/Kaleidoscope-Bundle-Keyboardio/avr/libraries/Kaleidoscope-LEDEffect-FunctionalColor/examples/fc_example/fc_example.ino:317:0:
/Users/jdlien/Documents/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope-LEDEffect-FunctionalColor/src/Kaleidoscope-LEDEffect-FunctionalColor.h:608:18: error: 'KeyAddr' has not been declared
   void refreshAt(KeyAddr key_addr);
                  ^
```


Can we remove the !important?


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2488 of 2489 tests passed, 2 test warnings)

Messages:\n
 * 2 tests had: ERR diffs.

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 772
 * Failed: 1

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


Add the assert comment For eg: "Did not create the formula field"


rename it to useExternalRoute


You sure you use the latest Version of the bundle (more specifically the Kaleidoscope repo)?


Go ahead and hide `$!`. That name fits our naming convention, so it's best to go with it.


Recommend utilizing bootstrap 4 instead of 3.


lololololololol


ok after some testing and banging my head on the wall, I can explain:
this map holds **strong reference** to the WeakReference, to avoid WeakReference being collected together with it's referent (in which case GC won't add the WeakReference to the ReferenceQueue).
I'll try to fix it not being cleaned up


rename to protocol


Recommend utilizing boostrap 4 instead of 3.


You can combine the lone argument in the second line to the first line, correct? I am assuming the line length limit is OK here! Same for all others like this!


The key addressing branch was merged only quite recently into `Kaleidoscope`.


When you use an environment, you do want the 'inner' code indented. The problem is that you're putting the `\noindent` on the same line, and that forces a huge indent instead of a small one. So probably change `<>` to be vertical in this case.


TeamCity SayMore / SayMore-V3.1 pull requests [Build *.*.346.254ded318b42ba22232bd108c84e8e6f355de1c3](https://build.palaso.org/viewLog.html?buildId=156869&buildTypeId=SayMore_SayMore31pullRequests) outcome was **FAILURE**
Summary: Compilation error: src\SayMore\SayMore.csproj (new) Build time: 00:00:43


a neat expressive way of writing this is

```
_max_var_number = std::max(_max_var_number, var_num);
```


Looks OK to me.


Successfully aliased the URL <https://zeit-now-sample-8n2igos5y.now.sh> to the following aliases:

* https://zeit-now-sample.fukufukupuku.now.sh
* https://zeit-now-sample-git-master.fukufukupuku.now.sh


Successfully aliased the URL <https://effector-a11ocgget.now.sh> to the following aliases:

* https://effector.now.sh
* https://effector.zerobias.now.sh
* https://effector-git-master.zerobias.now.sh


Successfully aliased the URL <https://neontribe-www-6mf5bnsvs.now.sh> to the following aliases:

* https://www.neontribe.co.uk
* https://neontribe-www.neontribe.now.sh
* https://neontribe-www-git-master.neontribe.now.sh


The `searchWord` here is not the same as the `searchWord` in `markup`. You want to actually write:

```js
const markup = searchWord => <mark className='search' key={ key }>{ searchWord }</mark>;
```

Otherwise, your markup will always use the original match value, instead of whatever value the `mark` function matches with.


@sophiefsadler

Did you manage to solve it yet? It just tested this in the Blocks environment, and it seems to work for me.


Oh and I would actually use a different variable name than `searchWord` in that tag function, to avoid confusion.


Ah yes.
```git submodule update --recursive --remote
```
did the trick. Thanks.

Now I just have to figure out what to remove to fix excessive memory use! I'm off to work now but hopefully I will be able to check it out tonight.


The code in the documentation example no longer restricts which fields are displayed. To give you a use-case, we use dynamic fields as described in the documentation when we would like to limit the fields in a nested serializer.

For example:
```
class DynamicFieldsModelSerializer(serializers.ModelSerializer):
    """
    A ModelSerializer that takes an additional `fields` argument that
    controls which fields should be displayed.
    """

    def __init__(self, *args, **kwargs):
        # Don't pass the 'fields' arg up to the superclass
        fields = kwargs.pop('fields', None)

        # Instantiate the superclass normally
        super(DynamicFieldsModelSerializer, self).__init__(*args, **kwargs)

        if fields is not None:
            # Drop any fields that are not specified in the `fields` argument.
            allowed = set(fields)
            existing = set(self.fields)
            for field_name in existing - allowed:
                self.fields.pop(field_name)

class TrackSerializer(DynamicFieldsModelSerializer):
    class Meta:
        model = Track
        fields = ['order', 'title', 'duration']

class AlbumSerializer(serializers.ModelSerializer):
    tracks = TrackSerializer(many=True, read_only=True, fields=['order', 'title'])

    class Meta:
        model = Album
        fields = ['album_name', 'artist', 'tracks']
```

In Rest Framework `3.10.0` this no longer works. The field `duration` now shows up in the `tracks` field of an instance of `AlbumSerializer`.

Thanks for looking into it.


Successfully aliased the URL <https://create-react-app-nca2u1n2s.now.sh> to the following aliases:

* https://create-react-app.nathaliecortz.now.sh
* https://create-react-app-git-master.nathaliecortz.now.sh


Derivaties is a 1D array (list).
When argmax is used on 1D Array it gives a scalar value as such the `[0]` throws an error.

Check argmax behaviour here: https://docs.scipy.org/doc/numpy/reference/generated/numpy.argmax.html

Were you able to test this function after adding this?


It feels like something is wrong with the `Eq` on `ValData`. I don't quite have enough information to really know. Can you point me to the specific places in the code to look at?


TeamCity SayMore / SayMore-V3.1 pull requests [Build *.*.347.ce6124ba75988e53a88ac3f24d0b6c8734da70b9](https://build.palaso.org/viewLog.html?buildId=156874&buildTypeId=SayMore_SayMore31pullRequests) outcome was **FAILURE**
Summary: Compilation error: src\SayMore\SayMore.csproj (new) Build time: 00:00:44


Look on los gerrit


Ok, ca me semble pas mal là !
Merci Eliam, on va mettre cela en place.


Note that you also need to call `shortid.generate()` in the function, otherwise all marked elements will have the same id.

```js
const tag = x =><mark className='search' key={ shortid.generate() }>{ x }</mark> ;
```


TeamCity SayMore / SayMore pull requests [Build *.*.352.ce6124ba75988e53a88ac3f24d0b6c8734da70b9](https://build.palaso.org/viewLog.html?buildId=156873&buildTypeId=SayMore_SayMorePullRequests) outcome was **SUCCESS**
Summary: Running Build time: 00:01:51


This typescript upgrade breaks compatibility with Ionic 4, which is still locked to Angular 7, which requires typescript >=3.1 && <3.3.0. Ionic 5 is planned to use angular 8, which does bump typescript max version do 3.5.


Added ($!) in 1a082d7cb796d01d3f2379dc75dd3fa7fc18a1aa.


hi, Sir, please give a test for V web server, Thx.


So if `$!` can't be used as a prefix operator without the `()`, it is a bad name. I don't remember Haskell's lexical conventions well enough to give an alternative though.


Successfully aliased the URL <https://glo-copy-board-czefzfkute.now.sh> to the following alias:

* https://glo-copy-board.now.sh


Hi @chris-pook. Please find more info in the related issue https://github.com/magento/magento-coding-standard/issues/108

The most recent recommendation I got from architecture team is that `ViewModel` should be used in order to avoid the use of `$this->helper()`.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (1805 of 1805 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)


Gute Punkte - geändert.


The reference to ../../static/ in your file won't work on the server, make sure you replace them with just a simple /.

I will recommend to find a good point to commit and push this to master so we can see your contributions and maybe we can test them on the production server in a page that wouldn't break the flow of the app.


Successfully aliased the URL <https://ae-icons-component-bdb3lzq1d.now.sh> to the following aliases:

* https://ae-icons-component.adaept.now.sh
* https://ae-icons-component-git-master.adaept.now.sh


oh well, server setup diddn't work for me, kept getting "steam subsystem failure" and server never popped up.


Indeed, thanks for the catch.
The variable name might be too long, I can change that if you find it better. It reflects on the fact that `snapshotRelPath` has a String containing "{pool-name}/{image-name}/{snap-name}".


need more line


Successfully aliased the URL <https://distance-learning-lp-vdcfjqxibe.now.sh> to the following aliases:

* https://lp.onlineschool.ru
* https://www.onlineschool.ru


Trying to work around failures on AppVeyor like this one https://ci.appveyor.com/project/cypress-io/cypress/builds/26035715/job/4eo809a7ct1xv8ji


@JuliaRegistrator register

Release notes:

Moved from REQUIRE to Project.toml
Bumped Julia and MacroTool minimal versions


Registration pull request created: [JuliaRegistries/General/2083](https://github.com/JuliaRegistries/General/pull/2083)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.9.0 -m "<description of version>" 3ad9428324701b227240e622ced1c9ff1fc908ec
git push origin v0.9.0
```


BTW, I got it to work again by changing my dynamic serializer fields mixin to look like:

```
class DynamicFieldsSerializerMixin(serializers.ModelSerializer):
    """
    A ModelSerializer mixin that takes an additional `fields` argument that
    controls which fields should be displayed.
    """
    _dynamic_fields = None

    def __init__(self, *args, **kwargs):
        # Don't pass the 'fields' arg up to the superclass
        self._dynamic_fields = kwargs.pop('fields', None)

        # Instantiate the superclass normally
        super().__init__(*args, **kwargs)

    @cached_property
    def fields(self):
        fields = super().fields

        if self._dynamic_fields is not None:
            # Drop any fields that are not specified in the `fields` argument.
            allowed = set(self._dynamic_fields)
            existing = set(fields)
            for field_name in existing - allowed:
                fields.pop(field_name)

        return fields
```

Do you think it is worth submitting a PR updating the documentation?


Ah ok, fair enough. Thanks for coming back to me!


@wido I will recheck this logger, might need a few changes, considering [67bc0d4971e68fa8cf40f649ab427fc7233f2ecf](https://github.com/PCextreme/cloudstack/commit/67bc0d4971e68fa8cf40f649ab427fc7233f2ecf).


I assume the group thing means supermarket isn't needed here?


Does this require that this modified code be used at both Rx and Tx radios?  I am using RF69CW radios at both ends, but one (the remote) is running older JeeLib.  When I tried updating just the other one (not the remove one) with the latest jeelib from the master branch, the link decidedly became unstable.

I am trying to debug the issue that I see now and is discussed as part of #92 . I have a basestation radio which receives packets and also sends out packets (ping-pong).  After about 2 days of continuous operation, it freezes (neither receives nor transmits packets).  I know it's the radio that's frozen since the rest of the sketch is working (interaction with the sketch via commands over the serial port confirms this).  Upon power cycle it works again (for about 2 days). Since the master branch makes the link even more unstable, I am now trying code that would call rf12_initialize() if no packets are receive for 10 sec.


j


develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


Nice, good call on the shellescape.


Successfully aliased the URL <https://mogul-cpcdl6w7z.now.sh> to the following aliases:

* https://mogul.mogul.now.sh
* https://mogul-git-master.mogul.now.sh


Now could not deploy this pull request since it contains the following references to invalid secrets in the `env` sections of the `now.json` file:

* `opencollective_url` (in env: `OPENCOLLECTIVE_URL)`

Add those secrets or remove them from the `env` maps in the `now.json` file.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


Collaborator: Review for this commit was created. [Link to review](http://217.170.125.19:40101/ui#review:id=11)


Function copy-pasted from [this point](https://github.com/AxelNennker/DroidLibIndy/blob/9481099e66906786328dfccf86f77656064bf83f/app/src/main/java/indy/hyperledger/org/droidlibindy/DroidLibIndy.java#L76) in the working Java implementation I've been reviewing.


If the commit broke a documented code example, it's a regression that should probably be fixed. I'll look at it later today. Thanks for the reproduction code.


done


lgtm!


line added by dev1


There is option to "enable all" and enable each of them individually as well..so we have these different variables for all of them. So eg- we could reset all, then disable some and enable one and hence may need these different values.


Definition of `ValData`:
https://github.com/JacquesCarette/Drasil/blob/1a082d7cb796d01d3f2379dc75dd3fa7fc18a1aa/code/drasil-code/Language/Drasil/Code/Imperative/Data.hs#L62-L63
`inOutCall` signature:
https://github.com/JacquesCarette/Drasil/blob/1a082d7cb796d01d3f2379dc75dd3fa7fc18a1aa/code/drasil-code/Language/Drasil/Code/Imperative/Symantics.hs#L449-L451
Code where `ValData`s are compared for equality:
https://github.com/JacquesCarette/Drasil/blob/1a082d7cb796d01d3f2379dc75dd3fa7fc18a1aa/code/drasil-code/Language/Drasil/Code/Imperative/LanguageRenderer/CSharpRenderer.hs#L650-L657
https://github.com/JacquesCarette/Drasil/blob/1a082d7cb796d01d3f2379dc75dd3fa7fc18a1aa/code/drasil-code/Language/Drasil/Code/Imperative/LanguageRenderer/CppRenderer.hs#L1853-L1858


hi


Successfully aliased the URL <https://og-image-14obdary3.zeit.sh> to the following aliases:

* https://og-image.now.sh
* https://api-og-image.zeit.sh
* https://og-image.zeit.sh
* https://og-image-git-master.zeit.sh


defaults should always be "false".


gps模块在2hz频率下不能看到卫星数量，能修复一下这个问题吗


Seems that the linux build of gmsh is problematic :/.


![](https://github.trello.services/images/mini-trello-icon.png) [0717 질문게시판에 서버 연결 테스트 구현 및 코드 정리](https://trello.com/c/3z9il7L0/9-0717-%EC%A7%88%EB%AC%B8%EA%B2%8C%EC%8B%9C%ED%8C%90%EC%97%90-%EC%84%9C%EB%B2%84-%EC%97%B0%EA%B2%B0-%ED%85%8C%EC%8A%A4%ED%8A%B8-%EA%B5%AC%ED%98%84-%EB%B0%8F-%EC%BD%94%EB%93%9C-%EC%A0%95%EB%A6%AC)


since there might be more options in the future, i suggest have an interface for this (```interface DebugViewOptions { ... }``` )


I've rewritten this, PR upcoming


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


yes!  This is because of the "match_groups" config file:
https://github.com/osmlab/name-suggestion-index/blob/master/config/match_groups.json

If a feature from OSM matches any of the tags in a match group, it's considered the same thing.
So if it appears in the data as `shop/food|Iceland` or `shop/supermarket|Iceland` we know that it's the same brand..

The iD editor reuses this code, and it will even show a validation warning to prompt the user to upgrade the tags to `shop/frozen_food` and add the `brand:wikidata` and other stuff that might be missing.


do ```!DebugView._debugViews```


файлы назови cargo_train.rb
нужно называть их в snake_case


Successfully aliased the URL <https://osu-speedsimosh-9bzvctvef.now.sh> to the following aliases:

* https://osu-speed-2.simo.sh
* https://osu-speedsimosh.fr3fou1.now.sh
* https://osu-speedsimosh-git-master.fr3fou1.now.sh


Successfully aliased the URL <https://og-image-avhb7rmbk.zeit.sh> to the following aliases:

* https://og-image.now.sh
* https://api-og-image.zeit.sh
* https://og-image.zeit.sh
* https://og-image-git-master.zeit.sh


[Circle has built](https://circleci.com/gh/cypress-io/cypress/135580) the `linux x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/linux-x64/circle-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-135540/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.4.1/circle-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-135550/cypress.tgz


Successfully aliased the URL <https://mogul-q3flxdf83.now.sh> to the following aliases:

* https://mogul.mogul.now.sh
* https://mogul-git-master.mogul.now.sh


Ты должен сохранять не number а сам объект поезд а


Можно назвать просто `@trains`


вместо station_name назови  просто name


Принимаешь name, но нигде не сохраняешь


end съехал


Отступ нужен


Great work!


Successfully aliased the URL <https://devplenoconvertmymoney-9afucnr8k.now.sh> to the following aliases:

* https://devplenoconvertmymoney.renatoelysiqueira.now.sh
* https://devplenoconvertmymoney-git-master.renatoelysiqueira.now.sh


Dear @w4x51m,
> I regret to inform you that your plugin "**QuiverCore**" (v2.0.0 submitted on 2019-07-16T15:10:32.000Z) has been rejected.

C1a — Namespace format:
> All plugins must choose a **unique** namespace that will not be accidentally collided by other plugins. The plugin must begin with the author name (unless its an official plugin, because the namespace `pocketmine` is disallowed), followed by any identifier such that the author himself remembers which plugin it corresponds to. The recommended namespace format is `AuthorName\PluginName`. The author name should use one that corresponds to the GitHub username/org name to prevent collision.

A2 — Serve a specific purpose:
> The plugin must serve a **specific** purpose and be useful to the majority of users. Core plugins are not accepted, because they are only useful on specific private servers. Plugins that contain many mutually irrelevant features are also not allowed, because they are a major source of bloatware.

Please resolve these issues and submit the plugin again.

> This comment is posted here because this is the last commit when the released build was created.


PR_opened/Fix_7378_StorageTankTempLimit (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1121 of 1123 tests passed, 0 test warnings)

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 771
 * Failed: 2

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


не `positive?` а `zero?`


Successfully aliased the URL <https://my-glo-next-site-b29ezriir.now.sh> to the following aliases:

* https://my-glo-next-site.jamesquigley.now.sh
* https://my-glo-next-site-git-master.jamesquigley.now.sh


А станция же должна узнать что поезд прибыл


Iniciando curso java script


don't edit .gitignore. it is just a trash


Поезд должен уехать с текущей станции и приехать к новой станции


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/26047816/job/20ejgjil0tifkbxh) the `win32 x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/win32-x64/appveyor-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-26047816/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.4.1/win32-x64/appveyor-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-26047816/cypress.zip


@JuliaRegistrator register


Registration pull request created: [JuliaRegistries/General/2084](https://github.com/JuliaRegistries/General/pull/2084)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.9.7 -m "<description of version>" 2f90c135d1fa679a7f1f6a39dc9ff9a0d6f36feb
git push origin v0.9.7
```
Also, note the warning: Version 0.9.7 skips over 0.9.6
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Snuggs whats an email for contact for you?


Registration pull request created: [JuliaRegistries/General/2085](https://github.com/JuliaRegistries/General/pull/2085)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.8.5 -m "<description of version>" 41d3fcd557939450270f6847d53d3f5b5b362ad6
git push origin v0.8.5
```


Do you know what happened?


@dschalep looks good! I will approve the pull request shortly and we can merge into master, and then fold master into feature_space. Thank you!!


review test


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/26047816/job/xpve2vuedlc4sj0o) the `win32 ia32` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/win32-ia32/appveyor-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-26047816/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.4.1/win32-ia32/appveyor-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-26047816/cypress.zip


your git clone is private it asks for username


[Circle has built](https://circleci.com/gh/cypress-io/cypress/135587) the `darwin x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/darwin-x64/circle-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-135585/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.4.1/circle-develop-b55eb8ee7b2946c1c255f924e798ee5f5edfd0ef-135583/cypress.tgz


I can run my code successfully on my computer. I think the problem might be related to 1. your pytorch version, 2. your numpy versions` 3. your ubuntu system configuration (my system is 64 bit) . The attachment is my command snapshot
![image](https://user-images.githubusercontent.com/14304965/61386626-3022a780-a8e7-11e9-97e4-4f7d25672036.png)


Successfully aliased the URL <https://adglossbossde-hrpvfc2vb.now.sh> to the following aliases:

* https://ad.glossboss.de
* https://adglossbossde.ntwcklng.now.sh
* https://adglossbossde-git-master.ntwcklng.now.sh


Thanks. I discovered after committing this to my local repo that mknod also creates extended attributes. I plan on reinstating EA support in the near term.

Steve

> On Jul 17, 2019, at 5:32 AM, pali <notifications@github.com> wrote:
>
> mkudffs 2.1 for UDF 1.50 revision with VAT (e.g. CD-R media type) already generates these extended attributes.
>
> So you can generate your own "example" medias.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.


[vg CI tests](https://ucsc-ci.com/vgteam/vg/pipelines/1108) complete for merge to master.  View the [full report here](http://vg-data.s3.amazonaws.com/vg_ci/vgci_reports/branch/master/index.html).

19 tests passed, 0 tests failed and 0 tests skipped in 13713 seconds

Tests produced 734 warnings. 734 were for lower-than-expected alignment scores


Successfully aliased the URL <https://calendars-7yr22ukyi.now.sh> to the following aliases:

* https://calendars.weaming.now.sh
* https://calendars-git-master.weaming.now.sh


Check the https://github.com/EagleW/PaperRobot#requirements for the environment requirement. @zhengLee123


I think the parentheses are the only way to use a prefix operator. From some googling, the only true prefix operator in Haskell is `-` (https://wiki.haskell.org/Unary_operator). Of course, if we used alphanumeric characters, we wouldn't need parentheses, but we already have that with `valueOf`.


Successfully aliased the URL <https://todo-app-kvajonk08.now.sh> to the following aliases:

* https://todo-app.vincentreynaud.now.sh
* https://todo-app-git-master.vincentreynaud.now.sh


m_ml_event_handle miss its destructor. it should be given during construction
```
    , m_ml_event_handle( nullptr, [this](vlc_ml_event_callback_t* cb ) {
            assert( m_ml != nullptr );
            vlc_ml_event_unregister_callback( m_ml, cb );
        })
```


Successfully aliased the URL <https://saika-eodzzc1pn.now.sh> to the following aliases:

* https://saika.evillt.now.sh
* https://saika-git-master.evillt.now.sh


Successfully aliased the URL <https://venia-o32jb6oxt.now.sh> to the following aliases:

* https://magento-venia-develop.now.sh
* https://venia.magento-research1.now.sh
* https://venia-git-develop.magento-research1.now.sh


I think because I don't use ubuntu,so pytorch need int64.


You're welcome! ... although it isn't me  :)


`ψ` is a morphism family so its indexer is made explicit. it's like `η` in natural transformation, which is also made explicit. we can review this if you think it's better the other way.

regarding `Cones`, this is worth discussing. in the original library they are separate, but when I port `Cones`, I figured that whenever it is used, `Cone` is necessary so if they are separated in two different files, it means two imports must come in pair, which is a bit redundant. but on the other hand, I understand why it's good to put `Cones` in `Category.Construction`. what do you think?


move modules/gui/qt/components/ml_folders_model.cpp  to modules/gui/qt/components/mediacenter


The following doc(s) have been deployed to the [gatsby](https://gatsby-static-docs.pantheonsite.io/docs) Multidev environment:
- [.circleci/config.yml](https://github.com/pantheon-systems/documentation/commit/ad06eb97b83526b6d260bd439e6280c78f257a6a/.circleci/config.yml)


@btn0s none of these icons are in the feather spec. These are copied icons from font awesome and material and then ported over to match the form of the other feather icons. I had to make these changes because the first time I ported them over I missed making these.


Emm, that might be one reason


I`m sad for this, is there no other solution than to eliminate, remove, deprecate everything there?


google search console