🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2934987)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/2934987/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: BuildFailure
 * framework-test/iOS Unified 64-bits - device/Debug: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Debug: Crashed
 * fsharp/iOS Unified 64-bits - device/Debug: Crashed
 * dont link/iOS Unified 64-bits - device/Debug: BuildFailure
 * link all/iOS Unified 64-bits - device/Debug: BuildFailure
 * link sdk/iOS Unified 64-bits - device/Debug: BuildFailure
 * mono-native-compat/iOS Unified 64-bits - device/Debug: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Debug: Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Debug: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Release: BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): BuildFailure
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): BuildFailure
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * 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
 * framework-test/iOS Unified 64-bits - device/Release: Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Release: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/Release: Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * dont link/iOS Unified 64-bits - device/Release: BuildFailure
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * link all/iOS Unified 64-bits - device/Release: BuildFailure
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * link sdk/iOS Unified 64-bits - device/Release: BuildFailure
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * 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
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * 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
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/Release: Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
</details>


Successfully aliased the URL <https://platforms-talk-gzarqpn5v.now.sh> to the following aliases:

* https://platforms-talk.bzelip1.now.sh
* https://platforms-talk-git-master.bzelip1.now.sh


I would prefer to `canManageProducts`. `canAccess*` is a new name which relates more to `view*` than `manage*`.


Solves #8


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

* https://blog.kaubosh.now.sh
* https://blog-git-master.kaubosh.now.sh


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


Nice!

Though also have to update it in `lib.rs`


Accepting the commit


Successfully aliased the URL <https://static-build-example-react-18ik67xph.now.sh> to the following aliases:

* https://static-build-example-react.moviedb.now.sh
* https://static-build-example-react-git-master.moviedb.now.sh


This is a single class called Scrabble() and then there are methods and the global variable inside it...?


Successfully aliased the URL <https://future-371k0g31u.now.sh> to the following aliases:

* https://future.dimitrykirpa.now.sh
* https://future-git-master.dimitrykirpa.now.sh


The original link was supposed to go to a page of the wiki containing information *about* configuration options (which has seemingly disappeared) - your replacement instead goes to the web-configurator itself.

A proper wiki page detailing the various configuration options for the Scrobbler, and what each does, really needs to be put up again, which this should then link to.


> You should have a single class Scrabble and all the data and functions modeled within it.

This is a single class called Scrabble() and then there are methods and the global variable inside it...?


@normanmaurer no, since eventFd is a counter we are "consuming" all the prior writes in one go. `eventWriteCount` is a count of _every_ write (of `1`) to the eventFd since the event loop was created.

It would be rare to go around this loop more than once (only when racing).


Now could not deploy this pull request since the `package.json` file contains a `now` configuration field.
The GitHub integration requires a `now.json` file which cannot be used in conjunction with a `package.json` file.

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

{
  "name": "ssc",
  "version": "1.0.0",
  "title": "Steady State Cycles • Pittsburgh, PA",
  "description": "A Pittsburgh cycling shop for top-tier road and mountain products and service. Now open at 1153 Old Freeport Rd.",
  "author": "James Acklin",
  "private": true,
  "scripts": {
    "dev": "nuxt",
    "build": "nuxt build",
    "start": "nuxt start",
    "generate": "nuxt generate",
    "lint": "eslint --ext .js,.vue --ignore-path .gitignore .",
    "precommit": "npm run lint",
    "now-build": "nuxt generate"
  },
  "now": {
    "name": "steadystatecycles",
    "alias": [
      "steadystatecycles.com",
      "www.steadystatecycles.com"
    ],
    "static": {
      "cleanUrls": true
    }
  },
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.17",
    "@fortawesome/free-solid-svg-icons": "^5.8.1",
    "@fortawesome/vue-fontawesome": "^0.1.6",
    "@nuxtjs/axios": "^5.4.1",
    "cross-env": "^5.2.0",
    "mapbox-gl": "^0.48.0",
    "mapbox-gl-vue": "^1.9.0",
    "nuxt": "^2.6.3",
    "tachyons": "^4.11.1",
    "vue-lazyload": "^1.2.6"
  },
  "devDependencies": {
    "@nuxt/webpack": "^2.6.3",
    "acorn": "^6.1.1",
    "acorn-dynamic-import": "^4.0.0",
    "babel-eslint": "^8.2.1",
    "eslint": "^5.16.0",
    "eslint-config-prettier": "^3.6.0",
    "eslint-loader": "^2.1.2",
    "eslint-plugin-prettier": "2.6.2",
    "eslint-plugin-vue": "^4.0.0",
    "image-webpack-loader": "^4.6.0",
    "nodemon": "^1.18.11",
    "prettier": "1.14.3",
    "webpack": "^4.30.0"
  }
}

Migrate any configuration from package.json into now.json and remove the now field from the package.json.


This should probably be a class constant. Also, why multiply by 2? Hyper threading or something?


@joeldenning, I believe the regular expression for matching patient-dashboard in the activity function is different than the pattern used previously. In this PR, the regex is /^patient\/.+\/dashboard/ (line25) . This would match something like: /patientUUIDdashboard. I believe this regex should be: /^patient-dashboard\/.+/ which would match /patient-dashboard/UUID


Great, now 16 people can scream at each other at once!


Fix indent


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

* https://carlo-clamucha.me
* https://portfolio-site.carloclamucha.now.sh
* https://portfolio-site-git-master.carloclamucha.now.sh


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

* https://garitma.com
* https://garitma.garitma.now.sh
* https://garitma-git-master.garitma.now.sh


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


**Perfecto**, los cambios funcionaron :+1:


ScheduleManagerRefactor (Myoldmopar) - x86_64-MacOS-10.13-clang: OK (2480 of 2494 tests passed, 642 test warnings)

Messages:\n
 * 644 tests had: AUD diffs.
 * 3 tests had: EIO diffs.
 * 2 tests had: ESO big diffs.
 * 2 tests had: MTR big diffs.
 * 2 tests had: Table big diffs.
 * 2 tests had: ERR diffs.
 * 1 test had: MTD diffs.
 * 1 test had: RDD diffs.

Failures:\n

integration Test Summary
 * Passed: 654
 * Failed: 12

regression Test Summary
 * Passed: 662
 * Failed: 2

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


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


![](https://github.trello.services/images/mini-trello-icon.png) [Create MongoDB Connection struct](https://trello.com/c/13TpBAAv/4-create-mongodb-connection-struct)


Was this tested?


This whole block should be commented out or we'll trigger a bunch of builds we don't want.


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

* https://tylerfreeman.dev
* https://dev.tylerfreeman.dev
* https://stage.tylerfreeman.dev
* https://next-9.tylerfrmn5.now.sh
* https://next-9-git-master.tylerfrmn5.now.sh


ttwgfdsd


For testing purposes, we should limit this to 'leap15'


![](https://github.trello.services/images/mini-trello-icon.png) [Create Visit model](https://trello.com/c/CiAcNqZC/5-create-visit-model)


What kind of error did u get? Maybe try deleting the old model weights folder.


![](https://github.trello.services/images/mini-trello-icon.png) [Create controller for campaigns](https://trello.com/c/txuzU81k/6-create-controller-for-campaigns)


![](https://github.trello.services/images/mini-trello-icon.png) [Write a README](https://trello.com/c/Qjm3HZP7/14-write-a-readme)


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 10e8a68860c522e8faa946e92aa9ad94969ff3e3.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 109104c60d60f2980c463659a1d7cf470768b04c.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


Hmmm this didn't work well.... *marked* issue perhaps or maybe just tables.


Fixes #251.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 74ca9c9707cae5a8a1349fae22fc550317c1b17a.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


This is good. Randomization ensures that race conditions aren’t biased. It looks like the evaluation result would be the same if traverse and parTraverse_ were swapped, but that should be verified.


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/3afe3af2-c7d2-4b47-94bd-885d23c3937a?env_id=ibm%3Ayp%3Aeu-de "springdoc-openapi-v3 -rest-test"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/737cd688-45b8-4311-a292-a111823c3fb8 "springdoc-openapi-v3-rest-test-pipeline") deployed [springdoc-openapi-demos](https://github.com/springdoc/springdoc-openapi-demos/releases/tag/deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190812-172530 "deploy-ibm-yp-eu-de-BNPP_BDDF_IT-dev-20190812-172530") to [dev](https://console.bluemix.net/apps/ed6a1c5e-0796-49c7-895a-78108b3eb43a?env_id=ibm:yp:eu-de "ibm:yp:eu-de:BNPP_BDDF_IT:dev"), including this commit


no a comma xD


Nope... not this either. Hmmm. Ah well... later.


QuickSort


reorder-window-struct (mjwitte) - 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)


maybe just set only item 'leap15' in AVAILABLE_DIST?


[Percentage](https://github.com/dead-hosts/hosts_facebook0_git_kowith337/blob/e3b32322bce4fb29eac152db175e4fc728e8c11c/output/logs/percentage/percentage.txt) report seems to be clear for the hosts entry that was pulled out from test were deleted, all duplicated test units seems disappear.

However, due to I've change my mobile device and having some catch to local `Free Basics` servers (Thanks to [personalDNSFilter](https://github.com/IngoZenz/personaldnsfilter) app that can do DNS change + hosts block + domain logging), I think I will re-add some hosts to test soon...


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


reorder-window-struct (mjwitte) - 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)


Of course!! How could I have been so stupid. I received the NullPointerException because i wasn't connected to the INTERNET. Make sure your android device is connected via mobile data or Wifi and also make sure to include an 'if' statement  within the onPostExecute block that displays a toast message or dialog that displays something like 'Check your internet connection' when the parameter is equals to null... Like this 'if(param == null)'.

Thank you @Abokorhassan.


Successfully aliased the URL <https://complemarta-318g7yq1p.now.sh> to the following aliases:

* https://complemarta.trebh.now.sh
* https://complemarta-git-master.trebh.now.sh


place the word "do" in that sentence.


Hmm, I guess what I meant is, why do you need a template here? Is there something you're doing that applicable to other Kubeapps installations so we can modify the upstream Kubeapps chart here to support it, or is there another way you can achieve the change you need?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 8d02e8ccd23702ea7dd318ed33d42d288f959ad6.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


That sounds right


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 324095a1e944cd27b0ecdac8d225d908ad7b32e1.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


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

* https://einscape.jeffreymendez1993.now.sh
* https://einscape-git-master.jeffreymendez1993.now.sh


Ketika dihadapkan pada pertanyaan *“Mana yang sebaiknya dipilih, menegakkan kebenaran secara mutlak atau menjaga kestabilan suasana?”* .Pendapat subjektif saya adalah pilihan yang kedua.

Karena dalam kebanyakan persoalan yang disebut kebenaran, tidak sama dengan menunjuk angka pada tabel bilangan biner. Saya berpendapat bahwa kebenaran adalah sesuatu yang cukup kita upayakan untuk didekati, bukan dicapai. Karena dalam situasi tertentu memang tidak bisa dicapai. Pada teori numerik, ada istilah perkiraan atau aproksimasi. Misalnya untuk mencari nilai luas lingkaran ternyata cukup menggunakan nilai 3.14 sebagai nilai phi, bukan 3,142857143.
Artinya hasil perhitungannya tidak sesuai dengan keadaan aslinya, karena pasti selisih sekian di belakang koma. Maksud saya, meskipun hasilnya bukanlah kebenaran, melainkan hanya mendekati saja itu cukup.
Anehnya, dalam banyak buku pelajaran di sekolah hasil hitung luas lingkaran yang nilai phi nya 3.14 malah menggunakan tanda equivalen (tanda sama dengan). Meskipun ini tidak tepat. Tidak ada yang mempermasalahkan ini. Jadi, kebenaran dalam matematika pun tidak eksak.

Misalnya kita sedang bertamu ke rumah teman non-muslim, lalu disuguhi segelas arak. Tentu, dengan bahasa sesopan mungkin, kita harus menjelaskan bahwa itu haram bagi muslim. Karena haramnya minuman arak itu eksak. Dan dengan penjelasan yang baik, tentu pemilik rumah tidak akan keberatan menerimanya.

Tetapi, misalnya saya menyaksikan teman sekolah saya merokok di area sekolah. Seharusnya saya berkewajiban melaporkannya kepada guru BK dan nilainya bakal otomatis jelek. Tapi kenyataannya,hati saya mengingkari itu. Kebenaran yg saya yakini kok tidak demikian. Saya malah berupaya menutupi kelakuan buruknya sembari menasehatinya pelan-pelan. Pilihan sikap seperti ini, sangat abu-abu. Meskipun, ketika ada siswa lain yang dengan segera melaporkan kejadian tersebut kepada guru adalah pilihan benar juga. Tapi, sebagaimana fungsi pembulatan adalah menyederhanakan angka. Maka menjaga kestabilan suasana juga bertujuan menghindari situasi yang lebih rumit tak terjadi.

Lalu, sebenarnya mana yang paling benar, diantara menegakkan kebenaran secara mutlak atau sebaiknya menjaga kestabilan suasana saja?. Kebenaran itu tidak eksak.
>Misalnya, hasil dari **5/ 3 = 1.66666666667**.

>Namun, **1.66666666667** * **3 = 5.00000000001**.

 Nah, kan tidak eksak. Artinya dalam beberapa situasi perhitungan matematika sebaiknya dicukupkan pada aproksimasi saja, karena equivalen memang tidak bisa dicapai.


エラーが発生しているようです。
こちらの問題は回答の途中でしょうか？


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 22de58239371ddf5376fcc1bbf32f50999ac933a.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


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

# Test results

<details>
<summary>10 tests failed, 103 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: TimedOut
 * [xUnit] Mono BCL tests group 3/tvOS - device/Debug: TimedOut
 * [xUnit] Mono BCL tests group 6/tvOS - device/Debug: TimedOut
 * monotouch-test/tvOS - device/Debug (interpreter): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Release: TimedOut
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): TimedOut
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): TimedOut
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug): TimedOut
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): TimedOut
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (release): TimedOut
</details>


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 50616e4464b3a6d2ba1a5d81a1eaf28fe84af584.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 8d050ceb51213890f3b6575f4e7ad95835b55a63.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


In future, it may behoove us to separate version bumps / cutting releases from feature changes. It would allow for reverts of features without affecting or introducing extra accounting for previously released versions of the playbook library.


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


AFAIK the order of the indices doesn’t matter. All that matters is that they're unique. In that case, I prefer the implementation in the previous commit with fewer lines 😛


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 75489dfed066e5f5a5faf570c16f81dc3ad07027.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


The following doc(s) have been deployed to the [4778fastve](https://4778fastve-static-docs.pantheonsite.io/docs) Multidev environment:
- [source/content/modules-plugins-known-issues.md](https://github.com/pantheon-systems/documentation/commit/8e7a77e2f2fca63766993c0bfabec206cff7df02/source/content/modules-plugins-known-issues.md)


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 7ea9211b352e627f4056b29a8fdc12513f8db4ba.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


Successfully aliased the URL <https://einscape-2mnh9it2j.now.sh> to the following aliases:

* https://einscape.jeffreymendez1993.now.sh
* https://einscape-git-master.jeffreymendez1993.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 03267f6b01e7886ecfe6d2658d8d51e64692c3d3.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


![](https://github.trello.services/images/mini-trello-icon.png) [Ignore visits with repeated ID](https://trello.com/c/NhTTTCsO/16-ignore-visits-with-repeated-id)


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 2b1afcdf7432b83b681185a319e5474b3c562cba.

You can try again later or [upgrade](https://zeit.co/teams/debtcollective/settings/plan) your plan.


It should have been in the form of
```axios.post(url[, data[, config]])```


Fixes #133


Using `STATE_OFF` instead of `STATE_STANDBY` will remove attributes when the tv is "off", so you'll lose the source_list attribute unnecessarily.


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

# Test results

<details>
<summary>70 tests failed, 43 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: BuildFailure
 * framework-test/tvOS - device/Debug: BuildFailure
 * interdependent-binding-projects/tvOS - device/Debug: BuildFailure
 * fsharp/tvOS - device/Debug: BuildFailure
 * dont link/tvOS - device/Debug: BuildFailure
 * link all/tvOS - device/Debug: BuildFailure
 * link sdk/tvOS - device/Debug: BuildFailure
 * mono-native-compat/tvOS - device/Debug: BuildFailure
 * mono-native-unified/tvOS - device/Debug: BuildFailure
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * monotouch-test/tvOS - device/Release: BuildFailure
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * monotouch-test/tvOS - device/Debug (dynamic registrar): BuildFailure
 * monotouch-test/tvOS - device/Release (all optimizations): BuildFailure
 * monotouch-test/tvOS - device/Debug (all optimizations): BuildFailure
 * monotouch-test/tvOS - device/Debug: SGenConc: BuildFailure
 * monotouch-test/tvOS - device/Debug (interpreter): BuildFailure
 * monotouch-test/tvOS - device/Debug (interpreter -mscorlib): BuildFailure
 * monotouch-test/tvOS - device/Release (interpreter -mscorlib): BuildFailure
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * framework-test/tvOS - device/Release: BuildFailure
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * interdependent-binding-projects/tvOS - device/Release: BuildFailure
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * fsharp/tvOS - device/Release: BuildFailure
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * dont link/tvOS - device/Release: BuildFailure
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * link all/tvOS - device/Release: BuildFailure
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * link sdk/tvOS - device/Release: BuildFailure
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * mono-native-compat/tvOS - device/Release: BuildFailure
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * mono-native-unified/tvOS - device/Release: BuildFailure
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
</details>


Successfully aliased the URL <https://vega-editor-backend-iq66knpsk.now.sh> to the following aliases:

* https://vega.now.sh
* https://vega-editor-backend.domoritz.now.sh
* https://vega-editor-backend-git-master.domoritz.now.sh


No, currently only in an internal preview.


Wow I could see this causing an issue on bigger shards!


Successfully aliased the URL <https://cover-image-generator-389sg9qk2.now.sh> to the following aliases:

* https://cover-image-generator.pjijin1.now.sh
* https://cover-image-generator-git-master.pjijin1.now.sh


Looking into it


this is actually odd :)


Нужно сначала показать вагоны

Исправь пункты главного меню


this line actually odd and for my debug purposes only :)


This file doesn't exist


This could fit on a single line, no?


single line


Probably also need `IOError` here, and same in `outputcat`


Looks OK to me :-)

```
$ time md5sum /tmp/1GB
af60e1b318ab83bad0626076abc8d551  /tmp/1GB

real	0m1.964s
user	0m1.753s
sys	0m0.204s

$ time rclone md5sum /tmp/1GB
af60e1b318ab83bad0626076abc8d551  1GB

real	0m1.976s
user	0m1.719s
sys	0m0.264s
```


Yeah, the hackathon was just throwing something together. I prefer `/patient/:uuid/dashboard` because it establishes the pattern of `/patient/:uuid/other-things`


Successfully aliased the URL <https://vega-editor-backend-i5fsfabsu.now.sh> to the following aliases:

* https://vega.now.sh
* https://vega-editor-backend.domoritz.now.sh
* https://vega-editor-backend-git-master.domoritz.now.sh


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

* https://complemarta.trebh.now.sh
* https://complemarta-git-master.trebh.now.sh


Successfully aliased the URL <https://vega-editor-backend-7by6xon8t.now.sh> to the following aliases:

* https://vega.now.sh
* https://vega-editor-backend.domoritz.now.sh
* https://vega-editor-backend-git-master.domoritz.now.sh


develop (Nigusse) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (668 of 668 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)


Get rid of the exception here as there isn't one. Just print the message that no default path is defined


Successfully aliased the URL <https://awesome-templates-jqq0t4004.now.sh> to the following aliases:

* https://pszx.tech
* https://awesome-templates.pszx.tech
* https://awesome-templates.pablosz.now.sh
* https://awesome-templates-git-master.pablosz.now.sh


Idem: get rid of exception


TeamCity Bvcms / Build [Build 1693](https://builds.tpsdb.com/viewLog.html?buildId=7685&buildTypeId=Bvcms_Build) outcome was **SUCCESS**
Summary: Tests passed: 62 Build time: 00:17:40


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


Danke @schuer - ich habe es vorhin nicht mehr geschafft


Looks good to me


Close #40, #48, #47, #43, #42, #19


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


TeamCity Bvcms / Build [Build 1694](https://builds.tpsdb.com/viewLog.html?buildId=7686&buildTypeId=Bvcms_Build) outcome was **UNKNOWN**
Summary: Canceled (Error while applying patch; cannot find commit bad0b755572d8ca4d624fae68e79dcf3d3479898 in the https://bvcms-teamcity@github.com/bvcms/bvcms repository, possible reason: refs/pull/600/merge branch was updated and the commit selected for the... Build time: 00:00:24


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


TeamCity Bvcms / Build [Build 1695](https://builds.tpsdb.com/viewLog.html?buildId=7687&buildTypeId=Bvcms_Build) outcome was **UNKNOWN**
Summary: Canceled (Error while applying patch; cannot find commit 6b9ebb92d5dc5a73bc67fd7c7298d81755345c5b in the https://bvcms-teamcity@github.com/bvcms/bvcms repository, possible reason: refs/pull/601/merge branch was updated and the commit selected for the... Build time: 00:00:08


yup, will move now


Что-то или опечатки, или ошибки:

- `^` - пишется один раз в самом начале
- `(((\d{3}))|(\s?\d{3}\s?))?` - скобки теперь совсем не поддерживаются
- `(\s|-)?\d{3}-?\d{2}-?\d{2}` - стало лучше, но подумай над тем, как ограничить формат так, чтобы либо были дефисы, либо их не было совсем после второй группы из трёх цифр (категория "Можно лучше")
- Можно лучше: хорошо бы учесть, что после `+7` / `8` **может** быть пробел, вне зависимости от наличия скобок. Тоже самое после закрывающей скобки, только там может быть или пробел, или дефис.

Можно лучше - сейчас в регулярке слишком много ненужных групп. Исправив опечатки (или ошибки?) и упростив, получим следующее:

`^(?:\+7|8)\s?(\d{3}|\s?\d{3}\s?)?[\s-]?\d{3}-?\d{2}-?\d{2}$`

- `(?:\+7|8)` - `(?:<pattern>)` - так называемая non-capturing group. Можно использовать для объединения последовательности, но в списке групп не будет значится.
- `[\s-]?` - тоже самое, что и `(\s|-)?`, только проще и симпатичнее.


Do you mean in the code or in the output? Probably both.


давай вынесем это в отдельный компонент


I'm pretty sure the generated inputs requirement isn't showing up in the trace table because it doesn't show up in `concIns`, the list of `ConceptInstance` that is used for two fields of `SystemInformation`: `_sysinfodb` and `refdb`. I'm not sure how to best approach this - should the requirement be built again everywhere for the traceability matrices, or should `consIns` use a constructor that also adds the inputs requirement? This would require that it always be used in conjunction with `FReqsSub`, the constructor for generating the inputs requirements, which is probably a bad idea. Any thoughts? @JacquesCarette @Mornix


I have added my name and other details as mentioned in the practice question


@pexcn 忘记了。


Now you'll get link errors when building libtess.dll


Давай вынесем этот кусочек в отдельную функцию

`const renderModal = (modal) => {
  if (!modal) {
   return null;
  }

  return // modalCode
 }`


yes, definitely in code. In output, if you are only printing the exception message then you can also do with a single line. Unless you want to print the traceback, but I wouldn;t


This implementation of Anxiety is actually outdated. Find the latest source here:

https://github.com/tytydraco/kernel_oneplus_guacamole/commits/pie/block/anxiety-iosched.c


`[\w\.-]*@` - перед `@` не может быть точки или дефиса - нужно исправить
`@\w*[a-zA-Z0-9]{1}` - можно лучше: `@\w+`
`\.\w*[a-zA-Z0-9]{1}` - можно лучше: `\.\w{2,5}` - не уверен, насколько длинным может быть домен. Надо читать спеку


I have a working betting system, for this I need data from oddsportal. How can I write you in a personal message?


@SGSSGene This cost us 2 days debugging! ;)


Хук довольно абстрактный может он понадобится где-нибудь еще? Вынесем?


> It looks like `SizeOnly` and `IgnoreChecksum` could be a single flag.

--ignore-checksum does something subtly different - it stops rclone checking the hashes after you upload/download  a file.  You normally want to check the hashes if you care about data integrity, even when using --size-only

So looking at that code makes me think that it is wrong since it disables calculating hashes for `--size-only` .
 It isn't a correctness issue - we'll still calculate the hashes but it will involve reading the file again.

So I think your intuition that there is something funny about that line is good - well spotted!


ah the 'as' is a pity.  Hope the language will improve that in the future :)


Successfully aliased the URL <https://awesome-templates-6afpar6e5.now.sh> to the following aliases:

* https://pszx.tech
* https://awesome-templates.pszx.tech
* https://awesome-templates.pablosz.now.sh
* https://awesome-templates-git-master.pablosz.now.sh


Чтобы не было хаоса с иконками давай создадим один компонет например `<Icon icon={ iconName } />`, в который ты будешь передавать название иконки, а он внутри по свитчу будет рендерить нужную


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 since it's in a migration this should be done in SQL. cc @ZogStriP


I think I found a better workaround for this.
By modifying the Facade.Expiration set:

> public DateTime Expiration
        {
            get => Message.Properties?.AbsoluteExpiryTime ?? syntheticExpiration;
            set
            {
                if (value != default)
                {
                    LazyCreateProperties();
                    Message.Properties.AbsoluteExpiryTime = value;
                }
                else if (Message.Properties != null)
                {
                    DateTime d = default;
                    Message.Properties.AbsoluteExpiryTime = new DateTime(d.Ticks, DateTimeKind.Utc);
                }
            }
        }

converting the default value of the to DateTimeKind.Utc seems to avoid the time shift of 5 hours that I read from the received message. This allows Message.IsExpired to to not return true as the DateTime.MinValue is ignored by that check. The AbsoluteExpiryTime message is still on the wire but the provider no longer treats the message as expired. This may cause issue with brokers/(other clients) that look at that field however that might be better then leaving the old value from a previous send.
Up to you @Havret.


- `([\w-]*\.){1,}` - можно проще: (group)+
- IP теперь можно, но попробуй учесть доступный диапазон. Сейчас можно так: `https://999.999.999.999` (необязательно)

В целом всё ок, зачту.


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.11', Running XM tests on '10.10', Running XM tests on '10.12', 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/mag%252Fmaster/3//console)
✅ Packages: [xamarin.ios-12.15.0.285.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/package/xamarin.ios-12.15.0.285.pkg) [xamarin.mac-5.15.0.285.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/package/xamarin.mac-5.15.0.285.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/jenkins-results/api-diff/index.html)
✅ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/jenkins-results/apicomparison/api-diff.html) (no change)
✅ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/jenkins-results/generator-diff/index.html) (no change)
🔥 [Xamarin.Mac tests on 10.11 failed: script returned exit code 1](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.10 failed: script returned exit code 1](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.12 failed: script returned exit code 1](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.9 failed: script returned exit code 1](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) 🔥
🔥 [Xamarin.Mac tests on 10.13 failed: script returned exit code 1](https://jenkins.internalx.com/job/macios/job/mag%252Fmaster/3/display/redirect) 🔥
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/mag/master/56cc5afb312e1bcdccc956c4b06954431617ea8c/3/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>55 tests failed, 116 tests passed.</summary>

## Failed tests

 * monotouch-test/iOS Unified 32-bits - simulator/Debug: BuildFailure
 * dont link/iOS Unified 32-bits - simulator/Debug: BuildFailure
 * dont link/iOS Unified 32-bits - simulator/Release: BuildFailure
 * link all/iOS Unified 32-bits - simulator/Debug: BuildFailure
 * link all/iOS Unified 32-bits - simulator/Release: BuildFailure
 * link sdk/iOS Unified 32-bits - simulator/Debug: BuildFailure
 * link sdk/iOS Unified 32-bits - simulator/Release: BuildFailure
 * monotouch-test/iOS Unified 32-bits - simulator/Debug (LinkSdk): BuildFailure
 * monotouch-test/iOS Unified 32-bits - simulator/Debug (static registrar): BuildFailure
 * monotouch-test/iOS Unified 32-bits - simulator/Release (all optimizations): BuildFailure
 * monotouch-test/iOS Unified 32-bits - simulator/Debug (all optimizations): BuildFailure
 * monotouch-test/iOS Unified 64-bits - simulator/Debug: BuildFailure
 * dont link/iOS Unified 64-bits - simulator/Debug: BuildFailure
 * dont link/iOS Unified 64-bits - simulator/Release: BuildFailure
 * link all/iOS Unified 64-bits - simulator/Debug: BuildFailure
 * link all/iOS Unified 64-bits - simulator/Release: BuildFailure
 * link sdk/iOS Unified 64-bits - simulator/Debug: BuildFailure
 * link sdk/iOS Unified 64-bits - simulator/Release: BuildFailure
 * monotouch-test/iOS Unified 64-bits - simulator/Debug (LinkSdk): BuildFailure
 * monotouch-test/iOS Unified 64-bits - simulator/Debug (static registrar): BuildFailure
 * monotouch-test/iOS Unified 64-bits - simulator/Release (all optimizations): BuildFailure
 * monotouch-test/iOS Unified 64-bits - simulator/Debug (all optimizations): BuildFailure
 * monotouch-test/tvOS - simulator/Debug: BuildFailure
 * framework-test/tvOS - simulator/Debug: BuildFailure
 * interdependent-binding-projects/tvOS - simulator/Debug: BuildFailure
 * fsharp/tvOS - simulator/Debug: BuildFailure
 * introspection/tvOS - simulator/Debug: BuildFailure
 * dont link/tvOS - simulator/Debug: BuildFailure
 * dont link/tvOS - simulator/Release: BuildFailure
 * link all/tvOS - simulator/Debug: BuildFailure
 * link all/tvOS - simulator/Release: BuildFailure
 * link sdk/tvOS - simulator/Debug: BuildFailure
 * link sdk/tvOS - simulator/Release: BuildFailure
 * mono-native-compat/tvOS - simulator/Debug: BuildFailure
 * mono-native-unified/tvOS - simulator/Debug: BuildFailure
 * monotouch-test/tvOS - simulator/Debug (LinkSdk): BuildFailure
 * monotouch-test/tvOS - simulator/Debug (static registrar): BuildFailure
 * monotouch-test/tvOS - simulator/Release (all optimizations): BuildFailure
 * monotouch-test/tvOS - simulator/Debug (all optimizations): BuildFailure
 * monotouch-test/watchOS 32-bits - simulator/Debug: BuildFailure
 * dont link/watchOS 32-bits - simulator/Debug: BuildFailure
 * dont link/watchOS 32-bits - simulator/Release: BuildFailure
 * link all/watchOS 32-bits - simulator/Debug: BuildFailure
 * link all/watchOS 32-bits - simulator/Release: BuildFailure
 * link sdk/watchOS 32-bits - simulator/Debug: BuildFailure
 * link sdk/watchOS 32-bits - simulator/Release: BuildFailure
 * [NUnit] Mono SystemWebServicesTests/watchOS 32-bits - simulator/Debug: Crashed
 * monotouch-test/watchOS 32-bits - simulator/Debug (LinkSdk): BuildFailure
 * monotouch-test/watchOS 32-bits - simulator/Debug (static registrar): BuildFailure
 * monotouch-test/watchOS 32-bits - simulator/Release (all optimizations): BuildFailure
 * monotouch-test/watchOS 32-bits - simulator/Debug (all optimizations): BuildFailure
 * introspection/tvOS - simulator/Debug (tvOS 9.0): BuildFailure
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
 * MSBuild tests/iOS: Failed (Execution failed with exit code 21)
 * MTouch tests/NUnit: Failed (Execution failed with exit code 13)
</details>


Here should be ClInclude tag
Fixed


reorder-window-struct (mjwitte) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2499 of 2499 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)


1:45380
2:31879950
3:129882384
4:8509810
5:6368084
6:


Теперь формой могут пользоваться только люди с именем в 20 символов


Thank you very much @hvlad !!


Este es mi villano favorito


o


Why not just an anonym closure function inside usort, like the previous yii style:

    function($a,$b){if($a[0]==$b[0]) {return 0;} return ($a[0]<$b[0]) ? 1 : -1;}


Entiendo porque agregaste a Deadshot


please use significant and well descriptive commit messages !!!!!! #swag


@bpasero Is `configuration` meant for `settings` and `userData` is super set


-20のスコアが上の


`\+?(7|8)` - +8 не корректно в данном случае - нужно исправить
`d+` - вообще не вариант. Номер `89259009090123123123123123123123123123` считается корректным
C дефисами тоже беда: `88005553-5-3-5`


Output:

Enter the five digits number
12391
New number obtained by adding one to each of its entered five 12391 digits is below
23402


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

* https://edm00secodes.edm00se.now.sh
* https://edm00secodes-git-source.edm00se.now.sh


Successfully aliased the URL <https://dotgov-components-mk9rvxflk.now.sh> to the following aliases:

* https://dotgov-components.martypowell.now.sh
* https://dotgov-components-git-integration.martypowell.now.sh


Diagrama


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

* https://edm00secodes.edm00se.now.sh
* https://edm00secodes-git-source.edm00se.now.sh


TeamCity Bvcms / Build [Build 1696](https://builds.tpsdb.com/viewLog.html?buildId=7688&buildTypeId=Bvcms_Build) outcome was **SUCCESS**
Summary: Tests passed: 64 Build time: 00:18:04


`(\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})?` - во первых, можно проще: `(\d{1,3}\.){3}\d{1,3}`, во вторых `?` здесь некорректно, ибо позволяет: `https://127.0.0.1yandex.ru`
Порт сломался: `https://localhost.ru:8080`


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


Thanks for renaming these, Alex -  "frdr:geospatial": "geolocation", "datacite:resourceTypeGeneral": "resourceType"