I'm in the process of writing my first (real) Kitura app and have been lost quite a lot. Kitura often sends Cannot GET /some/endpoint. responses without any error message in the log to help debug the issue. My log consists almost exclusively of [VERBOSE] [HTTPServerRequest.swift:215 parsingCompleted()] HTTP request from=127.0.0.1; proto=http; messages, even when there have been errors. I am us

In zebra/rt_netlink.c, we call vrf_lookup_by_id() when we get a route to find the associated vrf object for that table.

This should be improved to be a hash table mapping of Table ID to zebra_vrf object.

You would need to create a hash table probably in zebra/zebra_vrf.h that uses the table_id hash as a key and then update the code in vrf_lookup_by_id() to use this.

This shoul

Write the developers documentation of the following files

https://github.com/pgRouting/pgrouting/blob/develop/src/common/points_input.c
https://github.com/pgRouting/pgrouting/blob/develop/include/c_common/points_input.h

We use Doxygen to generate the documentation
http://www.stack.nl/~dimitri/doxygen/

Closed route-data spec validation doesn't allow :conflicting key

https://cljdoc.org/d/metosin/reitit/0.4.2/doc/basics/route-conflicts#route-conflicts