Provide a generalized interface for transport log replay capabilities
@silverv ci sta già lavorando.
Dal 10/12/2022.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
There may be different means of recording and replaying transport logs for diagnostic purposes. One existing solution is pycyphal.transport.can.media.candump.CandumpMedia. The following requirements are common for all log replay pseudo-transports:
- Report the origin and final timestamps of the log file (min and max timestamp value).
- Report the number of transport frames in the log file.
- Report the current position of the replay cursor as:
- timestamp (origin timestamp initially);
- index of the transport frame (0 initially).
- Position the replay cursor immediately before:
- the specified time point;
- the specified frame index.
- Resume/pause the replay.
- Set the replay speed (1.0 is the default).
- Single-stepping: replay one frame (disregarding the timing) and pause.
- Report the name of the underlying resource (file path).
Note that estimation of the final timestamp and the total number of frames would often require full traversal of the log file, which may be very costly. The API should be designed with that cost in mind.
The existing CandumpMedia should implement this interface.
To facilitate the proper integration of the log replay capability into user-level software, it might be sensible to extend the pycyphal.transport.Transport interface with a new method that checks whether the transport in its current configuration is connected to a log file. If the transport is connected to a live network, the method would return nothing; otherwise, it would return an instance implementing this playback interface. Higher-level software will be able to benefit from it in the following manner:
- Yakut would be able to report the current progress via stderr and automatically exit when the file is fully replayed.
- A GUI tool like Yukon will be able to present the user with a nice UI like this:

One feature not covered here is the ability to scan the log file for all transport frames at once. This will be required by graphical tools to present the user with a high-level analysis of the log file contents (see the screenshot above): which ports are available, how the traffic intensity is distributed across the log file per port, whether there are transport errors or other noteworthy events, etc. There are at least two obvious ways to approach this:
-
Implement a dedicated method that returns an async iterator going over every recorded item frame in the log file. The items will be returned as instances of
pycyphal.transport.Capture. The caller will then handle them the same way captured traffic is handled: by feeding them into apycyphal.transport.Tracerinstance. -
Implement a cloning method that allows the caller to construct an independent copy of the entire transport fully detached from its original owner, then invoke
begin_capture()on that transport instance. The result would be identical to the above.
Relates to https://github.com/OpenCyphal/yakut/issues/1
@silverv @thirtytwobits FYI
- Lingua principale
- Python
- Stelle
- 143
- Fork
- 110
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenCyphal/pycyphal
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 48/100
OpenCyphal/pycyphal#396 ·
-
Add flush() functionalityApertaclass-feature domain-core help wanted severity-minor
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
OpenCyphal/pycyphal#339 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 35/100
OpenCyphal/pycyphal#338 · 3 commenti ·
-
DiagnosticPublisher attempts to use the main asyncio event loop from worker threads (which fails)Apertaclass-defect domain-core help wanted severity-major
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
OpenCyphal/pycyphal#336 ·
-
class-defect domain-core help wanted severity-minor
Difficoltà 3/5 1-2 giorni Idoneità per principianti 38/100
OpenCyphal/pycyphal#334 ·
Tutte le issue di OpenCyphal/pycyphal
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
py-econometrics/pyfixest#2072 ·
I maintainer di solito rispondono entro 1 giorno
-
~planning docs
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
Kromatic-Innovation/athenaeum#3084 ·
I maintainer di solito rispondono entro 1 giorno
-
Bosch Room Thermostat II number entities offer -500 to 3000 °C setpoint limits and a -32768 to 32767 °C outdoor temperatureForse già presa @zigpy-review-bot l’ha presa oggi. Apertabot: code audit
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
zigpy/zha-device-handlers#5769 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 Mezza giornata Idoneità per principianti 80/100
R0Y00/Xbox2Windows#254 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
Kludex/python-multipart#375 ·
I maintainer di solito rispondono entro 1 giorno