Pavel Kirienko

Results 215 issues of Pavel Kirienko

Per the JSON specification, NaN floats cannot be represented natively, so many encoders substitute NaN with null. One would expect PJ to handle null values in JSON input as NaN...

bug

Stock NuttX seems to be using a standard O(n) best-fit list-traversal allocator. It should be trivial to replace and benchmark.

help wanted

The coding conventions are described here: https://kb.zubax.com/x/84Ah The existing codebase has certain deviations which should be fixed in the rewrite; the two things that come to mind are the capitalization...

v1

Imagine an ARINC-653-style unit running some logic on bare metal alongside with several virtualized applications sharing the same hardware. Suppose that the hardware is connected to a UAVCAN bus, and...

enhancement
v1
milestone constraint

So the current reception architecture was created back in 2014 when I was working on a very, very early proof-of-concept (the protocol was first announced in 2014). A lot of...

v1
milestone constraint

We don't have type signatures anymore, so this thing is no longer needed. Which is great news because the library will be singleton-free and not dependent on static initialization constructors...

v1
milestone constraint

This is related to type safety; the same principle should be followed wherever applicable. Objects of `NodeID` must always contain a valid value of node ID, which is an integer...

v1
milestone constraint

There are two types of clock in libuavcan: * Monotonic clock, which only goes forward steadily at the same rate (with possible minor rate deviations caused by the instability of...

minor
v1
milestone constraint

Once #181 and #185 are implemented, it will no longer be necessary to waste time on periodic list traversals to remove stale entries from them: https://github.com/UAVCAN/libuavcan/blob/67da0aae7dd4eedae7905ab98941592cebab4723/libuavcan/src/transport/uc_dispatcher.cpp#L306-L312 This behavior is bad...

v1
milestone constraint