Xavier asked for a state variable to allow withdraw/claim, not deposit:
https://github.com/boyuanx/B9Lab_Remittance/commit/7cd31d2e49dd6846391d477899cd506695da71fd#commitcomment-34458281

The idea is, the owner kills the contract so now no one should be able to deposit (you achieve that by using `isAlive()` on `deposit()` function).
Users should be able to get their money back from a killed contract, you achieve that by **not** applying `isAlive()` to `withdraw()` or `reclaim()` functions; instead, apply `onlyIfRunning()` so users can't withdraw or reclaim if the contract is paused (for instance the owner is suspecting something bad is happening; they can pause the contract until they finish the investigation).


let's use spdlog for error logging?
Also a point to discuss. Do we want to start using `int` return values that signify success or failure of calls, how do we do, when the function already returns data, and could instead exceptions be a better approach.


The original is accurate for the installation method at https://pages.nist.gov/fds-smv/


:white_check_mark: All Rules (5 / 5) Passed

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

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

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


- fix Ryzen3 cpu support
- etc fix


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

* https://smsbao-git-master.cuiqg.now.sh


why do you sort the individuals, not the fitness scores? what is this sorting doing?


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

* https://dashboards.joaorfclopes.now.sh
* https://dashboards-git-master.joaorfclopes.now.sh


@petyosi heya!

I don't think that I need the whole store. The change you see here was made very quickly without regard for virtuoso's API, because I was hoping to follow up with you later (but I needed the feature on a short timeline).

My hope here was to get updates as to "what items are in view", and in my case listening to `list$` was sufficient for that. Some thoughts I have:

1) I'm guessing `list$` is not sufficient for what's in view for all use cases (like maybe if "top items" are used, which they're not in my case).
2) I don't think my `getStore` prop is necessary. If the instance I get back from `<Virtuoso ref={...} />` were to return a stream I can listen to or something like that, that would be ideal.

Do you have any thoughts? For what it's worth, I'd be happy to work on getting something back in to `<Virtuoso />` if you think my case is valid but there's an approach to it that you prefer.

Cheers!


Should these be addressing pin GPIO2 rather than GPIO4?


Well, that's nice to know... I had given up. I humbly retract my accusation
and apologize for the incorrect Information.

On Mon, Jul 29, 2019, 10:50 AM Simon Ruggier <notifications@github.com
wrote:

> @starhawk64 <https://github.com/starhawk64> "To this day" may be a bit of
> an exaggeration:
>
> $ apt-cache policy xserver-xorg-video-openchrome
> xserver-xorg-video-openchrome:
>   Installed: 1:0.5.0-3
>   Candidate: 1:0.5.0-3
>   Version table:
>      1:0.6.0-3+b1 103
>         103 https://deb.debian.org/debian buster/main amd64 Packages
>         102 https://deb.debian.org/debian testing/main amd64 Packages
>         101 https://deb.debian.org/debian unstable/main amd64 Packages
>  *** 1:0.5.0-3 500
>         500 https://deb.debian.org/debian stretch/main amd64 Packages
>         100 /var/lib/dpkg/status
>
> If a bug exists in both Debian and Ubuntu, go to Debian first. They really
> are the upstream for Ubuntu, and updates to Debian packages will
> automatically propagate to the latest Ubuntu version in a few months,
> depending on where in the Ubuntu release cycle the update happens.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/torvalds/linux/commit/47d6a7607443ea43dbc4d0f371bf773540a8f8f4?email_source=notifications&email_token=AD33YGPWWELRFJY3V23JGT3QB37RTA5CNFSM4IHGSLQ2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA4KNM#commitcomment-34482604>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AD33YGOCAYFUQVOVKSO52TLQB37RTANCNFSM4IHGSLQQ>
> .
>


This is a major bug that makes the algorithm non-functioning as the sorting according to fitness scores is the most critical part of the GA methods.


Successfully aliased the URL <https://mock-x42-f4hv8q25o.now.sh> to the following aliases:

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


Yup upon reflection I think it's more consistent to just mimic the way Prettier (JS formatter) does it

That works fine without the export since it uses the `esutils` library (which I updated the Prettier plugin to also use) and Coffeescript should match JS in this regard (so doesn't need to import something Coffeescript-specific)


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

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


Yes, so you do something like this:
1. At the top of your contract: `uint constant oneYear = 35040;`
2. Inside your constructor: `defaultDeadlineDelay = oneYear;`


dagegen.


:x: 1 / 5 Rules Failed

      :cold_sweat: It's not you, it's your code. It may not be aligned with your organization's best practices

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

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


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


I don't agree with this statement. In our testing, performance was only slightly slower than Canteloupe (but used less memory).  As the primary developer, it was never "meant for development convenience".


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

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


first of all this is not a bug the fitness function score is the first element of each individual
so according to what i have written this is not a bug


:white_check_mark: All Rules (5 / 5) Passed

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

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

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


![](https://github.trello.services/images/mini-trello-icon.png) [Remove purgecss support?](https://trello.com/c/BXGPuMX8/193-remove-purgecss-support)


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

* https://lamhieu.info
* https://web-profile.lamhieu.now.sh
* https://web-profile-git-master.lamhieu.now.sh


Keep it `private` so inheriting contracts can only change it through the setter.


Please don't make random commits without discussion. Now the code is undocumented and does no longer follow the AppImage specification. This is AppImageUpdate, not ISOUpdate.


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

* https://game.fallemabc.now.sh
* https://game-git-master.fallemabc.now.sh


sh Hack fb.Target.txt.doc


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

* https://rtoprilagithubio.rfq24986.now.sh
* https://rtoprilagithubio-git-master.rfq24986.now.sh


@samehkamaleldin aslo in nsga-II i have embedded the rank , the crowding distance in the individual


Couldn't run policy because the pull request is closed
:point_right: click here to view a full list of the events :point_left:


So **anyone** can kill a contract? **OUCH!**


ubiquitous-fiesta/.gitignore


@Nkrb thanks for the code.
As per MS document "On capturing payment, the payment provider must confirm with Dynamics 365 for Marketing by calling a custom back-end service created by you"

Can you please help me on how to call the hosted service from Dynamics 365 event portal .


What branch is this?


7285-UnitVentControlProblem (RKStrand) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1127 of 1127 tests passed, 0 test warnings)

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


The whole point of `Killable` contract is not to used to `selfdestruct`, because it removes the contract code and if someone sends funds accidentally; they are trapped forever. With `Killable` contract we can achieve the same effect (i.e. make the contract un-usable) but we also can allow user to withdraw their funds by not applying the `_whenAlive` modifier to the withdraw function, so if someone sends funds to a killed contract; they can still call withdraw.


lol nevermind, I just saw that you removed it in the next commit.


Successfully aliased the URL <https://rtoprilagithubio-91d55df1f.now.sh> to the following aliases:

* https://rtoprilagithubio.rfq24986.now.sh
* https://rtoprilagithubio-git-master.rfq24986.now.sh


Vuex这个东西我已经看不懂了，美女哪天教我一下好嘛


Cool, I'll ask Xavier and Rob to have a final review.


tamam


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

* https://room.vacuumlabs.com


mcpenew


okayyy


Successfully aliased the URL <https://apidigistaxcom-53jknqpab.now.sh> to the following aliases:

* https://apidigistaxcom.digistax.now.sh
* https://apidigistaxcom-git-master.digistax.now.sh


@adelRestom Hmm, but doesn't this have the same effect while being simpler? Since in Stoppable, contracts must be paused before they can be killed to prevent contracts from being killed by accident, I would have to change stuff in Stoppable to allow the contract to be running and killed at the same time but that seems like a lot of things to change (and kinda weird? :P) and doesn't `onlyIfRunning` imply `isAlive`? I'm just failing to see the difference between: a. Disabling deposits while allowing withdraws and b. Enabling withdraws while killing the contract which disable the deposits. Maybe I'm not understanding things correctly...


In this line, you force the fitness output to one of the individual values. This is wrong, as you will not be able to recover this value then in mutation, natural selection, etc.


Obviously this is the mcpenew branch, but what branch is it going to be rewritten on since there is only this branch and master.


购物车作业完成


The diff looks messy on this file. The main difference is, instead of exporting `sendEvent`, now it exports `makeSendEvent` and it receives `requestFn` so that `bulkSendEvent` can use it.


@adelRestom Yeah my intention was to be able to modify defaultDeadlineDelay. Fixed in later commits by having a setter and putting it into the constructor.


The rewrite is currently being done privately.
Since there are way too many people asking for PE support despite all the warnings.


I think `depositFunds()` should only work if the contract is `alive` **&&** `running`. We don't want people sending funds to a dead contract (even though they can still withdraw them).


I'm good with this, I will Rob and Xavier to have a look.


AppImageUpdate needs to be able to update ISOs, as it always did. This commit should fix it and I am going to test it soon.


why would you add the fitness into the individual? why not make a new tuple that combines each individual and its fitness scores?

Also, you should use the fitness weights with the fitness scores to direct the sorting as some fitness output will be maximized and others will be minimized.


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

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


urllib.request.HTTPError


```
Cell::~Cell() = default;
```


Successfully aliased the URL <https://smsbao-50eq08tgt.now.sh> to the following aliases:

* https://smsbao.now.sh
* https://smsbao.cuiqg.now.sh
* https://smsbao-git-master.cuiqg.now.sh


Parsing HEX file: /home/rychu/workspace/Nordic/pc-ble-driver/hex/sd_api_v6/connectivity_1.0.0_1m_with_s140_6.1.1.hex


@JuliaRegistrator `register`


Error while trying to register: **Register Failed**
@iamed2, it looks like you are not a publicly listed member/owner in the parent organization (JuliaTime).
If you are a member/owner, you will need to change your membership to public. See [GitHub Help](https://help.github.com/en/articles/publicizing-or-hiding-organization-membership)


why is this a pointer to a double?


Thank you for reviewing this.

I wasn't aware that disallowing versions that change the most significant part of the version number (i.e. `0.6` to `0.7`) may become the default.

The problem I encounter with needing an explicit "0.6, 0.7" is keeping package dependencies in sync.  If `StatsModels` v"0.7.0" is released and `GLM`'s dependencies are updated to an exclusive "0.7" but I don't notice then the MixedModels dependency on "0.6" can  cause the package update to fail.


i recommend to take a look at the latest commit https://github.com/uniopt/libevolve/blob/feature/imp-ga/libevolve/ga/_base.py


exposed :D @Prashant-Acharya


c_cpp_properties.json:
{
    "configurations": [
        {
            "name": "Linux",
            "includePath": [
                "${workspaceFolder}/**",
                "~/workspace/qtdev/qtbase/include/**",
                "~/workspace/Nordic/pc-ble-driver/include/sd_api_v6/**",
                "~/workspace/Nordic/pc-ble-driver/include/**",
                "~/workspace/Nordic/pc-ble-driver/src/sd_api_common/sdk/components/libraries/util/**"
            ],
            "defines": [],
            "compilerPath": "/usr/bin/gcc",
            "cStandard": "c11",
            "cppStandard": "c++17",
            "intelliSenseMode": "clang-x64"
        }
    ],
    "version": 4
}


tasks.json:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build",
            "type": "shell",
            "command": "qmake && make && LD_LIBRARY_PATH=/home/rychu/rychu_home/workspace/Nordic/pc-ble-driver/build:$LD_LIBRARY_PATH ./QtSoftDevices",
            "problemMatcher": [
                "$gcc"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}


Yea, that's right.


also i recommend to discuss this in this stuff at the call not here because first i must explain what i have done then take any question


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

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


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

* https://babysleep.cerivitos.now.sh
* https://babysleep-git-master.cerivitos.now.sh


@chesio I could really help you if you have clients sending newsletter from a WordPress installation. Even if you have 10 subscribers and no business goals you should not pollute WordPress with this functionality. See my onboarding process https://github.com/szepeviktor/debian-server-tools/blob/master/Onboarding.md#email-delivery


Case


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

* https://johno.com
* https://www.johno.com
* https://johno.johno1.now.sh
* https://johno-git-master.johno1.now.sh


What I'm trying to say:
1. You don't need the `canDeposit` state variable and its modifier and setter.
2. Add a modifier to `Stoppable` and call it `onlyIfAlive`
3. Use `onlyIfAlive` on deposit function (users shouldn't be able to deposit to dead contracts).
4. As for the rest, you're good; withdraw and reclaim should be able to be called if the contract is dead (so don't apply the `onlyIfAlive` modifier).


asfasddf


Done in commit 061a1f1


why a pointer to double? Also we shoudl think about const correctness.


1. 1. 変### 更予定
2. 予定
#1
#1

![bitcoin](https://user-images.githubusercontent.com/33015400/62060249-bdf38080-b25f-11e9-918a-4ccbf58628da.png)

@soichikamiya
`puts 1+1=2`
[https://railstutorial.jp](url)


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

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


It is still supported. Just initialize VGA controller with the right pins instead of default parameters:

 VGAController.begin(GPIO_NUM_22, GPIO_NUM_21, GPIO_NUM_19, GPIO_NUM_18, GPIO_NUM_5);

> Il giorno 29 lug 2019, alle ore 16:02, RegyRegy <notifications@github.com> ha scritto:
>
> USE_8_COLORS - === 8 colors, 1 bit per channel, 3 bit per pixel ===
> mode is no longer available ??
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <https://github.com/fdivitto/FabGL/commit/1a695d59c9162679bcc02e372ea8863a8be9dca0?email_source=notifications&email_token=ACKNPCXY4F5WMDGPTYAVCMLQB3Z7VA5CNFSM4IHSYVMKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA4J33#commitcomment-34482043>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACKNPCVYRTR5SXFYLNJHPD3QB3Z7VANCNFSM4IHSYVMA>.
>


name -> id


disabled comment


include db connect file


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

* https://app.inboxcomics.now.sh
* https://app-git-master.inboxcomics.now.sh


@JuliaRegistrator register


@smsong : The evaluator is not using this change now. Please do make a new release, and push it to PyPi for the evaluator to be able to use it.


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

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

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


[](url)


7174-AddSETOutput (JasonGlazer) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


- [ ] ### **_herokuがファイル作成してた_**


I'm getting pretty consistent failures for the `should collapse on click` test

```javascript
[chrome 75.0.3770.142 MAC #0-0] 1) Interactive Suite should collapse on click
[chrome 75.0.3770.142 MAC #0-0] Error: element ("[data-qa-grid-item]") still displayed after 5000ms
[chrome 75.0.3770.142 MAC #0-0] Error: element ("[data-qa-grid-item]") still displayed after 5000ms
[chrome 75.0.3770.142 MAC #0-0]     at expandAssertGridItem (/Users/pthiel/Developer/manager/src/components/ExpansionPanel/ExpansionPanel.spec.js:30:17)
[chrome 75.0.3770.142 MAC #0-0]     at UserContext.it (/Users/pthiel/Developer/manager/src/components/ExpansionPanel/ExpansionPanel.spec.js:52:7)
```

I changed Line 29 to `browser.jsClick('[data-qa-panel-summary]')` and it appears to be passing each time, now.. not sure why though.


Hide　comment!!!!!!!


7174-AddSETOutput (JasonGlazer) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

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


This is actually to sort leading zero and BCE dates correctly, NOT default sort order in Browse


these are new in the sense that they didn't exist in the old library. there are 4 slots left. I believe the first three will not be as complicated but the last one is going to be a beast. I was trying to dig out a proof from the literature but I can't find any. I suppose it's one of those mathematical obviousnesses?


:white_check_mark: All Rules (2 / 2) Passed

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

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

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


<details>

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

Schema Validation Failed!
Rejecting Schema: https://schemas.taskcluster.net/queue/v1/create-task-request.json#
Errors:
  * data should NOT have additional properties: "0"
  * data should have required property 'provisionerId'
  * data should have required property 'workerType'
  * data should have required property 'deadline'
  * data.payload should be object
  * data should have required property 'metadata'

---

* method:     createTask
* errorCode:  InputValidationError
* statusCode: 400
* time:       2019-07-29T15:25:55.390Z

</details>


<details>

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

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

</details>


Move data from placeholder to value


You mean there is no reason to have this simplified class when you can just use the bigger one?


```
<select type="text" name="type" required>
    <option disabled>Выберите тип</option>
    <option <?if ($ticket->type == 'bug'): ?>selected="true"<?php endif; ?>>bug</option>
    <option <?if ($ticket->type == 'task'): ?>selected="true"<?php endif; ?>>task</option>
</select>
```


typo


This shouldn't return this output, it isn't a valid query.


Yes, but before 1.0 every minor version update is considered breaking.  So better to force packages to opt-in (with some possible delay in updating) to ensure compatibility than to have to go back and retroactively add upper-bounds (like what happened with the recent 0.5-0.6 Terms 2.0 update debacle...https://github.com/JuliaRegistries/General/pull/1611


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

* https://uploadnewcopy.jakesb1996.now.sh
* https://uploadnewcopy-git-master.jakesb1996.now.sh


Yes, I did experience an infinite loop. I didn't do a thorough investigation, but it only occurred when there was a model with revolute joints.


![](https://github.trello.services/images/mini-trello-icon.png) [Database setup](https://trello.com/c/n9EQ3KyD/4-database-setup)


Successfully aliased the URL <https://now-next9-static-bbzl0tpad.now.sh> to the following aliases:

* https://now-next9-static.ywgjhe.now.sh
* https://now-next9-static-git-master.ywgjhe.now.sh


In the splitter project your recommended that the kill function should only work when the contract is paused, so if it is killed it is also always paused right? Should I still add the `onlyIfAlive` modifier?


@athril Could you address these questions I put inside brackets please?


Ah, nevermind, I saw. Yes, it was late last night :wink:


@athril please address


The package manager does a virtually complete compliance with semantic versioning. Versions with a leading zero treat the minor version as breaking (e.g., `0.6` means `[0.6.0 - 0.7.0)` while `1.2` means `[1.2.0, 2.0.0)`). Most packages in the community follow that semantic versioning.

The example you mention is correct. However, the alternative would be for the package manager to use a new dependency solution that potentially breaks code (i.e., `≥x.y.z`). If one of the dependencies does release a breaking version the solution would be to first inspect whether the code doesn't break the functionality and release a new version after testing it.


debuggerメソッドで確認予定
#2 debuggerメソッドISSUE


point for scorpio


fixed random error occur because of argv version updated


De la forma scss


**handcuffTimer.tas**k = ESX.SetTimeout(Config.**HandcuffTimer**, function()

shouldnt it be HandcuffTimer.task?


also **handcuffTimer**.active = false


This error is an JavaScript error and the `maxFiles` are is replaced in the JavaScript. Therefore the UploadField component crashes, because of an undefined variable `maxFiles`

```
Error Type:

wcf\system\exception\ErrorException

Error Message:

Undefined index: maxFiles

File:

/Applications/MAMP/htdocs/hurricane/lib/system/WCF.class.php (338)

Stack Trace:

#0 /Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1_uploadFieldComponent.php (60):
wcf\system\WCF::handleError(8, 'Undefined index: maxFiles', '/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1_uploadFieldComponent.php', 60, [ 7 items ])
#1 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (334):
include('/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1_uploadFieldComponent.php')
#2 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (562):
wcf\system\template\TemplateEngine->display('uploadFieldComponent', 'wcf', false)
#3 /Applications/MAMP/htdocs/hurricane/lib/system/file/upload/UploadHandler.class.php (215):
wcf\system\template\TemplateEngine->fetch('uploadFieldComponent', 'wcf', [ uploadField => , uploadFieldId => , uploadFieldFiles => ])
#4 /Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___uploadFormField.php (39):
wcf\system\file\upload\UploadHandler->renderField('iconFile')
#5 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (334):
include('/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___uploadFormField.php')
#6 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (562):
wcf\system\template\TemplateEngine->display('__uploadFormField', 'wcf', false)
#7 /Applications/MAMP/htdocs/hurricane/lib/system/form/builder/field/AbstractFormField.class.php (111):
wcf\system\template\TemplateEngine->fetch('__uploadFormField', 'wcf', [ field => , javaScriptDataHandlerModule => ], true)
#8 /Applications/MAMP/htdocs/hurricane/lib/system/form/builder/field/UploadFormField.class.php (167):
wcf\system\form\builder\field\AbstractFormField->getHtml()
#9 /Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___formContainer.php (57):
wcf\system\form\builder\field\UploadFormField->getHtml()
#10 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (334):
include('/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___formContainer.php')
#11 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (562):
wcf\system\template\TemplateEngine->display('__formContainer', 'wcf', false)
#12 /Applications/MAMP/htdocs/hurricane/lib/system/form/builder/container/FormContainer.class.php (47):
wcf\system\template\TemplateEngine->fetch('__formContainer', 'wcf', [ container => ], true)
#13 /Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___form.php (103):
wcf\system\form\builder\container\FormContainer->getHtml()
#14 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (334):
include('/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1___form.php')
#15 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (562):
wcf\system\template\TemplateEngine->display('__form', 'wcf', false)
#16 /Applications/MAMP/htdocs/hurricane/lib/system/form/builder/FormDocument.class.php (416):
wcf\system\template\TemplateEngine->fetch('__form', 'wcf', [ form => ])
#17 /Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1_reactionTypeAdd.php (712):
wcf\system\form\builder\FormDocument->getHtml()
#18 /Applications/MAMP/htdocs/hurricane/lib/system/template/TemplateEngine.class.php (334):
include('/Applications/MAMP/htdocs/hurricane/acp/templates/compiled/0_wcf_1_reactionTypeAdd.php')
#19 /Applications/MAMP/htdocs/hurricane/lib/page/AbstractPage.class.php (323):
wcf\system\template\TemplateEngine->display('reactionTypeAdd', 'wcf')
#20 /Applications/MAMP/htdocs/hurricane/lib/form/AbstractFormBuilderForm.class.php (215):
wcf\page\AbstractPage->show()
#21 /Applications/MAMP/htdocs/hurricane/lib/page/AbstractPage.class.php (114):
wcf\form\AbstractFormBuilderForm->show()
#22 /Applications/MAMP/htdocs/hurricane/lib/system/request/Request.class.php (83):
wcf\page\AbstractPage->__run()
#23 /Applications/MAMP/htdocs/hurricane/lib/system/request/RequestHandler.class.php (107):
wcf\system\request\Request->execute()
#24 /Applications/MAMP/htdocs/hurricane/acp/index.php (9):
wcf\system\request\RequestHandler->handle('wcf', true)
```


Just tried `test_Skeleton` and it hangs without this patch.


Espacio y verificar todo.


const correctness


Nomenclatura kab case


```
php > $exploded = explode(",", $tags);

php > foreach ($exploded as $id => $tagName) {
php {     $exploded[$id] = trim($tagName);
php { }

print_r(array_unique($exploded));
```


app.module.ts 'e yazılan service'ler global. Component içine yazılan service 'ler local


Successfully aliased the URL <https://escritorio-pagarme-8iib8x3sj.now.sh> to the following aliases:

* https://escritorio.pagarme.now.sh
* https://escritorio-pagarme.pagarme.now.sh
* https://escritorio-pagarme-git-master.pagarme.now.sh


why do we pass pointers to data on this level? On the C interface it makes sense.. but I'm not sure this should propagate all the way into reportinglib core classes?


JSNLog.js is used on many other sites. Is there a good reason to block this everywhere?


Get new ticket id as:
```
$stmt = $db->prepare("...");
$stmt->execute();
$id = $db->lastInsertId();
```


lol this isso pathetic - ITS A SHARED TIP BOT. THERE IS LITERALLY NO COIN ON EARTH THAT DOESNT HAVE A **SHARED** TIP BOT


Thank you for your reply and kindly help. That's great ！

发自我的iPhone

------------------ Original ------------------
From: A. Mir <notifications@github.com>
Date: Sat,Jul 27,2019 6:58 PM
To: mir-am/LightTwinSVM <LightTwinSVM@noreply.github.com>
Cc: cumtlzhy <zy.liu@cumt.edu.cn>, Mention <mention@noreply.github.com>
Subject: Re: [mir-am/LightTwinSVM] A note for Windows users on the ExecutionPolicy. (9775129)

@cumtlzhy

I have added a page to the docs of the LightTwinSVM. The page explains each column of the Excel file. Hope it helps you analyze and solve your classification problem.

Unfortunately, at the moment LightTwinSVM does not support plotting a ROC curve. Please check out the docs of sklearn here for this matter. Also, check out the LightTwinSVM's API, which helps you use the TwinSVM esimators for your project.

Let me know if you need further help.

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


yup lol
still a tipbot
what's the point of our own if we are already on one? Lol


This would be a good candidate for a more detailed commit message. How does this fix the build? What was the previous mistake?


well whats the point in making our own gui wallet if you have a shared webwallet. hell whats the point in having your own chain then?


这里的点击事件，在PC端报错，是调用手机端原生的拍照功能吗？


Will this work after `clone()`?


Successfully aliased the URL <https://smartdatafetching-40y6501rw.now.sh> to the following aliases:

* https://smart-data-fetching.now.sh
* https://smart-data-fetching.gfrancischelli.now.sh
* https://smart-data-fetching-git-master.gfrancischelli.now.sh


Successfully aliased the URL <https://podcasts-i-listen-to-qa6vkypej.now.sh> to the following aliases:

* https://podcasts-i-listen-to.michaelbonner.now.sh
* https://podcasts-i-listen-to-git-master.michaelbonner.now.sh


Use lastInsertId


idk :joy:


Check if this tag already exists


heck lets make trtg into a waves token like blog because having your own chain isnt important


Great work priyansh!!
Your wirk reflects that you have good understanding of binary search quick sort merge sort use of fast and slow pointer to find middle element

Suggestion
Try to add more comments to explain your steps while coding


no u


`name` is not used here? I'm not sure how this uses the dataset created in `configure_attribute`.


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/78a9bbe7-85f2-4ef2-8393-189f0ad4b81b?env_id=ibm%3Ayp%3Aus-south "lightbluecompute-devops-20190724061746463"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/8fe523ee-a9f1-4909-a4c7-0e96fab59c30 "lightblue-customer") deployed [lightblue-customer-20190724061746463](https://github.com/vinayaksatapute/lightblue-customer-20190724061746463/releases/tag/deploy-ibm-yp-us-south-vinayakhs_007-yahoo.co.in-dev-20190729-154052 "deploy-ibm-yp-us-south-vinayakhs_007-yahoo.co.in-dev-20190729-154052") to [dev](https://console.bluemix.net/apps/152332c1-ef37-4311-8636-f56e15332589?env_id=ibm:yp:us-south "ibm:yp:us-south:vinayakhs_007@yahoo.co.in:dev"), including this commit


I think the correct value for BATTERY PRESENT RATE might be
BPR * 10 / DGVO * BPV.

as per the kernel's claim that values returned in mAh are incorrect and should be multiplied by 10000 and divided by voltage_design (https://github.com/torvalds/linux/blob/master/drivers/acpi/battery.c)

I am seeing very plausible power consumption rates with this formula on my 4 cell.


Apologies for the delay - and thanks for raising a ticket @michael-simons.


@adelRestom I see, so the idea is to only allow deposits if the contract is running (which means it must be alive) (I think it might be better if we can pause deposit by pausing the contract instead of hitting the killswitch?) and allow withdraw/reclaim all the time regardless of the state of the contract?


if this is not implemented yet, at least print out a log message or something


The [UX guidelines are for "sentence case" for phrases](https://ux.folio.org/docs/guidelines/language-rules/text-case/), so the "L" in "log" should be lower case.


Selecting last-child breaks current formatting. This example isn't working anymore. Content overflows table cell.

https://asciidoctor.org/docs/user-manual/#cell
|===
|Source Code 1 |Source Code 2

a|
[source,python]
----
import os
print "%s" %(os.uname())
----

a|
[source,python]
----
import os
print ("%s" %(os.uname()))
----
|===


True...hmm; you're right, keep it like it is.


Brakuje zmiennej typu `boolean` o nazwie np `isTaskExecuted`. Metoda `executeTask` powinna ustawiać wartość takiej zmiennej na true. Metoda `isTaskExecuted` powinna zwracać wartość tej zmiennej. Podobne rozwiązanie zastosuj proszę we wszystkich klasach implementujących `Task`


What's the use of this if we are closing the dataset after each write? On the other hand, do we need to close after each write?


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

* https://leaderboard.qvil.now.sh
* https://leaderboard-git-master.qvil.now.sh


I can't quite puzzle out all the stuff on the nLab surrounding this. What I do read makes the above seem overly complicated. It doesn't mean that it is, it might be that there's something non-trivial going on in 'our' setting that was straightforward in the classical setting.


@adelRestom Would it be a bad idea though, to not be able to stop withdraw/reclaim at all? I can see both sides of the argument...


Yes, let's allow withdraw/reclaim anytime, as for deposit only if it's running (i.e. not paused).


>One solution is to add `lib/` to `eager_load` paths, but that is deemed
non thread-safe

Adding _lib_ to _eager_load_paths_ is thread-safe.
Adding _lib_ to _autoload_paths_ is not thread-safe.


@a1ext Can you please elaborate as to why do you need this line? It currently breaks mona (https://github.com/x64dbg/mona/issues/6)
There is a known issue in python for win (https://stackoverflow.com/questions/4230855/why-am-i-getting-ioerror-9-bad-file-descriptor-error-while-making-print-st) which results in IOErrors when stdout is not available. And for x64dbg it is not available, because it is a GUI application and does not have a console window.


sdd


xad


some question...


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

* https://rtoprilagithubio.rfq24986.now.sh
* https://rtoprilagithubio-git-master.rfq24986.now.sh


Yes of course, there is not right way unfortunately; imagine if the a bug was discovered in the withdraw function that allows draining all the contract funds; the owner kills the contract but the withdraw function is still callable! It's a catch 22 you know. You can open that discussion on Slack channel of the course and see what other people think.


Cambiar que no sea `ul`


Successfully aliased the URL <https://ecommerce-project-nkk9sq3to.now.sh> to the following aliases:

* https://ecommerce-project.tivler.now.sh
* https://ecommerce-project-git-master.tivler.now.sh


Successfully aliased the URL <https://resume-8ihsdwyj4.now.sh> to the following aliases:

* https://resume.cambickel.com
* https://resume.camdenb.now.sh
* https://resume-git-master.camdenb.now.sh


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

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


Successfully aliased the URL <https://rules-component-2l9c3phd2.now.sh> to the following aliases:

* https://rules-component.fem-misc.now.sh
* https://rules-component-git-master.fem-misc.now.sh


o local que esse componente está sendo usado é isolado.. não existe conflito de nomes, não vejo a necessidade dessa alteração.


Hi @akhilnarang , The issue with the random reboot when the battery is below 10% is related to bcl,not this,disable bcl as a workaround until a real fix is found


```
Traceback (most recent call last):
  File "./manage.py", line 59, in <module>
    execute_from_command_line(sys.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/ubuntu/gitcoin/coin/app/economy/management/commands/refresh_bounties.py", line 51, in handle
    all_bounties = Bounty.objects.filter(current_bounty=True).order('-pk')
AttributeError: 'BountyQuerySet' object has no attribute 'order'
Sentry is attempting to send 0 pending error messages
Waiting up to 2.0 seconds
Press Ctrl-C to quit
Traceback (most recent call last):
  File "./manage.py", line 59, in <module>
    execute_from_command_line(sys.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/ubuntu/gitcoin/coin/app/economy/management/commands/refresh_bounties.py", line 51, in handle
    all_bounties = Bounty.objects.filter(current_bounty=True).order('-pk')
AttributeError: 'BountyQuerySet' object has no attribute 'order'
Sentry is attempting to send 0 pending error messages
Waiting up to 2.0 seconds
Press Ctrl-C to quit
Traceback (most recent call last):
  File "./manage.py", line 59, in <module>
    execute_from_command_line(sys.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/ubuntu/gitcoin/gitcoin-37/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/home/ubuntu/gitcoin/coin/app/economy/management/commands/refresh_bounties.py", line 51, in handle
    all_bounties = Bounty.objects.filter(current_bounty=True).order('-pk')
AttributeError: 'BountyQuerySet' object has no attribute 'order'
Sentry is attempting to send 0 pending error messages
```


7174-AddSETOutput (JasonGlazer) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2493 of 2493 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)


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

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


7285-UnitVentControlProblem (RKStrand) - Win64-Windows-10-VisualStudio-16: OK (2450 of 2453 tests passed, 0 test warnings)

Messages:\n
 * 3 tests had: EIO diffs.
 * 3 tests had: ESO big diffs.
 * 1 test had: MTR big diffs.
 * 3 tests had: Table big diffs.
 * 2 tests had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 659
 * Failed: 3

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


```
$stmt = $db->prepare("...");
$stmt->execute();
$id = $db->lastInsertId();
```


- Use classes.
- All the files should be in a separate directory as classes.
- The code inside the hook function should just run the class functions.
- Do not instantiate the classes inside the hooks. Instantiate them outside the hooks. We don't want to consume too much memory.
- The two utility functions that you are using should be in a separate class called: "Utility.php".


commit 7d78805523ddea85d55573bd403a8921118d7ac8


why is this mechanism needed? Looks a bit like a factory method to me.. but I'm not sure why this is needed.


Did `mssql-session-store` continue to function after the `mssql@3.3.0` update?


Esse código acabou ficando complexo demais.. o ideal seria parar de usar o datepicker do jquery, e gerar o html do calendário no backend


my fault https://github.com/gitcoinco/web/commit/3eca86f1e19c490c9f83e14e49983b15aec12804#diff-8f8c96fe9d5d098d20400c616f7e5917


Yes you are reusing the pipeline, which matches the flickering issue I was seeing in #225


Slight mistake in updaeStatus.txt, h5 file is no longer destroyed


Надо вынести этот insert из условия (обе ветки, if и else)


Successfully aliased the URL <https://zeit-test-ibg2vujw1.now.sh> to the following aliases:

* https://zeit-test.alessandrocuzzocrea.now.sh
* https://zeit-test-git-master.alessandrocuzzocrea.now.sh


como essa alteração foi feita com prazo curtíssimo na época não tivemos tempo para pensar direito, e o caso de uso se mostrou muito mais complexo do que parecia.. por isso o código ficou complexo.


This text was failing for accessibility, and the alignment wasn't pretty on mobile.


I think instead of this function, you should create a function called: "request". The request function should be something like:

class Utilities {
public function request($endpoint: string, $data: array){
return json_decode(localApi($endpoint, $data));
}
//Other utility functions.
}


I don't really understand what that means, is it supposed to point to the root url of the server? PURL is just a convention, it doesn't really mean anything


We actually need to retrieve back the xclass from the cloned doc, else we save a doc without any change.


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

* https://handbook-app.jrussclay.now.sh
* https://handbook-app-git-master.jrussclay.now.sh


Not sure why you're encoding and then decoding.


`DELETE FROM relation WHERE tag_id = :id AND ticket_id = :ticket_id;`


Please update this phrase to [use sentence case](https://ux.folio.org/docs/guidelines/language-rules/text-case/).


Successfully aliased the URL <https://escritorio-pagarme-r6jyzg4l3.now.sh> to the following aliases:

* https://escritorio.pagarme.now.sh
* https://escritorio-pagarme.pagarme.now.sh
* https://escritorio-pagarme-git-master.pagarme.now.sh


Successfully aliased the URL <https://zeit-test-ikbh6a9p9.now.sh> to the following aliases:

* https://zeit-test.alessandrocuzzocrea.now.sh
* https://zeit-test-git-master.alessandrocuzzocrea.now.sh


I do not see any article trying to show closed monoidal is closed though? in particular, I would be really curious to see how to make extranaturality of `L` simpler.

also note that I think the definition of closed monoidal category in this library is simpler than the classical settings: in the classical settings, even `[-,-]` requires a proof. that seems to make things more complicated. I think I will dig literature and see how was it shown.


that's unused


Thanks! While you're at it, can you also have a config for the url of the logo? it would be http://iiif.bdrc.io/static::logo.png/full/max/0/default.png for us


Another option would be to just call it Advanced. The name configuration is almost redundant given this API is only for advanced configuration


See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 for the discussion.


This `LOG_PREFIX` declaration should be copied at the top of RenderStates.cpp and TextureStates.cpp


this should be in the for loop


Can you please explain what this change is about? I don't need a very detailed explanation, just 1 or 2 sentences. Currently I don't understand it, but I guess I'm missing the bigger picture.


so you don't need the "i"


Sorry @GhostlyGems

I did not get your problems. What is the second part?

Actually, bugdb_v1 is a pretty straight forward 'Hello World' question, which let you start to get familiar with [GraphQL][1].

If you still have problems. Please open an [issue][2], which may potentially help other people in the future.

@testerting

[1]: https://graphql.org/
[2]: https://github.com/testerting/hacker101-ctf/issues


Successfully aliased the URL <https://escritorio-pagarme-mch9mnx6j.now.sh> to the following aliases:

* https://escritorio.pagarme.now.sh
* https://escritorio-pagarme.pagarme.now.sh
* https://escritorio-pagarme-git-master.pagarme.now.sh


Successfully aliased the URL <https://zeit-test-d97f8oh4y.now.sh> to the following aliases:

* https://zeit-test.alessandrocuzzocrea.now.sh
* https://zeit-test-git-master.alessandrocuzzocrea.now.sh


Hi @ngo,

Without this redirection I don't see any output of python in my [Labeless] plugin.


nit typo : s/menas/means/


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2891850)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/d16-3/407d1100e46b11afd018fc66f768a0b4d44706e4/2891850/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

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

## Failed tests

 * monotouch-test/iOS Unified 64-bits - device/Debug: Crashed
 * framework-test/iOS Unified 64-bits - device/Debug: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Debug: Crashed
 * fsharp/iOS Unified 64-bits - device/Debug: Crashed
 * dont link/iOS Unified 64-bits - device/Debug: Crashed
 * link all/iOS Unified 64-bits - device/Debug: Crashed
 * link sdk/iOS Unified 64-bits - device/Debug: Crashed
 * mono-native-compat/iOS Unified 64-bits - device/Debug: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Debug: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Debug: Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Debug: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release: Crashed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): Crashed
 * monotouch-test/iOS Unified 64-bits - device/Release (interpreter -mscorlib): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * framework-test/iOS Unified 64-bits - device/Release: Crashed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Release: Crashed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * fsharp/iOS Unified 64-bits - device/Release: Crashed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * dont link/iOS Unified 64-bits - device/Release: Crashed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link all/iOS Unified 64-bits - device/Release: Crashed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * link sdk/iOS Unified 64-bits - device/Release: Crashed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-compat/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mono-native-unified/iOS Unified 64-bits - device/Release: Crashed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Release: Crashed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * mscorlib/iOS Unified 64-bits - device/Release: Crashed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
 * mscorlib/iOS Unified 64-bits - device/Debug: SGenConc: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Release: Crashed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Crashed
</details>


oh I think I screwed this part up. I added an `iso` module in `NaturalIsomorphism` so that I can dot my way through but forgot to make things compile. good catch.


I did say this is not ready for review/highly incomplete/buggy :P
This whole branch and commits will disappear later, as they are replaced with updated versions


- Use classes.
- Hooks should only run class functions.
- Do not instantiate classes inside the hook. We don't want to consume unnecessary memory.
- Contain the classes in a separate folder.
- All utility functions should be in a separate class called: "Utilities.php"
- Try making use of the new typings feature of php 7.
https://ttmm.io/php/strict-typing/


I wonder if we should add some margin here. I thought we did that for the other transactions as well, but it doesn't seem like we do


Yes It's actuall unused so I am going to get rid of it.


s/;;/;/


Any clarification on which versions are affected? Has CVE-2017-7189 been patched?


Deployment failed with the following error:

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


I'll ask Xavier and Rob to have a quick look.


Is last excluded? Or should it be included?


Just a side note:
- These things may seem a bit annoying and unnecessary. But these matter a lot. Trust me!


-------------------------------------------------------------------------------
  Test 1: Check simple requests using basic HTTP methods
-------------------------------------------------------------------------------

  >            GET /pass                                     ... ok
  >           POST /pass                                     ... ok
  >            PUT /pass                                     ... ok
  >         DELETE /pass                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 2: Check simple requests using arbitrary alphanumeric methods
-------------------------------------------------------------------------------

  >       zFw2g9Lm /pass                                     ... ok
  >       YTevr6hu /pass                                     ... ok
  >       F63uxhHS /pass                                     ... ok
  >       IQtPHwFG /pass                                     ... ok
  >       sauT8DrW /pass                                     ... ok
  >       q7foHTeF /pass                                     ... ok
  >       GGCcoAgm /pass                                     ... ok
  >       YJv3vyGZ /pass                                     ... ok
  >       WwrIy0xL /pass                                     ... ok
  >       f1ferwRK /pass                                     ... ok
  >       w0axBkzb /pass                                     ... ok
  >       KBGOAtql /pass                                     ... ok
  >       ZdfOjnys /pass                                     ... ok
  >       UNcg7RtV /pass                                     ... ok
  >       4zZcHhkb /pass                                     ... ok
  >       BUDEiViB /pass                                     ... ok
  >       UeBR4oY3 /pass                                     ... ok
  >       Ym8P7GIJ /pass                                     ... ok
  >       bN7cBQFx /pass                                     ... ok
  >       K0lTRfcF /pass                                     ... ok
  >       XGRMWoMS /pass                                     ... ok
  >       RpWfBVWE /pass                                     ... ok
  >       JRztLAUj /pass                                     ... ok
  >       dlf5hs29 /pass                                     ... ok
  >       TCBPrDty /pass                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 3: Check that route methods are not case-sensitive
-------------------------------------------------------------------------------

  >            GET /pass                                     ... ok
  >            get /pass                                     ... ok
  >            gEt /pass                                     ... ok
  >            GeT /pass                                     ... ok
  >            GEt /pass                                     ... ok
  >            gET /pass                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 4: Check single path accessible via several simple HTTP methods
-------------------------------------------------------------------------------

  >            GET /pass                                     ... ok
  >           POST /pass                                     ... ok
  >            PUT /pass                                     ... ok
  >         DELETE /pass                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 5: Check that method of request is not altered by the router
-------------------------------------------------------------------------------

  >            GET /pass                                     ... ok
  >           POST /pass                                     ... ok
  >            PUT /pass                                     ... ok
  >         DELETE /pass                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 6: Check that common paths were not hard-coded
-------------------------------------------------------------------------------

  >            GET /                                         ... ok
  >            GET /index.html                               ... ok
  >            GET /feed                                     ... ok
  >            GET /threads                                  ... ok
  >            GET /threads/thread                           ... ok
  >            GET /threads/0                                ... ok
  >            GET /threads/1                                ... ok
  >            GET /users/user/recent                        ... ok
  >            GET /users/amit/recent                        ... ok
  >            GET /users/kap/recent                         ... ok
  >            GET /users/will/recent                        ... ok
  >           POST /                                         ... ok
  >           POST /index.html                               ... ok
  >           POST /feed                                     ... ok
  >           POST /threads/thread                           ... ok
  >           POST /threads/0                                ... ok
  >           POST /threads/1                                ... ok
  >           POST /threads/2                                ... ok
  >           POST /users/new                                ... ok
  >           POST /users/user/follow                        ... ok
  >           POST /users/amit/follow                        ... ok
  >           POST /users/kap/follow                         ... ok
  >           POST /users/will/follow                        ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 7: Check simple requests to long paths with multiple directories
-------------------------------------------------------------------------------

  >            GET /path/to/file                             ... ok
  >            GET /it/was/the/best/of/times                 ... ok
  >            GET /it/was/the/worst/of/times                ... ok
  >            GET /vagrant/assignments/assignment2/http_router ... ok
  >            GET /a/b/c/d/e/f/g/h/i/j/k/l                  ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 8: Check simple requests to very short paths
-------------------------------------------------------------------------------

  >            GET                                           ... ok
  >            GET /                                         ... ok
  >            GET /a                                        ... ok
  >            GET /a1                                       ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 9: Check that leading and trailing slashes are ignored
-------------------------------------------------------------------------------

  >            GET path                                      ... ok
  >            GET /path                                     ... ok
  >            GET path/                                     ... ok
  >            GET /path/                                    ... ok
  >            GET path/to/file                              ... ok
  >            GET /path/to/file                             ... ok
  >            GET path/to/file/                             ... ok
  >            GET /path/to/file/                            ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 10: Check that paths are case-sensitive
-------------------------------------------------------------------------------

  >            GET /PATH                                     ... ok
  >            GET /Path                                     ... ok
  >            GET /pAth                                     ... ok
  >            GET /paTH                                     ... ok
  >            GET /PAth                                     ... ok
  >            GET /PATh                                     ... ok
  >            GET /PaTh                                     ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 11: Check that adding a route more than once updates its handler.
-------------------------------------------------------------------------------

  >            GET /pathA                                    ... ok
  >            GET /pathB                                    ... ok
  >            GET /pathC                                    ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 12: Ensure nonexistant paths don't resolve to ancestors or descendants
-------------------------------------------------------------------------------

  >            GET /a                                        ... ok
  >            GET /a/b                                      ... ok
  >            GET /a/b/c                                    ... ok
  >            GET /a/b/c/d                                  ... ok
  >            GET /a/b/c/d/e                                ... ok
  >            GET /a/b/c/d/e/f                              ... ok
  >            GET /a/b/c/d/e/f/g                            ... ok
  >            GET /a/b/c/d/e/f/g/h                          ... ok
  >            GET /a/b/c/d/e/f/g/h/i                        ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 13: Check that router finds the longest possible matching path
-------------------------------------------------------------------------------

  >            GET /a                                        ... ok
  >            GET /a/b                                      ... ok
  >            GET /a/b/c                                    ... ok
  >            GET /a/b/c/d                                  ... ok
  >            GET /a/b/c/d/e                                ... ok
  >            GET /a/b/c/d/e/f                              ... ok
  >            GET /a/b/c/d/e/f/g                            ... ok
  >            GET /a/b/c/d/e/f/g/h                          ... ok
  >            GET /a/b/c/d/e/f/g/h/i                        ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 14: Check that router can have subdirectories with same name as parent
-------------------------------------------------------------------------------

  >            GET /a                                        ... ok
  >            GET /a/a                                      ... ok
  >            GET /a/a/a                                    ... ok
  >            GET /a/a/a/a                                  ... ok
  >            GET /a/a/a/a/a                                ... ok
  >            GET /a/a/a/a/a/a                              ... ok
  >            GET /a/a/a/a/a/a/a                            ... ok
  >            GET /a/a/a/a/a/a/a/a                          ... ok
  >            GET /a/a/a/a/a/a/a/a/a                        ... ok
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 15: Check that routes with simple captures can be resolved at all
-------------------------------------------------------------------------------

  >            GET value                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /value HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET alice                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /alice HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET bob                                       ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /bob HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET charlie                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /charlie HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET denise                                    ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /denise HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET eve                                       ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 16: Check simple captures yield correct keys in query string
-------------------------------------------------------------------------------

  >            GET value                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /value HTTP/1.1
    Expected: key
    Received: 404 page not found

  >            GET alice                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /alice HTTP/1.1
    Expected: key
    Received: 404 page not found

  >            GET bob                                       ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /bob HTTP/1.1
    Expected: key
    Received: 404 page not found

  >            GET charlie                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /charlie HTTP/1.1
    Expected: key
    Received: 404 page not found

  >            GET denise                                    ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /denise HTTP/1.1
    Expected: key
    Received: 404 page not found

  >            GET eve                                       ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 17: Check simple captures yield correct keys in query string
-------------------------------------------------------------------------------

  >            GET value                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /value HTTP/1.1
    Expected: value
    Received: 404 page not found

  >            GET alice                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /alice HTTP/1.1
    Expected: alice
    Received: 404 page not found

  >            GET bob                                       ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /bob HTTP/1.1
    Expected: bob
    Received: 404 page not found

  >            GET charlie                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /charlie HTTP/1.1
    Expected: charlie
    Received: 404 page not found

  >            GET denise                                    ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /denise HTTP/1.1
    Expected: denise
    Received: 404 page not found

  >            GET eve                                       ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 18: Check that basic capture yields correct keys and values
-------------------------------------------------------------------------------

  >            GET value                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /value HTTP/1.1
    Expected: key=value
    Received: 404 page not found

  >            GET alice                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /alice HTTP/1.1
    Expected: key=alice
    Received: 404 page not found

  >            GET bob                                       ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /bob HTTP/1.1
    Expected: key=bob
    Received: 404 page not found

  >            GET charlie                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /charlie HTTP/1.1
    Expected: key=charlie
    Received: 404 page not found

  >            GET denise                                    ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key
    Request:  GET /denise HTTP/1.1
    Expected: key=denise
    Received: 404 page not found

  >            GET eve                                       ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 19: Check that capture works at the end of a long path
-------------------------------------------------------------------------------

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/value            ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/g/h/i/j/k/l/:key
    Request:  GET /a/b/c/d/e/f/g/h/i/j/k/l/value HTTP/1.1
    Expected: key=value
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/alice            ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/g/h/i/j/k/l/:key
    Request:  GET /a/b/c/d/e/f/g/h/i/j/k/l/alice HTTP/1.1
    Expected: key=alice
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/bob              ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/g/h/i/j/k/l/:key
    Request:  GET /a/b/c/d/e/f/g/h/i/j/k/l/bob HTTP/1.1
    Expected: key=bob
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/charlie          ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/g/h/i/j/k/l/:key
    Request:  GET /a/b/c/d/e/f/g/h/i/j/k/l/charlie HTTP/1.1
    Expected: key=charlie
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/denise           ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/g/h/i/j/k/l/:key
    Request:  GET /a/b/c/d/e/f/g/h/i/j/k/l/denise HTTP/1.1
    Expected: key=denise
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/g/h/i/j/k/l/eve              ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 20: Check that capture works in the middle of a long path
-------------------------------------------------------------------------------

  >            GET /a/b/c/d/e/f/value/g/h/i/j/k/l/           ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/:key/g/h/i/j/k/l/
    Request:  GET /a/b/c/d/e/f/value/g/h/i/j/k/l HTTP/1.1
    Expected: key=value
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/alice/g/h/i/j/k/l/           ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/:key/g/h/i/j/k/l/
    Request:  GET /a/b/c/d/e/f/alice/g/h/i/j/k/l HTTP/1.1
    Expected: key=alice
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/bob/g/h/i/j/k/l/             ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/:key/g/h/i/j/k/l/
    Request:  GET /a/b/c/d/e/f/bob/g/h/i/j/k/l HTTP/1.1
    Expected: key=bob
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/charlie/g/h/i/j/k/l/         ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/:key/g/h/i/j/k/l/
    Request:  GET /a/b/c/d/e/f/charlie/g/h/i/j/k/l HTTP/1.1
    Expected: key=charlie
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/denise/g/h/i/j/k/l/          ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/c/d/e/f/:key/g/h/i/j/k/l/
    Request:  GET /a/b/c/d/e/f/denise/g/h/i/j/k/l HTTP/1.1
    Expected: key=denise
    Received: 404 page not found

  >            GET /a/b/c/d/e/f/eve/g/h/i/j/k/l/             ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 21: Check that captures support any directory, not just the key name
-------------------------------------------------------------------------------

  >            GET /:capture                                 ... ok
  >            GET /pass                                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:capture
    - Method: GET   	Path: /path/:capture2
    Request:  GET /pass HTTP/1.1
    Expected: PASS
    Received: 404 page not found

  >            GET /path/:capture2                           ... ok
  >            GET /path/pass                                ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:capture
    - Method: GET   	Path: /path/:capture2
    Request:  GET /path/pass HTTP/1.1
    Expected: PASS
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 22: Check that several captures can appear in one route
-------------------------------------------------------------------------------

  >            GET /person/Alice/11                          ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /person/:name/:age
    - Method: GET   	Path: /add/:a/:b/:c/:d
    - Method: GET   	Path: /sub/:e/:f/:g/:h/other/path/info
    Request:  GET /person/Alice/11 HTTP/1.1
    Expected: age=11&name=Alice
    Received: 404 page not found

  >            GET /person/Bob/22                            ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /person/:name/:age
    - Method: GET   	Path: /add/:a/:b/:c/:d
    - Method: GET   	Path: /sub/:e/:f/:g/:h/other/path/info
    Request:  GET /person/Bob/22 HTTP/1.1
    Expected: age=22&name=Bob
    Received: 404 page not found

  >            GET /person/Charlie/33                        ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /person/:name/:age
    - Method: GET   	Path: /add/:a/:b/:c/:d
    - Method: GET   	Path: /sub/:e/:f/:g/:h/other/path/info
    Request:  GET /person/Charlie/33 HTTP/1.1
    Expected: age=33&name=Charlie
    Received: 404 page not found

  >            GET /person/Dave/44                           ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /person/:name/:age
    - Method: GET   	Path: /add/:a/:b/:c/:d
    - Method: GET   	Path: /sub/:e/:f/:g/:h/other/path/info
    Request:  GET /person/Dave/44 HTTP/1.1
    Expected: age=44&name=Dave
    Received: 404 page not found

  >            GET /person/Eve/55                            ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /person/:name/:age
    - Method: GET   	Path: /add/:a/:b/:c/:d
    - Method: GET   	Path: /sub/:e/:f/:g/:h/other/path/info
    Request:  GET /person/Eve/55 HTTP/1.1
    Expected: age=55&name=Eve
    Received: 404 page not found

  >            GET /add/1/2/3/4                              ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 23: Check that multiple values can be captured under a single key
-------------------------------------------------------------------------------

  >            GET a/b                                       ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key/:key
    Request:  GET /a/b HTTP/1.1
    Expected: a&b
    Received: 404 page not found

  >            GET foo/bar                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key/:key
    Request:  GET /foo/bar HTTP/1.1
    Expected: bar&foo
    Received: 404 page not found

  >            GET 123/456                                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key/:key
    Request:  GET /123/456 HTTP/1.1
    Expected: 123&456
    Received: 404 page not found

  >            GET alice/bob                                 ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key/:key
    Request:  GET /alice/bob HTTP/1.1
    Expected: alice&bob
    Received: 404 page not found

  >            GET value/value                               ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:key/:key
    Request:  GET /value/value HTTP/1.1
    Expected: value&value
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 24: Tests that keys are overwritten when adding several capturing routes
-------------------------------------------------------------------------------

  >            GET /foo                                      ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: :alice
    - Method: GET   	Path: :bob
    - Method: GET   	Path: :charlie
    - Method: GET   	Path: :dave
    - Method: GET   	Path: :eve
    - Method: GET   	Path: /user/:alice/files
    - Method: GET   	Path: /user/:bob/files
    - Method: GET   	Path: /user/:charlie/files
    - Method: GET   	Path: /user/:dave/files
    - Method: GET   	Path: /user/:eve/files
    Request:  GET /foo HTTP/1.1
    Expected: eve
    Received: 404 page not found

  >            GET /user/foo/files                           ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: :alice
    - Method: GET   	Path: :bob
    - Method: GET   	Path: :charlie
    - Method: GET   	Path: :dave
    - Method: GET   	Path: :eve
    - Method: GET   	Path: /user/:alice/files
    - Method: GET   	Path: /user/:bob/files
    - Method: GET   	Path: /user/:charlie/files
    - Method: GET   	Path: /user/:dave/files
    - Method: GET   	Path: /user/:eve/files
    Request:  GET /user/foo/files HTTP/1.1
    Expected: eve
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 25: Check that non-capturing routes have precedence over capturing ones
-------------------------------------------------------------------------------

  >            GET /path/to/value                            ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /path/to/:file
    - Method: GET   	Path: /path/to/file
    Request:  GET /path/to/value HTTP/1.1
    Expected: value
    Received: 404 page not found

  >            GET /path/to/null                             ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /path/to/:file
    - Method: GET   	Path: /path/to/file
    Request:  GET /path/to/null HTTP/1.1
    Expected: null
    Received: 404 page not found

  >            GET /path/to/test                             ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /path/to/:file
    - Method: GET   	Path: /path/to/file
    Request:  GET /path/to/test HTTP/1.1
    Expected: test
    Received: 404 page not found

  >            GET /path/to/file                             ... ok
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 26: Check non-capturing route precedence with ambiguous routes.
-------------------------------------------------------------------------------

  >            GET /animals/reptiles/images                  ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /animals/mammals/:species
    - Method: GET   	Path: /animals/:type/images
    Request:  GET /animals/reptiles/images HTTP/1.1
    Expected: reptiles
    Received: 404 page not found

  >            GET /animals/birds/images                     ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /animals/mammals/:species
    - Method: GET   	Path: /animals/:type/images
    Request:  GET /animals/birds/images HTTP/1.1
    Expected: birds
    Received: 404 page not found

  >            GET /animals/amphibians/images                ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /animals/mammals/:species
    - Method: GET   	Path: /animals/:type/images
    Request:  GET /animals/amphibians/images HTTP/1.1
    Expected: amphibians
    Received: 404 page not found

  >            GET /animals/mammals/lions                    ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /animals/mammals/:species
    - Method: GET   	Path: /animals/:type/images
    Request:  GET /animals/mammals/lions HTTP/1.1
    Expected: lions
    Received: 404 page not found

  >            GET /animals/mammals/tigers                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /animals/mammals/:species
    - Method: GET   	Path: /animals/:type/images
    Request:  GET /animals/mammals/tigers HTTP/1.1
    Expected: tigers
    Received: 404 page not found

  >            GET /animals/mammals/bears                    ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 27: Check non-capturing route precedence with very ambiguous routes.
-------------------------------------------------------------------------------

  >            GET /a/b/c/d/e                                ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /a/b/:c/:d/:e
    - Method: GET   	Path: /a/:b/c/:d/e
    - Method: GET   	Path: /:a/b/c/d/:e
    - Method: GET   	Path: /:a/b/:c/d/:e
    - Method: GET   	Path: /a/:b/c/:d/e
    Request:  GET /a/b/c/d/e HTTP/1.1
    Expected: PASS
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 28: Check that greedy resolution doesn't cause you to ignore valid routes
-------------------------------------------------------------------------------

  >            GET /this/path/willnot/work                   ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /this/path/:will/work
    - Method: GET   	Path: /this/path/willnot/
    Request:  GET /this/path/willnot/work HTTP/1.1
    Expected: PASS
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 29: Check precedence and greedy resolution with ambiguous routes.
-------------------------------------------------------------------------------

  >            GET /a/b/c/d/e                                ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:a/b/c/d/e
    - Method: GET   	Path: /a/:b/c/d/e
    - Method: GET   	Path: /a/b/:c/d/e
    - Method: GET   	Path: /a/b/c/:d/f
    Request:  GET /a/b/c/d/e HTTP/1.1
    Expected: PASS
    Received: 404 page not found

###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 30: Check precedence and greedy resolution with very ambiguous routes.
-------------------------------------------------------------------------------

  >            GET /a/b/c/d/e                                ... FAIL

    ********* TEST FAILED *********
    Routes:
    - Method: GET   	Path: /:a/b/c/d/:e
    - Method: GET   	Path: /:a/:b/c/d/e
    - Method: GET   	Path: /:a/:b/:c/d/f
    - Method: GET   	Path: /:a/:b/:c/:d/e
    - Method: GET   	Path: /a/b/c/:d/f
    Request:  GET /a/b/c/d/e HTTP/1.1
    Expected: PASS
    Received: 404 page not found

###
                               -- test failed (-1.0) --

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed  14 / 30  tests     (16 failed)
>            Passed 125 / 199 subtests  (74 failed)
>
>        Score:
>            14.00 points of a possible 30.00  (46.67%)
>     ========================================================


That is a  nice idea in general but setup.py is not the best place. The pix2pixhd library will not be installed with the rest of the code. You either need to check this at runtime, copy all the files including the cloned repo on installation or fork and adapt pix2pixhd to be pypi compatible (like we did for pylsd)

I would recommend to **not** automate this and fail the dewarping script if the `pix2pixHD` parameter is not set, with a message explaining to clone the repository and set the path.


<html>test</html>


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

* https://dashboards.joaorfclopes.now.sh
* https://dashboards-git-master.joaorfclopes.now.sh


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

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


thanks, @erikzhang


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

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

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

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/linux-x64/circle-develop-3111ae102740efd7e9004528c66bbc2515afe2df-141050/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.4.1/circle-develop-3111ae102740efd7e9004528c66bbc2515afe2df-141060/cypress.tgz