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

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        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%)
>     ========================================================


This long ugly commit, as far as I remember, is just changing int/uint types to match what is expected during convex hull compilation


Ja.
Würde auch mit jedem anderen Runlevel so laufen, da das Plugin sie ja bestimmt.

Ist halt schöner, wenn sie zu denen passen, die vorher auch im Image waren.


Never keep commented code. Remove it if it is not used.


hmm, I guess it's not a problem since player1 didn't reveal their move yet...scratch the above; just be careful with this stuff 😉


Wheel file signing is still not supported correct? I think if so it should be noted in the PEP 427 documentation


<details>

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

InterpreterError at template.tasks: unknown context value pull_request

</details>


@chaukap how about:

`maximum seed dispersal distance for a given species`


無駄な空行


lol i doubt anyone did


You need to check that `msg.sender` is `player2`, otherwise anyone can call this function.


Yesterday I implemented an interface for the Arcade Learning Environment [here](https://github.com/eaplatanios/swift-ale) and when I use things from this module there, using `@inlinable` seems to have a big performance impact (especially so in tight loops). I plan to split this repository in multiple ones too (one for the general RL library and one for the Retro interface and environment) and that's why I added `@inlinable` in many places. My understanding is that it stores the original function code along with the compiled version so that it can be inlined in other modules if deemed necessary. Is that understanding correct? If yes, what is the disadvantage other than the increased binary size (which is still not very big for this library).


`<?=` -> `<?php`


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

* https://api.coral-guardian.now.sh
* https://api-git-master.coral-guardian.now.sh


質問はquestionsなのにanswerrequestは単数形


Successfully aliased the URL <https://side-quest-pblybnazz.now.sh> to the following aliases:

* https://side-quest.sidequest.now.sh
* https://side-quest-git-master.sidequest.now.sh


This is not the right way of comparing which button was clicked.


Nice idea...gl


Correct issue: https://github.com/upstreamplugin/UpStream-Custom-Fields/issues/77


TeamCity Glyssen / Glyssen pull requests [Build *.*.390.3c32fb254215f7dd0cda748f6c3dc552df0c4b13](https://build.palaso.org/viewLog.html?buildId=157362&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **FAILURE**
Summary: Tests failed: 3, passed: 2161, ignored: 18 Build time: 00:08:42
### Failed tests
```
ControlDataIntegrityTests.dll: ControlDataIntegrityTests.CharacterVerseDataTests.DataIntegrity_RequiredFieldsHaveValidFormatAndThereAreNoDuplicateLines: Test(s) failed.   Line with extra space(s): ROM	10	6	God		 righteousness which is of faith (God)	Quotation
  Expected: False
  But was:  True

   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)
   at NUnit.Framework.Assert.IsFalse(Boolean condition, String message)
   at ControlDataIntegrityTests.CharacterVerseDataTests.DataIntegrity_RequiredFieldsHaveValidFormatAndThereAreNoDuplicateLines() in C:\BuildAgent\work\9269096ed6fdb26d\ControlDataIntegrityTests\CharacterVerseDataTests.cs:line 86

GlyssenTests.dll: GlyssenTests.ProjectTests.SetReferenceText_ChangeFromEnglishToFrenchWithOneBlockMismatched_ReferenceTextClearedForAllRelatedBlocks: Test(s) failed.   Expected: True
  But was:  False

   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)
   at NUnit.Framework.Assert.IsTrue(Boolean condition)
   at GlyssenTests.ProjectTests.SetReferenceText_ChangeFromEnglishToFrenchWithOneBlockMismatched_ReferenceTextClearedForAllRelatedBlocks() in C:\BuildAgent\work\9269096ed6fdb26d\GlyssenTests\ProjectTests.cs:line 1156

GlyssenTests.dll: GlyssenTests.BookScriptTests.ApplyUserDecisions_AllSourceBlocksAlignedToReferenceTextWithManualSplitInMiddleOfVerse_TextUnchanged_SplitAppliedAndAllBlocksAligned: Test(s) failed.   String lengths are both 2. Strings differ at index 1.
  Expected: "26"
  But was:  "25"
  ------------^

   at NUnit.Framework.Assert.That(Object actual, IResolveConstraint expression, String message, Object[] args)
   at NUnit.Framework.Assert.AreEqual(Object expected, Object actual)
   at GlyssenTests.BookScriptTests.ApplyUserDecisions_AllSourceBlocksAlignedToReferenceTextWithManualSplitInMiddleOfVerse_TextUnchanged_SplitAppliedAndAllBlocksAligned() in C:\BuildAgent\work\9269096ed6fdb26d\GlyssenTests\BookScriptTests.cs:line 1397

```


That sounds both weird and very dangerous if any parsers change... but :man_shrugging: for this site I guess.


Is there a database interaction in the front-end code? The DB is in the backend. What if the `Exception` was thrown because of some other reason in the backend?


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

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


Предоставлен index.html файл


Hi, thanks’ a lot for answering, I will try to figure out what to do from the other thread. :-)


利用規約に同意みたいに、チェックボックスでチェック必須みたいなほうが結果ユーザのためになりそう


Why sir? Can't the user be a madam?


Successfully aliased the URL <https://texttv-3-app-oo0gu17ry.now.sh> to the following aliases:

* https://app.texttv.nu
* https://texttv-3-app.bonny.now.sh
* https://texttv-3-app-git-texttv2019.bonny.now.sh


Empty commit??


TeamCity Glyssen / Glyssen pull requests [Build *.*.391.7778897cc6f3600bccb0aad8ef7ce259978e603f](https://build.palaso.org/viewLog.html?buildId=157363&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **SUCCESS**
Summary: Tests passed: 2164, ignored: 18 Build time: 00:10:11


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @lize was added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

- @mrandrewandrade was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


$scoresが空の時にエラーがでそう


You had a session with Raju about Lombok. Why are you not using it in this project?


インデントがおかしい


any лучше не увлекаться


@dbo-odoo isn't this check very anti-performant? And what happens if a product without company is later assigned to only one company and has a purchase line from other company already?


↑に同じ


Why are you ignoring the `RestClientException`? Don't you want to show any message to the user if that exception occurs?


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

* https://sergeyfilimonov.com
* https://sergeyfilimonovcom.sfilimonov.now.sh
* https://sergeyfilimonovcom-git-master.sfilimonov.now.sh


filterName:string - должен быть пробел после ":".


=== で書いているのは素晴らしいですね、


No. Make `peers.length++` in another transaction, and the value will still be here. Unless you did `delete`.


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

* https://angular.amrandin.now.sh
* https://angular-git-master.amrandin.now.sh


I'll fix that. Thanks!


Oui, on voulait utiliser la master Branch pour la production non?


Will the UI show the image if I run the program in my computer? What can be done so that the image is shown irrespective of where the program is executed?


method="get" 不要


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @jan-janssen was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


Line 374 void Cmd_ZWaveGetBatteryLevels(WebEmSession& session, const request& req, Json::Value& root)
Should be void Cmd_ZWaveGetBatteryLevels(WebEmSession & session, const request& req, Json::Value &root) ?


Опять же. const newArray = [...this.state.toDoArray, { id: this.idGenerator() }]


В отдельный файл


Setting state to `success` where context is `continuous-integration/jenkins/branch`.

WatchOS issues are known: https://github.com/xamarin/maccore/issues/581


急にcontroller@show


routeで統一


It's supposed to be weird ;)

And yeah, like I said in the third paragraph I added to the comment above, one certainly shouldn't (and I wouldn't) do this in a real production setting.


syntax ko format kya aung yay pay lo ma main mhr ae lo pout loz pae sr ty yay yin sout khwat yite mhr


Setting state to `success` where context is `VSTS: device tests (TvOS)`.

mscorlib test app sizes issues has been reported: https://github.com/xamarin/maccore/issues/1896


Successfully aliased the URL <https://next-js-project-8ajwucksn.now.sh> to the following aliases:

* https://my-landing-page-project.now.sh
* https://next-js-project.nodeicode.now.sh
* https://next-js-project-git-master.nodeicode.now.sh


Если нужно менять стиль в зависимости от isActive, то лучше добавлять какой-то осмысленный класс, например todoItem__active


Learn when to use `CrudRepository` and when to use `JpaRepository`


'users.profile', Auth::user()


Deployment failed with the following error:

~~~
Ambiguous deployment (`package.json` and `Dockerfile` found). Please supply `--npm` or `--docker` to disambiguate.
~~~


@adelRestom Good idea, not sure why I deliberately decided against that... I've pushed a new commit!


不要空白


So is setsockopt allowed but not getsockopt?  Or is the problem that
your initialization function does both setsockopt and cap_enter?
Assuming the latter, you've got a decision to make.  Would it be
better to move cap_enter out of initialization so that you can use
getsockopt?  Or would it be better to leave it together, but not test
that socket options actually get set?  It's a judgement call.
Remember that the goal isn't 100% test coverage; the goal is to make
ping work, and make it maintainable.  Tests improve maintainability,
but so does good organization.

On Mon, Jul 22, 2019 at 8:35 AM Ján Sučan <notifications@github.com> wrote:
>
> I would like to ask for an advice. The good news is that capability mode works. The bad news is that it prevents testing of the setsockopt() calls. After the initialization is finished, capability mode is active and getsockopt() is not allowed.
>
> What direction should I take?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.


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

* https://sergeyfilimonov.com
* https://sergeyfilimonovcom.sfilimonov.now.sh
* https://sergeyfilimonovcom-git-master.sfilimonov.now.sh


В компоненте выше имена классов через дефис. По этому тут тоже должно быть также.


TodoItem и ItodoItemObject должны быть в отдельном файле.


And why is that problem?
I did it intentionally to save some gas, and to allow somebody whom player2 would maybe ask to do so. Is anything wrong with that?


Ok


Hmm, so your point is that only `peers.length--` won't truncate the array, thus `delete peers[peers.length - 1]` is required? That was clear for me, but thanks for reiterating it.


Hi Pedro!
1/ for the field's domain in the view: the field is indexed, I don't see how this would decrease performance more than an ir_rule with a domain that is entirely similar and happended to all queries anyway...
2/ for the constraint: it could certainly hamper performance for big POs - though it should not be a big nightmare, yet I don't see how to avoid this without related stored fields wich would recompute like hell
3/ what if the product's company is changed: same thing that happens now (you break stuff), except that you'll be warned about it. Perhaps we should add a constraint that checks the use of a product on all SO/PO/MO/Expense/account moves/etc. records and raise if it was *ever* used in another company? But there, performance clealry stresses me out...

I'm certainly listening for suggestions if you have any


Yes that was the same thing I was thinking about, but eventually decided to allow user to move funds.


Good point, will do.


multi-company is moving form record rules to the business layer, and we have to put at least _some_ protection in place to avoid a complete nightmare if users are careless (and they usually are). So we need to do something - we went with this solution. If you have another idea, please share :)


Лучше объявить тип ```type FilterType = 'all' | 'active' | 'done'```
И тут, соответственно, написать ```filter: FilterType```
Это не даст нам допустить ошибку, а редактор нам будет подсказывать.


@rwwagner90  just FYI, the reasoning for that is smaller bundle size. If you look at your minified js you will see a bunch of `this.classPrefix`. this trick will have single `var a=this.classPrefix` and then `a` (or some other letter) is used, saving some size.

If you are against it, I won't use it in other PRs.


Вообще, компонент TodoList не должен ничего знать о фильтре. Он должен заниматься только отображением списка. Логику фильтрации массива следует вынести в компонент TodoApp


Sure :)


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/d16-3/15/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/d16-3/15/display/redirect) (on internal Jenkins) failed in stage(s) 'Upload to Azure' 🔥 : hudson.AbortException: script returned exit code 2

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/d16-3/15//console)


itemsToShow - плохое название для функции. В данном случае лучше getItemsToShow или getFilteredItems.
Название функции должно быть либо действием (getItems, saveData, update, setNewParam и т.д.), либо вопросом (isNewUser, hasEnoughItems), если возвращает boolean.


@fadeevab I did not consider that all recipes are interpreted per shell...in that case, even the current behavior:

![image](https://user-images.githubusercontent.com/896331/61646394-84c37b00-ac77-11e9-8e47-6d94b8b1dbb3.png)

is presuming an sh-like shell in that it is highlighting the first line of the recipe as a comment.  For myself, I'd like to see the `#` style "comments" highlighted in recipes, but to truly reveal the Makefile syntax, you should not highlight that first line.

Your call, and you can close my bug as you see fit.


Вместо string лучше FilterType


Промежуточная переменная idCounterOld не нужна.


20.07.2019, 13:23, "Anatoliy Kurichev" <notifications@github.com>:???—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.Непонятно, что-то с github


I know it. This is the code from exericise, I didn't refactor it.


POST:
![postman6](https://user-images.githubusercontent.com/22013087/61646919-90686f00-ac82-11e9-9e43-526e24925fe1.PNG)

GET:
![postman7](https://user-images.githubusercontent.com/22013087/61646920-90686f00-ac82-11e9-964d-a5eb51fbe3cb.PNG)


Biggest performance increase of a`+` ever?


Successfully aliased the URL <https://redfish-server-prod-7t7wkufh5.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://mockup-web-g3zl2dcov.now.sh> to the following aliases:

* https://mockup-web.cubedesign-inpe.now.sh
* https://mockup-web-git-master.cubedesign-inpe.now.sh


Deployment failed with the following error:

~~~
Your project already has domains configured at https://zeit.co/geut/geut-www/domains, please remove `alias` from your now.json file.
~~~


ここを見直す


ah ouais je trouvais ca drole cest tout


Successfully aliased the URL <https://geut-www-qo4ilglf4.now.sh> to the following aliases:

* https://geutstudio.com
* https://geut-www.geut1.now.sh
* https://geut-www-git-master.geut1.now.sh


Deployment failed with the following error:

~~~
Ambiguous deployment (`package.json` and `Dockerfile` found). Please supply `--npm` or `--docker` to disambiguate.
~~~


Ok ,Mubin thanks for your feedback.
I will definitely try to fix this issues in my code tomorrow.
On 22-Jul-2019 8:59 pm, "Mubin Ahmed" <notifications@github.com> wrote:

> Will the UI show the image if I run the program in my computer? What can
> be done so that the image is shown irrespective of where the program is
> executed?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kasanikrp920/RestTemplate-SWT/commit/5ce7eab3b5893ef64a12e6f07779d475387621cc?email_source=notifications&email_token=AMGZQA3TN2ZG2376WW6KADDQAXG7FA5CNFSM4IFZYXUKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAZXEL#commitcomment-34397323>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMGZQAYKKT5FQSZKFRJGVADQAXG7FANCNFSM4IFZYXUA>
> .
>


oh yoneda computes seriously slow. I suppose proving the isomorphism directly type cheks much faster.


(for reference sake: I eventually did dig up and publish the old-old repo. It is over here: https://github.com/graydon/rust-prehistory)


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @flrs was added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


I can't quite believe the chances of this. I just spent (I won't admit how long) trying to debug something that called `react` (in the importer), and finally concluded that the docstrings were misleading, and I had _just_ about figured out what it needed to be changed to, then came to check the history of the file so I could confirm when it had changed and open an issue,... then found this commit from 4 days ago.  It is more than 4 days since I merged from master, and I had the old docstrings. 🤦♂

Anyway, thanks for fixing them, Max!


Yes after this commit, it is broken @bradtraversy @developerkunal - Please guys can we get this fixed?


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

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


hello my friend, did you ever used with cygwin? im trying to over here, hard stuff. thanks for the time bro or sis :)


processingEnv.elementUtils.getPackageOf(it).toString()


Successfully aliased the URL <https://geut-www-gymdvdvvg.now.sh> to the following aliases:

* https://geutstudio.com
* https://geut-www.geut1.now.sh
* https://geut-www-git-master.geut1.now.sh


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

* https://bivrost.notmyself.io


thank


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

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


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

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

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

### Deployments updated

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

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


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

Created multidev environment [ci-830](https://dashboard.pantheon.io/sites/ad79477c-5d06-4234-b6b8-582ebeee0e5c#ci-830) for mtcv.


Yes, your `delete` is necessary if you want to be a good citizen and reduce the world state.


<details>

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

Schema Validation Failed!
Rejecting Schema: https://schemas.taskcluster.net/queue/v1/create-task-request.json#
Errors:
  * data should have required property 'deadline'

---

* method:     createTask
* errorCode:  InputValidationError
* statusCode: 400
* time:       2019-07-22T16:31:53.386Z

</details>


merge from develop


Is it only me or when  ```django-pyodbc-azure==2.1.0.0``` was added,
it made the ```docker-compose up``` command fail ? @Hironsan


Sweet! Thanks!


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

* https://mattseemon.com
* https://mattseemonin.mattseemon.now.sh
* https://mattseemonin-git-masterv2.mattseemon.now.sh


```
data-hide="#elementId"
```


Just tried to vote with a user that has no username, and the bot gives no answer. I suppose the error is right here, because `None` has no `lower()` attribute (assuming `tg_user` is a python-telegram-bot's `User` object)


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

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


We might need to seek some advice from the Agda gurus. I've also started to encounter some serious slow spots.


Hi. I've followed your advice and removed the command and I added it again. Then I tried again copying the command link. The notification appeared and I clicked the _Import_ button but, again, nothing happens... I checked CopyQ Process Manager looking for an error, but everything is fine there. I go to Show Log but there is no entry for today there...

I have _ERROR, Warning, Note, DEBUG, TRACE_ enabled in the Log.
It shows me the following notes:
```
Note [2019-07-19 12:48:44.425] <Server-5544>: Command “copyq monitorClipboard”
Note [2019-07-19 12:48:44.425] <Server-5544>:    Error: Process crashed
Note [2019-07-19 12:48:44.425] <Server-5544>:    1. copyq monitorClipboard
```

But these are from other days and seem unrelated.
How can I help to clarify what's wrong?

THANKS


Il suffisait d'ajouter cette ligne pour régler le bug ;)


ok


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

Created multidev environment [pr-74](https://dashboard.pantheon.io/sites/ad79477c-5d06-4234-b6b8-582ebeee0e5c#pr-74) for mtcv.


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

Created multidev environment [pr-11](https://dashboard.pantheon.io/sites/533c69ec-70af-4cb2-af59-49d50e7d05f7#pr-11) for aledade.


Ow, tabs are painful


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

# Test results

# No tests selected.


3번째 커밋


Successfully aliased the URL <https://svg-to-image-proxy-52jd3atqa.now.sh> to the following aliases:

* https://shields-raster-staging.now.sh
* https://svg-to-image-proxy.shields11.now.sh
* https://svg-to-image-proxy-git-master.shields11.now.sh


such freshness


Fixed with https://github.com/emacs-lsp/dap-mode/commit/7d22cf541d7a23d6366a36b33bc8a36d4b583d66


DELETE com qualquer ID para forçar um erro:
![postman9](https://user-images.githubusercontent.com/22013087/61648575-19cd7080-ac86-11e9-992b-84cfe0c6779f.PNG)

DELETE com ID:
![postman8](https://user-images.githubusercontent.com/22013087/61648574-1934da00-ac86-11e9-88d7-b8d4abdf1986.PNG)

GET para verificar:
![postman10](https://user-images.githubusercontent.com/22013087/61648576-19cd7080-ac86-11e9-9622-3e66f2c685d4.PNG)


I get the feeling that the right thing to do here is to indicate a priori what each parameter is used for (input, output, both) in GOOL. Then each language can interpret that as it wishes.  There ought to be a 'coherence' check that parameter names are unique, with failure in that case.

I think your code above tries to reconstruct / guess information that should have been given.


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

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

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

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/linux-x64/circle-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-137056/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.4.1/circle-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-137041/cypress.tgz


grappig commit bericht :joy:


I left them blank, thinking you would fill the values.
Yes, it makes sense to remove default value so it prompts user when applying changes.


maybe `lambda` could be used here?


Can you make it for alice and bob only?


I submitted PR #2884 just now, with a fix that seems to work for me.


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/26156898/job/f0v308ln8t1cg89f) the `win32 ia32` version of the Test Runner.

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

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

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/win32-ia32/appveyor-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-26156898/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.4.1/win32-ia32/appveyor-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-26156898/cypress.zip


Successfully aliased the URL <https://alpaca-ui-9dqq2gh4h.now.sh> to the following aliases:

* https://alpaca-ui.now.sh
* https://alpaca-ui.snowdog1.now.sh
* https://alpaca-ui-git-develop.snowdog1.now.sh


Tell me what happens when the number of participants goes ever higher.


@G-Rath FYI. Maybe a `new Set<DescribeAlias>(Object.keys(DescribeAlias))` or something makes sense?


Ooh dangerous. Instead, I would have assumed that all indices are 1-based or 0-based depending on what we ask.


> Did you test `find /v ""` on Windows?

No (I have no Windows).  Is it using stdin?

Anyway, it seems like we should use `cat` everywhere then, no?

But I am not sure I understand your comment:

> `cat` is inconsistent for the tests here.


Yes. That was the main reason for the fork. Since the buildpack is downloading the binaries from github releases instead of building it on the fly (what makes a lot of sense) I decided to create a fork so we can control the binary builds.


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/26156898/job/hvigwoj05rahs1u7) the `win32 x64` version of the Test Runner.

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

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

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/win32-x64/appveyor-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-26156898/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.4.1/win32-x64/appveyor-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-26156898/cypress.zip


This is an anti-pattern about the safe handling of money and talking to strangers. The problem is this.

What if bob is a contract and it decides to revert? Does carol get paid? What about the other way around? Either one of them can DoS the contract. This is a real problem if there are hundreds of refunds to distribute and one bad actor can DoS the whole system.

A solution to that problem is to never talk to more than one untrusted contract at a time. `msg.sender` counts as one. Therefore, you can send to the `msg.sender` (not sure why you would want to, but it wouldn't hurt), or you can interact with other contracts that you yourself made the source code or you see the source code and you trust it. Bob isn't such a thing so it also counts as an untrusted contract, making two. Carol makes three. Not good.

When you think about this rule, in practice it means this `payable` function can only accept the funds and do some accounting. It can't safely forward to strangers in one move. Therefore, consider tracking bob's balance and carol's balance and give them a function `withdrawFunds()` they can use to get their funds. This is sometimes called the withdrawal pattern, or preferring a "pull" style over "push".


So your participants are full of holes and you ask the contract to traverse everything and skip the holes?
Wow, I hope your users are rich because computation is expensive in Ethereum.
What you need to achieve is that your contract is always in a good state. A good state is a list of participants without holes.


Don't reuse the same deployed instance as this makes your tests depend on each other. Do `.new` instead.


Can you confirm that this test passes when run against Geth?


```
Throwable throwable = Throwable.catchThrowable(() -> wywołanieMethodyKtoraRzucaWyjatek());

        assertThat(throwable)
                .isExactlyInstanceOf(HttpClientErrorException.class)
                .hasMessage("400 Bad Request");
```


i can't find where this attribute (T) is defined
maybe a unique name would facilitate the search


What i did
- Corrected dport port in config files
- Renamed config file name to represent correct port mapping

- A picture of a cute animal (not mandatory but encouraged)
       xe19      0    20        20        19       190/10               190/10
      xe29      0    30        30        29       290/10               290/10
      xe30      0    31        31        30       300/10               300/10
      xe42      0    43        43        42       420/10               420/10
      xe43      0    44        44        43       430/10               430/10
      xe44      0    45        45        44       440/10               440/10


Please remove "\n" from lines with injecting css (lines 485 and 496) in file MainWindow.cpp

Removing nodes with an injected css code does not delete "\n" characters and unnecessary empty lines are created before "</head>".

The issue appears when:
a) we use our own css file (custom_webview_style.css)
b) we have enabled in the preferences (css-white-space: pre-wrap)


taw tl ae lae, shr loz ma ya tr shi yin issue mhr new issue open lite


What a coincidence! We really should have updated the docstrings earlier when we changed behavior.

Note that this was motivated by another change in the return values for `react`, so you may need additional changes in the importer tool.


the same here?


Ok okie

On Mon, Jul 22, 2019 at 11:21 PM Aung Khant Min <notifications@github.com>
wrote:

> taw tl ae lae, shr loz ma ya tr shi yin issue mhr new issue open lite
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/AungKhantMin/Dooms/commit/dcaccbd02250d13045029f5acd592f2b5f788481?email_source=notifications&email_token=AMVN43JWPYEVQERWB35RTGDQAXQQHA5CNFSM4IF2KTMKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAZXXR#commitcomment-34397937>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMVN43IC42VLZIQSW6ZNUT3QAXQQHANCNFSM4IF2KTMA>
> .
>


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

* https://js.ricardordzfc.now.sh
* https://js-git-master.ricardordzfc.now.sh


Looks good.


this was code we took from codepath, so that was their reminder to change the datatypes to type "Post". I think initially it was of type "Tweet".


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

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

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

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.4.1/darwin-x64/circle-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-137060/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.4.1/circle-develop-ec25c7dff893dca748d26e052cf2407d9475ac5e-137058/cypress.tgz


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

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


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

* https://express-now.morganhallmon.now.sh
* https://express-now-git-master.morganhallmon.now.sh


Fix_7396_QtIFW_Windows (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (667 of 667 tests passed, 0 test warnings)

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


@nickmorales when uploading an existing split plot trial, the cvterm splitplot trial type is missing


I think part of `Code.Imperative.Import` is misnamed.  `Import` is used in others parts of Drasil to translate from (say) `Expr` that is semantic to a more display-oriented `Expr` in the printers.  And 'Import' is a bad name there too!

I think here there are multiple things happening. We need to try to describe "semantically" what the routines are doing. I think that when we do that, the words we use in the description will give us a better idea of where to put each piece.

In particular, some of the code above generates modules in a very specific way, a la @smiths . It contains all sorts of design decisions, implicitly (and this isn't news to @smiths ). The rest of the stuff in the file is for generating 'code', which is at a very different level of abstraction.


undo


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

* https://fritch.mn
* https://fritchmn.dan-fritchman.now.sh
* https://fritchmn-git-master.dan-fritchman.now.sh


That makes sense, I've seen several other groups do it as well and I've been wondering if a JEMALLOC_REPOSITORY environment variable would be useful for these cases where a team could point it at a controlled URL. Of course that still leaves the potential attack vector of the environment variable being ignored in a future release which is why I haven't added it yet.


Ok

On Mon, Jul 22, 2019 at 11:25 PM Aung Khant Min <notifications@github.com>
wrote:

> while loop nk pat p exit so mha exit lote lae ya tl
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/AungKhantMin/Dooms/commit/dcaccbd02250d13045029f5acd592f2b5f788481?email_source=notifications&email_token=AMVN43OXPGHGJZIZG4ZYXLDQAXQ77A5CNFSM4IF2KTMKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAZX2A#commitcomment-34398016>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AMVN43IOVQIKDA7IPNI6C3LQAXQ77ANCNFSM4IF2KTMA>
> .
>


Writing C tests of the initialization turned out to be quite difficult. One of the reasons is ATF's incompatibility with capsicum. The other are that not only cap_enter should be moved out of the initialization but also the socket opening because some predefined socket options need to be set before calling the init function. Considering that there is only one month of GSoC left, I would go for good organization. There are many possibilities for improvment in this way.

Are there any tools for checking code? I remember that you mentioned Coverity and Valgrind. I found out that setting `WARNS?` to 5 in the Makefile is also a good source of feedback from the compiler.


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

* https://my-portfolio.mindfuljs.now.sh
* https://my-portfolio-git-master.mindfuljs.now.sh


TeamCity Consultations / "Private Beta" - BuildAndPublish .NET Core 2.1 [Build 0.1.0.2283-EC-668-Yes-No-Questi](https://teamcity.nice.org.uk/viewLog.html?buildId=56149&buildTypeId=Consultations_PrivateBetaBuildAndPublish21) outcome was **SUCCESS**
Summary: Tests passed: 436 Build time: 00:08:07


Think if subplot level is not added to upload that may be difficult to generate from the trial page


Yes, it can go into a separate PR.


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

* https://express-now.morganhallmon.now.sh
* https://express-now-git-master.morganhallmon.now.sh


As far as I know, not important -- go ahead!