-------------------------------------------------------------------------------
  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 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 10: Check that adding a route more than once updates its handler.
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 11: 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 12: 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 13: 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 14: Check that routes with simple captures can be resolved at all
-------------------------------------------------------------------------------

  >            GET value                                     ... FAIL
    router_test.go:426:

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

  >            GET alice                                     ... FAIL
    router_test.go:426:

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

  >            GET bob                                       ... FAIL
    router_test.go:426:

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

  >            GET charlie                                   ... FAIL
    router_test.go:426:

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

  >            GET denise                                    ... FAIL
    router_test.go:426:

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

  >            GET eve                                       ... FAIL
    router_test.go:426:

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

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

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

  >            GET value                                     ... FAIL
    router_test.go:426:

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

  >            GET alice                                     ... FAIL
    router_test.go:426:

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

  >            GET bob                                       ... FAIL
    router_test.go:426:

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

  >            GET charlie                                   ... FAIL
    router_test.go:426:

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

  >            GET denise                                    ... FAIL
    router_test.go:426:

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

  >            GET eve                                       ... FAIL
    router_test.go:426:

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

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

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

  >            GET value                                     ... FAIL
    router_test.go:426:

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

  >            GET alice                                     ... FAIL
    router_test.go:426:

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

  >            GET bob                                       ... FAIL
    router_test.go:426:

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

  >            GET charlie                                   ... FAIL
    router_test.go:426:

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

  >            GET denise                                    ... FAIL
    router_test.go:426:

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

  >            GET eve                                       ... FAIL
    router_test.go:426:

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

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

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

  >            GET value                                     ... FAIL
    router_test.go:426:

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

  >            GET alice                                     ... FAIL
    router_test.go:426:

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

  >            GET bob                                       ... FAIL
    router_test.go:426:

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

  >            GET charlie                                   ... FAIL
    router_test.go:426:

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

  >            GET denise                                    ... FAIL
    router_test.go:426:

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

  >            GET eve                                       ... FAIL
    router_test.go:426:

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

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

-------------------------------------------------------------------------------
  Test 18: 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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/eve HTTP/1.1
    Expected: key=eve
    Received: 404 page not found

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

-------------------------------------------------------------------------------
  Test 19: 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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/eve/g/h/i/j/k/l HTTP/1.1
    Expected: key=eve
    Received: 404 page not found

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

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

  >            GET /:capture                                 ... ok
  >            GET /pass                                     ... FAIL
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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 21: Check that several captures can appear in one route
-------------------------------------------------------------------------------

  >            GET /person/Alice/11                          ... FAIL
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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 /add/1/2/3/4 HTTP/1.1
    Expected: a=1&b=2&c=3&d=4
    Received: 404 page not found

  >            GET /add/5/6/7/8                              ... FAIL
    router_test.go:426:

    ********* 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 /add/5/6/7/8 HTTP/1.1
    Expected: a=5&b=6&c=7&d=8
    Received: 404 page not found

  >            GET /add/316/317/318/319                      ... FAIL
    router_test.go:426:

    ********* 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 /add/316/317/318/319 HTTP/1.1
    Expected: a=316&b=317&c=318&d=319
    Received: 404 page not found

  >            GET /add/0/0/1/2                              ... FAIL
    router_test.go:426:

    ********* 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 /add/0/0/1/2 HTTP/1.1
    Expected: a=0&b=0&c=1&d=2
    Received: 404 page not found

  >            GET /add/3/5/8/13                             ... FAIL
    router_test.go:426:

    ********* 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 /add/3/5/8/13 HTTP/1.1
    Expected: a=3&b=5&c=8&d=13
    Received: 404 page not found

  >            GET /sub/1/2/3/4/other/path/info              ... FAIL
    router_test.go:426:

    ********* 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 /sub/1/2/3/4/other/path/info HTTP/1.1
    Expected: e=1&f=2&g=3&h=4
    Received: 404 page not found

  >            GET /sub/5/6/7/8/other/path/info              ... FAIL
    router_test.go:426:

    ********* 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 /sub/5/6/7/8/other/path/info HTTP/1.1
    Expected: e=5&f=6&g=7&h=8
    Received: 404 page not found

  >            GET /sub/316/317/318/319/other/path/info      ... FAIL
    router_test.go:426:

    ********* 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 /sub/316/317/318/319/other/path/info HTTP/1.1
    Expected: e=316&f=317&g=318&h=319
    Received: 404 page not found

  >            GET /sub/0/0/1/2/other/path/info              ... FAIL
    router_test.go:426:

    ********* 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 /sub/0/0/1/2/other/path/info HTTP/1.1
    Expected: e=0&f=0&g=1&h=2
    Received: 404 page not found

  >            GET /sub/3/5/8/13/other/path/info             ... FAIL
    router_test.go:426:

    ********* 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 /sub/3/5/8/13/other/path/info HTTP/1.1
    Expected: e=3&f=5&g=8&h=13
    Received: 404 page not found

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

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

  >            GET a/b                                       ... FAIL
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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 23: Tests that keys are overwritten when adding several capturing routes
-------------------------------------------------------------------------------

  >            GET /foo                                      ... FAIL
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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 24: Check that non-capturing routes have precedence over capturing ones
-------------------------------------------------------------------------------

  >            GET /path/to/value                            ... FAIL
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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
    router_test.go:426:

    ********* 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 25: Check that greedy resolution doesn't cause you to ignore valid paths
-------------------------------------------------------------------------------

  >            GET /this/path/willnot/work                   ... FAIL
    router_test.go:426:

    ********* 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 summary:
>            Passed  13 / 25  tests     (12 failed)
>            Passed 115 / 179 subtests  (64 failed)
>
>        Score:
>            13.00 points of a possible 25.00  (52.00%)
>     ========================================================


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

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

{
    "version": 2,
    "name": "venia",
    "alias": [
        "magento-venia-develop"
    ],
    "scope": "magento-research",
    "env": {
        "UPWARD_JS_BIND_LOCAL": "false",
        "IMAGE_OPTIMIZING_ORIGIN": "backend",
        "MAGENTO_BACKEND_URL": "https://master-7rqtwti-mfwmkrjfqvbjk.us-4.magentosite.cloud/",
        "NODE_ENV": "production"
    },
    "build": {
        "env": {
            "MAGENTO_BACKEND_URL": "https://master-7rqtwti-mfwmkrjfqvbjk.us-4.magentosite.cloud/"
        }
    },
    "builds": [
        {
            "src": "src/package.json",
            "use": "@now/static-build"
        },
        {
            "config": {
                "includeFiles": [
                    "package.json",

                ],
                "maxLambdaSize": "20mb"
            }
        }
    ],
    "routes": [
        {
            "src": "^/([0-9A-Fa-e]\\.svg)",
            "dest": "src/$1"
        },

        {
            "src": "^/(js/.*\\.js)",
            "dest": "src/$1"
        }

    ],
    "regions": [
        "sfo1",
        "bru"
    ],
    "public": true
}

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


<details>

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

Client ID project/taskcluster/tc-github/production-2 does not have sufficient scopes and is missing the following scopes:

```
secrets:get:repo:github.com/mozilla/balrog:coveralls
```

This request requires the client to satisfy the following scope expression:

```
{
  "AllOf": [
    "secrets:get:repo:github.com/mozilla/balrog:coveralls",
    "queue:route:statuses",
    {
      "AnyOf": [
        {
          "AllOf": [
            "queue:scheduler-id:taskcluster-github",
            {
              "AnyOf": [
                "queue:create-task:highest:aws-provisioner-v1/github-worker",
                "queue:create-task:very-high:aws-provisioner-v1/github-worker",
                "queue:create-task:high:aws-provisioner-v1/github-worker",
                "queue:create-task:medium:aws-provisioner-v1/github-worker",
                "queue:create-task:low:aws-provisioner-v1/github-worker",
                "queue:create-task:very-low:aws-provisioner-v1/github-worker",
                "queue:create-task:lowest:aws-provisioner-v1/github-worker"
              ]
            }
          ]
        },
        {
          "AnyOf": [
            "queue:create-task:aws-provisioner-v1/github-worker",
            {
              "AllOf": [
                "queue:define-task:aws-provisioner-v1/github-worker",
                "queue:task-group-id:taskcluster-github/HhnFsMsNTtetuxHOzzdUag",
                "queue:schedule-task:taskcluster-github/HhnFsMsNTtetuxHOzzdUag/HhnFsMsNTtetuxHOzzdUag"
              ]
            }
          ]
        }
      ]
    }
  ]
}
```

---

* method:     createTask
* errorCode:  InsufficientScopes
* statusCode: 403
* time:       2019-07-22T14:43:33.504Z

</details>


Название файлов с компонентами тоже должно начинаться с большой буквы.


wouldn't that be the name of the parameter though?


麻烦完下，cordova-plugin-tencent-mlvb  这个插件，您什么时候能更新ios未完善的功能呢，非常感谢。


Yes, I forgot to remove it after changing the parse function's signature (previously I just returned _frame_list, but later changed it so that the caller allocates it).

This is also related to the comment below (about returning _frame_list), so I guess it's best to keep this internally and return it through parse().


likely line 131, change that to just `project.version`


Thanks for the clarification @samm82.  I had already edited my comment after I realized this was the game physics example.  I was looking for "AB" and "AP" in the code; I should have been thinking about the output of the generator.  😄


спробуй ще так
text.replaceAll("\\s+"," ");
в цій функції перший параметр вичитується як регулярка


@adelRestom It's all good :) I just made a new commit fixing 2 and 3.


I somewhat find there are too many names ranging over objects, but I think lower case of the name of the category makes sense.


How can we prevent it from happening in future? This broken code passes CI. @zhouqiang-cl


So in a case like this, where should `Label "O"` be defined so that it can be reused?


Yes, I was a bit confused on this. Good to clarify.


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

* https://oneapi.now.sh
* https://oneapi.bazzite-opensource.now.sh
* https://oneapi-git-develop.bazzite-opensource.now.sh


Deployment failed with the following error:

~~~
Failed to validate now.json: Invalid request: builds[1] should have required property 'use'
~~~


Successfully aliased the URL <https://synadia-website-abqdqt3kx.now.sh> to the following aliases:

* https://synadia.com
* https://downloads.synadia.com
* https://www.synadia.com
* https://synadia-website.connecteverything.now.sh
* https://synadia-website-git-master.connecteverything.now.sh


Successfully aliased the URL <https://my-gatsby-project-atm4djyt0.now.sh> to the following aliases:

* https://my-gatsby-project.faramazpat.now.sh
* https://my-gatsby-project-git-master.faramazpat.now.sh


Related to https://github.com/IntelLabs/vdms/commit/c3227aee366782cda55ae3f9894ae3f76a869724#commitcomment-34396387, I'll change this to return the list.


Successfully aliased the URL <https://voicestoemotions-24d8me12c.now.sh> to the following aliases:

* https://voices-to-emotions.com
* https://www.voices-to-emotions.com
* https://voices-to-emotions.osoc19.now.sh
* https://voices-to-emotions-git-master.osoc19.now.sh


Will fix.


Дуже добре, молодець


@JuliaRegistrator register

Release notes:
v0.1.14
  - Add compat to Project.toml
  - Julian function names (part)
  - descriptive_!() -> descriptive_()
  - randomtable() included and add test


Yes, this was needed for decoding (not needed for parsing though).


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

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

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


How should I properly test this without adding a payable function to Stoppable? Or should I test this in Splitter? :P


Problem with `selfdestruct` is that it removes the contract code from the network, so if someone sends funds here by mistake; they are trapped forever. Try to implement it like you did with `pasuse`, only difference is that a killed contract cannot be resumed.


Yes, av_packet_alloc() returns NULL on failure anyway


Не нужно писать Object. Интерфейсом объекты и описываются ). Но если бы это был тип (type) - то все равно не нужно писать.


@Rocky640 It's really difficult to come up with something better (and more readable), in fact!!! So, good job!
Further improving the comments is always a good idea, imho. :-)

Just one more suggestion: do we really need to flag this pawn as passed since we don't score it here but in our main eval? Simply OR it to the passedPawns[Us] bitboard.
```
        if (      !(stoppers ^ lever)
            || (  !(stoppers ^ leverPush)
                &&  popcount(phalanx) >= popcount(leverPush))
            || (    r >= RANK_5
                &&  stoppers == square_bb(s + Up)
                && (shift<Up>(support) & ~(theirPawns | dblAttackThem)))
            e->passedPawns[Us] |= s;
```


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

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


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

* https://oneapi.now.sh
* https://oneapi.bazzite-opensource.now.sh
* https://oneapi-git-develop.bazzite-opensource.now.sh


does dividing it by 2.0 not make sure it's a double? there was no compile error


> @dyf19118 , do you can related issue link?

Thanks for your reply, i haven't created a issue yet so i can't provide a link . The [jsfiddle](https://jsfiddle.net/dyf19118/bjxc43zp/) i provided shows a different use case error than the test example of this fix. But since this fix can also solve my problem, i think there's no need to create an another issue any more.

I just want to know how this bug causes my problem, and after several hours of debugging i have got it. It seems that there's no direct relation between this bug and my problem, the problem is caused unintentionally and the test example just can't cover all cases.

Anyone interested can use my jsfiddle to have a try and debug, load and run the jsfiddle, click submit button with no midification, and you can see the error message occurs at unexpected place.


Ωραίος εδώ! Απλά θέλουν αλλαγή τα name των httpGet και httpPost, στη μια περίπτωση το Get είναι HTTP verb στην περίπτωση του Post εννοείς το Post resource.


That being said, would it be complicated to create a simple txt log file summing up the table creation process so users could check which tables were created?


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

* https://destiny.report
* https://destiny-report.sarkurd.now.sh
* https://destiny-report-git-master.sarkurd.now.sh


@jmmk @thadeshammer had to update mongolastic to work with ES-5.6 ... i don't see why we can't just bring this in-house and maintain this logic ourselves... this library isn't doing anything fancy


Προσπάθησε για convention να κρατήσεις αυτή την ονομασία στα http requests πχ. createPost, updatePost, getPost etc.


και εδώ, rename το Helpers σε lowercase


Need to move the hostobject to a different component. Operator service is a base component. Having hostobject there causes un-intended problems.


Looks good, thanks a lot!
I'll want to clarify in the help message and the docs that this is optional; I'm currently traveling, so I'll probably leave this unmerged until early August.


These constant should reside in a different component.


Resolves hypertrack/issues#1509


All tables should *always* be created - if not, there should be an error message. LimeSurvey is not designed to work with a half-baked database install.


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

* https://neojs.dev
* https://nextjs.neosiae.now.sh
* https://nextjs-git-master.neosiae.now.sh


There won't be a compiler error because an integer divided by a floating-point type is implicitly converted into a floating point type by the compiler. In my experience though, it's always good to be explicit about these casts and cast directly to what we want.


`Data`, `Methods`, `Computed` and `Props` are not used, wouldn't be better removed them?


Πρόσεχε λίγο με τα ορθογραφικά στο commit message έχεις δυο _refactor: **imporve** **BrouswerRouter** as Router and use Switch_


Checking to see if the list you are deleting isn't the first list, if so I am setting the `activeTodoListId` to the second `id` in the list, of not I am setting it to the first `id` in the list.


-------------------------------------------------------------------------------
  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 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 10: Check that adding a route more than once updates its handler.
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 11: 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 12: 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 13: 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 14: 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

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

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

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

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

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

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

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

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

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

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

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

    ********* 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/eve HTTP/1.1
    Expected: key=eve
    Received: 404 page not found

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

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

    ********* 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/eve/g/h/i/j/k/l HTTP/1.1
    Expected: key=eve
    Received: 404 page not found

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

-------------------------------------------------------------------------------
  Test 20: 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 21: 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

    ********* 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 /add/1/2/3/4 HTTP/1.1
    Expected: a=1&b=2&c=3&d=4
    Received: 404 page not found

  >            GET /add/5/6/7/8                              ... 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 /add/5/6/7/8 HTTP/1.1
    Expected: a=5&b=6&c=7&d=8
    Received: 404 page not found

  >            GET /add/316/317/318/319                      ... 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 /add/316/317/318/319 HTTP/1.1
    Expected: a=316&b=317&c=318&d=319
    Received: 404 page not found

  >            GET /add/0/0/1/2                              ... 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 /add/0/0/1/2 HTTP/1.1
    Expected: a=0&b=0&c=1&d=2
    Received: 404 page not found

  >            GET /add/3/5/8/13                             ... 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 /add/3/5/8/13 HTTP/1.1
    Expected: a=3&b=5&c=8&d=13
    Received: 404 page not found

  >            GET /sub/1/2/3/4/other/path/info              ... 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 /sub/1/2/3/4/other/path/info HTTP/1.1
    Expected: e=1&f=2&g=3&h=4
    Received: 404 page not found

  >            GET /sub/5/6/7/8/other/path/info              ... 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 /sub/5/6/7/8/other/path/info HTTP/1.1
    Expected: e=5&f=6&g=7&h=8
    Received: 404 page not found

  >            GET /sub/316/317/318/319/other/path/info      ... 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 /sub/316/317/318/319/other/path/info HTTP/1.1
    Expected: e=316&f=317&g=318&h=319
    Received: 404 page not found

  >            GET /sub/0/0/1/2/other/path/info              ... 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 /sub/0/0/1/2/other/path/info HTTP/1.1
    Expected: e=0&f=0&g=1&h=2
    Received: 404 page not found

  >            GET /sub/3/5/8/13/other/path/info             ... 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 /sub/3/5/8/13/other/path/info HTTP/1.1
    Expected: e=3&f=5&g=8&h=13
    Received: 404 page not found

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

-------------------------------------------------------------------------------
  Test 22: 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 23: 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 24: 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 25: Check that greedy resolution doesn't cause you to ignore valid paths
-------------------------------------------------------------------------------

  >            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 summary:
>            Passed  13 / 25  tests     (12 failed)
>            Passed 115 / 179 subtests  (64 failed)
>
>        Score:
>            13.00 points of a possible 25.00  (52.00%)
>     ========================================================


As a general comment, the entire `target` directory should be ignored as it is full of compiler output that is not necessary to be in the source tree.


Deployment failed with the following error:

~~~
Failed to validate now.json: Invalid request: builds[1] should have required property 'use'
~~~


Форму тоже следует вынести в отдельный компонент.


Yes, I'll include the exception header.


Και εδώ **Boundary** instead of Bounry or ErrorBoundry. Πρόσεχέ λίγο τα ορθογραφικά θα τα ψάχνουμε με το search του editor και δεν θα τα βρίσκουμε.


I think this comment should be removed as it doesn't add any useful information for us.


Для корректной работы компонента необходимо ещё настроить переадресацию URL в файле .htaccess:


Will do.


Και στο commit message


Yes, it belongs there.


Resolves hypertrack/issues#1509


Here is the version with my latest changes, I would rather leave it this way.
It does not matter for the compiler.
https://github.com/official-stockfish/Stockfish/compare/master...Rocky640:PawnCleanUp


Можно так: const newArray = [ ...this.state.toDoArray ]


In general, no, since we always use parallelLevel-based function to get the number of threads. If parallelLevel is 0, just like in this case, it just always returns 1.


I had to wrap each item so I could relatively position the list delete button.


Προσπάθησε να αφήνεις κενά μεταξύ των import και των export.


It's a good idea to refactor the creation of this `filtered` array into a private method. This allows us to improve readability of the constructor and code in general.


We prefer not to have so much logic in the constructor. I would recommend moving this logic out into the getOutput function.


I think this variable needs a better name that explains it's purpose for existing as a member of the class.


Commented out code should always be removed.


This comment isn't necessary, it's clear from context


Весь этот цикл можно заменить на const newArray = this.state.toDoArray.filter(item => item.id !== id);


Should me moved to an environment variable. Also, we miss you :P


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

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


.menu-bg {
  background-color: #D7E1CE;
  color: #5B4943;
}


Thanks. d6d0bb054219da26a55f880f48f00902a4fbaf56


Relates https://github.com/elastic/elasticsearch/issues/44695


Hello


[vg CI tests](https://ucsc-ci.com/vgteam/vg/pipelines/1144) complete for branch handleify.  View the [full report here](http://vg-data.s3.amazonaws.com/vg_ci/vgci_reports/commit/560f79c8d47f72986627dae1fed8111e523073c7/index.html).

5 tests passed, 14 tests failed and 0 tests skipped in 12045 seconds

Failed tests:

* test_map_mhc_primary (313 seconds)
* test_map_mhc_primary_genotype (680 seconds)
* test_sim_chr21_snp1kg (1722 seconds)
* test_sim_chr21_snp1kg_trained (746 seconds)
* test_sim_mhc_cactus (524 seconds)
* test_sim_mhc_snp1kg (262 seconds)
* test_sim_mhc_snp1kg_mpmap (220 seconds)
* test_sim_yeast_cactus (1194 seconds)
* test_full_brca2_cactus (35 seconds)
* test_full_brca2_primary (35 seconds)
* test_map_brca1_cactus (32 seconds)
* test_map_brca1_primary (30 seconds)
* test_map_brca1_snp1kg (32 seconds)
* test_map_brca1_snp1kg_genotype (38 seconds)


That's right. On the other hand, as we discussed during the last week's sync, maybe we should move this functionality entirely outside of the Video class, as *any* read operation on the video renders key frame parsing moot (the video would've been decoded already anyway).

I still couldn't quite come up with what's the best way without reordering _operations.


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

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


^ Actually, maybe it sometimes matters anyway. I'm seeing segfaults during application exit sometimes (not frequently), when running in the actually-supported manner (`python3 launch.py`). I think those may also be related to this change, though they're not attributed to anything and there's no traceback.

Yesterday, though, _libopenshot_ threw an exception in its Timeline destructor, again as the program was exiting.


jglakj


<details>

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

InterpreterError at template.tasks[0]: object keys must be strings

</details>


By using uuid version 3.0.0 I'm still getting error:
_referenceerror: global is not defined at rng-browser.js_


можеш конвертнути стрінгу в стрінгбілдер і там викликати функцію reverse()


This filtering by env type was done because we didn't have time to work on a proper fix. Please check if this can be refactored and whether we can remove environment specific code here.


Je n’ai réalisé que le bouton “Editer note” permettait une édition manuelle qu’après mes dernières modifs.
Du coup, c’est effectivement tentant d’en rester au textarea, et de changer le “Editer note” en "Edition manuelle”!
Que faudrait il faire pour que ce textarea soit transmis lors de l’écriture de la note?
Ma dernière version est encore très bancale (trop copier/collé sans vraiment comprendre!!). Par exemple, la fonction add_new_group  ajoute bien une nouvelle ligne, mais casse les précédentes!!

A+

Henri Gouraud
06 08 45 34 21

> Le 22 juil. 2019 à 12:32, lledieu <notifications@github.com> a écrit :
>
> Pas top car il va y avoir 2 appels JSON, un pour chaque tableau...
> Je préférais la solution textarea qui permettait de simplifier le problème.
> Il va falloir repenser la source de données avec DataTables mais je n'ai pas encore expérimenté cette façon de faire.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


@kpalmqui 9e22edc addresses your comment.


Perhaps it'd make sense to add the possibility to tag attributes with the standard they are applicable to. Something like `<use-retval std=c++11/>` (the exact syntax could probably be tweaked but you get the idea)?


I'm turning this into a set if you don't mind. Mostly semantics because performance with 2 elements won't make any difference.


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

* https://jesmodrazik.fr
* https://www.jesmodrazik.fr
* https://jesmodrazik.drazik.now.sh
* https://jesmodrazik-git-master.drazik.now.sh


I think not - I read something about that in some agda issues recently.


y


Percolation Thresholds in Square/percolation.py

`or` or `and`? Basically a cell should get flooded if upper cell is flooded **not** if upper cell is simply vacant but was not flooded.


I think it's a convention used by some category theorists as well.


Aliasing was ignored due to a new commit existing for this branch, which will be aliased instead.


Successfully aliased the URL <https://sun-shine-builders-adb7c2wu8.now.sh> to the following aliases:

* https://sun-shine-builders.harshppatel2880.now.sh
* https://sun-shine-builders-git-master.harshppatel2880.now.sh


So there's a zero-width space here that kills HTML tags?


@JuliaRegistrator: register


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

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


A gotcha here would be to protect the user from accidentally killing the contract, which has irreversible outcomes!
You can do that by making it a 2-step process:
1. The user calls the `pause` function
2. The user calls the `kill` function (which uses the modifier that checks that the contract is paused)


Hello,
following Uyen orientation I'm posting here a suggestion for Ledger Live (not sure if I'm posting correctly, I apologize in advance for misplacement).

I think there should be the option to show balances (on Accounts or Portfolio sections) in FIAT and Crypto at the same time, both lines on the chart simultaneously, instead of only one at a time (so, suggestion is having 3 options for the chart: Crypto or Fiat, like it already has, plus the option of both together).
In Portfolio section it only shows FIAT, while in the Accounts section it shows FIAT currency OR the CryptoCurrency (e.g. BTC), but not both at the same time.

Best Regards


Successfully aliased the URL <https://sun-shine-builders-1iwn93beg.now.sh> to the following aliases:

* https://sun-shine-builders.harshppatel2880.now.sh
* https://sun-shine-builders-git-master.harshppatel2880.now.sh


add shell sh as valid shell for usePipefail

this can be verified with these to docker file:

```
FROM alpine:3.8

SHELL ["/bin/sh","-o", "pipefail","-c"]
RUN exit 1 | echo "bonjour" > file.txt
```
that will fail at build

and this one :
```
FROM alpine:3.8

SHELL ["/bin/sh","-c"]
RUN exit 1 | echo "bonjour" > file.txt
```
that won't fail


@gelever Thanks a ton for this. As a novice developer, building and using cmake has ironically been one of the most challenging aspects of the project. Also, sorry for the delayed response, as I just got back from Holiday.


please integrate sending message to Telegram..., very thanks...


`whenRunning` is less mental overload, no? 🙂


centence = centence.replaceAll("\\s+", " ");


`whenAlive`.


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


Can you add a comment explaining why not? (I'd expect clang to support it in general :)


This gives the owner too much power, they can kill the contract then steal all the funds. Of course there is no right way about this, because for instance maybe some user found a way to hack the contract so the owner kills it and moves the funds to a safe place...


EXAMPLE:

:global TelegramToken "YOUR TOKEN"
:global TelegramGroupID "-YOUR ID"
:global TelegramURL "https://api.telegram.org/bot$TelegramToken/sendMessage?chat_id=$TelegramGroupID&parse_mode=Markdown&text="

/system package update
check-for-updates

:global InstalledVersion
:global LatestVersion

:global OSversion
:set OSversion [/system resource get version]
:global SystemName
:set SystemName [/system identity get name]

:set InstalledVersion [get installed-version]
:set LatestVersion [get latest-version]
:delay 1s;

:if ($InstalledVersion != $LatestVersion) do={
      :local TelegramMessage "*$SystemName upozornenie $OSversion* %0ASystem bude upgradovany z verzie $InstalledVersion na $LatestVersion.%0A*Instalujem and Restartujem !!!*"
      /tool fetch url=($TelegramURL . $TelegramMessage) keep-result=no
    install
}


Interesting idea. So after percolating downwards, the sideways percolation loops now happen overall `len(M)` times
So, surely a flooded cell in any row will percolate on over to the left or right fully.
But recall we percolate downwards only at the beginning, before all this left-right shaking

So remember out example on phonecall? We percolate along last column. This logic is in lines 26-30
Good. Then from this new code of qwerty loop we flood the entire second last row successfully.
Then that's it. We don't percolate downwards in the last row (downwards percolation logic is already over)


It's the version of the actual repository files for the package. Lets you specify an upgrade to the package without there being a new release of the package upstream. Usually used to fix bugs in the build script, add patches etc.


README


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

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


TeamCity Glyssen / Glyssen pull requests [Build *.*.388.84da6b9a2548b637f4aac969cd71849f8356d805](https://build.palaso.org/viewLog.html?buildId=157359&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **SUCCESS**
Summary: Tests passed: 2165, ignored: 18 Build time: 00:09:51


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


Successfully aliased the URL <https://redfish-server-prod-3njzyv6qt.now.sh> to the following aliases:

* https://redfish-server-prod.guandjoy.now.sh
* https://redfish-server-prod-git-master.guandjoy.now.sh


Successfully aliased the URL <https://nar-serve-r0dnkz77t.now.sh> to the following aliases:

* https://nar-serve.zimbatm.now.sh
* https://nar-serve-git-master.zimbatm.now.sh


TeamCity Glyssen / Glyssen pull requests [Build *.*.389.b45e6a2e1683095397fbe66dad14b013b48311a3](https://build.palaso.org/viewLog.html?buildId=157361&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **FAILURE**
Summary: Compilation error: GlyssenTests\GlyssenTests.csproj (new) Build time: 00:01:04


TeamCity Glyssen / Glyssen pull requests [Build *.*.387.61d2bf5f008c58318214a3ff43235985c6ba9da0](https://build.palaso.org/viewLog.html?buildId=157358&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **SUCCESS**
Summary: Tests passed: 2164, ignored: 18 Build time: 00:13:09


This can be written as `for (Integer i : modeMap.values())`


Yes :)

It's not exactly in compliance with the HTML standard, but Firefox and Chrome both treat `<whatever>` as an (unknown) tag, while the same thing with a zero-width space after the `<` is considered as a literal `<` that accidentally didn't get escaped, plus the string `whatever`.


I would move the below validation one line up, always start by validating the parameters first, because what happens in your current code if I pass a UNSET move, is that you access `storage` to check `games[gameKey].player2 == msg.sender` then you check the `move` and the function fails (because I passed UNSET); so you wasted gas on accessing `storage`, if you checked the `move` first (which is located on the call stack of the function) then you wouldn't have spent that gas.


non sono d'accordo


Based on https://stackoverflow.com/questions/12464656/get-todays-date-in-jekyll-with-liquid-markup


Hi guys!
I tried this code but error keeps coming up.
Can u help fix the transfer method


I think it's okay here because part of the exercise is doing it in different ways.


@hegyhati : how come clicking on this icon works well in Firefox, but not well in Chrome?opens a download window in firefox, but opens the raw code


These two loops can be collapsed into one loop that keeps track of counts and reports the maximum.


When you set `bet` to 0 here; you are allowing `startTheGame()` to re-use keys (this will pass `require(games[gameKey].bet == 0, "Key already used");` if I reuse the same key).


@chaukap perhaps `dispersalProb ` instead of `probabilityOfDispersing`?


Always space before and after `=`