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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  >            GET value                                     ... FAIL

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

  >            GET alice                                     ... FAIL

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

  >            GET bob                                       ... FAIL

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

  >            GET charlie                                   ... FAIL

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

  >            GET denise                                    ... FAIL

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

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

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

  >            GET value                                     ... FAIL

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

  >            GET alice                                     ... FAIL

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

  >            GET bob                                       ... FAIL

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

  >            GET charlie                                   ... FAIL

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

  >            GET denise                                    ... FAIL

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

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

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

  >            GET value                                     ... FAIL

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

  >            GET alice                                     ... FAIL

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

  >            GET bob                                       ... FAIL

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

  >            GET charlie                                   ... FAIL

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

  >            GET denise                                    ... FAIL

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

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

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

  >            GET value                                     ... FAIL

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

  >            GET alice                                     ... FAIL

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

  >            GET bob                                       ... FAIL

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

  >            GET charlie                                   ... FAIL

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

  >            GET denise                                    ... FAIL

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  >            GET a/b                                       ... FAIL

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

  >            GET foo/bar                                   ... FAIL

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

  >            GET 123/456                                   ... FAIL

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

  >            GET alice/bob                                 ... FAIL

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

  >            GET value/value                               ... FAIL

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

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

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

  >            GET /foo                                      ... FAIL

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/master/821/display/redirect) (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/master/821//console)
✅ Packages: [xamarin.ios-12.15.0.283.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/master/b2f8db0682f0b8503f45b3d7c5176fce9a41c04a/821/package/xamarin.ios-12.15.0.283.pkg) [xamarin.mac-5.15.0.283.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/master/b2f8db0682f0b8503f45b3d7c5176fce9a41c04a/821/package/xamarin.mac-5.15.0.283.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/master/b2f8db0682f0b8503f45b3d7c5176fce9a41c04a/821/jenkins-results/api-diff/index.html)
🔥 [Failed to compare API and create generator diff](https://jenkins.internalx.com/job/macios/job/master/821//console) 🔥
    ** Error: Working directory isn't clean:
    HEAD detached at b2f8db06
    Untracked files:
    (use "git add <file>..." to include in what will be committed)

    tests/bcl-test/BCL tests group 1.csproj
    tests/bcl-test/BCL tests group 2.csproj
    tests/bcl-test/BCL tests group 3.csproj
    tests/bcl-test/BCL tests group 4.csproj
    tests/bcl-test/BCL tests group 6.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-modern.csproj
    tests/bcl-test/generated/
    tests/bcl-test/mscorlib-mac-full.csproj
    tests/bcl-test/mscorlib-mac-modern.csproj
    tests/bcl-test/mscorlib.csproj

    nothing added to commit but untracked files present (use "git add" to track)
    Search for `Comparing API & creating generator diff` in the log to view the complete log.
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/master/b2f8db0682f0b8503f45b3d7c5176fce9a41c04a/821/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>2 tests failed, 169 tests passed.</summary>

## Failed tests

 * [NUnit] Mono SystemXmlTests/watchOS 32-bits - simulator/Debug: Crashed
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
</details>


а я если я выберу второй месяц? к примеру 01.02.2000, год високосный и мне дадут порядковый номер 33
а если год не високосный, то вообще ошибка вываливается


Successfully aliased the URL <https://robert-portfolio-37t8goybj.now.sh> to the following aliases:

* https://robert-portfolio.olivernordlund.now.sh
* https://robert-portfolio-git-master.olivernordlund.now.sh


This commit has been mentioned on **Discourse Meta**. There might be relevant details there:

https://meta.discourse.org/t/full-url-in-assets-erb-file-multisite-issues/124393/11


excelente


поставь последнюю версию ruby, там есть метод .sum для массива
а еще есть метод take что бы взять определенное количество элементов со списка

https://ruby-doc.org/core-2.6.3/Array.html#method-i-take
https://ruby-doc.org/core-2.6.3/Array.html#method-i-sum


Am humbled. Thanks so much for your advice

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: endepointe <notifications@github.com>
Sent: Friday, August 2, 2019 10:17:17 PM
To: jonasschmedtmann/complete-javascript-course <complete-javascript-course@noreply.github.com>
Cc: Derick Makuto Simiyu <derickmakuto@outlook.com>; Comment <comment@noreply.github.com>
Subject: Re: [jonasschmedtmann/complete-javascript-course] Updated FAQ (ee5254d)

Just keep making mistakes, getting stuck, and figuring it out. Your code doesn’t have to be perfect but you should know why it (hopefully) works.

From: Derick Makuto Simiyu
Sent: Friday, August 2, 2019 10:56 AM
To: jonasschmedtmann/complete-javascript-course
Cc: endepointe; Comment
Subject: Re: [jonasschmedtmann/complete-javascript-course] Updated FAQ(ee5254d)

I just uninstalled the babel-loader@8 n reinstalled babel-loader@7 with babel-core@6 then the 9-forkify package compiled successfully.
Thanks...
Also my objective is to be a reactjs/redux developer. I won't mind if you could reference me as a beginner for your best tutorial.
Thanks

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: endepointe <notifications@github.com>
Sent: Friday, August 2, 2019 8:03:12 PM
To: jonasschmedtmann/complete-javascript-course <complete-javascript-course@noreply.github.com>
Cc: Derick Makuto Simiyu <derickmakuto@outlook.com>; Comment <comment@noreply.github.com>
Subject: Re: [jonasschmedtmann/complete-javascript-course] Updated FAQ (ee5254d)

Have you tried installing the Babel core module or reading the Babel
documents?

On Thu, Aug 1, 2019, 7:30 PM Derick Makuto Simiyu <notifications@github.com>
wrote:

> Hi Jonas,
> I've tried to build forkify project by following your instructions step by
> step using my api key from food2fork as a practice project, and i get this
> error:
> Uncaught Error: Module build failed (from
> ./node_modules/babel-loader/lib/index.js):
> Error: Cannot find module '@babel/core'
> babel-loader@8 requires Babel 7.x (the package '@babel/core'). If you'd
> like to use Babel 6.x ('babel-core'), you should install 'babel-loader@7'.
> at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:690:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object.
> (C:\innerLoop\my-projects\forkify\node_modules\babel-loader\lib\index.js:10:11)
> at Module._compile (internal/modules/cjs/loader.js:776:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module.
>
>
>
> *load (internal/modules/cjs/loader.js:585:3) at eval
> (webpack:///./src/js/index.js?:1:7) at Object../src/js/index.js
> (http://localhost:8080/js/bundle.js:4197:1
> <http://localhost:8080/js/bundle.js:4197:1>) at webpack_require
> (http://localhost:8080/js/bundle.js:20:30
> <http://localhost:8080/js/bundle.js:20:30>) at eval (webpack:///multi*
> (webpack)-dev-server/client?:3:18)
> at Object.0 (http://localhost:8080/js/bundle.js:4208:1)
> at *webpack_require* (http://localhost:8080/js/bundle.js:20:30)
> at http://localhost:8080/js/bundle.js:84:18
> at http://localhost:8080/js/bundle.js:87:10
>
> Help!!!
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/jonasschmedtmann/complete-javascript-course/commit/ee5254d8a7d383b6fc2dddcf42abcdfc8c9ea4d7?email_source=notifications&email_token=AHKQYI5PMYUGJ6ARRZYWXYDQCOL57A5CNFSM4IIZ2RJ2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA6FC5#commitcomment-34542685>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHKQYIYBUGMJZY2MQQZXQTDQCOL57ANCNFSM4IIZ2RJQ>
> .
>

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/jonasschmedtmann/complete-javascript-course/commit/ee5254d8a7d383b6fc2dddcf42abcdfc8c9ea4d7?email_source=notifications&email_token=AKDFQ6NYJZYC6OGMADLHICDQCRSFBA5CNFSM4IIZ2RJ2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA6OCF#commitcomment-34551877>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKDFQ6PYNWOV3AXXCOFNMVTQCRSFBANCNFSM4IIZ2RJQ>.

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

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/jonasschmedtmann/complete-javascript-course/commit/ee5254d8a7d383b6fc2dddcf42abcdfc8c9ea4d7?email_source=notifications&email_token=AKDFQ6L56VJYG3WZN666R5LQCSB33A5CNFSM4IIZ2RJ2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA6PSR#commitcomment-34553425>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKDFQ6IREBMLHO7CFKXJJFDQCSB33ANCNFSM4IIZ2RJQ>.


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

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


используй `puts` а не `p`, p работает как `puts твойкод.inspect`


I looked into what kind of issues I had when I used physical plan as `recursivePlan`.
So in that case my problem mostly came from:
1. `BroadcastExchangeExec`:
   First of all you need to provide `computeStats()` on `RecursiveReferences` as otherwise a analysis of this example query will fail:
   ```
   create temporary view t(id) as values (0), (1), (2), (3), (4), (5);

   WITH RECURSIVE r(level, id) AS (
     VALUES (0, 0)
     UNION ALL
     SELECT level + 1, t.id
     FROM r
     LEFT JOIN t ON t.id = r.level
     WHERE level < 10
   )
   SELECT * FROM r AS
   ```
   The minor issue is that wee can't provide correct statistics during analysis and so join selection will not be optimal.
   What's more what we need to do here is to provide `override def computeStats(): Statistics =
   Statistics(BigInt(conf.defaultSizeInBytes))` (`Long.MaxValue`) to disallow recursive reference on the broadcasted side because its size may grow beyond the broadcastable size limit.
2. Any exchange reuse on recursive references:
   Please consider:
   ```
   create temporary view t(id) as values (0), (1), (2), (3), (4), (5);

   SET spark.sql.autoBroadcastJoinThreshold=-1;

   WITH RECURSIVE r(level, id) AS (
     VALUES (0, 0)
     UNION ALL
     SELECT level + 1, t.id
     FROM r
     LEFT JOIN t ON t.id = r.level
     WHERE level < 10
   )
   SELECT *
   FROM r AS r1
   JOIN r AS r2 ON r1.id = r2.id AND r1.level = r2.level
   ```
   In this example the physical plan is:
   ```
   == Physical Plan ==
   SortMergeJoin [id#1, level#17], [id#20, level#19], Inner
   :- Sort [id#1 ASC NULLS FIRST, level#17 ASC NULLS FIRST], false, 0
   :  +- Exchange hashpartitioning(id#1, level#17, 5), true
   :     +- Project [(level + 1)#15 AS level#17, id#1]
   :        +- Filter isnotnull(id#1)
   :           +- RecursiveUnion
   :              :- LocalTableScan [col1#3, col2#4]
   :              +- Project [(level#11 + 1) AS (level + 1)#15, id#1]
   :                 +- SortMergeJoin [level#11], [id#1], LeftOuter
   :                    :- Sort [level#11 ASC NULLS FIRST], false, 0
   :                    :  +- Exchange hashpartitioning(level#11, 5), true
   :                    :     +- Project [col1#7 AS level#11]
   :                    :        +- Filter (col1#7 < 10)
   :                    :           +- RecursiveScan [col1#7,col2#8]
   :                    +- Sort [id#1 ASC NULLS FIRST], false, 0
   :                       +- Exchange hashpartitioning(id#1, 5), true
   :                          +- Project [col1#0 AS id#1]
   :                             +- Filter (col1#0 < 10)
   :                                +- LocalTableScan [col1#0]
   +- Sort [id#20 ASC NULLS FIRST, level#19 ASC NULLS FIRST], false, 0
      +- Exchange hashpartitioning(id#20, level#19, 5), true
         +- Project [(level + 1)#16 AS level#19, id#1 AS id#20]
            +- Filter isnotnull(id#1)
               +- RecursiveUnion
                  :- LocalTableScan [col1#5, col2#6]
                  +- Project [(level#13 + 1) AS (level + 1)#16, id#1]
                     +- SortMergeJoin [level#13], [id#1], LeftOuter
                        :- Sort [level#13 ASC NULLS FIRST], false, 0
                        :  +- ReusedExchange [level#13], Exchange hashpartitioning(level#11, 5), true
                        +- Sort [id#1 ASC NULLS FIRST], false, 0
                           +- ReusedExchange [id#1], Exchange hashpartitioning(id#1, 5), true
   ```
   This will fail because your `planWithNewInput` doesn't handle `ReusedExchange` as it has no children.
   But even if it handle `ReusedExchange`, reusing an exchange (containing a recursive reference) outside of `RecursiveUnion` leads to issues as a recursive reference means different data in each iteration. I solved this by modifying `ReuseExchange` to disallow reuse of an exchange when it contains a recursive reference. (Please note that this applies to `ReuseSubquery` as well.)
3. My biggest issue was that `ShuffleExchangeExec` contained a coordinator at the time I was trying the physical recursive plan approach. That coordinator needed to be hacked in my version of `planWithNewInput`. But I've just noticed that `ShuffleExchangeExec` has changed in this PR: https://github.com/apache/spark/pull/24978/files#diff-3ceee31a3da1b7c71dddd32f666126fbL44-L47 and coordinator disappeared so this is not an issue anymore.

All in all I think I can give one more try to this approach and see if we run into something else...


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

* https://robert-portfolio.olivernordlund.now.sh
* https://robert-portfolio-git-master.olivernordlund.now.sh


В качестве ключей хеша используй какие-то "кодовые" названия, например, price, count, а не полноценные строки. Несмотря на то, что потом будет проще выводить результат, вычислять его будет сложнее. Хеш - это все-таки структура для внутреннего хранения данных, удобная для обработки, а не для представления.


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

* https://petgram.bautistatancredi.now.sh
* https://petgram-git-master.bautistatancredi.now.sh


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

Created multidev environment [p-cloneliv](https://dashboard.pantheon.io/sites/d1c0bbdc-f8cc-4693-bf9c-a0adb583cc0f#p-cloneliv) for ocad.


-------------------------------------------------------------------------------
  Test 1: Check that the client can establish basic connections
-------------------------------------------------------------------------------

    panic: runtime error: invalid memory address or nil pointer dereference [recovered]
    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x545ad3]

    goroutine 5 [running]:
    testing.tRunner.func1(0xc000222100)
    /usr/local/go/src/testing/testing.go:830 +0x392
    panic(0x578ca0, 0x6ea590)
    /usr/local/go/src/runtime/panic.go:522 +0x1b5
    _/app/assignment1.(*Client).StopRefServer(0xc0000a5f10, 0x6d723c, 0x25)
    _/app/assignment1.testClient(0xc000222100, 0x5ac3b3, 0x9, 0x5ab75e, 0x5, 0x0)
    _/app/assignment1.TestClientBasicConnect(0xc000222100)
    testing.tRunner(0xc000222100, 0x5b5e58)
    /usr/local/go/src/testing/testing.go:865 +0xc0
    created by testing.(*T).Run
    /usr/local/go/src/testing/testing.go:916 +0x35a
    exit status 2
    FAIL	_/app/assignment1	3.142s
###
                               -- test failed (-1.0) --

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed   0 / 23  tests     (23 failed)
>
>        Score:
>            0.00 points of a possible 23.00  (0.00%)
>     ========================================================


The original code was correct, as this if statement will create a reference calibration file (test.fits) if one does not exist. This has the same function as `calibrate.py`.


Используй
`{ 'january' => 31, 'february' => 28...`
либо
`{ january: 31, february: 28...`
иначе у тебя и ковычки считаются за символы


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

* https://mtgpricebackend.kevlavery.now.sh
* https://mtgpricebackend-git-master.kevlavery.now.sh


Неплохо, а сможешь через метод [step](https://ruby-doc.org/core-2.6.3/Range.html#method-i-step)?


@snicolet @ElbertoOne @Vizvezdenec Someone there to stop this test? Thanks.


Что бы не вычислять дважды, сохрани значение в переменной прямо в условии


Successfully aliased the URL <https://gatsby-themes-lbhrnsabc.now.sh> to the following aliases:

* https://gatsby-themes.now.sh
* https://gatsby-themes.jxnblk.now.sh
* https://gatsby-themes-git-master.jxnblk.now.sh


epic ram death allah approved
punjabi movi leak (2011) (free download) (no punjabi survey)


That does seem to work, replacing 'remote' with 'nil'.

--
Jonathon McKitrick

On Fri, Aug 2, 2019 at 4:09 PM Jonas Bernoulli <notifications@github.com>
wrote:

> Thanks!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/magit/magit/commit/904bb82ca69fd2539efd92ad3ab96eb6282bf65c?email_source=notifications&email_token=AAD6PKLJ7MD7N3LPQDAYE3DQCSH7RA5CNFSM4IJAOTHKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBA6QER#commitcomment-34554001>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAD6PKJMAF5DPFMVTTYLN6LQCSH7RANCNFSM4IJAOTHA>
> .
>


I'm trying to pull together a minimal sketch to enable testing.  In the process of doing that, I (re)discovered that Greiman has two closely-related repos:

SdFs: https://github.com/greiman/SdFs
SdFat: https://github.com/greiman/SdFat

I think that Frank/Walter's microSoundRecorder uses SdFs.  It's SdFat that I happen to care about.  It appears that both have a problem with sdhc_isr().


@JuliaRegistrator register()


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

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.3 -m "<description of version>" 91efc7a002a1d758bef6c7e1adc522a5124007b2
git push origin v0.6.3
```


lis


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

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


--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed   0 / 23  tests     (23 failed)
>
>        Score:
>            0.00 points of a possible 23.00  (0.00%)
>     ========================================================


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

* https://pepega.com
* https://pepega.sygeman.now.sh
* https://pepega-git-master.sygeman.now.sh


I was suggesting the other linking arrangement (tag in -main, comment in extension), but this also works great. I mostly just want to make sure that we can find all of the instances of CANVAS in the -main, which this achieves.


7400-Plant-Flow-Resolver-Revision (EnergyArchmage) - Win64-Windows-10-VisualStudio-16: OK (2449 of 2452 tests passed, 3 test warnings)

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

Failures:\n

regression Test Summary
 * Passed: 659
 * Failed: 3

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


Looks like the quote mark was accidentally changed


Probably. At least that's my current understanding.


-------------------------------------------------------------------------------
  Test 1: Check that the client can establish basic connections
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 2: Send a short simple ASCII message terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 3: Send a short simple ASCII message not terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 4: Send a multi-line ASCII message
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 5: Send the entire text of Moby Dick to the server
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 6: Send random short alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 7: Send random long alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... ''
>     Message: 2                                             ... ''
>     Message: 3                                             ... ''
>     Message: 4                                             ... ''
>     Message: 5                                             ... ''
>     Message: 6                                             ... ''
>     Message: 7                                             ... ''
>     Message: 8                                             ... ''
>     Message: 9                                             ... ''
>     Message: 10                                            ... ''
>     Message: 11                                            ... ''
>     Message: 12                                            ... ''
>     Message: 13                                            ... ''
>     Message: 14                                            ... ''
>     Message: 15                                            ... ''
>     Message: 16                                            ... ''
>     Message: 17                                            ... ''
>     Message: 18                                            ... ''
>     Message: 19                                            ... ''
>     Message: 20                                            ... ''
>     Message: 21                                            ... ''
###
                               -- test ed --

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed   0 / 23  tests     (23 failed)
>            Passed   0 / 25  subtests  (25 failed)
>
>        Score:
>            0.00 points of a possible 23.00  (0.00%)
>     ========================================================


We allow additional sections for other tools own configuration; see the commits I merged to mainline master.


Thanks!  I appreciate it and will update the Debian package shortly.  BTW, I understand how that can be annoying, so I submitted #104 to eliminate this annoyance.


Changing the data on the .js document.


![image](https://user-images.githubusercontent.com/11821758/62397020-828bd700-b529-11e9-8e8e-d01a3ccbda48.png)
ETH pause fixed


you may use stack as a 4th option


@all-contributors please add @naltatis for code.


All good


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

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


This addresses  #10 and #11 from @wigging. Don't have an automated schema enforcer for future submissions (not sure how to build that runner), but users will take the template for each folder to add their information.


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

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


I copy and paste from the devs list of perms if there are mistakes tell me so I can see what they are.


Deployment failed with the following error:

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


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit a188f8016c527c476d957422b5e8b6bafafd2644.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


I don't think so. I'm not sure how it would happen since you're renaming within a single directory.


the main problem is this
```
PORT_DIPSETTING(      0x0000, "Very_Hard" )
PORT_DIPSETTING(      0x0008, "Hard" )
PORT_DIPSETTING(      0x0018, "Normal" )
PORT_DIPSETTING(      0x0010, "Easy" )
```

If I compile these, inptport.h complains about missing STRs on the driver, and throws out an error.


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

* https://unzzz.now.sh
* https://unzzz.now.mckay.la
* https://unzzz.partheseas.now.sh
* https://unzzz-git-master.partheseas.now.sh


зачем тут этот `x`??


@jfescobar18  The real issue here is that we have another test that isn't cleaning up the contributions it has created.  So, maybe we should delete all the contributions before starting this test?  Otherwise, this is just testing that the `Sum()` function works 😄


Hi, Nice work, please see feedback below and please reach out to me if you have any questions on slack @RuddyR
The Good
1. Clean, easy to understand the flow
2. Successfully writes to a file

To Improve: this is to be done to mark the project a success
1. No load function
2. No tests
3. visitor.save() will always return visitor_01.json and will never return visitor_02.json or visitor_03.json because of how you handle your count - try make it a global variable
4. Your stringify has 2 other parameters in it,(JSON.stringify(this,null,2)) why and what do they mean.
5. Why did you use writeFileSync instead of writeFile for your file write


в вашем коде очень часто повторяеться
```
std::numeric_limits<int>::min() и std::numeric_limits<int>::max()
вынесите это в отдельную переменную
const int INT_MIN = std::numeric_limits<int>::min();
const int INT_MAX = std::numeric_limits<int>::max();
```


primer


great commit))


Copy of this build can be found at
https://builds.myetherwallet.com/build/7cb980f43a21b5b657bb9b13548bf4e31d2e2ccf/index.html
                       https://www.cloudflare-ipfs.com/ipfs/QmfZ8WBvw5F5tMYHPAHvweK63USJ3S7R8ykZYUqjo9kg6Y
                       Virus Total analysis
                       https://www.virustotal.com/file/125371142c679e784317a796f20631be25bb741a1e9740e5d19743555ff9333e/analysis/1564778474/


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

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


потом у вас очень длинная строка, надо их разбивать, т.е правило то что строка должна помещаться на экран, типа лимит 100 символов на одной строке
```
std::cout << "Entering the number: 'a' it must be more then : " <<
                    std::numeric_limits<int>::min()                               <<
                    ", less then : "  << std::numeric_limits<int>::max() << std::endl;
```


`firstTemplatePass`, `staticViewQueries` and `staticContentQueries` produce 3 memory reads and also make the TView bigger making it more likely that there will be L2 cache miss.

I propose to put them all into a single field where bits have meaning. This should decrease the read count and make this faster.


немного github подкачал в форматировании текста


sync_pool worked.


что за труууууууу


-------------------------------------------------------------------------------
  Test 1: Check that the client can establish basic connections
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 2: Send a short simple ASCII message terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 3: Send a short simple ASCII message not terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 4: Send a multi-line ASCII message
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 5: Send the entire text of Moby Dick to the server
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 6: Send random short alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 7: Send random long alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... ''
>     Message: 2                                             ... ''
>     Message: 3                                             ... ''
>     Message: 4                                             ... ''
>     Message: 5                                             ... ''
>     Message: 6                                             ... ''
>     Message: 7                                             ... ''
>     Message: 8                                             ... ''
>     Message: 9                                             ... ''
>     Message: 10                                            ... ''
>     Message: 11                                            ... ''
>     Message: 12                                            ... ''
>     Message: 13                                            ... ''
>     Message: 14                                            ... ''
>     Message: 15                                            ... ''
>     Message: 16                                            ... ''
>     Message: 17                                            ... ''
>     Message: 18                                            ... ''
>     Message: 19                                            ... ''
>     Message: 20                                            ... ''
>     Message: 21                                            ... ''
###
                               -- test ed --

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed   0 / 23  tests     (23 failed)
>            Passed   0 / 25  subtests  (25 failed)
>
>        Score:
>            0.00 points of a possible 23.00  (0.00%)
>     ========================================================


что это за такое)


ну зачем разделять обьявление с инициализацией
```
const int DISCRIMINANT = (b * b) - (FOUR * a * c);
```


ok


Hi @simonmichael, I got an error compiling hledger and I bissected it to this commit.

The error:

```
/var/home/mildred/Projects/hledger/hledger-api/hledger-api.hs:257:10: error:
    • Couldn't match type ‘Maybe
                             (SwaggerType 'Data.Swagger.Internal.SwaggerKindSchema)’
                     with ‘SwaggerType t0’
        arising from a functional dependency between:
          constraint ‘HasType Schema (SwaggerType t0)’
            arising from a use of ‘type_’
          instance ‘HasType
                      Schema
                      (Maybe (SwaggerType 'Data.Swagger.Internal.SwaggerKindSchema))’
            at <no location info>
    • In the first argument of ‘(.~)’, namely ‘type_’
      In the second argument of ‘(&)’, namely ‘type_ .~ SwaggerNumber’
      In the first argument of ‘(&)’, namely
        ‘mempty & type_ .~ SwaggerNumber’
    |
257 |        & type_   .~ SwaggerNumber
    |          ^^^^^

```


зачем тут использовать переменную second_x если вы ее не используете)


This would be even more useful if the scope created here could be cascaded - such that downstream components rendered within this component, woulf have their dependencies injected from this cascaded scope, rather than the default application level services. The benefit of this would be that downstream components need not be aware of scopes or inherit from any special component- they'd just get their dependencies injected as normal. I'll await to read the docs on this but will be keen to see how this current design plays out.


а про приоритет операции забыли?
```
значало будет выполнено деление, а потом результат будет суироваться
x = -c / (b + .0f);
```


You need to increment this number after making a change to schema.graphql. I know this is strange and weakening.


We'll fix this


this colon was causing the error


and this would also cause an error. I removed it for now as I wasn't sure exactly how this field is supposed to work.


Successfully aliased the URL <https://coip-7z25x7rc7.now.sh> to the following aliases:

* https://car-over-ip.now.sh
* https://coip.ladwig.now.sh
* https://coip-git-master.ladwig.now.sh


how about

`value = dictionary[key]
if  value is none or value.lower() in  ('null', 'unknown', 'none'):`

just a thought


@hawkeye116477 Tak, w sumie może jednak lepiej przeniosę plik do ScriptsPlayground.


опять же можно заюзать константу для литерала 50


-------------------------------------------------------------------------------
  Test 1: Check that the client can establish basic connections
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 2: Client: Send a short simple ASCII message terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 3: Client: Send a short simple ASCII message not terminated by a newline
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 4: Client: Send a multi-line ASCII message
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 5: Client: Send the entire text of Moby Dick to the server
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 6: Client: Send random short alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 7: Client: Send random long alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 8: Client: Send a short binary message
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 9: Client: Send random short binary messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 10: Client: Send random long binary messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... FAIL
>     Message: 2                                             ... FAIL
>     Message: 3                                             ... FAIL
>     Message: 4                                             ... FAIL
>     Message: 5                                             ... FAIL
>     Message: 6                                             ... FAIL
>     Message: 7                                             ... FAIL
>     Message: 8                                             ... FAIL
>     Message: 9                                             ... FAIL
>     Message: 10                                            ... FAIL
>     Message: 11                                            ... FAIL
>     Message: 12                                            ... FAIL
>     Message: 13                                            ... FAIL
>     Message: 14                                            ... FAIL
>     Message: 15                                            ... FAIL
>     Message: 16                                            ... FAIL
>     Message: 17                                            ... FAIL
>     Message: 18                                            ... FAIL
>     Message: 19                                            ... FAIL
>     Message: 20                                            ... FAIL
>     Message: 21                                            ... FAIL
    Output from additional subtests was suppressed...
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 11: Check that the server is open to accepting connections
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 12: Try to run the server on several different ports.
-------------------------------------------------------------------------------

>     Port: 10316                                            ... FAIL
>     Port: 11316                                            ... FAIL
>     Port: 12316                                            ... FAIL
>     Port: 13316                                            ... FAIL
>     Port: 14316                                            ... FAIL
>     Port: 15316                                            ... FAIL
>     Port: 16316                                            ... FAIL
>     Port: 17316                                            ... FAIL
>     Port: 18316                                            ... FAIL
>     Port: 19316                                            ... FAIL
>     Port: 20316                                            ... FAIL
###
                               -- test failed (-1.0) --

-------------------------------------------------------------------------------
  Test 13: Try to connect to the server several times sequentially
-------------------------------------------------------------------------------

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

-------------------------------------------------------------------------------
  Test 14: Try to connect to the server several times concurrently
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 15: Server: Send a short simple ASCII message terminated by a newline
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 16: Server: Send a short simple ASCII message not terminated by a newline
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 17: Server: Send a multi-line ASCII message
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 18: Server: Send the entire text of Moby Dick to the server
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 19: Server: Send random short alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... skip
>     Message: 2                                             ... skip
>     Message: 3                                             ... skip
>     Message: 4                                             ... skip
>     Message: 5                                             ... skip
>     Message: 6                                             ... skip
>     Message: 7                                             ... skip
>     Message: 8                                             ... skip
>     Message: 9                                             ... skip
>     Message: 10                                            ... skip
>     Message: 11                                            ... skip
>     Message: 12                                            ... skip
>     Message: 13                                            ... skip
>     Message: 14                                            ... skip
>     Message: 15                                            ... skip
>     Message: 16                                            ... skip
>     Message: 17                                            ... skip
>     Message: 18                                            ... skip
>     Message: 19                                            ... skip
>     Message: 20                                            ... skip
>     Message: 21                                            ... skip
>     Message: 22                                            ... skip
>     Message: 23                                            ... skip
>     Message: 24                                            ... skip
>     Message: 25                                            ... skip
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 20: Server: Send random long alphanumeric messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... skip
>     Message: 2                                             ... skip
>     Message: 3                                             ... skip
>     Message: 4                                             ... skip
>     Message: 5                                             ... skip
>     Message: 6                                             ... skip
>     Message: 7                                             ... skip
>     Message: 8                                             ... skip
>     Message: 9                                             ... skip
>     Message: 10                                            ... skip
>     Message: 11                                            ... skip
>     Message: 12                                            ... skip
>     Message: 13                                            ... skip
>     Message: 14                                            ... skip
>     Message: 15                                            ... skip
>     Message: 16                                            ... skip
>     Message: 17                                            ... skip
>     Message: 18                                            ... skip
>     Message: 19                                            ... skip
>     Message: 20                                            ... skip
>     Message: 21                                            ... skip
>     Message: 22                                            ... skip
>     Message: 23                                            ... skip
>     Message: 24                                            ... skip
>     Message: 25                                            ... skip
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 21: Server: Send a short binary message
-------------------------------------------------------------------------------

###
                               -- test skipped --

-------------------------------------------------------------------------------
  Test 22: Server: Send random short binary messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... skip
>     Message: 2                                             ... skip
>     Message: 3                                             ... skip
>     Message: 4                                             ... skip
>     Message: 5                                             ... skip
>     Message: 6                                             ... skip
>     Message: 7                                             ... skip
>     Message: 8                                             ... skip
>     Message: 9                                             ... skip
>     Message: 10                                            ... skip
>     Message: 11                                            ... skip
>     Message: 12                                            ... skip
>     Message: 13                                            ... skip
>     Message: 14                                            ... skip
>     Message: 15                                            ... skip
>     Message: 16                                            ... skip
>     Message: 17                                            ... skip
>     Message: 18                                            ... skip
>     Message: 19                                            ... skip
>     Message: 20                                            ... skip
>     Message: 21                                            ... skip
>     Message: 22                                            ... skip
>     Message: 23                                            ... skip
>     Message: 24                                            ... skip
>     Message: 25                                            ... skip
###
                               -- test passed --

-------------------------------------------------------------------------------
  Test 23: Server: Send random long binary messages to the server
-------------------------------------------------------------------------------

>     Message: 1                                             ... skip
>     Message: 2                                             ... skip
>     Message: 3                                             ... skip
>     Message: 4                                             ... skip
>     Message: 5                                             ... skip
>     Message: 6                                             ... skip
>     Message: 7                                             ... skip
>     Message: 8                                             ... skip
>     Message: 9                                             ... skip
>     Message: 10                                            ... skip
>     Message: 11                                            ... skip
>     Message: 12                                            ... skip
>     Message: 13                                            ... skip
>     Message: 14                                            ... skip
>     Message: 15                                            ... skip
>     Message: 16                                            ... skip
>     Message: 17                                            ... skip
>     Message: 18                                            ... skip
>     Message: 19                                            ... skip
>     Message: 20                                            ... skip
>     Message: 21                                            ... skip
>     Message: 22                                            ... skip
>     Message: 23                                            ... skip
>     Message: 24                                            ... skip
>     Message: 25                                            ... skip
###
                               -- test passed --

--------------------------------------------------------------
Results
--------------------------------------------------------------
>     ========================================================
>        Test summary:
>            Passed   4 / 23  tests     (19 failed)
>            Passed   0 / 111 subtests  (111 failed)
>
>        Score:
>            4.00 points of a possible 23.00  (17.39%)
>     ========================================================


вас не смущает что у вас `i` знаковый а `count_num` беззнаковый???


вот посмотрите чем плох это цикл для этой задачи?


а вот чем) наверное лучше заюзать while


@ableegoldman Is this line number that you are referring to?
https://github.com/confluentinc/kafka-streams-examples/blob/156b93c0955e6514f8ab40d83d926477fadd44b8/docker-compose.yml#L91


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

* https://dylanandspencer.wedding
* https://wedding.spencer.now.sh
* https://wedding-git-master.spencer.now.sh


немного у вас тут поплыло)


If you mean line 92, then yes


[KAËLLI](https://www.kaelli.ch)
Kreativität, Spiritualität und Sponsoren


а зачем переменную num обьявлять в не цикла? если она реально нужна только в цикле


@samhouts Will all these commits, can we see another nightly build? I thought nightly builds were supposed to run every night?


This commit touches a *lot* of unrelated stuff. Are you sure you meant to commit all this at once?


@adrianknight89 there was an issue with the CI process that's been resolved so they should start back up again soon.


I have pushed that fix already. It might take a few hours for it to make its way into a Melpa snapshot.


I don't think it's fair to ask a maintainer to keep working on something for free at the time they've decided to step down. It might be reasonable to reach out to him directly and offer to ship him floppy hardware for free, but from [the commit description](https://github.com/torvalds/linux/commit/be2ece49e68361f9b56098e5df3ddbccf87d140a), it sounds like he's done.

The driver isn't going to disappear overnight. If it breaks in the future, you can report bugs and offer to test fixes, and that might be enough to keep it working in the future.


ну вот с сообщения вообще не ясно зачем мне вводить число больше нуля