1. Assets/e-Assets/Scripts/R_handTrigger.cs can most likely be deleted
2. Refer to the [TDD ](https://github.com/emanisgrand/RPS-Wrestling/wiki/TDD) for state handling


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

* https://cameronwestland.com
* https://cameronwestlandcom.cameronwestland.now.sh
* https://cameronwestlandcom-git-master.cameronwestland.now.sh


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1127 of 1127 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.41%25-green.png)


Collaborator: Review for this commit was created. [Link to review](http://tests-a.collabdevteam.net:8080/ui#review:id=284)


Collaborator: Review for this commit was created. [Link to review](http://tests-a.collabdevteam.net:8080/ui#review:id=286)


This (and the former) version has not been published via PyPI: https://pypi.org/project/fastcov/#history


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)


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)


@dutchTender @serra-trinh @JackieBabos for integration


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

* https://blog.suddjian.com
* https://suddjian-blog.suddjian.now.sh
* https://suddjian-blog-git-master.suddjian.now.sh


## フォームフィールド

~~~py
    class Meta:
        model = User
        fields = ("username",)
        field_classes = {'username': UsernameField}
~~~

~~~py
In [10]: UserCreationForm().fields
Out[10]:
OrderedDict([(u'username',
              <django.contrib.auth.forms.UsernameField at 0x7f236c0d4210>),
             ('password1', <django.forms.fields.CharField at 0x7f236c0d42d0>),
             ('password2', <django.forms.fields.CharField at 0x7f236c0d43d0>)])
~~~


also fix grdnstrmg


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

* https://callumflackdesign.callum.now.sh
* https://callumflackdesign-git-master.callum.now.sh


+ 7308 is bonus line! :)


PR_opened/Fix_7315_BuildDocs (jmarrec) - Win64-Windows-10-VisualStudio-16: OK (2446 of 2447 tests passed, 0 test warnings)

Messages:\n
 * 1 test had: BND diffs.
 * 1 test had: EIO diffs.
 * 1 test had: ERR diffs.
 * 1 test had: ESO big diffs.
 * 1 test had: MTD diffs.
 * 1 test had: MTR big diffs.
 * 1 test had: Table big diffs.

Failures:\n

regression Test Summary
 * Passed: 661
 * Failed: 1

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


delete the figures for readme.md, which are about the mechanisms and differential equations. I will upload them after publication!


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

* https://callumflackdesign.callum.now.sh
* https://callumflackdesign-git-master.callum.now.sh


Successfully aliased the URL <https://simonlyllyyy-caculator1-oghf0734i.now.sh> to the following aliases:

* https://simonlyllyyy-caculator1.now.sh
* https://simonlyllyyy-caculator1.simonlyllyyy.now.sh
* https://simonlyllyyy-caculator1-git-master.simonlyllyyy.now.sh


Successfully aliased the URL <https://at-the-wall-apq5pbepq.now.sh> to the following aliases:

* https://at-the-wall.now.sh
* https://at-the-wall.atanas.now.sh
* https://at-the-wall-git-master.atanas.now.sh


thnx
@jkarelbroer  @KsAmJ
try last version
#13


Reverted because the resizing performance wasn't very good on my laptop, and that may make it look bad. What might help instead would be to offer to hide application category groupboxes, and make the window smaller or larger when showing or hiding them.


Second try


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

* https://accessabar.handsfree.now.sh
* https://accessabar-git-master.handsfree.now.sh


@kytwb This commit ensures hard reset do NOT happen when mergeability is null. Thanks for the bug report!


I know, but I don't see that log being sent anywhere, unless I missed something.


ScheduleManagerRefactor (Myoldmopar) - x86_64-MacOS-10.13-clang: OK (2390 of 2466 tests passed, 595 test warnings)

Messages:\n
 * 595 tests had: AUD diffs.
 * 582 tests had: RDD diffs.
 * 1 test had: EIO diffs.
 * 2 tests had: ERR diffs.
 * 1 test had: MTD diffs.

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 773
 * Failed: 3
 * SEGFAULT: 1

integration Test Summary
 * Passed: 597
 * Failed: 68

SchedulingTestFixture Test Summary
 * Passed: 6
 * Failed: 4

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


I love having these initials (PBR) ...stuff like this happens by accident all the time :-)


This is because the string "false" is actually truthy in javascript.


@Rakanfalroba  [
![45929165](https://user-images.githubusercontent.com/45929165/61990104-747a1a00-b042-11e9-9a5f-223336f0eaa6.png)
](url) (راكان بن فريح الربع)


good


🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2888072)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/e8eec97d20d4ae659a14fda1acc8b5b22c977c97/2888072/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
 * mscorlib/tvOS - device/Release: Failed (MT1032: This application executable might be too large (976 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (MT1032: This application executable might be too large (555 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
</details>


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

 * `monitoring-listrik.com`(for alias `monitoring-listrik.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=monitoring-listrik.com).


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/0082bd3a-e486-4734-bf37-ad62c803b134?env_id=ibm%3Ayp%3Aus-south "cloud-native-toolchain-tutorial-20190726182722776"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/3128a0fe-3a87-4291-b77c-7588ba2fdd0f "sample-cloud-native-toolchain-tutorial-20190726182722776") deployed [sample-cloud-native-toolchain-tutorial-20190726182722776](https://github.com/marktoldoibm/sample-cloud-native-toolchain-tutorial-20190726182722776/releases/tag/deploy-ibm-yp-au-syd-toldom-ph.ibm.com-dev-20190727-045233 "deploy-ibm-yp-au-syd-toldom-ph.ibm.com-dev-20190727-045233") to [dev](https://console.bluemix.net/apps/6694fc14-c8b3-49fb-90ec-bec1b6f79aec?env_id=ibm:yp:au-syd "ibm:yp:au-syd:toldom@ph.ibm.com:dev"), including this commit


![](https://github.trello.services/images/mini-trello-icon.png) [Corrigir Controller e Repository de Projetos](https://trello.com/c/IRLZFfR0/53-corrigir-controller-e-repository-de-projetos)


GSHP_desuperheater (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2496 of 2496 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)


added to master


Actually, doing what I said in the last comment won't work either. Maybe doing what was in this commit would work minus allowing for resizing. Actually, maybe not. That would require changing the size of the columns from code, which isn't something I'm used to yet. Maybe just showing or hiding the status bar would be good for now.


ugh!


should have been re ced0eb4aa0d2783a177570bdea954032b78bd20d


There is also an trailing newline with args being longer than the available width (e.g. with `:exe 'args '.repeat('X', &columns+1)`).

This fixes it:

```diff
diff --git i/src/version.c w/src/version.c
index 8518667e9..3cfe53119 100644
--- i/src/version.c
+++ w/src/version.c
@@ -4414,8 +4414,9 @@ list_in_columns(char_u **items, int size, int current)
        for (i = 0; i < item_count; ++i)
        {
            version_msg_wrap(items[i], i == current);
-           if (msg_col > 0)
+           if (msg_col > 0 && i < item_count - 1) {
                msg_putchar('\n');
+           }
        }
        return;
     }
```


I think this was down to some confusion about `match` semantics, thinking that match meant that the whole string matched, i.e. '^' and '$' implied.

I think the '^' is implied, but not '$'


Adding this line stopped my players from being able to revive with medikit.  Removing the line consistently re-enabled the ability to auto-revive while carrying medikit


Added hardcoded reviews
Linked pets page to contact page
added styling


In general this library doesn't do much validation, at it was originally intended for something internal and most the validation was done by RippleAPI. There's likely other nasties lurking.

#10


Horse/b
:thonk:


you should not encourage downloading as a zip file. this makes updating harder for no reason.
you should add something like "if you want to be able to easily update the prototype, use git"

just tell to download [git](https://git-scm.com/download/win) and run these commands in cmd :
`cd <path to save Pulsarc in>`
`git clone --single-branch --branch MonoGame-Prototype-Adri https://github.com/PulsarcGame/Pulsarc.git`
or, if it's merged to master, you can have a more stable version but updated less frequently
`git clone https://github.com/PulsarcGame/Pulsarc.git`


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

* https://autochess.gabriel-wu.com
* https://autochess.lucifer1004.now.sh
* https://autochess-git-master.lucifer1004.now.sh


merge


Hi there. I am on node 10.10 and using Typescript and I think this change broke. Now I get:

```
import {Timer} from 'react-compound-timer'
```

```
Attempted import error: 'Timer' is not exported from 'react-compound-timer'.
```


Do you think my version of node is too old to use your new syntax?


Why not document.head?


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

 * `snuggsi.com`(for alias `snuggsi.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=snuggsi.com).


Shouldn't there be a semicolon on this line?


安装包在这里


GSHP_desuperheater (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1128 of 1128 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.44%25-green.png)


@JuliaRegistrator register()

Release notes:

Bound LogDensityProblems, fixes #51.


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

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 v1.0.6 -m "<description of version>" 991fac3306fb6d26598a1a6b099ce080f0d905f4
git push origin v1.0.6
```


nullfile


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


If `MRB_USE_FLOAT` or `MRB_INT16` is defined, it will cause problematic behavior because the numerical precision is insufficient.

  - If `MRB_USE_FLOAT` is set, time will be skipped.

    Since the mantissa of an IEEE 754 single-precision floating-point number is equivalent to 24 bits, its limit that can represent 1 second units is `1970-07-14 04:20:16 UTC`.

    If you want to represent the nearly current time, you need 31 bits, but because 7-bit precision falls, the time will fly in 128 seconds alignment.

    For example (build by `CFLAGS='-DMRB_USE_FLOAT' ./minirake`):

    ```irb
    % ./build/host/bin/mirb
    mirb - Embeddable Interactive Ruby Shell

    > Math.log(Time.now.to_i, 2)
     => 30.542782
    > Time.now
     => 2019-07-27 13:48:53 +0900               # <= OK!
    > Time.now + 0
     => 2019-07-27 13:48:00 +0900               # <= Rounded to integer high-order 24 bits
    > Time.local(2019, 7, 27, 13, 48, 53) + 63
     => 2019-07-27 13:48:00 +0900               # <= Same as before
    > Time.local(2019, 7, 27, 13, 48, 53) + 64
     => 2019-07-27 13:50:08 +0900               # <= Indicates 128 seconds ahead
    > Time.local(2019, 7, 27, 13, 48, 53) - 63
     => 2019-07-27 13:48:00 +0900               # <= Same as before
    > Time.local(2019, 7, 27, 13, 48, 53) - 64
     => 2019-07-27 13:45:52 +0900               # <= Indicates 128 seconds ago
    ```

  - If `MRB_INT16` is set, the subsecond representation is limited to `0 .. 32767` microseconds.

  - If `MRB_INT16` + `MRB_WITHOUT_FLOAT` is set, the date and time that can be expressed is limited to `1970-01-01 09:06:08 UTC`.


I'm just copying this from my other repository, the tetris git.


it will make better visual effect(scrolling)


> (i know not delaying bomber running)

it will make better visual effect(scrolling)


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

* https://verificar.jondotsoy.now.sh
* https://verificar-git-master.jondotsoy.now.sh


This module uses forFeature() method to define which repositories shall be registered in the current scope.


What is that think


If `MRB_WITHOUT_FLOAT` and `MRB_INT16 / MRB_INT32` are defined, `(mrb_sec)INT64_MAX` is `-1` and `(mrb_sec)INT64_MIN` is` 0`.

```console
% ./build/host/bin/mruby -e 'p Time.at 0'
trace (most recent call last):
        [0] -e:1
-e:1: 0 out of Time range (ArgumentError)
```

Therefore, this `if` statement is always true.


Correction: Only added portfolio-style.css on this commit. Missed adding html skeletons for contact.html and portfolio.html


Just tried the first issue again (COLUMNS=79):
```
[1] 5   9   13  17  21  25  29  33  37  41  45  49  53  57  61  65  69  73  77
2   6   10  14  18  22  26  30  34  38  42  46  50  54  58  62  66  70  74  78
3   7   11  15  19  23  27  31  35  39  43  47  51  55  59  63  67  71  75  79
4   8   12  16  20  24  28  32  36  40  44  48  52  56  60  64  68  72  76  80
```

With `1 .. 81` however:
```
[1] 6   11  16  21  26  31  36  41  46  51  56  61  66  71  76  81
2   7   12  17  22  27  32  37  42  47  52  57  62  67  72  77
3   8   13  18  23  28  33  38  43  48  53  58  63  68  73  78  4   9   14  19
24  29  34  39  44  49  54  59  64  69  74  79  5   10  15  20  25  30  35  40
45  50  55  60  65  70  75  80
```

```
ncol = 20
nrow = 5
```
But only rows 3 and 4 have 20 items, and looking at in gdb showed that `cur_row` was getting too big.

This fixes that:

```diff
diff --git i/src/version.c w/src/version.c
index 8518667e9..00bed7c07 100644
--- i/src/version.c
+++ w/src/version.c
@@ -4459,9 +4460,11 @@ list_in_columns(char_u **items, int size, int current)
        else
        {
            // this row is out of items, thus at the end of the row
-           if (msg_col > 0 && cur_row < nrow)
-               msg_putchar('\n');
-           ++cur_row;
+           if (msg_col > 0) {
+               if (cur_row < nrow)
+                   msg_putchar('\n');
+               ++cur_row;
+           }
        }
     }
 }
```

But it is not clear to me what the initial patch here was fixing, and if it is still fixed.

Having tests for those would be good therefore.


Fair point.


Successfully aliased the URL <https://simonlyllyyy-caculator1-oghf0734i.now.sh> to the following aliases:

* https://simonlyllyyy-caculator1.now.sh
* https://simonlyllyyy-caculator1.simonlyllyyy.now.sh
* https://simonlyllyyy-caculator1-git-master.simonlyllyyy.now.sh


`.className = "...";` or `.classList.add("...");`?


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2888069)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/e8eec97d20d4ae659a14fda1acc8b5b22c977c97/2888069/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
 * 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: Crashed
 * link all/iOS Unified 64-bits - device/Debug: Crashed
 * link sdk/iOS Unified 64-bits - device/Debug: Crashed
 * 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): TimedOut
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): TimedOut
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): TimedOut
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): Crashed
 * 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): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/Release: Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/Release: Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/Release: Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * 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): TimedOut
 * [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://boycott-knfyvcb3t.now.sh> to the following aliases:

* https://boycott.gabriel-wu.com
* https://boycott.lucifer1004.now.sh
* https://boycott-git-master.lucifer1004.now.sh


Thanks


`deleteElement` also?


Even if `time_t` is 64 bits, it will be restricted if` MRB_INT16 / MRB_INT32` is defined.

It thinks better to use `sec` for` time_t` (or `int64_t`?) and `usec` for` int32_t` (or `time_t`?).


This just released `v7-beta`, please disable releases on this branch


7385-MovableInsulationSupportEquivalentWindow (RKStrand) - 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)


Resolved


7385-MovableInsulationSupportEquivalentWindow (RKStrand) - 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://mock-x42-o9e7w1s1u.now.sh> to the following aliases:

* https://mock-x42.eswat2.now.sh
* https://mock-x42-git-master.eswat2.now.sh


it's me jess is referencing me i'm uncivilised


greem be like https://jessica.is-pretty.cool/AUbyf2R.png


jess be like https://img.greemdev.net/dCTZglvrha/firefox_2019-07-27_00-41-03.png


github be like ![image](https://jessica.is-pretty.cool/5tETDwz.png)


libris more like gayris


最近在查水表，为了防止出问题，下线Demo。大家最近也慎用本脚本


八皇后和去年快手迷宫题目都是这种回溯法可以解决的问题


This notebook might fail to train models well as follows.

11 epoch
![epoch-11](https://user-images.githubusercontent.com/16191443/61990500-e4a59180-b07c-11e9-847a-e54e69c00e6a.jpg)

16 epoch
![epoch-16](https://user-images.githubusercontent.com/16191443/61990503-eff8bd00-b07c-11e9-97ca-9e1ab1311af9.jpg)


Make this `Display` or `Debug`.


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2886349)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump-163/55ea5e5bd1d35cd7334f1bbfd670fae37dcb50ae/2886349/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
 * 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: Crashed
 * link all/iOS Unified 64-bits - device/Debug: Crashed
 * link sdk/iOS Unified 64-bits - device/Debug: Crashed
 * 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: TimedOut
 * [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): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): Crashed
 * 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): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/Release: Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/Release: Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/Release: Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * 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): TimedOut
 * [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: TimedOut
 * [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): TimedOut
 * 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>


@JuliaRegistrator register()


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

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


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

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


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

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.1.2 -m "<description of version>" 8039d93e848952171c1b279de44bb39377760740
git push origin v0.1.2
```
Also, note the warning: Version 0.1.2 skips over 0.1.1
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


> 八皇后和去年快手迷宫题目都是这种回溯法可以解决的问题

https://leetcode-cn.com/problems/word-search/submissions/


Undoing the deletion of readme file


join for memes if not anything else


7385-MovableInsulationSupportEquivalentWindow (RKStrand) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2494 of 2494 tests passed, 0 test warnings)

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


hi bro,

i have installed python 3.7.4 and i have installed tkinter and mysql but when i open GUI its not working.

please tell me how to run the application .

than you.


Have handled the disabled button part, but still trying to figure out how to prevent the form submission when the password is still wear. This is because the password strength is a component on its own, so transferring the password strength score prop from that component to the reset password component so as to ensure that the form does not submit when the password strength score is weak is a an issue for me. I don't know how I will transfer that prop without using redux.


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - Win64-Windows-10-VisualStudio-16: OK (2453 of 2453 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)


ignore this


> it will make better visual effect(scrolling)

So why reply two times...


böyle daha iyi aga !!


Successfully aliased the URL <https://ota-solid-ijx5w6ary.now.sh> to the following aliases:

* https://ota-solid.now.sh
* https://ota-solid.ota.now.sh
* https://ota-solid-git-master.ota.now.sh


✅ Device tests passed on iOS32b on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2886993)(iOS32b): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/bump-mono-2019-06-head/2de3287c2410e53959ce000d89647afb1dca34d1/2886993/device-tests/jenkins-results/tests/index.html) ✅

# Test results

# No tests selected.


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

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/xcode11/177/display/redirect) (on internal Jenkins) failed in stage(s) 'Running XM tests on '10.15', Running XM tests on '10.15'' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/xcode11/177//console)
✅ Packages: [xamarin.ios-12.99.2.28.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/package/xamarin.ios-12.99.2.28.pkg) [xamarin.mac-5.99.2.28.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/package/xamarin.mac-5.99.2.28.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/jenkins-results/api-diff/index.html)
✅ [API Diff (from PR only)](http://xamarin-storage/jenkins/xamarin-macios/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/jenkins-results/apicomparison/api-diff.html) (no change)
✅ [Generator Diff](http://xamarin-storage/jenkins/xamarin-macios/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/jenkins-results/generator-diff/index.html) (no change)
🔥 [Xamarin.Mac tests on 10.15 failed: Xamarin.Mac tests on macOS 10.15 failed (xammac_tests)](https://jenkins.internalx.com/job/macios/job/xcode11/177/display/redirect) 🔥
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/xcode11/5fdc25ebe75651d3ea3d8699d6f702c7b2fe2a41/177/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>1 tests failed, 233 tests passed.</summary>

## Failed tests

 * System.ServiceModel/iOS Unified 32-bits - simulator/Debug: Failed
</details>


run "npm install pg" for the database driver if 'postgres' is being used instead of mysql


OK, could you send us a pull request? Or should I fix it by myself?


@rgtoth, this is not the way to get help.  Please continue the conversation you started in the group at RCGroups.


Q.
自分のモンスターゾーンに「切り込み隊長」2体が存在し、そのうちの1体に「仁王立ち」の②効果が適用された場合、相手のモンスターは攻撃を行えますか？
A.
ご質問の場合、相手は攻撃を行うことができません。

Q.
自分のモンスターゾーンに「青眼の白龍」と、「仁王立ち」の②効果が適用された「地縛神 Ccapac Apu」が存在している場合、相手のモンスターは攻撃を行えますか？
A.
ご質問の場合、相手は攻撃を行うことができません。


哇偶好棒


Can you explain how pushing to this branch triggered a v7 release?


Rationale: The user needs to add yet another repository to the list for the usage of only two packages. I'm going to move the obsolete list to the README.


It picked up "breaking" from v6 release commit https://travis-ci.org/sequelize/sequelize/jobs/564160134


We should start releasing this as a beta when we merge this over master


Agree, feel free to make these changes, I will be n/a for a few days.


7385-MovableInsulationSupportEquivalentWindow (RKStrand) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1128 of 1128 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.4%25-green.png)


Podejrzewam, że cały folder `.idea/` powinien być dodany do `.gitignore`.


Build version: __`3.2.0-master.600`__ :crossed_fingers: [`master`](https://github.com/streamich/md-mdast/tree/master) on [*CircleCI*](https://circleci.com/gh/streamich/md-mdast/600) :tada:


second day


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

* https://goiblas.com
* https://personal-blog.goiblas.now.sh
* https://personal-blog-git-master.goiblas.now.sh


✅ Device tests passed on iOS32b on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2887514)(iOS32b): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/d16-3/31467d21befe0fdd0336ca71c31f37755ff19686/2887514/device-tests/jenkins-results/tests/index.html) ✅

# Test results

# No tests selected.


@JuliaRegistrator `register()`


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

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>" c98744b1dead3b0ec7327616188707415b7713e6
git push origin v0.2.0
```


> 实际写业务代码的话，有更简单的方式：函数式+第三方库，请看测试的写法：https://github.com/hcsp/how-many-prime-numbers/blob/master/src/test/java/com/github/hcsp/controlflow/MainTest.java#L14

嗯嗯！基本做题前都会顺便看下测试怎么写的，以便更理解题目意思


Good


Powinno tutaj być odwołanie do repozytorium zamiast bezpośredniego calla do AR.


I tutaj też dobrze by było uderzyć o repozytorium zamiast bezpośrednio o AR.


@terranc 已更新


Ah crap, good eye there!
Hasn’t caused any noticeable issues but obviously does need to be addressed.


Successfully aliased the URL <https://gatsby-theme-documentation-me7zv7y9e.now.sh> to the following aliases:

* https://docs-theme.johno.com
* https://gatsby-theme-documentation.johno1.now.sh
* https://gatsby-theme-documentation-git-master.johno1.now.sh


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

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


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

 * `snuggsi.com`(for alias `snuggsi.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=snuggsi.com).


Perhaps the whole thing needs a change, such as turning `mrb_sec` into` time_t`.
So I would like to propose as a PR if there is no problem.
Please wait for the patch to be written from now on.


GSHP_desuperheater (yzhou601) - 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.47%25-green.png)


@JuliaRegistrator register


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

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


fix #11


W sumie ta metoda niewiele się różni od powyższej, więc może miałoby sens zrobienie z tego po prostu jednej metody, która ma w keyword argumentach defaulty. Coś na tej zasadzie:

```ruby
# frozen_string_literal: true

module Users
  class Repository
    attr_reader :adapter

    def initialize(adapter: User)
      @adapter = adapter
    end

    def fetch(filter: {}, columns: DEFAULT_COLUMNS)
      adapter.where(filter).select(columns)
    end

    private

    def default_columns
      adapter.column_names - ['password_digest']
    end
  end
end
```

Co myślisz? Na pewno bardziej elegancko byłoby wrzucić te defaultowe kolumny do constanta, ale tam nie będziemy mieli dostępu do zmiennej `adapter`, więc na szybko wrzuciłam to do prywatnej metody, ale pewnie można by wykminić coś ładniejszego


Można by tutaj dodać default param, żeby ten `#fetch` też obsługiwał query po wszystkie rekordy, czyli:
```ruby
def fetch(filter = {})
  ...
end
```


Thank you!


Build version: __`0.10.0-master.936`__ :crossed_fingers: [`master`](https://github.com/streamich/ci-scripts/tree/master) on [*CircleCI*](https://circleci.com/gh/streamich/ci-scripts/936) :tada:


✅ Device tests passed on iOS32b on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2887518)(iOS32b): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/alex-mono-bump-163/55ea5e5bd1d35cd7334f1bbfd670fae37dcb50ae/2887518/device-tests/jenkins-results/tests/index.html) ✅

# Test results

# No tests selected.


Hi @cowtowncoder, this change on `2.9` branch to address #2331 seems to have caused some kind of regression for us in `2.9.9.2` - the [changelog](https://github.com/FasterXML/jackson-databind/blob/master/release-notes/VERSION-2.x) has it in `2.9.9.1` per above, however I believe it's actually been released in `2.9.9.2`, although the intention was probably for `2.9.10` based on the commit comment.

We started getting NPEs on this exact line after this bump

Haven't dug into root cause and reproduced, as I'm not super-familiar with Jackson internals, but we're seeing it on our use with `spring-data-redis`'s [Jackson2HashMapper](https://docs.spring.io/spring-data/redis/docs/current/api/org/springframework/data/redis/hash/Jackson2HashMapper.html) in this line [here](https://github.com/spring-projects/spring-data-redis/blob/2.1.9.RELEASE/src/main/java/org/springframework/data/redis/hash/Jackson2HashMapper.java#L134)

```
java.lang.NullPointerException
	at com.fasterxml.jackson.databind.type.ResolvedRecursiveType.getBindings(ResolvedRecursiveType.java:42)
	at com.fasterxml.jackson.databind.type.TypeFactory._fromAny(TypeFactory.java:1243)
	at com.fasterxml.jackson.databind.type.TypeFactory._fromParamType(TypeFactory.java:1452)
	at com.fasterxml.jackson.databind.type.TypeFactory._fromAny(TypeFactory.java:1221)
	at com.fasterxml.jackson.databind.type.TypeFactory._resolveSuperInterfaces(TypeFactory.java:1367)
	at com.fasterxml.jackson.databind.type.TypeFactory._fromClass(TypeFactory.java:1314)
	at com.fasterxml.jackson.databind.type.TypeFactory._fromAny(TypeFactory.java:1217)
	at com.fasterxml.jackson.databind.type.TypeFactory.constructType(TypeFactory.java:631)
	at com.fasterxml.jackson.databind.cfg.MapperConfig.constructType(MapperConfig.java:281)
	at com.fasterxml.jackson.databind.cfg.MapperConfig.introspectClassAnnotations(MapperConfig.java:311)
	at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findTypeDeserializer(BasicDeserializerFactory.java:1571)
	at com.fasterxml.jackson.databind.DeserializationContext.findRootValueDeserializer(DeserializationContext.java:483)
	at com.fasterxml.jackson.databind.ObjectMapper._findRootDeserializer(ObjectMapper.java:4191)
	at com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:3980)
	at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2385)
	at com.fasterxml.jackson.databind.ObjectMapper.valueToTree(ObjectMapper.java:2800)
	at org.springframework.data.redis.hash.Jackson2HashMapper.toHash(Jackson2HashMapper.java:134)
        at <REDACTED>
```

`ResolvedRecursiveType` is a `JsonNode` with no `_referencedType`

```
this = {ResolvedRecursiveType@3886} "[recursive type; UNRESOLVED"
 _referencedType = null
 _superClass = null
 _superInterfaces = null
 _bindings = {TypeBindings@3896} "<>"
 _canonicalName = null
 _class = {Class@3897} "class com.fasterxml.jackson.databind.JsonNode"
 _hash = -887947255
 _valueHandler = null
 _typeHandler = null
 _asStatic = false
_referencedType = null
```

Any chance of reverting this so we can pick up the CVE fixes, and relook at this for `2.9.10`? Let me know if you'd like me to file an issue and what additional detail would be useful.


Build version: __`0.10.0-master.1448`__ :crossed_fingers: [`master`](https://github.com/streamich/ci-scripts/tree/master) on [*Travis*](https://travis-ci.org/streamich/ci-scripts/builds/564308795) :tada:


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

* https://api.firstmeanseverything.com
* https://fme-api.firstmeanseverything.now.sh
* https://fme-api-git-master.firstmeanseverything.now.sh


1st project master file creation


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

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


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

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


Have you tested this? This isn't going to work, because essentially you can't copy nothing to a directory. Needs another implementation.


FWIW, I already leak uptime on main with my Pokemon Showdown Updates thread


first readme file


Dobrą praktyką jest używać `subject` dla podmiotów speców zamiast `let` - do poczytania https://stackoverflow.com/questions/38437162/whats-the-difference-between-rspecs-subject-and-let-when-should-they-be-used :).


# 递归
tips：本蒟蒻的第一篇博客
***
在学完顺序，条件和循环结构后，摆在OIer面前的
第一道门槛便出现了，那便是

![7ea99ae720db8514b8925d9263d8c028](https://user-images.githubusercontent.com/45810001/61991172-00aa3280-b07f-11e9-9ab4-c2bd309970ff.jpg)

递归
***
进入正题：

* ### 递归der定义
	递归（英语：Recursion），又译为递回，在数学与计算机科学中，是指在函数的定义中使用函数自身的方法。递归一词还较常用于描述以自相似方法重复事物的过程。例如，当两面镜子相互之间近似平行时，镜中嵌套的图像是以无限递归的形式出现的。也可以理解为自我复制的过程。
![6af89bc8gw1f8quiwiufkj20af09gaa4](https://user-images.githubusercontent.com/45810001/61991116-313d9c80-b07e-11e9-96fe-0795d99c7a28.jpg)

	就....就就就我用我记几吗。
* ### 一个小栗子
  	```cpp
  	int f(int x)
  	{
	  	if(x==1||x==2) return 1;
	  	return f(x-1)+f(x-2);
  	}
  	```
  	这就是大名鼎鼎的 **斐波那契数列**

  	就是1,1,2,3,5,8,13....;

	那么这样一个程序是如何运作的呢

	![ 如图 ](https://i01piccdn.sogoucdn.com/f98896f8b21b6fc0)

	在我们输入6之后,程序开始将f(6)拆分成f(5)和f(4)再依照此程序对f(5)和f(4)进行拆分,直到来到了**边界条件**f(1)和f(2)。
	此时再返回至f(3),f(4)得出f(3),f(4)的值后再计算f(5),f(6)

	若是将递归的内容全部朴素的写出来
	```cpp
	int f(int x)
  	{
	  	if(x==1||x==2) return 1;
	  	int x1=x-1,x2=x-2;
		if(x1==1||x1==2) x1=1;
		else
		{
			int x11=x1-1,x12=x1-2;
			if(x11==1||x11==2) x11=1;
			else
			{
				.......
			}
		}
  	}
	```
	可以看出，递归能够让我们无数次的运行同一段代码，进行计算机最擅长的：**重复运算**
* ### 递归与循环的区别
	这时可能有人要问了,那递归和循环有什么区别呢？？？？

	的确，我在一开始学递归的时候也是将其看作一种特殊的**循环**。

	在上一波官方解释

	>1.程序独立性
	>
	>递归由程序和系统共同完成。递归需要系统维护一个系统工作栈。
	>
	>循环由程序单独完成。但是，循环需要程序设定好循环条件。
	>
	>2.程序规模
	>
	>递归的规模很小，受到系统工作栈大小的限制。
	>
	>循环的规模很大，几乎不会受到限制。
	>
	>在VS2012中计算1+2+3+······+n
	>
	>使用递归n只能达到4710.
	>
	>使用循环n可以达到20 0000 0000.
	>
	>3.复用单位
	>
	>递归的复用单位是函数。
	>
	>循环的复用单位是语句（for循环语句或while循环语句）。
	>

	有很多算法都是用到递归的，最好的一个例子便是关于树的前中后序遍历。用递归的实现分别是
	```cpp
	void qian(tree i)//前序遍历
	{
		cout<<tree->root;//输出根的信息
		qian(i->lchild);
		qian(i->rchild);
	}
	void zhong(tree i)//中序遍历
	{
		zhong(i->lchild);
		cout<<tree->root;//输出根的信息
		zhong(i->rchild);
	}
	void hou(tree i)//后序遍历
	{
		hou(i->lchild);
		hou(i->rchild);
		cout<<tree->root;//输出根的信息
	}
	```
	这样的三行代码简单清晰明了

	而关于非递归实现，~~我以前是写过的但是找不到了。。。~~
	我这样的蒟蒻只能从网上找代码了
	```cpp
	void DLR(BinaryTree *p) //前序遍历非递归算法
	{
    stack<BinaryTree> *s;    //定义堆栈s
    BinaryTree *p=root;    //指向根节点
    while(p!=NULL || !s.empty())
    {
        while(p!=NULL)
        {
            cout<<p->data<<endl;
            s.push(p);
            p=p->lchild;
        }
        if(!s.empty())
        {
            p=s.top();
            s.pop();
            p=p->rchild;
        }
    }
	```
	大家不用关心看不看得懂，说是不是很长就可以了
***
差不多就完啦，本蒟蒻的第一篇博客，写得不好多多见谅。


This drawer is what will hold the sliding panel coming from the right.


Successfully aliased the URL <https://enum-converter-n8rd9pale.now.sh> to the following aliases:

* https://enum-converter.now.sh
* https://enum-converter.nitzano.now.sh
* https://enum-converter-git-master.nitzano.now.sh


ScheduleManagerRefactor (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2426 of 2506 tests passed, 595 test warnings)

Messages:\n
 * 595 tests had: AUD diffs.
 * 582 tests had: RDD diffs.
 * 1 test had: EIO diffs.
 * 2 tests had: ERR diffs.
 * 1 test had: MTD diffs.

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 773
 * Failed: 3
 * SEGFAULT: 1

integration Test Summary
 * Passed: 596
 * Failed: 72

SchedulingTestFixture Test Summary
 * Passed: 6
 * Failed: 4

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


You can send a callback function as a prop to the password strength
component that the password strength component will call when it verifies
and it's weak that way the state of the parent component can be modified in
the child component. Instead of passing a normal prop you pass but a
function

On Sat, Jul 27, 2019, 6:59 AM Tendonge Ryan <notifications@github.com>
wrote:

> Have handled the disabled button part, but still trying to figure out how
> to prevent the form submission when the password is still wear. This is
> because the password strength is a component on its own, so transferring
> the password strength score prop from that component to the reset password
> component so as to ensure that the form does not submit when the password
> strength score is weak is a an issue for me. I don't know how I will
> transfer that prop without using redux.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/tenas97/OpenmrsPasswordResetUI/commit/8043c0752a7ebf59cc940ea663af05fc8951ba72?email_source=notifications&email_token=AC6GJZNWSVPKTX57VQ2K32DQBPP4PA5CNFSM4IGXNMHKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA33TG#commitcomment-34467430>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AC6GJZI4CQCECHUNBSUZVPTQBPP4PANCNFSM4IGXNMHA>
> .
>


Tak samo jak w `With invalid params` przeniosłabym te paramsy do bloku `With valid params`. Bo one obecnie są poza blokiem, ale tak czy siak są aplikowalne jedynie wewnątrz tego bloku, ale zasada jest raczej taka, że wynosimy poza bloki coś, co jest współdzielone.

Też można by zmienić nazwy zmiennych `valid_params` i `invalid_params` na po prostu `params` i wtedy możesz sobie zdefiniować subject jako:
```ruby
subject(:create_user) { described_class.new.call(params) }
```

dzięki czemu w poszczególnych specach nie będziesz musiał wywoływać `create_user.call(params)` tylko po prostu `create_user`.

Co myślisz?


`ElementGeometryCreator` is using NodeWayMap.

`NodeWayMap` is using some structures that are not guaranteeing a stable order

https://github.com/westnordost/StreetComplete/blob/3244b26320754907a44bfa622338293d39318db9/app/src/main/java/de/westnordost/streetcomplete/data/osm/download/NodeWayMap.java#L12

> This implementation makes no guarantees regarding the order of enumeration of keys, values and entries collections.

https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.collections/-hash-map/index.html

As result https://github.com/westnordost/StreetComplete/blob/74f4241bb43aeb38e65df1c304e14079a7987c2e/app/src/main/java/de/westnordost/streetcomplete/data/osm/download/ElementGeometryCreator.java#L188 may not start from the expected node (or may, especially with small object count in a hashmap)


✅ Device tests passed on iOS32b on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2888070)(iOS32b): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/e8eec97d20d4ae659a14fda1acc8b5b22c977c97/2888070/device-tests/jenkins-results/tests/index.html) ✅

# Test results

# No tests selected.


To sam komentarz, co w specu `Users::UseCases::Create`.


Using ReadUncommited is almost always a bad idea. It may hurt performance a little bit, but it's important for maintaining consistency. Why do you use this here? Especially on an operation that happens very infrequently?


dfd


fdf


Амир, почему ты все никак не запомнишь, что ВСЕ переменные нужно называть осмысленно. Не только в руби, даже в C++, который ты учил.
Почему ты перебираешь массив с поездами, а переменную называешь `x`? Что такое х? Это не математика, где все коэффициенты называются `a, b, c, x`.
Если перебираешь массив с поездами, то так и называй переменную `train`.

И кстати говоря, что это такое `x[1]`? Ты обращаешься к поезду как к массиву? Почему?
Тут все должно быть намного проще. В аргументе `type` ты передаешь тип поезда. Тогда все поезда с этим типом можно просто найти например так: `@trains.select { |train| train.type == type }`. Все.
Ведь у тебя у поезда есть атрибут `@type`. Использую эти атрибуты, они задаются не просто так.


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


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

 * `snuggsi.com`(for alias `snuggsi.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=snuggsi.com).


Successfully aliased the URL <https://react-jsonschema-form-material-ui-f3ar8rx1w.now.sh> to the following aliases:

* https://react-jsonschema-form-material-ui.github56.now.sh
* https://react-jsonschema-form-material-ui-git-master.github56.now.sh


Почему `train_name`? Зачем передавать `type`?
Станция имеет список поездов, что это значит? Это значит просто массив с поездами, объектами класса Train. Зачем усложняешь?


```sh
$ nix-shell -A bolt --run "python3 -c 'import dbusmock'"
```
seems to function just fine.

The test suite imports `dbusmock` also fine. A subprocess is created, and there the interpreter cannot find the module. However, I do not see where Python is used in the subprocess; all I see is `boltd` and `boltctl`.

The error message indeed also shows a different store path for the interpreter, one outside the env. Actually, it is the unwrapped interpreter that is invoked.

Before, `PYTHONHOME` would be passed through which is why it likely worked. I suspect one of the dependencies somewhere uses  imagine that the subprocess that is executed (`boltd` or `boltctl`) depends on the Python environment somehow.

Note that using the Python env in a subprocess also works fine:
```sh
$ nix-shell -A bolt --run "python3 -c 'import subprocess; subprocess.run(\"which python3\", shell=True).stdout'"
/nix/store/ayvr6zdkiz4zj8nadcdyakqf2m670yv8-python3-3.7.4-env/bin/python3
```
and
```
$ nix-shell -A bolt --run python3
```
followed by
```
>>> import subprocess; subprocess.run('python3 -c "import dbusmock"', shell=True).stdout
```

Even so, setting `PYTHONHOME` does seem to fix the test suite. Checking further, shows that, using the wrapped Python 3, we have
```
$ nix-shell -A bolt --run "python3 -c 'import sys; print(sys.executable)'"
/nix/store/hzzfz9llr2f714fhdr35hna5a21a35my-python3-3.7.4/bin/python3
```
This is still problematic.

I think this implies that somewhere *another* Python 3 is being referenced.


Good job, Jihoo.
You did a great job.
I'm worried about my absent. But you did extremely well.
Love you Bro. I'll take care my body well, and will come back as soon as possible.


А вот здесь ты как раз почему-то удаляешь именно объект поезда.


Successfully aliased the URL <https://react-jsonschema-form-material-ui-rmmhy2xjn.now.sh> to the following aliases:

* https://react-jsonschema-form-material-ui.github56.now.sh
* https://react-jsonschema-form-material-ui-git-master.github56.now.sh


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

* https://training.efleurine.now.sh
* https://training-git-master.efleurine.now.sh


test


Что это за `temp`? Опять сильно усложняешь. По условию, мы можем в маршрут добавить промежуточную станцию. Ты мог бы погуглить, например, как можно добавить в массив объект на определенную позицию, и нашел бы примерно такое решение: `stations.insert(-2, station)`. Все.


Посмотри обновленные условия задачи. Нужно проверить, что удаляемая станция – не первая и не последняя.


everything is good


The train_log file is empty.How do you load ckpt?


some descriptions


Perfect! :+1:


응응 고생했당 ~


Почему опять же обращаешься к объекту `route` как к массиву?
По идее должно быть так: `current_station = route.stations.first`. У тебя объект маршрута имеет список станций (массив). А тут получается маршрут – это и есть массив со станциями? Это не правильно.


Вот так нужно было сделать с самого начала. Только опять же, нужно исправить это `@route[-1]`. Маршрут – это объект класса Route. У него есть специальные атрибуты и методы, для того чтобы получить нужную станцию в этом маршруте, используй их.


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

* https://training.efleurine.now.sh
* https://training-git-master.efleurine.now.sh


I have send you some code snippet so you can get a look at them and fix this one


No, I don't. I am assuming you can train the model by yourself.


У тебя тут в классе Train есть методы `next_station` и `previous_station`. Почему бы не использовать их для передвижения поезда?
Что-то типа:
```
current_station.send_train(self)
next_station.take_train(self)
```
Выглядит же намного проще и понятнее, не так ли?


[Your benchmark job](https://github.com/JuliaLang/julia/commit/20ef26286041558aecaeedc649f2bbcc9bf1f65f#commitcomment-34467067) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/a45fefc1087c38fc23d5b36302ab24c42e44b6d2/daily_2019_07_27/report.md). cc @ararslan


Тут читай условия задачи 13 урока и сделай все по ним.


nice, i waiting for it :)


In the current version we use T_WATER_FREEZE = 0. in SI; furthermore all arguments to functions are in C; so I think it is legitimate that we use Celsius for SI and Fahrenheit for IP. Using K and R would not match the rest of the code and would require extra lines of code for conversion.


See SI comment above.


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

* https://calmbook.page
* https://calmbook.sobstel.now.sh
* https://calmbook-git-master.sobstel.now.sh


See above. Here 32 in the current code was in Fahrenheit so it makes sense to keep TRIPLE_POINT_WATER_IP in Fahrenheit too,


GSHP_desuperheater (yzhou601) - Win64-Windows-10-VisualStudio-16: OK (2456 of 2456 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)


I understood. Thank you

------------------ 原始邮件 ------------------
发件人: "Taihong Xiao"<notifications@github.com>;
发送时间: 2019年7月27日(星期六) 下午3:20
收件人: "Prinsphield/Adversarial_Reprogramming"<Adversarial_Reprogramming@noreply.github.com>;
抄送: "上官"<529707112@qq.com>; "Comment"<comment@noreply.github.com>;
主题: Re: [Prinsphield/Adversarial_Reprogramming] multi-gpu training andtesting on single gpu bug (5c0e4eb)

No, I don't. I am assuming you can train the model by yourself.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Same as above.


I think I may need to incorporate some more robust error checking around these massive db executions.  Basically, the default isolation level for MariaDB "REPEATABLE READ" seems to lock the whole table during execution and some of the executions here can run on thousands of rows in a single table (it is the same for the API delete functionality).  So basically I am trying to cope with the possibilities of deadlock, which I had started experiencing a little too often lately in the integration tests.  As for safety, since this operation never runs unless the edition is locked (and delete never happens unless all editors have lost write access), the API ensures that no relevant rows will be altered during these processes.  Perhaps there is a different approach that I can take though that will allow the massive writes to occur, without blocking access to the table for so long?


Thanks, will fix that.


Same comment as above.


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> 554 Message rejected: Sending paused for this account. For more information, please check the inbox of the email address associated with your AWS account.

Please, copy and paste this stack trace to GitHub:

```
Net::SMTPFatalError
554 Message rejected: Sending paused for this account. For more information, please check the inbox of the email address associated with your AWS account.

/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:969:in `check_response'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:914:in `data'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:659:in `block in send_message'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:854:in `rcptto_list'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:659:in `send_message'
/app/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp_connection.rb:54:in `deliver!'
/app/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:101:in `block in deliver!'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/net/smtp.rb:519:in `start'
/app/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:109:in `start_smtp_session'
/app/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/network/delivery_methods/smtp.rb:100:in `deliver!'
/app/vendor/bundle/ruby/2.6.0/gems/mail-2.7.1/lib/mail/message.rb:276:in `deliver!'
/app/objects/job_emailed.rb:72:in `block in proceed'
/app/objects/job_emailed.rb:44:in `each'
/app/objects/job_emailed.rb:44:in `rescue in proceed'
/app/objects/job_emailed.rb:34:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:358:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1635:in `block in compile!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1040:in `block in process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1038:in `process_route'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1097:in `block in dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1094:in `dispatch!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `block in invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `catch'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1076:in `invoke'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-protection-2.0.4/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `block in call'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1729:in `synchronize'
/app/vendor/bundle/ruby/2.6.0/gems/sinatra-2.0.4/lib/sinatra/base.rb:1502:in `call'
/app/vendor/bundle/ruby/2.6.0/gems/rack-2.0.6/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.6.0/lib/ruby/2.6.0/webrick/server.rb:307:in `block in start_thread'
```


so it has to be 1?

like if its not 1 no vehicle will be created with createVehicleLocal?


done


@JuliaRegistrator register branch=master


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

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.11.2 -m "<description of version>" 8d59614d9c2c8a762d252635e362f996a0d00cec
git push origin v0.11.2
```


Fix (probably) in https://github.com/NixOS/nixpkgs/pull/65454.


Found spelling mistakes in documentation file AnalysisPP.md<<
 analytical
 Found spelling mistakes in documentation file CollectiveVariablesPP.md<<
 eigenvectors Paramagnetic minima minima minima eigenvectors eigenvectors
 Found spelling mistakes in documentation file GettingStartedPP.md<<
 regex
 Found spelling mistakes in documentation file GlossaryPP.md<<
 eigenvectors eigenvectors eigenvectors Paramagnetic
 Found spelling mistakes in documentation file InstallationPP.md<<
 functionalities optimizations functionalities login login login
 Found spelling mistakes in documentation file IntroductionPP.md<<
 PDF PDF PDF PDF PDF
 Found spelling mistakes in documentation file ISDBPP.md<<
 Paramagnetic
 Found spelling mistakes in documentation file MiscelaneousPP.md<<
 login login preinstalled plumedincludefile endplumedincludefile plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile
 Found spelling mistakes in documentation file PerformancesPP.md<<
 functionalities
 Found spelling mistakes in documentation file RegexPP.md<<
 regex wildcard regex wildcard wildcards
 Found spelling mistakes in documentation file automatic/ADAPTIVE_PATH.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/AVERAGE.txt<<
 formulae
 Found spelling mistakes in documentation file automatic/BF_COSINE.txt<<
 vdots vdots
 Found spelling mistakes in documentation file automatic/BF_FOURIER.txt<<
 vdots vdots
 Found spelling mistakes in documentation file automatic/BF_POWERS.txt<<
 vdots vdots
 Found spelling mistakes in documentation file automatic/BF_SINE.txt<<
 vdots vdots
 Found spelling mistakes in documentation file automatic/CLASSICAL_MDS.txt<<
 eigenvectors
 Found spelling mistakes in documentation file automatic/CLUSTER_DIAMETER.txt<<
 differentiable
 Found spelling mistakes in documentation file automatic/CLUSTER_NATOMS.txt<<
 differentiable
 Found spelling mistakes in documentation file automatic/COORDINATIONNUMBER.txt<<
 differentiable
 Found spelling mistakes in documentation file automatic/COORDINATION.txt<<
 differentiable
 Found spelling mistakes in documentation file automatic/CS2BACKBONE.txt<<
 amino OUTLIERS
 Found spelling mistakes in documentation file automatic/DISTANCE_FROM_CONTOUR.txt<<
 differentiable
 Found spelling mistakes in documentation file automatic/driver-float.txt<<
 analytical
 Found spelling mistakes in documentation file automatic/driver.txt<<
 analytical
 Found spelling mistakes in documentation file automatic/DRMSD.txt<<
 auxfile endauxfile auxfile endauxfile
 Found spelling mistakes in documentation file automatic/DRR.txt<<
 extendedTimeConstant extendedLangevinDamping kbt
 Found spelling mistakes in documentation file automatic/DUMPDERIVATIVES.txt<<
 analytical
 Found spelling mistakes in documentation file automatic/EDS.txt<<
 covariance ramping
 Found spelling mistakes in documentation file automatic/EXTERNAL.txt<<
 auxfile nbins endauxfile auxfile nbins nbins endauxfile
 Found spelling mistakes in documentation file automatic/FIT_TO_TEMPLATE.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/FIXEDATOM.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/FRET.txt<<
 efficiencies
 Found spelling mistakes in documentation file automatic/FUNCPATHMSD.txt<<
 auxfile CLP OL HL endauxfile auxfile CLP OL HL endauxfile auxfile CLP OL HL endauxfile
 Found spelling mistakes in documentation file automatic/GPROPERTYMAP.txt<<
 auxfile CLP OL HL CRP CLP OL HL CRP endauxfile
 Found spelling mistakes in documentation file automatic/GROUP.txt<<
 plumedincludefile endplumedincludefile auxfile endauxfile
 Found spelling mistakes in documentation file automatic/INCLUDE.txt<<
 plumedincludefile endplumedincludefile plumedincludefile groupa groupb endplumedincludefile plumedincludefile endplumedincludefile plumedmultireplicafile endplumedmultireplicafile plumedincludefile endplumedincludefile plumedincludefile endplumedincludefile
 Found spelling mistakes in documentation file automatic/JCOUPLING.txt<<
 OUTLIERS radians peptide
 Found spelling mistakes in documentation file automatic/LOAD.txt<<
 functionalities
 Found spelling mistakes in documentation file automatic/METAD.txt<<
 auxfile nbins endauxfile
 Found spelling mistakes in documentation file automatic/METAINFERENCE.txt<<
 OUTLIERS OUTLIERS outliers
 Found spelling mistakes in documentation file automatic/MOLINFO.txt<<
 amino amino
 Found spelling mistakes in documentation file automatic/MULTI_RMSD.txt<<
 auxfile HNT HB HB HB endauxfile
 Found spelling mistakes in documentation file automatic/MULTI-RMSD.txt<<
 auxfile HNT HB HB HB endauxfile auxfile HNT HB HB HB endauxfile
 Found spelling mistakes in documentation file automatic/NOE.txt<<
 OUTLIERS
 Found spelling mistakes in documentation file automatic/OPT_AVERAGED_SGD.txt<<
 filename filename plumedmultireplicafile td td endplumedmultireplicafile
 Found spelling mistakes in documentation file automatic/OPT_DUMMY.txt<<
 filename filename
 Found spelling mistakes in documentation file automatic/PAMM.txt<<
 covariance auxfile kerneltype endauxfile covariance
 Found spelling mistakes in documentation file automatic/PATHMSD.txt<<
 auxfile CLP OL CLP OL CLP OL endauxfile
 Found spelling mistakes in documentation file automatic/pathtools.txt<<
 parameterize parameterize
 Found spelling mistakes in documentation file automatic/PATH.txt<<
 auxfile CLP OL CLP OL CLP OL endauxfile formulae auxfile endauxfile
 Found spelling mistakes in documentation file automatic/PCARMSD.txt<<
 eigenvectors eigenvectors auxfile CLP OL endauxfile eigenvectors eigenvectors auxfile eigenvectors CLP OL CLP OL endauxfile
 Found spelling mistakes in documentation file automatic/PCA.txt<<
 covariance covariance covariance covariance covariance
 Found spelling mistakes in documentation file automatic/PCAVARS.txt<<
 eigenvectors eigenvectors covariance eigenvector auxfile HB HH HH HB HH HH endauxfile
 Found spelling mistakes in documentation file automatic/PCS.txt<<
 OUTLIERS
 Found spelling mistakes in documentation file automatic/POSITION.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/PRE.txt<<
 Paramagnetic paramagnetic OUTLIERS
 Found spelling mistakes in documentation file automatic/PROPERTYMAP.txt<<
 auxfile CLP CLP endauxfile
 Found spelling mistakes in documentation file automatic/PUCKERING.txt<<
 nucleotide
 Found spelling mistakes in documentation file automatic/RDC.txt<<
 paramagnetic OUTLIERS
 Found spelling mistakes in documentation file automatic/READ.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/RESET_CELL.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/RMSD.txt<<
 auxfile CLP OL HL endauxfile
 Found spelling mistakes in documentation file automatic/SAXS.txt<<
 OUTLIERS
 Found spelling mistakes in documentation file automatic/SPRINT.txt<<
 eigenvector
 Found spelling mistakes in documentation file automatic/TARGET.txt<<
 auxfile endauxfile
 Found spelling mistakes in documentation file automatic/TD_GAUSSIAN.txt<<
 covariance covariance covariance
 Found spelling mistakes in documentation file automatic/TD_GRID.txt<<
 filename auxfile nbins endauxfile
 Found spelling mistakes in documentation file automatic/TD_UNIFORM.txt<<
 minima maxima minima maxima
 Found spelling mistakes in documentation file automatic/VES_LINEAR_EXPANSION.txt<<
 filename filenames filename filenames filename filename filename filename filename filename
 Found spelling mistakes in documentation file automatic/ves_md_linearexpansion.txt<<
 Filename Filename Filename Filename filename
 Found spelling mistakes in documentation file automatic/VES_OUTPUT_BASISFUNCTIONS.txt<<
 filename filename filename filename
 Found spelling mistakes in documentation file automatic/VES_OUTPUT_TARGET_DISTRIBUTION.txt<<
 filename filename
 Found spelling mistakes in documentation file ../CHANGES/v2.0.md<<
 Sep Sep
 Found spelling mistakes in documentation file ../CHANGES/v2.1.md<<
 Sep Optimizations PDF eigenvectors SVN covariance
 Found spelling mistakes in documentation file ../CHANGES/v2.2.md<<
 refactoring refactoring
 Found spelling mistakes in documentation file ../CHANGES/v2.3.md<<
 eigenvector
 Found spelling mistakes in documentation file ../CHANGES/v2.5.md<<
 API
 Found spelling mistakes in documentation file tutorials/aa-lugano-1.txt<<
 handson PLUMED's trjconv PBCs PBCs PBCs PBCs timeline PBCs
 Found spelling mistakes in documentation file tutorials/aa-lugano-2.txt<<
 analytical minima analytical minima accummulated minima minimun reweigthing reweightin neighbour aroud optimisation neighobur analysed
 Found spelling mistakes in documentation file tutorials/aa-lugano-3.txt<<
 minima minima kBT propto learnt kBT
 Found spelling mistakes in documentation file tutorials/aa-lugano-4.txt<<
 minima minima Boltzmann's minima
 Found spelling mistakes in documentation file tutorials/aa-lugano-5.txt<<
 covariance covariance eigenvectors covariance eigenvectors
 Found spelling mistakes in documentation file tutorials/aa-lugano-6b.txt<<
 dinucleotide dinucleotide dinucleotide monophosphate dinucleotide analyse colums oxygens BT
 Found spelling mistakes in documentation file tutorials/aa-lugano-6c.txt<<
 initio inp initio equilbrate natively inp prelimnary challanged oxygens accout hydrongen
 Found spelling mistakes in documentation file tutorials/aa-lugano-6d.txt<<
 hydrogens minima
 Found spelling mistakes in documentation file tutorials/a-trieste-1.txt<<
 nucleotide nucleotide
 Found spelling mistakes in documentation file tutorials/a-trieste-2.txt<<
 Boltzmann's auxfile endauxfile analytical mynormal auxfile mynormal endauxfile unweighted mycorr auxfile mycorr endauxfile mcdata somethign auxfile mcdata endauxfile
 Found spelling mistakes in documentation file tutorials/a-trieste-3.txt<<
 analytical minima analytical minima analytical minima
 Found spelling mistakes in documentation file tutorials/a-trieste-4.txt<<
 minima minima
 Found spelling mistakes in documentation file tutorials/a-trieste-5.txt<<
 plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile plumedmultireplicafile endplumedmultireplicafile minima minima minima
 Found spelling mistakes in documentation file tutorials/a-trieste-6.txt<<
 peptide minima amino peptide amino amino amino minima
 Found spelling mistakes in documentation file tutorials/belfast-1.txt<<
 functionalities peptide
 Found spelling mistakes in documentation file tutorials/belfast-2.txt<<
 kinase vert vert vert vert vert vert
 Found spelling mistakes in documentation file tutorials/belfast-4.txt<<
 minima minima minima Hooke’s
 Found spelling mistakes in documentation file tutorials/belfast-6.txt<<
 minima minima
 Found spelling mistakes in documentation file tutorials/belfast-7.txt<<
 minima
 Found spelling mistakes in documentation file tutorials/belfast-8.txt<<
 peptide minima peptide amino peptide versa peptide
 Found spelling mistakes in documentation file tutorials/cambridge.txt<<
 minima minima minima peptide amino peptide minima minima
 Found spelling mistakes in documentation file tutorials/cineca.txt<<
 minima minima minima minima
 Found spelling mistakes in documentation file tutorials/julich-devel.txt<<
 analytical analytical workflow
 Found spelling mistakes in documentation file tutorials/lyon.txt<<
 minima functionalities minima
 Found spelling mistakes in documentation file tutorials/marvel-1.txt<<
 PLUMED's peptide
 Found spelling mistakes in documentation file tutorials/marvel-2.txt<<
 amino vert vert
 Found spelling mistakes in documentation file tutorials/munster.txt<<
 minima minima minima minima
 Found spelling mistakes in documentation file tutorials/performance-optimization.txt<<
 lookup
 Found spelling mistakes in documentation file tutorials/others/isdb-1.txt<<
 peptide peptide
 Found spelling mistakes in documentation file tutorials/others/ves-lugano2017-01-metad.txt<<
 sim
 Found spelling mistakes in documentation file tutorials/others/ves-lugano2017-04-kinetics.txt<<
 nanotube nanotube covalent covalent


Hi! Just coming through, but I have noticed this one.
IANAL but I think you are required to leave the original copyright, when your work is derived from another. Otherwise it is a violation.


This commit breaks SmartBar's buttons alpha adjustment. Looks like it completely removes relevant piece of code. So we have seekbar for alpha adjustment visible in preferences but it does nothing.


7385-MovableInsulationSupportEquivalentWindow (RKStrand) - 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)


Good


Would it make more sense to free tensors and their names when # of tensors is reduced?


Instead of entirely removing this comment block with the final three Xbox transformation steps, please mention them above, where you're reverting their effects step by step.


ScheduleManagerRefactor (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1130 of 1138 tests passed, 0 test warnings)

Failures:\n

EnergyPlusFixture Test Summary
 * Passed: 773
 * Child aborted: 1
 * Failed: 3

SchedulingTestFixture Test Summary
 * Passed: 6
 * Failed: 4

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


Could the cast to double be commented here?


@ReneHonig added to 1.8.1b24. Use MQTT topic `home/ems-esp/boiler_cmd_flowtemp` and payload as the temperature value


Could pOffset and pScale be passed directly here? That'd save variables and copying


No.


Different data types, D3DVECTOR != float array


Good to see this uncertainty go away!


above explains how the transform works, this instruction sequence is not useful information in this case, because many games use a different instruction set, and sometimes even different registers for the scale.
That's why we use our own copy of the viewport offset/scale registers, rather than relying on the reserved constants, and we don't specifically rely on this sequence.

I figured the "undo offset addition, undo perspective device (explaining how) and undoing the scale comments above were sufficient


this was my main motivation for addressing this particular issue


이 함수는 이전 데이터와 비교해서 문제가 있는 것들을 체크하고 알려주는 함수인데, 이전에 비교할 데이터가 없으면 따로 체크할 필요가 없어서 빈 리스트를 반환하게 해놨습니다. 제 로직상으로는 맞습니다. ㅎ


Do you think it's necessary? It's just to make sure the calculation doesn't lose precision before being cast back down to a float.


theme:Jekyll-theme-Cayman


Hello. Could you pleae explain this soluton, I don't understand it, thank you!


"Lego set"


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

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


Successfully aliased the URL <https://operation-code-7pdyciycb.now.sh> to the following aliases:

* https://operation-code.now.sh
* https://operation-code.operation-code.now.sh
* https://operation-code-git-master.operation-code.now.sh


`base.extend(ClassMethods)
`


Adding PyCon Thailand


Trailing coma(,) should be removed from `modhoster.de,play3.de,quotenmeter.de,##+js(setTimeout-defuser.js, 0&&)`


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

* https://tetris.isthe.link
* https://tetris.rem.now.sh
* https://tetris-git-master.rem.now.sh


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

* https://tetris.isthe.link
* https://tetris.rem.now.sh
* https://tetris-git-master.rem.now.sh


This is a good reminder that there might be bias in the noise generators!

For noise-identification I tried using the kasdin-generator to generate different noise-types and the the lag-1 ACF algorithm for detecting the noise. The summary of the results looks like this:
http://www.anderswallin.net/wp-content/uploads/2018/01/noise_ID_ACF_2018-01-04.png
It should be easiest to identify the noise-type at short tau (left edge of the figure). I don't know what is going on in this figure, where the estimated noise alpha seems to have a 'bend' for some noise types.
For large tau it is natural that estimating the noise type is difficult.

In general for power-law noise maybe one should also bin the power-spectrum points into some log-spaced bins before doing a least-squares fit? Maybe there is some literature on this?
(for the steep types least-squares must give a lot of weight to the short-tau (low fourier f) and almost no weight at all to long-tau (high f), because the y-values go steeply down in a loglog plot...)


https://github.com/uBlockOrigin/uAssets/commit/738648cb49058f49d0bcab400c05ba2bca4d89ce
thx


Ok, `ppc|ppc-musl)` should be a case similar to `armv5tel*)` while there's more to check actually. I still cannot cross compile to  `ppc64*{,-musl}` from `x86_64`. The reason is that some target `C{,XX}FLAGS` are leaking into a host compiler call.


Awesome, many thanks!