```
fun Completable.async() =
    subscribeOn(Schedulers.io()).observeOn(AndroidSchedulers.mainThread())

fun <T> Single<T>.async() =
    subscribeOn(Schedulers.io()).observeOn(AndroidSchedulers.mainThread())

fun <T> Observable<T>.async() =
    subscribeOn(Schedulers.io()).observeOn(AndroidSchedulers.mainThread())

fun <T> Single<T>.loading(liveData: MutableLiveData<Boolean>) =
    doOnSubscribe { liveData.value = true }.doFinally { liveData.value = false }

fun Completable.loading(liveData: MutableLiveData<Boolean>) =
    doOnSubscribe { liveData.value = true }.doFinally { liveData.value = false }

fun <T> Single<T>.loading(block: (Boolean) -> Unit) =
    doOnSubscribe { block(true) }.doFinally { block(false) }

fun Completable.loading(block: (Boolean) -> Unit) =
    doOnSubscribe { block(true) }.doFinally { block(false) }
```


Cách dùng:
`val loading = MutableLiveData<Boolean>()`
```
.async()
.loading(loading)
```


tham khảo cái extension bên dưới e


建议这里加一个资源限定「/模块限定/资源限定」->'/usr/ciflimitset/'，然后下面的接口可以以POST标识添加个人客户限额设置、GET获取.....


Thanks!


type="cn.jiiiiiin..entity.UserPb" 是不是少了一个包节点


cái này có thể chế thêm như này trong base:
```
protected fun rx(block: () -> Disposable?) {
        if (disposable == null) throw IllegalArgumentException(
            "No worry! You've just forgot inject disposable, DO IT!")
        block()?.let { disposable?.add(it) }
    }
```
Cách dùng:
rx {
 Single
    .just()
    .....
    .subscribe(...) //chỉ cần subscribe để trả về disposable là đc
}


@charuidong 看一下注释，然后看看对应建议是否可行，整理到编码规范中


nếu số lượng code để handle không nhiều line code, thì không cần tách thành function riêng e nhé


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

* https://express.adrianm.now.sh
* https://express-git-master.adrianm.now.sh


ops, era pra ser "Apontando eles para NULL (só pra ficar tudo zerado no debug)". Esqueci de alterar :/


test


此处修复了文章页面以小分类进行跳转无法正常传参的bug


This needs to be improved


Successfully aliased the URL <https://gatsby-themes-i63w0wwc9.now.sh> to the following aliases:

* https://gatsby-themes.undataforum.now.sh
* https://gatsby-themes-git-master.undataforum.now.sh


selam :)


Successfully aliased the URL <https://dabas-thing-py7c168yv.now.sh> to the following aliases:

* https://dabas-thing.datner.now.sh
* https://dabas-thing-git-master.datner.now.sh


selam:))


Deleting this line was an error. It is needed for deleting terms.


should consider l.maxpool_depth?


Hi Guys
I have just installed this and it is showing in HA States as UNKNOWN
Here is code in config file. I tried using my Life360 tracker as well and that came back with same result, UNKNOWN

  - platform: yandex_maps
    start: '-41.220699, 174.905709'
    destination: '-41.331283, 174.773062,
    name: Time to Home

Hope you can help


🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2860415)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/7b1dada4563514ad2af3461e4fb47da5ceac7c23/2860415/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>3 tests failed, 110 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug (interpreter): Failed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fbdb26a0060): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/tvOS - device/Release: Failed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f966d04cb80): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fdd424add80): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
</details>


ChangelogFixUTF (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1120 of 1120 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-42.34%25-green.png)


半角に直してみましたが、ダメでした...。なんかyo hubotをする時に英語で、重複したjsonファイルがー、みたいなエラーメッセージが出てきたので、jsonファイルを別フォルダに格納してyo hubotして起動してみましたが、エラーは取れたけどbot自体は反応しませんでした..(語彙力なくてすみません...！)


Python的条件判断不需要使用括号

```python
if int(n) == 0:
  n=10
```

另外多处对n进行了 int(n) 这样的转换操作，实际上如果代码中多处需要这样处理，直接使用一个新的变量保存转换结果，然后替换掉后面的 int(n) 即可。

这样即可。逻辑很清楚，细节还有改进空间。


Thanks to you and your gang of thugs now we have to deal with this, Rouing. Thank you so much:

![image](https://user-images.githubusercontent.com/42406302/61425031-8a216e00-a8e3-11e9-8328-462d8d6086ab.png)


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

I updated the Github team because of this commit.

- @arnekr, @frodepedersen were added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

You should get push access to this feedstock and CI services.

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

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
  "version": 2,
  "name": "akhila-blog",
  "alias": "akhilaariyachandra.com",
  "builds": [
    {
      "src": "package.json",
      "use": "@now/static-build",
      "config": { "distDir": "public" }
    }
  ],
  "routes": [
    {
      "src": "/post/(.*)",
      "status": 301,
      "headers": { "Location": "/$1" }
    }
}

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


deal with it stop complaining about it just do something


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

* https://fenews.org
* https://fenewsorg.fe-news.now.sh
* https://fenewsorg-git-master.fe-news.now.sh


Successfully aliased the URL <https://away-with-me-l0zc7a1oo.now.sh> to the following aliases:

* https://away-with-me.away-with-me-jam.now.sh
* https://away-with-me-git-trunk.away-with-me-jam.now.sh


> deal with it stop complaining about it just do something

It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.


> > deal with it stop complaining about it just do something
>
> It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.

i get that its not nice but why don't you report it to discord and other people


heat_exchanger_sizing_updates (drewyh) - x86_64-MacOS-10.13-clang: Tests Failed (2549 of 3118 tests passed, 70 test warnings)

Messages:\n
 * 637 tests had: EIO diffs.
 * 562 tests had: Table big diffs.
 * 130 tests had: ESO big diffs.
 * 294 tests had: BND diffs.
 * 70 tests had: ERR diffs.
 * 84 tests had: MTR big diffs.
 * 7 tests had: AUD diffs.
 * 51 tests had: ESO small diffs.
 * 62 tests had: MTR small diffs.
 * 95 tests had: MDD diffs.
 * 109 tests had: MTD diffs.
 * 103 tests had: RDD diffs.
 * 4 tests had: SSZ big diffs.
 * 5 tests had: ZSZ big diffs.
 * 1 test had: SSZ small diffs.

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 737
 * Failed: 1

regression Test Summary
 * Passed: 70
 * Failed: 568

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


> > > deal with it stop complaining about it just do something
> >
> >
> > It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.
>
> i get that its not nice but why don't you report it to discord and other people

Already did, and I did put the warning on Discord and the website as well. The Rouing the clown came here and try to defend his indefensible actions


Successfully aliased the URL <https://away-with-me-5934qkigy.now.sh> to the following aliases:

* https://away-with-me.away-with-me-jam.now.sh
* https://away-with-me-git-trunk.away-with-me-jam.now.sh


GSHP_desuperheater (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2490 of 2490 tests passed, 2 test warnings)

Messages:\n
 * 1 test had: EIO diffs.
 * 1 test had: ESO small diffs.
 * 1 test had: BND 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)


-5점: 닫는태그는 엔터치고 하셈


help me^~^


-5점: 닫는태그는 엔터치고 하셈ㅇㅇ


총점: 90점
layout_weight 사용법 절대 까먹지 말기


It is that this change does not convince me at all, I think it can be improved, but at this moment it does not give me the mind, I did it more than anything thinking about a provisional solution for today's update 😕


Successfully aliased the URL <https://effector-h6fi2ygv9.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://monorepo-4ptlvc1s3.now.sh> to the following aliases:

* https://monorepo.storybook.now.sh
* https://monorepo-git-next.storybook.now.sh


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

Created multidev environment [v0-14](https://dashboard.pantheon.io/sites/9dc3b9a0-4853-4dfd-b01f-6fe8cb0d08fd#v0-14) for rescue-x-comms.


-1점: 불필요한 엔터가 너무많음 여기


총점: 99점 (사실상 80점대)
불필요한 엔터들만 주의하고
layout_weight 사용법은 절대 까먹지 말기 핵심임ㅇㅇㅇ


-3점: 자바도 줄정리해주기 아마 단축키가 ctrl + alt + l 인듯


Well, this line should have been in another commit.

It's a new way to make `nextFrame` smarter: if a help dialog / vomnibar / linkhints is showing on the top frameset frame, then not skip the frame.


GSHP_desuperheater (yzhou601) - 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)


>
>
> > deal with it stop complaining about it just do something
>
> It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.

A gang of thugs did just that with me. Ive seem to dealt with it by putting out proof. Seems to me like the truth is coming out and biting you in the ass.


真牛逼


Successfully aliased the URL <https://away-with-me-p8f2eoj6g.now.sh> to the following aliases:

* https://away-with-me.away-with-me-jam.now.sh
* https://away-with-me-git-trunk.away-with-me-jam.now.sh


GSHP_desuperheater (yzhou601) - 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)


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

Created multidev environment [ci-365](https://dashboard.pantheon.io/sites/a1cb0631-9c51-4439-bd6f-e7b7c38806ea#ci-365) for claimyourcoordinatescom.


-5점: 왜 ContraintLayout씀 맘에안듬
+2점: CircleImageView 알아서 써본거 굳


총점: 97점 ㅇㅇㅇ
gradle통해서 라이브러리 사용하는거 까먹지말고
layout_weight 절대 까먹지 말기


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

Created multidev environment [v0-14](https://dashboard.pantheon.io/sites/39804e8f-253e-474e-82cf-725b36fddde0#v0-14) for rescue-x-base.


Haha, good catch. It's a Czech "cute" misspelling of the Italian word. 👶


添加省市二级联动


> > > deal with it stop complaining about it just do something
> >
> >
> > It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.
>
> A gang of thugs did just that with me. Ive seem to dealt with it by putting out proof. Seems to me like the truth is coming out and biting you in the ass.

Oh really? You come here bitching about a warning against you and your gang, who plotted the tech destruction again? You literally came out of nowhere, caused all this shit then shift blame to me who has ABSOLUTELY NOTHING to do with your evil plan. Accept the fucking responsibility and stop doing nasty shit in someone's name who wants absolutely nothing to do with you.

https://user-images.githubusercontent.com/42406302/61342275-a9eb6000-a817-11e9-86e5-c65b3e5e772e.png


god


Successfully aliased the URL <https://burger-builder-qem6mq3m6.now.sh> to the following aliases:

* https://burger-builder.obododavid5.now.sh
* https://burger-builder-git-master.obododavid5.now.sh


Deployment failed with the following error:

~~~
The chosen alias "back-end.now.sh" is already in use by another account.
~~~


Successfully aliased the URL <https://akhila-blog-ge9mqkknd.now.sh> to the following aliases:

* https://akhilaariyachandra.com
* https://akhila-blog.heshan-1010.now.sh
* https://akhila-blog-git-master.heshan-1010.now.sh


>
>
> > > > deal with it stop complaining about it just do something
> > >
> > >
> > > It's not that easy when a gang of thugs do nasty shit out of nowhere and shift blame to us.
> >
> >
> > A gang of thugs did just that with me. Ive seem to dealt with it by putting out proof. Seems to me like the truth is coming out and biting you in the ass.
>
> Oh really? You come here bitching about a warning against you and your gang, who plotted the tech destruction again? You literally came out of nowhere, caused all this shit then shift blame to me who has ABSOLUTELY NOTHING to do with your evil plan. Accept the fucking responsibility and stop doing nasty shit in someone's name who wants absolutely nothing to do with you.
>
> https://user-images.githubusercontent.com/42406302/61342275-a9eb6000-a817-11e9-86e5-c65b3e5e772e.png

Endeavor is apart of your gang. Not mine. Sorry not sorry. I aint accepting responsibility for your team's bullshit. Get salty.


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

* https://sharing.wrather.now.sh
* https://sharing-git-master.wrather.now.sh


Add contributor : Nikhil Dabhade


Sounds like we also need to add WPS support in out image... I hope I had the time...


Need to check what happens `if self.ref is None`.


I think a better naming can be invented. What is `args`?


We also need to specify whether mentioning a parameter in in post condition refers to it's initial value when entering the function or its possibly changed value just before exiting the function.


I believe it can be solved with `filter`.


@JuliaRegistrator register()


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

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.2.0 -m "<description of version>" e01ecdbce13c9c96a4d29ac1aa423ed6477a42e6
git push origin v0.2.0
```


IBM Cloud [toolchain](https://console.bluemix.net/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi](https://github.com/springdoc/springdoc-openapi/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200217 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200217") to [dev](https://console.bluemix.net/apps/1530d1fa-00ae-4b10-b035-13bfb4b99020?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


@rogersanick I would say only the one who places and pays needs to sign. The others trust the process thanks to the other parts of this contract.


This is so great, thanks for being so good at coding.


Why one dash is used here? There's one in other places.


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

Created multidev environment [p-component](https://dashboard.pantheon.io/sites/b35a0caa-be8e-4f9a-b4e7-ba20d37ce7e9#p-component) for edspring.


Why do we need `setReadable`?


awe


![](https://github.trello.services/images/mini-trello-icon.png) [Desenvolver Controller para Tarefas](https://trello.com/c/6hXK4YDs/19-desenvolver-controller-para-tarefas)


Why `one` is needed in the name?


Puzzle `116-e55fec98` disappeared from [`core/Action.h`](https://github.com/DronMDF/doors/blob/master/core/Action.h), that's why I closed #119. Please, remember that the puzzle was not necessarily removed in this particular commit. Maybe it happened earlier, but we discovered this fact only now.


Puzzle `119-bfecade2` discovered in   [`core/BytesLock.h`](  https://github.com/DronMDF/doors/blob/master/core/BytesLock.h)   and submitted as #208. Please, remember that the puzzle was not   necessarily added in this particular commit. Maybe it was added earlier, but   we discovered it only now.


Puzzle `119-19a7427f` discovered in   [`core/RawBytes.h`](  https://github.com/DronMDF/doors/blob/master/core/RawBytes.h)   and submitted as #209. Please, remember that the puzzle was not   necessarily added in this particular commit. Maybe it was added earlier, but   we discovered it only now.


IBM Cloud [toolchain](https://console.bluemix.net/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi](https://github.com/springdoc/springdoc-openapi/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200439 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200439") to [dev](https://console.bluemix.net/apps/a80dcdf9-d860-4ce8-b4c3-4ee140ef7f7a?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


It won't work in production.


Good point. In the contracts proposal I think it is undefined if the two is not equivalent:
```
int f(int x) [[ensures r: r == x]]
{
  return ++x; // undefined behavior
}
```

Here, I assumed that the post conditions refers to the initial values.


The error message should be `'Type conversion for "{}" and "{}" is not implemented'.format(cf_attr_type, ax_attr_type)`.


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

* https://sharing.wrather.now.sh
* https://sharing-git-master.wrather.now.sh


xsbbsj


TeamCity Bvcms / Build [Build 1511](https://builds.tpsdb.com/viewLog.html?buildId=7288&buildTypeId=Bvcms_Build) is now running


fdfd


I guess if this passes, all of king_proximity can be removed as well.


IBM Cloud [toolchain](https://console.bluemix.net/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi](https://github.com/springdoc/springdoc-openapi/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200625 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200625") to [dev](https://console.bluemix.net/apps/1530d1fa-00ae-4b10-b035-13bfb4b99020?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


Probably name should be named `readCommits`.


It doesn't make any difference to the compiler, of course.  The only purpose for the names is documentation.  Use names if you think it will make the arguments' purpose more clear.


ZEIT Now cannot deploy this project to production due to following domain related issues:

 * alias `https://transform.tools` is an invalid domain. Correct it.


Hi Will,
So on O365 console I will add only the o365.mydomain. The mydomain.com will add only before the entire migration?


i honestly have no idea why this worked before


IBM Cloud [toolchain](https://console.bluemix.net/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi](https://github.com/springdoc/springdoc-openapi/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200817 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-200817") to [dev](https://console.bluemix.net/apps/a80dcdf9-d860-4ce8-b4c3-4ee140ef7f7a?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


Very suspicious code... `hasNext()` and multiple `next()` inside...


Successfully aliased the URL <https://my-portfolio-bhuglkibk.now.sh> to the following aliases:

* https://my-portfolio.mindfuljs.now.sh
* https://my-portfolio-git-master.mindfuljs.now.sh


> We could make the net module in the std library where SslContext comes from declare a empty SslContext if ssl isnt defined (maybe along with all other ssl types).

It already does that (or some other module does), otherwise how could httpclient define a procedure taking SslContext when ``-d:ssl`` isn't passed?


IBM Cloud [toolchain](https://console.bluemix.net/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi](https://github.com/springdoc/springdoc-openapi/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-201002 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190718-201002") to [dev](https://console.bluemix.net/apps/1530d1fa-00ae-4b10-b035-13bfb4b99020?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


![](https://github.trello.services/images/mini-trello-icon.png) [Desenvolver Controller para Usuarios](https://trello.com/c/5ZzgL6gj/20-desenvolver-controller-para-usuarios)


For future reference the appropriate semver version would be `1.8.0`. There should never be a `+1` release after the major version is `1`.

`0.major.feature+patch` or `major.feature.patch` are the 2 schemes depending on the leading `0`.


Of course, if an `if` statement fits on a single line then it should stay on a single line...


Great fix sir :rocket:


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

* https://ryan-ccn.now.sh
* https://blog.ryanccn.now.sh
* https://blog-git-master.ryanccn.now.sh


Actually just got this crash, interesting it never happened before


Lol I see, will fix


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

* https://nextjs.patricktanderson.now.sh
* https://nextjs-git-master.patricktanderson.now.sh


A


ru


En apprenant à créer un "pull request" (en corrigeant une nouvelle coquille) j'ai expérimenté la "comparaison" entre les différences dans le même fichier "readme-edits" avec le "update README.md"


Successfully aliased the URL <https://blog-3380kn1ii.now.sh> to the following aliases:

* https://ryan-ccn.now.sh
* https://blog.ryanccn.now.sh
* https://blog-git-master.ryanccn.now.sh


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

Created multidev environment [v0-14](https://dashboard.pantheon.io/sites/9dc3b9a0-4853-4dfd-b01f-6fe8cb0d08fd#v0-14) for rescue-x-comms.


Successfully aliased the URL <https://hello-next-e39onp66e.now.sh> to the following aliases:

* https://hello-next.sayhicoelho.now.sh
* https://hello-next-git-master.sayhicoelho.now.sh


TeamCity Bvcms / Build [Build 1511](https://builds.tpsdb.com/viewLog.html?buildId=7288&buildTypeId=Bvcms_Build) outcome was **SUCCESS**
Summary: Running Build time: 00:08:59


TeamCity Bvcms / Build [Build 1512](https://builds.tpsdb.com/viewLog.html?buildId=7289&buildTypeId=Bvcms_Build) is now running


Test passed!


removing old structure


![](https://github.trello.services/images/mini-trello-icon.png) [Desenvolver Controller para Categorias](https://trello.com/c/rLwtZlRI/21-desenvolver-controller-para-categorias)


: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:


I'm currently seeing if I can continue the work on the feature/1.13-update branch. But since it appears that you're overhauling a lot of the rendering, is it a better idea for me to work on something else?


>... phrase "avro type" refers ...

ok

`avro_typeId` (would be consistent with similar mappings in our RabbitMQ mappers).

 `avro_typeHint`

`avro_typeKey`

...

I issued the PR to choose the value in the toAvro transformer: https://github.com/spring-projects/spring-integration/pull/2991

(all with `recordKey` substituted per Artem's suggestion.


oshe todo un pro, pero aun puedes hacer la consulta mas pequeña


Successfully aliased the URL <https://enworld-twitterbot-5b3d9otus.now.sh> to the following aliases:

* https://enworld-twitterbot.now.sh
* https://enworld-twitterbot.wesbaker.now.sh
* https://enworld-twitterbot-git-master.wesbaker.now.sh


Successfully aliased the URL <https://tenkarstavern-twitterbot-4m1alu16b.now.sh> to the following aliases:

* https://tenkarstavern-twitterbot.now.sh
* https://tenkarstavern-twitterbot.wesbaker.now.sh
* https://tenkarstavern-twitterbot-git-master.wesbaker.now.sh


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

* https://solari.nicotudela.now.sh
* https://solari-git-master.nicotudela.now.sh


Esta parte elimina el usuario en sesion actual y evita que permanezca la sesion, a mi se me olvido actualiar esta parte


Successfully aliased the URL <https://vela-store-16fgv30r4.now.sh> to the following aliases:

* https://velabikes.com.br
* https://vela-store.velabikes1.now.sh
* https://vela-store-git-master.velabikes1.now.sh


The database feeder for The Scoop


If you remove actual implementation then this is not going to work.
That is protected[mock] def protectedMethod() without = ()


You should use only one format for naming
[https://github.com/airbnb/javascript#naming--camelCase](url)


I wrote what I mean in https://github.com/abo-abo/swiper/pull/2150


como baixo o amazmod-service-1893.apk?


I think it should be an `input type='radio'`
How do you get the value from the button?


Ignore les données venant de localhost


It's better to not use the database name in the queries fx just `SELECT * FROM users`. This way the database name is not hardcoded to "homework_lesson3".


TeamCity Bvcms / Build [Build 1512](https://builds.tpsdb.com/viewLog.html?buildId=7289&buildTypeId=Bvcms_Build) outcome was **SUCCESS**
Summary: Tests passed: 21 Build time: 00:12:55


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

Created multidev environment [v0-14](https://dashboard.pantheon.io/sites/39804e8f-253e-474e-82cf-725b36fddde0#v0-14) for rescue-x-base.


### lipsum
 this is a filler text


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

* https://nextjs2.danjonesdev.now.sh
* https://nextjs2-git-master.danjonesdev.now.sh


we are getting better


I honestly have no idea why they ever used strict equal `===`, if they could grasp the simplicity of `==`? (so no need to compare with string, but I guess it's minor, because things work after your change)


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

* https://solari.nicotudela.now.sh
* https://solari-git-master.nicotudela.now.sh


why you used spread operator here?


Created multidev environment [dpworkshop#pr-27](https://dashboard.pantheon.io/sites/154fb06c-ec2e-4aca-bdaa-64d2d054b4f8#pr-27).

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


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

* https://api.genhub.co
* https://api.genhub.now.sh
* https://api-git-master.genhub.now.sh


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

I updated the Github team because of this commit.

- @carlodri was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

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

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


is is


Successfully aliased the URL <https://docs-3qk9jv20u.zeit.sh> to the following aliases:

* https://docs.zeit.sh
* https://docs-git-master.zeit.sh


Gah, absolute positioning without relative-positioned parent always messes things up. Good to see it's fixed!


You could split the query into multiple lines so it's more readable.

Also as we talked about in class: It's unsafe to use the request values directly in the query like this. You should use escaping to avoid SQL injection vulnerabilities, ie. the ? placeholders. See: https://github.com/mysqljs/mysql#escaping-query-values


Successfully aliased the URL <https://vote-it-1ld62h7kg.now.sh> to the following aliases:

* https://vote-it.now.sh
* https://vote-it.eugrdn.now.sh
* https://vote-it-git-master.eugrdn.now.sh


I imagine this might be broken?


:+1:
Calling the function each time is not always the best decision, indeed.


Fix_7396_QtIFW_Windows (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2492 of 2492 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)


Why you use Boolean for variables `title genre search `?
if the variable has a string, you can just write an empty string
But not `false / true `


Still interested! Haven’t had time to work on that recently :-(
But we are planning to release the new version of our manual soon, and this will be super useful.
Will check it out sometime next week.

Thanks!!!

> On Jul 18, 2019, at 20:47, Vladimír Vondruš <notifications@github.com> wrote:
>
> Hi again, not sure if this is still relevant for you but as of mosra/m.css@63e8d47 there's support for up to 2048 results (with some restrictions, but you're unlikely to hit those as well). Cheers! :)
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


And disabled hardware acceleration to fix bitmaps crashing certain devices


Successfully aliased the URL <https://bricks-react-ssr-cy3j2aia9.now.sh> to the following aliases:

* https://bricks-react-ssr.jinmayamashita1.now.sh
* https://bricks-react-ssr-git-master.jinmayamashita1.now.sh


Don't understand this
You should submit a form on click


Screenshot of navigation bar:
![Screen Shot 2019-07-18 at 1 37 56 PM](https://user-images.githubusercontent.com/29050494/61490221-4a00d080-a961-11e9-872c-b5031c95bd6b.png)


Deployment failed with the following error:

~~~
The property `NPM_TOKEN` is not allowed in now.json when using Now 2.0 – please remove it.
~~~


looks good but you is there a reason you need `sudo` only for the 2nd setting?


# 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)|


Fix_7396_QtIFW_Windows (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)


@justindirose I don't think this should be here ;)


Fix_7396_QtIFW_Windows (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://bricks-react-ssr-esj856zg2.now.sh> to the following aliases:

* https://bricks-react-ssr.jinmayamashita1.now.sh
* https://bricks-react-ssr-git-master.jinmayamashita1.now.sh


You should read about proptypes


Successfully aliased the URL <https://demo-sync-moltin-to-shipengine-gdgbf0i6w.now.sh> to the following aliases:

* https://particular-sync-moltin-to-shipengine.now.sh
* https://demo-sync-moltin-to-shipengine.particular.now.sh
* https://demo-sync-moltin-to-shipengine-git-master.particular.now.sh


Successfully aliased the URL <https://bitcoin-cost-i0yelc46k.now.sh> to the following aliases:

* https://bitcoin-cost.brunopulis.now.sh
* https://bitcoin-cost-git-master.brunopulis.now.sh


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2863947)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/mmp_assembly_resolution_spam/e5ff15686c9c9cd0ef0bb7bd476393e316a3f3a3/2863947/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 (0x7ff957726380): 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 (0x7fc8c68e6050): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f838478a7a0): 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 (0x7fcce34a17b0): 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 (0x7fb846b9d590): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd9a5613a40): 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 (0x7fa30ae3e6a0): 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 (0x7f994b984690): 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 (0x7fec37793fd0): 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 (0x7fb41de0fb10): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb37e1d5100): 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 (0x7fdd642e2c80): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcf5c0a1050): 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 (0x7fd83322deb0): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd4ec4e51a0): 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 (0x7fceced10f40): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe5a6b1ad80): 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 (0x7ff1315d7310): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fba4c690b40): 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 (0x7fdc1f8ed970): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa4e70407b0): 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 (0x7fe7c228bf50): 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 (0x7fd977c68410): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f910f4508c0): 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 (0x7fbddf5a7490): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f962acb86e0): 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 (0x7faca3caa550): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcab1db0ed0): 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 (0x7f85755f57b0): 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 (0x7ffe7b2947a0): 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): Crashed
 * 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 (0x7fcd6960a110): 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 (0x7f916c3d6290): 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 (0x7fd2991e3df0): 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 (0x7fa6a14db9a0): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc6b5edbff0): 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 (0x7fe66cde49c0): 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 (0x7fd9080afdc0): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7feea2eb3b70): 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
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8d96976d30): 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 (0x7fbba0605c10): 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 (0x7fd698c86c00): 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
 * fsharp/iOS Unified 64-bits - device/Release: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc273988aa0): 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 (0x7fbcb42b9bd0): 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 (0x7f8dfd881330): 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 (0x7feae461d330): 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 (0x7ffa01c5e250): 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 (0x7fe7ac442eb0): 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 (0x7ff6d453a4d0): 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 (0x7fb4436d79c0): 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 (0x7fb3131bfc80): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f95654b40a0): 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 (0x7fe228589b10): 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 (0x7fcca1c75100): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fea9a047570): 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 (0x7f992b1b75d0): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fa64c61bdd0): 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 (0x7ff281b5b270): 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 (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9b47b26160): 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, profiling): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f962aa1fff0): 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 (0x7f9059914490): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7faa696d9b60): 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 (0x7fb9af618a00): 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
 * 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 (0x7fdb6d5538c0): 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 (0x7fe91b6cfe50): 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 (0x7fb99899f6d0): 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 (0x7fc71f43dfb0): 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 (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fcfddd99930): 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): Crashed
 * 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 (0x7fe5e2cca6a0): 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 (0x7feea62d52a0): 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
 * 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 (0x7fbcd0b9a390): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7faa0d4e0690): 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 (0x7ffe26472c40): 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 (0x7ff383c70420): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe3c5568c50): 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 (0x7fe9112f4500): 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 (0x7f8f1b649b30): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe010cda270): 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 (0x7ff70b8f8a40): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f8cfbfaf0c0): 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 (0x7fc0d8e26440): 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 (0x7fac32c4ee10): 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 (0x7ffcfbd88990): 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 (0x7f7f0c546860): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fd169535d50): 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 (0x7fbe81610b10): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fc196d2b970): 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 (0x7f8cf1c92000): 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 (0x7fe7dec85570): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f856abecfd0): 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 (0x7fc369d93d80): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fb831b69760): 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 (0x7ff3fadd6370): 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 (0x7fd4ba6c2160): 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 (0x7f81417137e0): 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 (0x7fe925588550): 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 (0x7ffac00bf660): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f81b18eb160): 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 (0x7fc8ce70aa40): 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 (0x7fa52fe31920): 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 (0x7fde502e7870): 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: Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7f9d094a3f90): 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 (0x7f9858b6a0a0): 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 (0x7fca195d8f10): 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): Crashed (HE0041: Error while processing device notifications from fff50:32:37:a1:c8:31fff (0x7fe5dae9b640): 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 (0x7fe4d2fb6270): 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 (0x7fe100665270): 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 (0x7f807c8498b0): Failed to communicate with the device. Please ensure the cable is properly connected, and try rebooting the device (error: 0xe8000065 kAMDMuxConnectError))
</details>


Why did you switch back to the info icon instead of dagger?


Successfully aliased the URL <https://bricks-react-ssr-g0l26j1mg.now.sh> to the following aliases:

* https://bricks-react-ssr.jinmayamashita1.now.sh
* https://bricks-react-ssr-git-master.jinmayamashita1.now.sh


So young. So filled with hope. :(


Do you really need these functions in the object ?


the same
read about the spread operator


.ipynb version


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

* https://apollo.mseale.now.sh
* https://apollo-git-master.mseale.now.sh


Successfully aliased the URL <https://bricks-react-ssr-h195xwxg0.now.sh> to the following aliases:

* https://bricks-react-ssr.jinmayamashita1.now.sh
* https://bricks-react-ssr-git-master.jinmayamashita1.now.sh


My last two years have been consumed with getting _Avro_, _MQTT_, and _Kafka_ to play well together with _spring-integration_ and _spring-cloud-stream_,  so at this point I am pretty experienced in and opinionated about those technologies.


Good


This may be the reason why we lost high energy photons. These events are likely to have 22=photon as mother.


develop (Myoldmopar) - 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.45%25-green.png)


We will definitely defer to your expertise; we just need to agree on the name 😄


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

* https://transform.tools
* https://transform.ritz078.now.sh
* https://transform-git-master.ritz078.now.sh


I don't think it's going to work for `lanker` and `peach`. Their `CSV` files follow a different format.


Deployment failed with the following error:

~~~
You defined 1 build that did not match any source files (please ensure they are NOT defined in .nowignore):
~~~


Yes App Store version installs Slack as `root` vs Homebrew or Direct Download.


Well I somehow thought, if the _name variable gets its value only on the level of species, but the getName function is defined up in the Animal class header, I need the virtuality to "get through" to it.
But I see now, that what matters is the level of the _name variable definition - and that getName doesn't have to work differently for the different species.

Thanks for the point!


They are the properties that should change in link.json.


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

* https://ricklouie.org
* https://portfolio.rvlouie.now.sh
* https://portfolio-git-master.rvlouie.now.sh


Thank you!


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

* https://simple-app.github-meteorhacks.now.sh
* https://simple-app-git-master.github-meteorhacks.now.sh


For example:
https://github.com/wsp-sag/network_wrangler/blob/786d617d75ae5f4d4d30e3b2044033feab380655/example/single/link.json#L26-L28


so, change properties could be defined either way in the project card?
LANES: [3, -1]
LANES: 2


Successfully aliased the URL <https://a-totally-new-one-9qew211kz.now.sh> to the following aliases:

* https://a-totally-new-one.github-meteorhacks.now.sh
* https://a-totally-new-one-git-master.github-meteorhacks.now.sh


Well, thanks for the explanation on the need of it. :)


Initialization of basic web app.


@djmitche :+1: ty


Created multidev environment [dpworkshop#pr-27](https://dashboard.pantheon.io/sites/154fb06c-ec2e-4aca-bdaa-64d2d054b4f8#pr-27).

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


Approved


Thanks for this resource hub.


👍
now, we need to add the example code and output to Settings.rst.


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

I updated the Github team because of this commit.

- @frodepedersen, @arnekr were added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

You should get push access to this feedstock and CI services.

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

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


Considerando que a parte que realmente é executada para compilação é só isso aqui, não seria melhor simplesmente "quebrar" esse arquivo em dois: um pra instalar as dependências do projeto e um apenas para compilar? Acho que ficaria mais rápido e mais organizado dessa forma.
@LBBassani


I believe the value range should remain 0-100 as with the ProgressBar - but internally you have a ValueConverter to translate into the angle.

Ideally, you would be able to swap a ProgressBar and ProgressRing, and existing code would just work.


There should be no calls to IO.inspect/1.


What is the motivation for introducing these synonyms?
There are already definitions `pubN_t` for public unsigned integers and these are in turn convertible to `FStar.UIntN.t`.


This is the commit when we decided to get rid of the kick, ban, info,  buttons.


IsIndeterminate could be set to True by default on the ProgressRing so it reduces any pain in moving projects to WinUI


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

* https://simple-app.github-meteorhacks.now.sh
* https://simple-app-git-master.github-meteorhacks.now.sh


Purposed at allowing variation


TeamCity Gribble ORM :: Deploy [Build 1.6.193.0](http://build.mikeobrien.net/viewLog.html?buildId=4054&buildTypeId=gribble&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 492, ignored: 2 Build time: 00:01:39


Deployment failed with the following error:

~~~
You defined 1 build that did not match any source files (please ensure they are NOT defined in .nowignore):
~~~


Além disso, dado que todas as distros listadas acima são literalmente os mesmos comandos, talvez fosse melhor remover esse arquivo que lida com a instalação completamente e simplesmente listar quais pacotes são necessários para a compilação (seriam as linhas que se repetem em todos os casos desse if aqui). Isso possibilitaria também que distros baseadas em Arch, que usam pacman ao invés do apt, instalassem as dependências manualmente, sem ter que editar esse arquivo aqui. Ficaria ainda mais simples de começar a trabalhar no projeto.
@LBBassani


Looks like I need to change my API key.


Another thing that I was curious about: should the _Avro_ classes not be in, at least, a dedicated package?

_JSON_ and _Kryo_ have their own packages it seems inconsistent to place _Avro_ classes under `org.springframework.integration.transformer;`.

I mentioned in my [comments](https://github.com/spring-cloud/spring-cloud-stream/issues/1767#issuecomment-512887696) regarding [spring-cloud-stream #1767](https://github.com/spring-cloud/spring-cloud-stream/issues/1767) that I thought a  _spring-integration-avro_ project or module (similar to _spring-integration-xml_) might be a good idea.

At a minimum I think it would be wise to mimic the package structure used in _spring-integration-xml_, even if the classes stay in -core. So I would suggest moving the avro transformer specific items to `org.springframework.integration.avro.transformer`.


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

Created multidev environment [p-master](https://dashboard.pantheon.io/sites/d1c0bbdc-f8cc-4693-bf9c-a0adb583cc0f#p-master) for ocad.


Successfully aliased the URL <https://node-fd-54znvvvu1.now.sh> to the following aliases:

* https://node-fd.willemliu.now.sh
* https://node-fd-git-master.willemliu.now.sh


Hi, Can I get your training datasets?


Again you should build the query without using the request parameters directly. You can do this by keeping an array of parameters for the query and using https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/push to add parameters when needed.


Successfully aliased the URL <https://docs-dqx6xmk32.zeit.sh> to the following aliases:

* https://docs.zeit.sh
* https://docs-git-master.zeit.sh


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

I updated the Github team because of this commit.

- @rabernat was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

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

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.10', Running XM tests on '10.12', Running XM tests on '10.11', Running XM tests on '10.9', Running XM tests on '10.13', Running XM tests on '10.13'' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2//console)
✅ Packages: [xamarin.ios-12.15.0.222.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/mmp_assembly_resolution_spam/e5ff15686c9c9cd0ef0bb7bd476393e316a3f3a3/2/package/xamarin.ios-12.15.0.222.pkg) [xamarin.mac-5.15.0.222.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/mmp_assembly_resolution_spam/e5ff15686c9c9cd0ef0bb7bd476393e316a3f3a3/2/package/xamarin.mac-5.15.0.222.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/mmp_assembly_resolution_spam/e5ff15686c9c9cd0ef0bb7bd476393e316a3f3a3/2/jenkins-results/api-diff/index.html)
🔥 [Failed to compare API and create generator diff](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2//console) 🔥
    ** Error: Working directory isn't clean:
    HEAD detached at e5ff1568
    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.
🔥 [Xamarin.Mac tests on 10.10 failed: Xamarin.Mac tests on macOS 10.10 failed (dontlink (system))](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.12 failed: Xamarin.Mac tests on macOS 10.12 failed (dontlink (system))](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.11 failed: Xamarin.Mac tests on macOS 10.11 failed (dontlink (system))](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.9 failed: Xamarin.Mac tests on macOS 10.9 failed (dontlink (system))](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.13 failed: Xamarin.Mac tests on macOS 10.13 failed (dontlink (system))](https://jenkins.internalx.com/job/macios/job/mmp_assembly_resolution_spam/2/display/redirect) 🔥
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/mmp_assembly_resolution_spam/e5ff15686c9c9cd0ef0bb7bd476393e316a3f3a3/2/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>24 tests failed, 147 tests passed.</summary>

## Failed tests

 * Xtro/Mac: Failed (Test run failed.)
 * [NUnit] Mono SystemCoreTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemNumericsTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemXmlTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemXmlLinqTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemComponentModelDataAnnotationsTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemJsonTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemServiceModelWebTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemIOCompressionTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemSecurityTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono MonoRuntimeTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemDataTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemNetHttpTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemServiceModelTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono CorlibTests/watchOS 32-bits - simulator/Debug: Crashed
 * [NUnit] Mono SystemWebServicesTests/watchOS 32-bits - simulator/Debug: Crashed
 * [xUnit] Mono SystemJsonXunit/watchOS 32-bits - simulator/Debug: Crashed
 * [xUnit] Mono SystemXunit/watchOS 32-bits - simulator/Debug: Crashed
 * [xUnit] Mono SystemNetHttpUnitTestsXunit/watchOS 32-bits - simulator/Debug: Crashed
 * monotouch-test/watchOS 32-bits - simulator/Debug (static registrar): Crashed
 * monotouch-test/watchOS 32-bits - simulator/Debug (all optimizations): Crashed
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
 * MSBuild tests/iOS: Failed (Execution failed with exit code 1)
</details>


Again use ? placeholders. Also you don't need the `LOWER()` since the matching is case insensitive


Acredito que uma simples nota no README.md explicando que é necessário instalar os pacotes `g++ cmake libxmu-dev libxi-dev protobuf-compiler libprotobuf-dev pkg-config (ou pkgconf)` funcionaria melhor do que ter um arquivo dedicado exclusivamente a isso. No pior dos casos, a gente poderia deixar um "install_dependencies.sh" que basicamente rodaria o apt no terminal, mas seria um bash que roda uma única linha de comando, então acho que talvez a remoção dessa parte do arquivo e a reestruturação para dentro do readme seja o caminho ideal a se tomar.


true


Successfully aliased the URL <https://vote-it-5m5zcbj5u.now.sh> to the following aliases:

* https://vote-it.now.sh
* https://vote-it.eugrdn.now.sh
* https://vote-it-git-master.eugrdn.now.sh


CSP-0050 Task


Yikes, sorry about that! Might be worth waiting until we merge https://github.com/malariagen/binder/pull/52 then upgrade vector-ops, as that will be a better environment build anyway.


No


Do u have that training datasets?


maybe event delefation?


Successfully aliased the URL <https://dupe-report-kvnj7y47o.now.sh> to the following aliases:

* https://artsy-dupe-report.now.sh
* https://dupe-report.artsy.now.sh
* https://dupe-report-git-master.artsy.now.sh


Successfully aliased the URL <https://scoop-docs-nm7q5vvbe.now.sh> to the following aliases:

* https://scoop-docs.now.sh
* https://scoop-docs.kidonng.now.sh
* https://scoop-docs-git-master.kidonng.now.sh


Please fix indentation.


Remember to always use ? placeholders for any values coming from the user. Please don't hesitate to ask questions if you are unsure of what i mean or need help implementing the changes :)