##### [Bitrise Output](https://www.bitrise.io/build/4e5f5b808f4590b8)
```ini
+------------------------------------------------------------------------------+

| (3) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:03:04-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.2f7BbU.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/vagrant/git/Carthage/Checkouts/PrettyColors/PrettyColors.xcodeproj -scheme PrettyColors -configuration Release -sdk watchos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build (launched in /Users/vagrant/git/Carthage/Checkouts/PrettyColors)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.2f7BbU.log
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  18.15s user 3.71s system 101% cpu 21.443 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 23 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (4) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:03:27-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.bJY0Rp.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/vagrant/git/Carthage/Checkouts/PrettyColors/PrettyColors.xcodeproj -scheme PrettyColors -configuration Release -sdk watchos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build (launched in /Users/vagrant/git/Carthage/Checkouts/PrettyColors)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.bJY0Rp.log
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.54s user 2.90s system 105% cpu 18.387 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (5) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:03:47-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.NCNe72.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/vagrant/git/Carthage/Checkouts/PrettyColors/PrettyColors.xcodeproj -scheme PrettyColors -configuration Release -sdk watchos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build (launched in /Users/vagrant/git/Carthage/Checkouts/PrettyColors)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.NCNe72.log
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  17.36s user 3.15s system 105% cpu 19.387 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 21 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (6) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:04:09-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.kec6H6.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/vagrant/git/Carthage/Checkouts/PrettyColors/PrettyColors.xcodeproj -scheme PrettyColors -configuration Release -sdk watchos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build (launched in /Users/vagrant/git/Carthage/Checkouts/PrettyColors)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.kec6H6.log
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  20.42s user 3.53s system 104% cpu 22.871 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 25 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (7) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:04:33-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.Y58SKc.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/vagrant/git/Carthage/Checkouts/PrettyColors/PrettyColors.xcodeproj -scheme PrettyColors -configuration Release -sdk watchos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build (launched in /Users/vagrant/git/Carthage/Checkouts/PrettyColors)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.Y58SKc.log
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  19.10s user 3.22s system 104% cpu 21.279 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 23 sec   |
+---+---------------------------------------------------------------+----------+
+------------------------------------------------------------------------------+
|                               bitrise summary                                |
+---+---------------------------------------------------------------+----------+
|   | title                                                         | time (s) |
+---+---------------------------------------------------------------+----------+
| ✓ | git-clone@3.5.1                                               | 77 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Restore Workspace                                             | 5.72 sec |
+---+---------------------------------------------------------------+----------+
| ✓ | Build Carthage                                                | 176 sec  |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 23 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 21 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 25 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 23 sec   |
+---+---------------------------------------------------------------+----------+
| Total runtime: 371 sec                                                       |
+------------------------------------------------------------------------------+
```

##### Bitrise Configuration
bitrise.yml

```yml
---
format_version: 1.3.1
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
workflows:
  benchmark--stdout-error-parsing:
    steps:
    - git-clone@3.5.1:
        inputs:
        - repository_url: https://github.com/jdhealy/Carthage.git
    - script:
        title: Restore Workspace
        inputs:
        - content: git checkout --theirs HEAD~30 Carthage.xcworkspace/contents.xcworkspacedata
        - runner_bin: "/bin/zsh"
    - script:
        title: Build Carthage
        inputs:
        - content: |-
            brew uninstall carthage
            make install
        - runner_bin: "/bin/zsh"
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    before_run: []
    after_run: []
app:
  envs:
  - opts:
      is_expand: false
    CI: 'true'
```
</detail>


The full error is:

````bash
$ hk-maple tests/RoundTrip/gmm_gibbs.0.hk
hk-maple.exe: MapleException:
Error, (in type/complex) time expired

after sending to Maple:
use Hakaru, NewSLO in timelimit(90, RoundTrip(eval(lam(`as`, HArray(HReal(Bound(`>=`,0))), lam(`z`, HArray(HInt(Bound(`>=`,0))), lam(`t`, HArray(HReal()), lam(`docUpdate`, HInt(Bound(`>=`,0)), case(And((size(`z`) = size(`t`)), `docUpdate` < size(`z`)), Branches(Branch(PDatum(true, PInl(PDone)), Bind(app(`dirichlet`, `as`), `theta`, Bind(Plate(size(`as`), `k`, Gaussian(0, 1)), `phi`, Bind(Categorical(ary(size(`as`), `i`, 1)), `zNew`, Bind(Plate(size(`t`), `i`, eval(Bind(Bind(Msum(Weight((idx(`theta`, `zz`) * 1/(Sum(idx(`theta`, x0), x0=0..(size(`theta`))-1))), Ret(Datum(unit, Inl(Done))))), x20, Ret(`zz`)), `zz`, Bind(Msum(Weight((exp(((-(((idx(`t`, `i`) + (-(idx(`phi`, `zz`)))) ^ 2))) * 1/(((2/1) * (1 ^ 2))))) * 1/(1) * 1/(root(((2/1) * Pi), 2))), Ret(Datum(unit, Inl(Done))))), x21, Ret(idx(`t`, `i`)))), `zz`=(case((`i` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `i`))))))), `t`, Ret(`zNew`)))))), Branch(PDatum(false, PInr(PInl(PDone))), Msum()))))))), `dirichlet`=(lam(`as`, HArray(HReal(Bound(`>=`,0))), Bind(Plate((size(`as`) + (-(1))), `i`, BetaD(Sum(idx(`as`, `j`), `j`=(`i` + 1)..(size(`as`))-1), idx(`as`, `i`))), `xs`, Ret(ary(size(`as`), `i`, eval((`x` * case(((`i` + 1) = size(`as`)), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), (1 + (-(idx(`xs`, `i`)))))))), `x`=(Product(idx(`xs`, `j`), `j`=0..(`i`)-1))))))))), HFunction(HArray(HReal(Bound(`>=`,0))), HFunction(HArray(HInt(Bound(`>=`,0))), HFunction(HArray(HReal()), HFunction(HInt(Bound(`>=`,0)), HMeasure(HInt(Bound(`>=`,0))))))), _command=Simplify)) end use;
````


##### [Bitrise Output](https://www.bitrise.io/build/127c2cf9a0bc834e)
```ini

+------------------------------------------------------------------------------+

| (3) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:09:49-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.EMrF13.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
error: No targets could be built for architectures and platforms which support the Thread Sanitizer.
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.86s user 3.46s system 101% cpu 19.999 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 22 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (4) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:10:11-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.JkkTnl.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
error: No targets could be built for architectures and platforms which support the Thread Sanitizer.
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.24s user 2.98s system 105% cpu 18.145 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (5) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:10:31-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.TAuorX.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
error: No targets could be built for architectures and platforms which support the Thread Sanitizer.
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.23s user 2.99s system 105% cpu 18.188 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (6) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:10:51-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.p5VWZJ.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
error: No targets could be built for architectures and platforms which support the Thread Sanitizer.
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.61s user 3.01s system 105% cpu 18.594 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
                                          ▼
+------------------------------------------------------------------------------+

| (7) Build PrettyColors · Time Execution                                     |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-08-01T13:11:11-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
==> Start
==> Switching to working directory: /Users/vagrant/git
*** xcodebuild output can be found in /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/carthage-xcodebuild.qzRism.log
*** Building scheme "PrettyColors" in PrettyColors.xcodeproj
error: No targets could be built for architectures and platforms which support the Thread Sanitizer.
ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current  16.45s user 3.03s system 105% cpu 18.447 total
==> Script finished with exit code: 0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
+------------------------------------------------------------------------------+
|                               bitrise summary                                |
+---+---------------------------------------------------------------+----------+
|   | title                                                         | time (s) |
+---+---------------------------------------------------------------+----------+
| ✓ | git-clone@3.5.1                                               | 69 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Restore Workspace                                             | 4.11 sec |
+---+---------------------------------------------------------------+----------+
| ✓ | Build Carthage                                                | 170 sec  |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 22 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Build PrettyColors · Time Execution                          | 20 sec   |
+---+---------------------------------------------------------------+----------+
| Total runtime: 345 sec                                                       |
+------------------------------------------------------------------------------+
```

##### Bitrise Configuration
bitrise.yml

```yml
---
format_version: 1.3.1
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
workflows:
  benchmark--stdout-error-parsing:
    steps:
    - git-clone@3.5.1:
        inputs:
        - repository_url: https://github.com/jdhealy/Carthage.git
    - script:
        title: Restore Workspace
        inputs:
        - content: git checkout --theirs HEAD~30 Carthage.xcworkspace/contents.xcworkspacedata
        - runner_bin: "/bin/zsh"
    - script:
        title: Build Carthage
        inputs:
        - content: |-
            brew uninstall carthage
            make install
        - runner_bin: "/bin/zsh"
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    - script@1.1.4:
        inputs:
        - runner_bin: "/bin/zsh"
        - content: |-
            cd Carthage/Checkouts/PrettyColors

            time ENABLE_THREAD_SANITIZER=YES carthage build --no-skip-current
            rm -rf ${BITRISE_SOURCE_DIR}/Carthage/Checkouts/PrettyColors/Carthage
        - is_debug: 'yes'
        title: Build PrettyColors · Time Execution
    before_run: []
    after_run: []
app:
  envs:
  - opts:
      is_expand: false
    CI: 'true'
```
</detail>


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/17f4bcdb-25ab-4e33-ad02-bb555e4ff084 "simple-toolchain-chatbot-web-o2tb"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/8c0f4b84-9de3-4e89-87b8-ac70c754a955 "simple-toolchain-chatbot-web-o2tb") deployed [simple-toolchain-chatbot-web-o2tb](https://github.com/rfuchimi/simple-toolchain-chatbot-web-o2tb/releases/tag/deploy-ibm-yp-us-south-contato-o2tb.com.br-prod-20170801-202402 "deploy-ibm-yp-us-south-contato-o2tb.com.br-prod-20170801-202402") to [prod](https://console.bluemix.net/apps/afa93fab-b3a2-49ca-b63d-7e86d7b225f3?env_id=ibm:yp:us-south "ibm:yp:us-south:contato@o2tb.com.br:prod"), including this commit


Can you open issue with this info so we can properly track it? Thanks


added routes for page clicks and controllers. started menu nav - added hamburger menu.


Christian wrote:

> This should be Terminal Normal Mode, or?

It's hard to see what you comment on...

Oh, it appears to be this line:

+|CTRL-W_N|	CTRL-W N	   terminal window: go to Terminal mode

Well, "Terminal mode" is short for "Terminal Normal mode".
Unfortunately CTRL-W T was already taken.

--
DEAD PERSON:  I don't want to go in the cart!
CUSTOMER:     Oh, don't be such a baby.
MORTICIAN:    I can't take him...
DEAD PERSON:  I feel fine!
CUSTOMER:     Oh, do us a favor...
MORTICIAN:    I can't.
                                  The Quest for the Holy Grail (Monty Python)

 /// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Removing problem : it is used by a tribal building to convert to this


I could send you a patch tomorrow

On 1 Aug 2017 10:23 PM, "Patrice Lopez" <notifications@github.com> wrote:

> ah indeed I see !
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/kermitt2/grobid/commit/a35706a2db27cc7d1b24167bbcee1494d9c26246#commitcomment-23421078>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA-rZaDtt7PbzkcK8cTHSDeDr939nVEzks5sT4kzgaJpZM4OqO1->
> .
>


mion carry
```
░░░▐▀▀▄█▀▀▀▀▀▒▄▒▀▌░░░░
░░░▐▒█▀▒▒▒▒▒▒▒▒▀█░░░░░
░░░░█▒▒▒▒▒▒▒▒▒▒▒▀▌░░░░
░░░░▌▒██▒▒▒▒██▒▒▒▐░░░░
░░░░▌▒▒▄▒██▒▄▄▒▒▒▐░░░░
░░░▐▒▒▒▀▄█▀█▄▀▒▒▒▒█▄░░
░░░▀█▄▒▒▐▐▄▌▌▒▒▄▐▄▐░░░
░░▄▀▒▒▄▒▒▀▀▀▒▒▒▒▀▒▀▄░░
░░█▒▀█▀▌▒▒▒▒▒▄▄▄▐▒▒▐░░
░░░▀▄▄▌▌▒▒▒▒▐▒▒▒▀▒▒▐░░
░░░░░░░▐▌▒▒▒▒▀▄▄▄▄▄▀░░
░░░░░░░░▐▄▒▒▒▒▒▒▒▒▐░░░
░░░░░░░░▌▒▒▒▒▄▄▒▒▒▐░░░
```


Full error is:

````bash
$ hk-maple tests/RoundTrip/gmm_gibbs.expected.hk
hk-maple.exe: MapleException:
Error, (in remnull) time expired

after sending to Maple:
use Hakaru, NewSLO in timelimit(90, RoundTrip(lam(`as`, HArray(HReal(Bound(`>=`,0))), lam(`z`, HArray(HInt(Bound(`>=`,0))), lam(`t`, HArray(HReal()), lam(`docUpdate`, HInt(Bound(`>=`,0)), case(And((size(`z`) = size(`t`)), `docUpdate` < size(`z`)), Branches(Branch(PDatum(true, PInl(PDone)), Msum(Weight(((2 ^ ((size(`as`) * 1/(2)) + (size(`t`) * (-1/2)))) * (Pi ^ (size(`t`) * (-1/2))) * exp((Sum((idx(`t`, `_a910`) ^ 2), `_a910`=0..(size(`t`))-1) * (-1/2))) * Product(Product(((`j` + idx(`as`, `_a`)) * 1/(Product((`_a` + Sum(idx(`as`, `_a910`), `_a910`=0..(size(`as`))-1)), `_a`=0..(Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case(idx(`z`, `_a910`) < 0, Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), 1)))))), `_a910`=0..(size(`t`))-1))-1))), `j`=0..(Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case((`_a` = idx(`z`, `_a910`)), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0)))))), `_a910`=0..(size(`t`))-1))-1), `_a`=0..(size(`as`))-1)), Categorical(ary(size(`as`), `zNew6`, (exp((Sum(((Sum(case((`_a910` = case((`i` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `i`))))), Branches(Branch(PDatum(true, PInl(PDone)), idx(`t`, `i`)), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `i`=0..(size(`t`))-1) ^ 2) * 1/((1 + Sum(case((`_a910` = case((`i` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `i`))))), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `i`=0..(size(`t`))-1)))), `_a910`=0..(size(`as`))-1) * 1/(2))) * 1/(root(Product((2 + (Sum(case((`_a` = case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `_a910`))))), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `_a910`=0..(size(`t`))-1) * 2)), `_a`=0..(size(`as`))-1), 2)) * (Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case((`zNew6` = idx(`z`, `_a910`)), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0)))))), `_a910`=0..(size(`t`))-1) + idx(`as`, `zNew6`)) * 1/((Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case(idx(`z`, `_a910`) < 0, Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), 1)))))), `_a910`=0..(size(`t`))-1) + Sum(idx(`as`, `_a910`), `_a910`=0..(size(`as`))-1))))))))), Branch(PDatum(false, PInr(PInl(PDone))), Msum()))))))), HFunction(HArray(HReal(Bound(`>=`,0))), HFunction(HArray(HInt(Bound(`>=`,0))), HFunction(HArray(HReal()), HFunction(HInt(Bound(`>=`,0)), HMeasure(HInt(Bound(`>=`,0))))))), _command=Simplify)) end use;
````


input_processor_refactor (mbadams5) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


Created multidev environment [ivc-web#ci-1](https://dashboard.pantheon.io/sites/bdcdc27b-16d7-444f-800e-c6c37c2b7232#ci-1).

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


Looks like this "returns" comment is the correct one and should be used in all the cases where WebServer instance is being returned


That's the only use case I have for negative contentOffset, idk if there are others. RefreshControl already has a prop called `progressViewOffset` that is Android only so we could make it work on iOS to control where it appears.


Should have a returns comment


@yuriy0 The Maple error is a little different in this context:

````bash
### Error in:   6:RoundTrip:6:3:gmm_gibbs:0
    MapleException:
    Error, (in sdmp:-mul) time expired

    after sending to Maple:
    use Hakaru, NewSLO in timelimit(90, RoundTrip(lam(`as`, HArray(HReal(Bound(`>=`,0))), lam(`z`, HArray(HInt(Bound(`>=`,0))), lam(`t`, HArray(HReal()), lam(`docUpdate`, HInt(Bound(`>=`,0)), case(And((size(`z`) = size(`t`)), `docUpdate` < size(`z`)), Branches(Branch(PDatum(true, PInl(PDone)), Msum(Weight(((2 ^ ((size(`as`) * 1/(2)) + (size(`t`) * (-1/2)))) * (Pi ^ (size(`t`) * (-1/2))) * exp((Sum((idx(`t`, `_a910`) ^ 2), `_a910`=0..(size(`t`))-1) * (-1/2))) * Product(Product(((`j` + idx(`as`, `_a`)) * 1/(Product((`_a` + Sum(idx(`as`, `_a910`), `_a910`=0..(size(`as`))-1)), `_a`=0..(Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case(idx(`z`, `_a910`) < 0, Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), 1)))))), `_a910`=0..(size(`t`))-1))-1))), `j`=0..(Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case((`_a` = idx(`z`, `_a910`)), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0)))))), `_a910`=0..(size(`t`))-1))-1), `_a`=0..(size(`as`))-1)), Categorical(ary(size(`as`), `zNew6`, (exp((Sum(((Sum(case((`_a910` = case((`i` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `i`))))), Branches(Branch(PDatum(true, PInl(PDone)), idx(`t`, `i`)), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `i`=0..(size(`t`))-1) ^ 2) * 1/((1 + Sum(case((`_a910` = case((`i` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `i`))))), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `i`=0..(size(`t`))-1)))), `_a910`=0..(size(`as`))-1) * 1/(2))) * 1/(root(Product((2 + (Sum(case((`_a` = case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), `zNew6`), Branch(PDatum(false, PInr(PInl(PDone))), idx(`z`, `_a910`))))), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0))), `_a910`=0..(size(`t`))-1) * 2)), `_a`=0..(size(`as`))-1), 2)) * (Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case((`zNew6` = idx(`z`, `_a910`)), Branches(Branch(PDatum(true, PInl(PDone)), 1), Branch(PDatum(false, PInr(PInl(PDone))), 0)))))), `_a910`=0..(size(`t`))-1) + idx(`as`, `zNew6`)) * 1/((Sum(case((`_a910` = `docUpdate`), Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), case(idx(`z`, `_a910`) < 0, Branches(Branch(PDatum(true, PInl(PDone)), 0), Branch(PDatum(false, PInr(PInl(PDone))), 1)))))), `_a910`=0..(size(`t`))-1) + Sum(idx(`as`, `_a910`), `_a910`=0..(size(`as`))-1))))))))), Branch(PDatum(false, PInr(PInl(PDone))), Msum()))))))), HFunction(HArray(HReal(Bound(`>=`,0))), HFunction(HArray(HInt(Bound(`>=`,0))), HFunction(HArray(HReal()), HFunction(HInt(Bound(`>=`,0)), HMeasure(HInt(Bound(`>=`,0))))))), _command=Simplify)) end use;
### Error in:   6:RoundTrip:6:3:gmm_gibbs:1
    haskell\Language\Hakaru\Pretty\Maple.hs:(173,1)-(228,35): Non-exhaustive patterns in function mapleSCon
````


Not so bad....


doesn't return a block of bytes


Thanks for the feedback. I'll try to test this.


![](https://github.trello.services/images/mini-trello-icon.png) [Add Upload Instructions to README](https://trello.com/c/Z6DdZCqW/41-add-upload-instructions-to-readme)


I've only just come across this commit when having a fiddle through the git history for something. Why was this line added?


- Electron has been updated! I'd presume to the latest current version, which would be Electron v1.7.5 beta. Anyway, this should fix quite a few (old) bugs!

### New variables
- `t.CallModalScenes`
- `PRIVATE_CHANNEL_CALL_SELECT_CHANNEL: null,`
- `CALL_ENQUEUE_RING: null,`

### New strings
- `CONNECT_TO_VIDEO: "Connect to Video",`
- `SHARE_LINK: "Share Link",`
-  Removed and added:
```diff
-            ON_THE_CALL: "On the call",
-            NOT_ON_THE_CALL: "Not on the call",
+            IN_THE_VOICE_CHANNEL: "In the voice channel",
+            NOT_IN_THE_VOICE_CHANNEL: "Not in the voice channel",
```
- `DURATION_MINS: "{mins, plural, =1 {1 min} other {{mins} mins}}",`
- `COLLAPSE_CATEGORY: "Collapse Category",`


Please, don't hand-edit this file or indeed any file in `grammars` directory that aren't in `grammars/src`. These files are all automatically generated, so once you (or we) rebuild the new grammar, any hand-made changes will be completely lost. Please follow the instructions for setting up the development environment (https://github.com/MagicStack/MagicPython#development) and just use `make test` to build and test the grammar.

I'm guessing that you've edited the `.cson` file directly mainly because I'd have expected identical change in  `.tmLanguage` otherwise.


Please *remove* this rule from `MagicPython.syntax.yaml` to avoid code duplication. It will be properly included by the grammar build process.


This file is kind of a "macro" file, so please don't include just plain rules here. Instead the `codetags` rule belongs to the `regexp-common.inc.syntax.yaml` from which it will be correctly imported.

Much like the `fstring-formatting-braces` rule, please *remove* it from the `MagicPython.syntax.yaml`, when making a copy.


I feel like we should probably use `self.path.insert(0, path)`, otherwise `kivyunittest.main` is picked up (in unit test imports) rather than the one we test against.


Is that change alright? the memcpy is commented out


thanks in advance !


I do check log in dev/null, I am awesome :stuck_out_tongue_closed_eyes:


Yikes. That was supposed to go on a branch first. :-1:


147520311-CoolingPanelUACalcBug (RKStrand) - x86_64-MacOS-10.9-clang: OK (2572 of 2572 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)


input_processor_refactor (mbadams5) - Win64-Windows-7-VisualStudio-14: Build Failed

Failures:

integration Test Summary
 * Passed: 1
 * Failed: 604

regression Test Summary
 * Passed: 601
 * Failed: 2

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


input_processor_refactor (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: Tests Failed (719 of 1394 tests passed, 0 test warnings)

Failures:

EnergyPlusFixture Test Summary
 * Passed: 1
 * OTHER_FAULT: 498

InputProcessorFixture Test Summary
 * Passed: 5
 * OTHER_FAULT: 43

SurfaceGeometryUnitTests Test Summary
 * Passed: 18
 * OTHER_FAULT: 5

WaterCoilsTest Test Summary
 * Passed: 1
 * OTHER_FAULT: 7

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


git init


oops, duplicated .h and .cpp entries


git add


It makes me uncomfortable to have 2D multiplication hard-coded like that.  Why not use a `zip` ?  [Plus, shouldn't that be `getX` rather than `getx` ?]

Also, should negation be done via `map` (the Haskell function) of unary negation?  I don't like this multiplication by -1.0.


Bro me interesa repararlo realmente lo necesito para mi servidor ya que un 1 cc es importante para los players y me mencionan que es molesto no poder llenar la bp de gold


@a-frobot docs-v0.6.0


@szymczdm Should `Client` and `Cstmr` even be created (see lines 96 and 97)? The current `stakeholderGeneral` function that is used to create the **Stakeholders** section automatically creates the subsections for "The Client" and "The Customer", which is why I'm hesitant in breaking up the `StkhldrProg` type...


this is kind of a weird response, why is value an array?


I think there's a bug in the vector projection function?

Also, shouldn't we be able to write these functions at a much higher level of abstraction, and then generate the above low-level looking "implementation"?


Thanks! GTK+ is full of traps, indeed. A handy macro or something to wrap this magic would be helpful, I think.


Isnt previous version cleanier? :p


Thanks, man! Love it! ;)


Sure @CarsonF issue raised here:
https://github.com/bolt/bolt/issues/6873


Can't you use the derived `Eq` and `Ord` instances?


There will be alot of restrictions and checks in the future, so first version is cleanier I think


Thank you very much for the explanation, Wendy! 👍


The `timelimit` I used at https://list.indiana.edu/sympa/arc/ppaml-l/2017-08/msg00001.html is 300 seconds, because indeed `gmm_gibbs.hk` takes a long time to simplify.


+1 for deprecation cycle for all public methods.


Perfect, didn't know about this c++11 syntax. :D


The `timelimit` I used at https://list.indiana.edu/sympa/arc/ppaml-l/2017-08/msg00001.html is 300 seconds, because indeed `gmm_gibbs.hk` takes a long time to simplify. I haven't tried simplifying the output of simplifying `gmm_gibbs.hk` though.


Yes, its nice, visual studio keeps re-formating this code for me :/


Wonderful.


Same as before, there will be more checks in the future.


Yep. That's fine.


There have been some updates in my version, but most of them are documentation changes and unit test things. Code-wise you are close to updated. Just FYI, in case you see you have an old version


m_(variable) is a pretty standard convention for naming _member_ variables, but I'm all for using some other convention to denote mutexes (muticies?)


I've used formula from wiki,it's works. But by the terms of task,for inputing value "6" it should return only 4 lines... Is it mistake in task?


регистрация/index.html

удалить br )


Nice. I'll try it out!


Removing it for now.


kivy


This update broke the font style for me.
Before, the font size was like how it is in GMS.

**In-game example)**
![.](https://cdn.discordapp.com/attachments/236180502200057856/342047757609205760/ingame.png)

**Before the update)**
![.](https://cdn.discordapp.com/attachments/236180502200057856/342047774629691392/before.png)

**After the update)**
![.](https://cdn.discordapp.com/attachments/236180502200057856/342047773803282433/after.png)

My MapRenderFonts.cs: https://pastebin.com/SBsw8FE4
My MapRenderUIRoot.cs: https://pastebin.com/vhEbtZiL


Please leave your pull request open until you get feedback from us :) In the typical git workflow, you'll commit multiple times while working on a single change, which means that (without the PR) we'd only be able to comment on the most recent commit.


The original version doesn't work on my computer. So I make a little modification. The warnings I have are
Warning messages:
1: In plot.window(...) : "label" is not a graphical parameter
2: In plot.window(...) : "arrowhead.cex" is not a graphical parameter
3: In plot.window(...) : "edge.col" is not a graphical parameter
4: In plot.xy(xy, type, ...) : "label" is not a graphical parameter
5: In plot.xy(xy, type, ...) : "arrowhead.cex" is not a graphical parameter
6: In plot.xy(xy, type, ...) : "edge.col" is not a graphical parameter
7: In axis(side = side, at = at, labels = labels, ...) :
  "label" is not a graphical parameter
8: In axis(side = side, at = at, labels = labels, ...) :
  "arrowhead.cex" is not a graphical parameter
9: In axis(side = side, at = at, labels = labels, ...) :
  "edge.col" is not a graphical parameter
10: In axis(side = side, at = at, labels = labels, ...) :
  "label" is not a graphical parameter
11: In axis(side = side, at = at, labels = labels, ...) :
  "arrowhead.cex" is not a graphical parameter
12: In axis(side = side, at = at, labels = labels, ...) :
  "edge.col" is not a graphical parameter
13: In box(...) : "label" is not a graphical parameter
14: In box(...) : "arrowhead.cex" is not a graphical parameter
15: In box(...) : "edge.col" is not a graphical parameter
16: In title(...) : "label" is not a graphical parameter
17: In title(...) : "arrowhead.cex" is not a graphical parameter
18: In title(...) : "edge.col" is not a graphical parameter


Are you sure that this information should be here?


O sube tus sources bro actualizadas y nomas lo compilo


@goutamtadi1 looks like you published without a date (required) and an image (optional).


I have renamed the returned data to _ret_ to make it more verbose and match the _runJob_ func style.


Does that v2 mean v2 api?
according to https://dev.twitch.tv/docs/, use V5 instead

from twitch example https://dev.twitch.tv/docs/v5/reference/ingests/
https://api.twitch.tv/kraken/ingests?client_id=uo6dggojyb8d6soh92zknwmi5ej1q2


as aspas devem estar dentro do parenteses. XD


Why remove this?


I'm glad that you're considering special cases and edge cases, that's exactly what you'll need to do in an interview :)

In the future, try to leave us a note about what questions you've "asked" the interviewer and what their answers were. In this case, it looks like you're only considering characters from the alphabet and that capital and lower case letters should be treated the same.


C0103 is the code name for "Invalid constant name" error message. You can disable it and see what happens; It will keep asking you to update some variables names to be upper case if they're not constants :/


input_processor_refactor (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Tests Failed (720 of 1999 tests passed, 0 test warnings)

Failures:

EnergyPlusFixture Test Summary
 * Passed: 1
 * OTHER_FAULT: 498

InputProcessorFixture Test Summary
 * Passed: 5
 * OTHER_FAULT: 43

integration Test Summary
 * Passed: 1
 * Failed: 604

SurfaceGeometryUnitTests Test Summary
 * Passed: 18
 * OTHER_FAULT: 5

WaterCoilsTest Test Summary
 * Passed: 1
 * OTHER_FAULT: 7

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


The title of this commit is not correct :)


Hi Dan,
thanks for your contribution. I'm an owner of an Evohome thermostat with 4 zones, and I'd really like to control it from HA not by setting the individual temperatures, but changing the thermostat mode (e.g keeping in "away" mode if the house is empty).

I'm not a Python programmer, but I'm trying to involve the original developers of the component and the underlying library. I also reached Honeywell for some help, and a nice guy from the company told me that the API call used in the library is old, and he's sending me some official documentation.

If you have some spare time and are willing to help, I'll share with you the docs and any news from other contributors.

Obviously the invitation is open to anyone else reading this comment ( @rcloran , @titilambert , @turbokongen ? ) and willing to help. :-)

Thanks,
Nicholas


Thanks for testing/including your test cases!


interesting test... how does a commit has no change?


teste de code review


@jensens Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.recipe.codeanalysis/6/violations
```
plone/recipe/codeanalysis/analyser.py:59:9: T003 print function found.
plone/recipe/codeanalysis/analyser.py:59:15: S100 First argument on the same line
plone/recipe/codeanalysis/analyser.py:59:53: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:66:13: T003 print function found.
plone/recipe/codeanalysis/analyser.py:157:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:157:35: C812 missing trailing comma
plone/recipe/codeanalysis/analyser.py:179:75: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:190:58: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:190:77: C812 missing trailing comma
plone/recipe/codeanalysis/analyser.py:201:21: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:201:75: C812 missing trailing comma
plone/recipe/codeanalysis/analyser.py:206:21: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/analyser.py:206:60: C812 missing trailing comma
plone/recipe/codeanalysis/analyser.py:232:44: S100 First argument on the same line
plone/recipe/codeanalysis/analyser.py:234:44: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:24:9: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:24:10: C812 missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:54:39: S100 First argument on the same line
plone/recipe/codeanalysis/clean_lines.py:54:58: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:55:56: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:55:63: C812 missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:63:35: S100 First argument on the same line
plone/recipe/codeanalysis/clean_lines.py:63:54: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:64:52: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/clean_lines.py:64:59: C812 missing trailing comma
plone/recipe/codeanalysis/check_manifest.py:21:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/check_manifest.py:21:17: C812 missing trailing comma
plone/recipe/codeanalysis/check_manifest.py:28:25: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/check_manifest.py:43:48: S100 First argument on the same line
plone/recipe/codeanalysis/check_manifest.py:45:48: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/check_manifest.py:50:38: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:40:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:40:20: C812 missing trailing comma
plone/recipe/codeanalysis/__init__.py:44:54: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:87:59: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:87:74: C812 missing trailing comma
plone/recipe/codeanalysis/__init__.py:95:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:96:61: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:96:70: C812 missing trailing comma
plone/recipe/codeanalysis/__init__.py:97:14: C812 missing trailing comma
plone/recipe/codeanalysis/__init__.py:155:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/__init__.py:155:32: C812 missing trailing comma
plone/recipe/codeanalysis/__init__.py:176:13: T003 print function found.
plone/recipe/codeanalysis/__init__.py:191:9: T003 print function found.
plone/recipe/codeanalysis/__init__.py:200:9: T003 print function found.
plone/recipe/codeanalysis/__init__.py:248:9: T003 print function found.
plone/recipe/codeanalysis/__init__.py:248:15: S100 First argument on the same line
plone/recipe/codeanalysis/__init__.py:249:22: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/jshint.py:33:37: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/flake8.py:23:32: C812 missing trailing comma
plone/recipe/codeanalysis/flake8.py:35:17: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/flake8.py:35:36: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_jshint.py:113:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_jshint.py:113:29: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_jshint.py:148:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_jshint.py:148:37: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:24:25: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:24:42: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:29:17: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:29:37: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:35:55: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:35:75: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:40:25: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:40:67: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:52:25: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_check_manifest.py:52:67: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_jscs.py:82:28: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_jscs.py:82:36: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_csslint.py:24:0: P103 other string does contain unindexed parameters
plone/recipe/codeanalysis/tests/test_flake8.py:80:28: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:80:36: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:105:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:105:53: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:118:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:118:53: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:128:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_flake8.py:128:45: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_i18ndude.py:70:28: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_i18ndude.py:70:36: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:76:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:76:28: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:86:21: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:86:27: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:92:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_script.py:92:28: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:51:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:51:20: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:64:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:64:22: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:68:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:68:21: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:83:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:83:22: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:107:27: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:107:78: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:139:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:139:32: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:152:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:152:60: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:160:13: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_recipe.py:160:32: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_clean_lines.py:43:28: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_clean_lines.py:43:36: C812 missing trailing comma
plone/recipe/codeanalysis/tests/test_clean_lines.py:62:28: S101 Multi-line construct missing trailing comma
plone/recipe/codeanalysis/tests/test_clean_lines.py:62:36: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


input_processor_refactor (mbadams5) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


Tentative fix: 1a23c5dcf6c8d1f066ad735adfdd10b095d8ca43


Excellent naming!


`git commit --allow-empty`


[R/internal-cbList.R:23:1:](https://github.com/hbc/bcbioSinglecell/blob/48817246fa6b9c0cfc2cac4623f799f313ee983f/R/internal-cbList.R#L23) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/internal-cbList.R:24:1:](https://github.com/hbc/bcbioSinglecell/blob/48817246fa6b9c0cfc2cac4623f799f313ee983f/R/internal-cbList.R#L24) *style:* **Trailing blank lines are superfluous.**
```r

^
```
[R/internal-cbList.R:25:1:](https://github.com/hbc/bcbioSinglecell/blob/48817246fa6b9c0cfc2cac4623f799f313ee983f/R/internal-cbList.R#L25) *style:* **Trailing blank lines are superfluous.**
```r

^
```


I think we are all in agreement here. I was too eager here, removing the method, instead of figuring out deprecation pattern which is generally followed for integration endpoints (for frameworks; public endpoints for app code have much longer deprecation cycle).


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210729 "deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210729") to [prod](https://console.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19?env_id=ibm:yp:us-south "ibm:yp:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210735 "deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210735") to [prod](https://console.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19?env_id=ibm:yp:us-south "ibm:yp:us-south:user@ibm.com:prod"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-Prod-20170801-210740 "deployed-2-env-Prod-20170801-210740") to [Prod](https://console.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19?env_id=ibm:yp:us-south "There was a problem retrieving the space name"), including this commit


Bluemix toolchain: An unknown tool deployed [testRepo-Traceability](https://github.com/idsdev/testRepo-Traceability/releases/tag/deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210748 "deployed-2-env-ibm-yp-us-south-user-ibm.com-prod-20170801-210748") to [prod](https://console.bluemix.net/apps/6e3bc311-c83d-4cd1-a457-99d9a5f20f19?env_id=ibm:yp:us-south "ibm:yp:us-south:user@ibm.com:prod"), including this commit


Tesing v1c without correction of negative difficulties with averages. Fount this interesting - after forward stamping block one hour ahead too large solve time and negative solve time do not counterweigh each other when first one goes past M window:

```
    Solve time: 242
    Solve time: 284
    Solve time: 291
    Solve time: 127
    Solve time: 157
    Solve time: 54
    Solve time: 339
    Solve time: 2160
    Solve time: -1863
    Solve time: 3
    Solve time: 369
    Solve time: 556
    Solve time: 30
    Solve time: 546
    Solve time: 287
    Solve time: 53
    Temp N T: 3635, M T: 19, O T: 916
    Difficulty for N: 3271.91, M: 248966, O: 1864.06
    nextD: 84700.6
```
average difficulty for that hashrate on testing machine is 4000


Thanks @wanam, you're right.


Perfect! I was just trying to debug this behavior.

Do you know how soon this change will hit npm?


haha you read my fork branches funny, well i want to make a bunch of changes and you can cherry pick the ones you like, this change actually needs to be rebased into another commit, need some commit clean up


Your solution is very close. Try the following test case: "a**bacde**"


It should be as soon as @lozjackson hits the publish button


👍

2017-07-31 21:32 GMT+02:00 Miczys <notifications@github.com>:

> @DariuszLuber <https://github.com/dariuszluber>
> https://miczys.github.io/SitOnChair/
> chyba sie udalo :)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Miczys/SitOnChair/commit/c6cb4614b758af954fdfdba9ada8b65728f2a27f#commitcomment-23398674>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AThHZfXJYCGX6nxazEgrqBTaaAf1SQ1_ks5sTiu1gaJpZM4OoaTT>
> .
>


It returns an array because there can be multiple values when there are multiple classification fields. But, I can parse it into a string like esri does.


Bluemix [toolchain](https://console.bluemix.net/devops/toolchains/ab6395b6-6c2c-4065-8e18-3164053feacb "LISA_ER"): [Delivery Pipeline](https://console.bluemix.net/devops/pipelines/7ecd5b84-0c0a-4aed-ac63-5b0b50bd991b "LISA_ER") deployed [LISA_ER](https://github.com/paulonannini/LISA_ER/releases/tag/deploy-ibm-yp-us-south-paulonannini-gmail.com-dev-20170801-210936 "deploy-ibm-yp-us-south-paulonannini-gmail.com-dev-20170801-210936") to [dev](https://console.bluemix.net/apps/3942b010-d344-404c-9c14-4e43ea41e993?env_id=ibm:yp:us-south "ibm:yp:us-south:paulonannini@gmail.com:dev"), including this commit


looking at this with naïve eyes... ( I have not used X-Ray ), this value could contain something similar to an ARN. if it did, the owner of that ARN could be permissive (allow writes from anywhere) and capture state/stacktraces of code/tests being built with this docker image.

If instead, its an artifact of that particular lambda invocation, then there is not a security implication.


What happens if you don't use G_ADD_PRIVATE here? I'm surprised that's needed. We don't use that in EphyWindow, and it's not mentioned in the GObject tutorial documentation for implementing interfaces.


hola


- Some small changes to server/channel muting, likely to do with channel categories.


okay makes sense then


Just realised that naming a function renderSortedList might create the expectation that the result will be an ordered list `<ol>`. Should be `renderListOrderedAlphabetically` for full verbosity.


Yeah, thanks for pointing it out. I fixed it in another commit.


Nice!


![](https://github.trello.services/images/mini-trello-icon.png) [Optymalizacja](https://trello.com/c/j0EcwAWg/146-optymalizacja)


The `timelimit` I used at https://list.indiana.edu/sympa/arc/ppaml-l/2017-08/msg00001.html is 300 seconds, because indeed `gmm_gibbs.hk` takes a long time to simplify.


Ops


i switched from OOP style to functional programming syle a while ago, lamdba functions (also called closures) are pretty common there, thats basically a function defined insided a function


I really agree with this. "I propose fairness needs Truth, Trust, and the willingness to Communicate."


Aw, drat. Silly me, this doesn't work. You're going to have an empty user agent now, unless the user has manually overridden the user agent.

So this needs more work. You'll have to move the functions for computing the user agent out of ephy-embed-prefs and down into lib. But it will be worth it in the end: I really think enforcing layering does result is better-maintainable code.

The EphyTabsCatalog work all looks good. That's better than I expected it to turn out.


Yes it's similar to a thing in C#.


That text is not coming from anywhere. You have to change `mapTo` to `map(text =>`


You're quite right; I wasn't thinking, sorry.


makes more sense to do something like `{count: 3, genus: 'Southern Magnolia', diameter: 75}`


try out vim ^^


ND/MN, rather


input_processor_refactor (mbadams5) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed (1338 of 2636 tests passed, 0 test warnings)

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


@mcatanzaro Removing G_ADD_PRIVATE results in a crash at startup: https://paste.gnome.org/ppq83mtns. It is required because EphyEmbedShell is defined with private data.


@PerfectPixel Apologies for the delay.. it is now published on npm


was reading on some issues... :D


now worries, you are doing a great job 👍


147520311-CoolingPanelUACalcBug (RKStrand) - i386-Windows-7-VisualStudio-14: OK (2574 of 2578 tests passed, 0 test warnings)

Failures:

EnergyPlusFixture Test Summary
 * Passed: 496
 * Failed: 4

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


Ran an "npm update --save --dev"


You don't need to call `super()` when you're not `extend`ing another class


<%= image_tag "item_img_resize.jpg", class: "card-img-top" %>


allright, i think this function complexity is okay. Saw some monster functions (switch case), exact like inix.  Reminds me of the IDA C code that i saw some years ago, i mean your code is very close to the inix implementatiom, i like that, some things that inix did wrong should be corrected


I put sleep 7 days ago back to 180 and have had no issues since with duplicate ad deletions or image tokens


Done. This is much easier to do anyways.


You can skip creating a local variable here by replacing these lines with: `mMinutes = (NumberPicker) findViewById(R.id.minutes);`


<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
<script>
  (adsbygoogle = window.adsbygoogle || []).push({
    google_ad_client: "ca-pub-2190969569968181",
    enable_page_level_ads: true
  });
</script>


It's good practice to name subclasses after their parents – for `Activities`, this normally means suffixing classes with `*Activity`, e.g. `IntervalSetupActivity`


When trying to return to the previous screen, rather than starting a new instance of the Activity you should instead just call `finish()`


its called https://en.wikipedia.org/wiki/Fluent_interface


@jsonbank I'm *really* confused as to the scenario in which you think this docker image might be run where such a thing could happen.

Just to make sure we're on the same page:

1. This project is a docker image to emulate the live lambda environment for local testing purposes
2. The `_X_AMZN_TRACE_ID` value you see is hardcoded. You can see the value it has here in the code: `Root=1-dc99d00f-c079a84d433534434534ef0d;Parent=91ed514f1e5c03b2;Sampled=0`
3. Unless someone changes it manually, that value will never change. I have no idea why someone would want to change it.
4. Even if they did change it – they'd have to change it something real to reveal anything. I actually have no idea how they'd change it to a "real" trace ID in a timely fashion anyway.
5. Even if they did change it to something real, they'd have to somehow output it in a console log or similar.
6. That console log would have to be publicly available to reveal anything.

I feel like there might be a disconnect happening here with what you think this project is? You're not confusing it with https://github.com/lambci/lambci in some way by any chance?


ultimo cambio realizado por visual studio  2016


Yes, it is because it is passing out of the 2nd N=8 window.  One more step and it will correct itself.  It will happen again at the end.  I had not thought about this because I thought you could store the limited solvetime on the block chain.    So if you can store the limited ST values as the correct solvetime on the blockchain, then it will happen only the first time.


na jau visai ir neblogai gaunasi!


> The title of this commit is not correct :)

Oops, yes. I'm gonna change with the next rebase.


You probable meant `There are too few articles.`


/** URL for earthquake data from the USGS dataset */
    private static final String USGS_REQUEST_URL =
            "https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson&orderby=time&minmag=6&limit=10";

change to that for error 301


Why do you need the first check? When will the `.length` be less than zero?


You don't want to add a Maven dependency to gson 2.7, as it's already available in the TP. You're adding an extra jar.

 Rather add com.google.gson;bundle-version="2.7.0" to your MANIFEST.MF (see .core)


Please extract the magic number 3 into a constant


@somedayrainbows thanks for testing this, should be working now


this extra jar needs to be removed


nepatinka man tavo evento pavadinimas - turetu buti - ``clientAdded``, o tada jau atitinkamas subscriberis atliks tai ka reikia


se habilita la validación de catpcha de Google


147520311-CoolingPanelUACalcBug (RKStrand) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


![screen_2017-08-01 14 31 41](https://user-images.githubusercontent.com/18017741/28848091-256067ea-76be-11e7-8179-a0610c54ec88.jpg)
![screen_2017-07-31 15 08 46](https://user-images.githubusercontent.com/18017741/28848149-5e3f20b0-76be-11e7-9668-b0e87f5e2836.jpg)
![screen_2017-07-31 16 59 56](https://user-images.githubusercontent.com/18017741/28848168-6e7b4d00-76be-11e7-973c-38e4e0ec2475.jpg)
![screen_2017-07-31 17 07 48](https://user-images.githubusercontent.com/18017741/28848191-837a8112-76be-11e7-9fe3-148d5894f2dc.jpg)
![screen_2017-07-31 17 09 51](https://user-images.githubusercontent.com/18017741/28848200-88817116-76be-11e7-9a15-7a5fa3e09dd8.jpg)


Fixed via PR#216.


There are a couple of problems here:

1. You're not using variable `i` anywhere. Consider `while` loop instead.
1. The loop is very ineffective and will probably run thousands of times on small articles list because of how `Math.random` works. Consider another algorithm instead.


![screen_2017-08-01 13 05 29](https://user-images.githubusercontent.com/18017741/28848258-bcfeb354-76be-11e7-9119-944659d2bf2d.jpg)
![screen_2017-08-01 13 20 23](https://user-images.githubusercontent.com/18017741/28848260-bedda39c-76be-11e7-9dee-0453f98bf750.jpg)
![screen_2017-08-01 14 14 21](https://user-images.githubusercontent.com/18017741/28848265-c0963294-76be-11e7-87d2-cb5309b134fc.jpg)
![screen_2017-08-01 14 16 17](https://user-images.githubusercontent.com/18017741/28848273-cd6af07c-76be-11e7-9e90-8c130af0956a.jpg)
![screen_2017-08-01 14 16 43](https://user-images.githubusercontent.com/18017741/28848278-d02fa53c-76be-11e7-8f5c-5b55889e06ca.jpg)
![screen_2017-08-01 14 20 01](https://user-images.githubusercontent.com/18017741/28848282-d21e2f26-76be-11e7-9bfb-68dd240fe701.jpg)


"paslepciau" ``private`` funkcijas atitinkamuose servisuose, kad tavo kontroleriai pasiliktu labai kudi. Kodel? sitas kodas gali potencialiai dublikuoits - isivaizduok, kad implementini API, kur tau reikia grazinti ta pacia infomacija..


Thanks for catching this.
I extended a bit the fix (https://github.com/brainstorm-tools/brainstorm3/commit/6ce41e96a8fd21c4e0c2805c8da5a65691c48e68). Does it is still works?
(I don't have two screens to test it here...)


`git status`


Since you're passing the same argument to the callback function, you could just write it as `.then(filter_articles_by_length)`. This will do exactly the same semantically. Please don't over-use this, though, since this makes code more implicit and will make refactoring harder.


`git diff`


Nah, I'd never leave IntelliSense


kitas dalykas - o cia jau bus kitos savaites taskas - tavo kontroleris yra potencialiai labai "sunkus" - isivaizduok, jog turetum didele duombaze su milijonais klientu... Taigi - kaip paotimizuotum?


@tomgross Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.linkintegrity/33/violations
```
plone/app/linkintegrity/testing.py:59:9: D001 found xmlconfig.file( replace it with self.loadZCML(
plone/app/linkintegrity/testing.py:59:24: S100 First argument on the same line
plone/app/linkintegrity/testing.py:60:24: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:136:49: S100 First argument on the same line
plone/app/linkintegrity/testing.py:137:49: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:144:5: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:144:50: C812 missing trailing comma
plone/app/linkintegrity/testing.py:149:5: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:149:50: C812 missing trailing comma
plone/app/linkintegrity/testing.py:154:5: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:154:49: C812 missing trailing comma
plone/app/linkintegrity/testing.py:158:5: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/testing.py:158:49: C812 missing trailing comma
plone/app/linkintegrity/handlers.py:30:1: C901 'findObject' is too complex (12)
plone/app/linkintegrity/handlers.py:126:5: T000 Todo note found.
plone/app/linkintegrity/handlers.py:139:17: S100 First argument on the same line
plone/app/linkintegrity/handlers.py:140:10: S100 First argument on the same line
plone/app/linkintegrity/handlers.py:140:10: S100 First argument on the same line
plone/app/linkintegrity/handlers.py:141:28: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/handlers.py:141:28: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/retriever.py:60:35: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/utils.py:13:20: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/utils.py:13:42: C812 missing trailing comma
plone/app/linkintegrity/utils.py:40:20: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/utils.py:40:42: C812 missing trailing comma
plone/app/linkintegrity/upgrades.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/upgrades.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/upgrades.py:4:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/upgrades.py:7:25: Q000 Remove bad quotes.
plone/app/linkintegrity/upgrades.py:8:1: I001 isort found an import in the wrong position
plone/app/linkintegrity/upgrades.py:9:1: I001 isort found an import in the wrong position
plone/app/linkintegrity/upgrades.py:11:1: I001 isort found an import in the wrong position
plone/app/linkintegrity/upgrades.py:32:41: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/upgrades.py:42:5: T000 Todo note found.
plone/app/linkintegrity/upgrades.py:47:25: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/upgrades.py:47:25: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/upgrades.py:47:76: C812 missing trailing comma
plone/app/linkintegrity/browser/info.py:43:5: C901 'DeleteConfirmationInfo.get_breaches' is too complex (16)
plone/app/linkintegrity/browser/info.py:67:61: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:82:29: S100 First argument on the same line
plone/app/linkintegrity/browser/info.py:82:36: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:83:26: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:83:45: C812 missing trailing comma
plone/app/linkintegrity/browser/info.py:85:34: S100 First argument on the same line
plone/app/linkintegrity/browser/info.py:85:41: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:87:21: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:87:38: C812 missing trailing comma
plone/app/linkintegrity/browser/info.py:89:36: S100 First argument on the same line
plone/app/linkintegrity/browser/info.py:89:43: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:91:21: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:91:45: C812 missing trailing comma
plone/app/linkintegrity/browser/info.py:97:25: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/browser/info.py:97:37: C812 missing trailing comma
plone/app/linkintegrity/browser/update.py:88:16: S001 found module formatter
plone/app/linkintegrity/tests/test_upgrade.py:6:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/tests/test_upgrade.py:6:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/tests/test_upgrade.py:6:1: I003 isort expected 1 blank line in imports, found 0
plone/app/linkintegrity/tests/test_upgrade.py:11:1: I001 isort found an import in the wrong position
plone/app/linkintegrity/tests/base.py:31:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/base.py:42:34: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_imagescales.py:38:19: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_imagescales.py:53:24: S100 First argument on the same line
plone/app/linkintegrity/tests/test_imagescales.py:53:30: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_imagescales.py:54:18: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_references.py:44:31: S100 First argument on the same line
plone/app/linkintegrity/tests/test_references.py:45:52: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_references.py:64:11: T000 Todo note found.
plone/app/linkintegrity/tests/test_references.py:87:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_references.py:87:23: C812 missing trailing comma
plone/app/linkintegrity/tests/test_references.py:99:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_references.py:101:23: C812 missing trailing comma
plone/app/linkintegrity/tests/test_references.py:112:26: S100 First argument on the same line
plone/app/linkintegrity/tests/test_references.py:113:26: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_references.py:125:26: S100 First argument on the same line
plone/app/linkintegrity/tests/test_references.py:126:26: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:26:32: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:27:44: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:43:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:46:35: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:53:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:54:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:55:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:56:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:59:11: T000 Todo note found.
plone/app/linkintegrity/tests/test_functional.py:80:56: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:96:62: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:103:27: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:103:76: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:104:34: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:119:56: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:123:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:124:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:148:68: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:149:41: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:149:65: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:150:14: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:153:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:154:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:155:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:156:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:173:43: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:185:30: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:189:22: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:189:77: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:190:34: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:192:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:193:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:212:68: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:213:38: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:213:59: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:214:14: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:217:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:218:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:252:27: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:252:72: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:253:37: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:255:23: S100 First argument on the same line
plone/app/linkintegrity/tests/test_functional.py:256:23: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:295:68: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:296:38: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:296:59: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:297:14: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:300:54: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:304:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:304:34: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:308:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:308:34: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:317:47: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:326:60: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:335:68: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:336:41: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:336:65: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:337:14: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:342:13: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:342:34: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:374:68: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:375:41: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:375:65: C812 missing trailing comma
plone/app/linkintegrity/tests/test_functional.py:376:14: C812 missing trailing comma
plone/app/linkintegrity/tests/test_circular.py:48:66: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_circular.py:65:60: S101 Multi-line construct missing trailing comma
plone/app/linkintegrity/tests/test_circular.py:67:60: S101 Multi-line construct missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


@msva `original-source.otf` has been cleaned up (and subsequently much smaller now as well).
I have also corrected the metadata in the file.

--

Still working on updating the symbols.. was seeing an issue while re-patching them


In JS world, most common practice is to camelCase identifiers. Consider `setDefaultSettings` over underscored version everywhere.


meu primeiro comentário sem importância para este commit.


Also, I personally think for cases like this `function` is more explicit. Please also note that `=>` changes semantics around `this`. It does the same thing in this case, though, so it's more a style issue.


i don't know yet

I think what i actually want is more like this

```perl
/[:alnum:_-. ]{1,255}/
```

assuming 255 is `NAME_MAX`.


Meta-programming FTW! Instead of hardcoding and repeating keys as string, consider abstracting this to an array of keys to check + a loop over it with a single check inside.


Previous function declaration can be self-called here by adding `()` instead


I didn't see the polypill for `Object.values` anywhere...


Consider `Array.prototype.reduce` instead of for loop


Why do you need this assignment here?


You may be interested by this PR adding support for VS2015 for python 2.7
See https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/pull/188

Otherwise, support for VS2015 and more recent python version was added in https://github.com/python-cmake-buildsystem/python-cmake-buildsystem/commit/37ed7482b80ec505296ea5a226bbab6673c52dea


This should not be part of the tests.... The migration should have been created and committed before


Instead of assembling everything by a single node, you could just use the `innerHTML` with a HTML as string


Consider `Array.prototype.map` instead


Added a blank Readme.txt file here, to practice using Git and commits on this initial repository of mine


If you've got a minute would you mind doing another release? v0.1.8 is broken without this. Thanks!


You could use shorthand property:

```js
{
  item_id
}
```


Oops, this is for #1006


Why not use Object and `JSON.Stringify`?


AFAIK fetch works perfectly with Objects as body


This can be written as `.then(response => response.json())`


The session object is created to interact with the database.


First try and fully intend to amend when I get the chance!


Added to print the user information along with their email address from the database.


Same thing here


Testing code review comments...


Importing db_session from app/__init__.py


Indentation 😱


With this change, it now causes your `SimpleCache` to fail because when you call `Add` the `Constructor` property is still `null`.


Fetching all the rows from the table 'User' from database


No `var`s please


Passing the user_list variable to Jinja engine


This implicitly create a global variable. Not good


Don't use `this` like this. This is very implicit and error prone. You already have a reference to the element so just use it.


Same


remember it from Visual Srudio 2010, have to admit that VS might be the strongest cpp IDE, but no linux support (only VS Code). I use https://github.com/Valloric/YouCompleteMe which is quite strong, but not as strong as IntelliSense


This is now bound to another `this`


typo?


`function` -> `=>`


It's faster because it checks no conditions, whereas a while loop or any condition is evaluated, even if always true.


just FYI, `@test_throws Exception` is not a very good test - it would pass if the code had a typo in it, much better to test for the specific exception type you expect


I've added link on ragezone how to integrate VS17 with remote build to linux. Check it out.


Good practice is to name variables with reference to DOM nodes with `element` or `el` suffix


Why `1200`?


*da Interface de plugin


well the prob is that i dont have windows, not even on a partition, i would need to run VS17 inside a VM ^^


Wow, thanks for the quick response! :)

It works great.

(in the docs, you might make a note that config needs to replaced with a new object - when I simply update "mask" nothing happens).


Test


Sorry I can not reproduce that. I've updated the online demo with a "Test getValue()" button. Please take a look if it is working for you. Also please make sure you cleared your browser cache before loading the page.


Tst


Fixing.


Yeah, I've removed both of these.


I think it's definitely possible, but dealing with the different types of synonyms could be a bit messy (esp. if you also need to support the regex ones).

How important do you see a feature like this? (I know there is work being done on auto-completion in Funnelback at the moment)


Bleeding edge with the newest Spring Boot 2 Milestone… I like!


@mholt Just curious, is the source of Go code you used to create `gofmt.js` available anywhere?


@joshbowdoin well that is not a specific of text mask but how angular change detection works


Thats true, this isn't technically busy-waiting. In testing I've seen quite a few iterations of this loop though as there is no waiting/blocking on getting `errSSLWouldBlock` back, so in reality it's sort of too close to busy-wait for comfort. Not sure what would be better though. Other projects tend to either do just this, or go off and sleep a bit, no real concensus afaict.


ohhhh lol


147520311-CoolingPanelUACalcBug (RKStrand) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2612 of 2612 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)


Last commit fixes this issue


@korli getrusage is on Haiku, but this code uses **ru_maxrss**, which doesn't exist in the [rusage struct](http://cgit.haiku-os.org/haiku/tree/headers/posix/sys/resource.h#n44) on Haiku yet.


Me pasó esto cuando lo probé
![screenshot from 2017-08-01 19-05-31](https://user-images.githubusercontent.com/11140160/28849269-af09975e-76ec-11e7-98c8-569da2d476bf.png)
Al parecer están tratando de setear manualmente una variable de JiraClient que está como privada. Mirando el código entiendo igual por qué lo hicieron ¿no tiene setters? ¿No les pasó esto cuando lo probaron? Lo que se me ocurre es que hayan modificado la librería, y yo cuando hice composer install sobreescribió.


Liberal use of air-quotes follow.

The certificates marked as "trusted" are the ones in the user default keychain which the user has explicitly gone in and clicked the "Trust" button on. These are obviously trusted. Then there are the certificates that we have loaded from a file into memory and added to the chain for the connection. These are trusted by the users, as he/she otherwise wouldn't have configured them for use, but they are not "trusted" in the sense that they are marked as such in the Keychain. We can't also mark them since we don't load the certificates into keychain but into memory (it would also need the users password being entered etc).

I guess this comment can do with some expansion.


I assume you've also considered `-fspecialise-aggressively`?


Yes, it is a great tool!
I've used it for many years. I'll continue using it regardless of the graphics issue.
I'll paste in graphics after I transfer the text to MS Word.
Thanks for the recommendation.  :)


Just tried that. No cigar: https://travis-ci.org/flyway/flyway/builds/259966681#L2815


I think in v1b the same will occure when long gap passes beyond window N but negative solve time is still there. Should be spike in difficulty.


Can compile with MSVC because of this changes
/cc @Orvid

```
D:\Work\vcpkg\buildtrees\folly\src\folly-2017.07.31.00\folly/Launder.h(40): error C2338: folly::launder is not implemented for this environment
D:\Work\vcpkg\buildtrees\folly\src\folly-2017.07.31.00\folly/Optional.h(313): note: see reference to function template instantiation 'T *folly::launder<Value>(T *) noexcept' being compiled
        with
        [
            T=std::string,
            Value=std::string
        ]
```


Wow.


147520311-CoolingPanelUACalcBug (RKStrand) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1370 of 1370 tests passed, 0 test warnings)

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


I also changed the (separate project) Album Page line break syntax from
 to
 here.