Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connecting crowtty at default (info) level apparently does not register with services #328

Open
spookyvision opened this issue Aug 13, 2024 · 0 comments

Comments

@spookyvision
Copy link
Contributor

on Lichee RV:

❯ just crowtty serial /dev/cu.usbmodem113102
cargo run --profile release --bin crowtty -- serial /dev/cu.usbmodem113102
    Finished `release` profile [optimized + debuginfo] target(s) in 0.47s
     Running `/tmp/cargo/release/crowtty serial /dev/cu.usbmodem113102`
[2 +0000.000020917s] UART KEYB pseudo-keyboard (SerMux port :2) reading from STDIN
[3 +0000.105567917s] UART BEAT Max level set to Some(INFO)

– no further output.

compared to:

❯ just crowtty serial -t debug /dev/cu.usbmodem113102
cargo run --profile release --bin crowtty -- serial -t debug /dev/cu.usbmodem113102
    Finished `release` profile [optimized + debuginfo] target(s) in 0.17s
     Running `/tmp/cargo/release/crowtty serial -t debug /dev/cu.usbmodem113102`
[2 +0000.000037167s] UART KEYB pseudo-keyboard (SerMux port :2) reading from STDIN
[3 +0000.402139875s] UART BEAT Max level set to Some(DBUG)
[3 +0000.425152875s] UART INFO SerialMuxServer::register: kernel::services::serial_mux: SPAN (0001)
[3 +0000.447915708s] UART INFO loopback{settings=LoopbackSettings { enabled: true, port: 0, buffer_size: 128 }}: kernel::daemons::sermux: SPAN (0002)
[3 +0000.471969042s] UART INFO hello{settings=HelloSettings { enabled: true, port: 1, buffer_size: 32, message: "hello\r\n", interval: 1s }}: kernel::daemons::sermux: SPAN (0003)
[3 +0000.497125042s] UART INFO KeyboardMuxServer::register: kernel::services::keyboard::mux: SPAN (0004)
[3 +0000.521085333s] UART INFO KeyboardMuxServer::register: kernel::services::keyboard::mux: Registering keyboard mux, settings=KeyboardMuxSettings { enabled: true, max_keyboards: 32, buffer_capacity: 8, sermux_port: Some(2) }
[3 +0000.543749042s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::mux::KeyboardMuxService}: kernel::registry: SPAN (0005)
[3 +0000.566199333s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::mux::KeyboardMuxService}: kernel::registry: Registered KOnly, service_id=0, uuid=70861d1c-9f01-4e9b-89e6-ede77d8f26d8
[3 +0000.566245083s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::mux::KeyboardMuxService}: kernel::registry:  END (0005): 22.525041ms
[3 +0000.566276833s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::KeyboardService}: kernel::registry: SPAN (0006)
[3 +0000.566285917s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::KeyboardService}: kernel::registry: Registered KOnly, service_id=1, uuid=524d77b1-499c-440b-bd62-e63c0918efb5
[3 +0000.566291500s] UART INFO KeyboardMuxServer::register:Registry::register_konly{svc=kernel::services::keyboard::KeyboardService}: kernel::registry:  END (0006): 33.5µs
[3 +0000.590133958s] UART INFO SpawnulatorServer::register: kernel::services::forth_spawnulator: SPAN (0007)
[3 +0000.613373875s] UART INFO SpawnulatorServer::register: kernel::services::forth_spawnulator: Who spawns the spawnulator?, settings=SpawnulatorSettings { enabled: true, capacity: 16 }
[3 +0000.637964250s] UART INFO SpawnulatorServer::register:Registry::register_konly{svc=kernel::services::forth_spawnulator::SpawnulatorService}: kernel::registry: SPAN (0008)
[3 +0000.638017875s] UART INFO SpawnulatorServer::register:Registry::register_konly{svc=kernel::services::forth_spawnulator::SpawnulatorService}: kernel::registry: Registered KOnly, service_id=2, uuid=4ae4a406-005a-4bde-be91-afc1900f76fa
[3 +0000.638041292s] UART INFO SpawnulatorServer::register:Registry::register_konly{svc=kernel::services::forth_spawnulator::SpawnulatorService}: kernel::registry:  END (0008): 99.708µs
[3 +0000.650481292s] UART INFO SpawnulatorServer::register: kernel::services::forth_spawnulator: ForthSpawnulatorService registered
[3 +0000.650501083s] UART INFO SpawnulatorServer::register: kernel::services::forth_spawnulator:  END (0007): 60.37725ms
[3 +0000.675678792s] UART INFO SpiSenderServer::register{queued=4}: mnemos_d1_core::drivers::spim: SPAN (0009)
[3 +0000.698593083s] UART INFO SpiSenderServer::register{queued=4}: mnemos_d1_core::drivers::spim: Starting SpiSenderServer, queued=4
[3 +0000.698644000s] UART INFO SpiSenderServer::register{queued=4}:Registry::register_konly{svc=mnemos_d1_core::drivers::spim::SpiSender}: kernel::registry: SPAN (0010)
[3 +0000.698659542s] UART INFO SpiSenderServer::register{queued=4}:Registry::register_konly{svc=mnemos_d1_core::drivers::spim::SpiSender}: kernel::registry: Registered KOnly, service_id=3, uuid=b5fd3487-08c4-4c0c-ae97-65dd1b151138
[3 +0000.698672583s] UART INFO SpiSenderServer::register{queued=4}:Registry::register_konly{svc=mnemos_d1_core::drivers::spim::SpiSender}: kernel::registry:  END (0010): 36.541µs
[3 +0000.721995167s] UART INFO SpiSenderServer::register{queued=4}: mnemos_d1_core::drivers::spim: return=()
[3 +0000.722047708s] UART INFO SpiSenderServer::register{queued=4}: mnemos_d1_core::drivers::spim:  END (0009): 46.386ms
[3 +0000.745466458s] UART INFO D1Uart::register: mnemos_d1_core::drivers::uart: SPAN (0011)
[3 +0000.767176583s] UART INFO D1Uart::register: mnemos_d1_core::drivers::uart:  END (0011): 21.72275ms
[3 +0001.423909125s] UART DBUG SerialMuxServer::register: mnemos_d1_core::drivers::sharp_display: Toggling vcom, vcom=false
[3 +0002.399931292s] UART DBUG SerialMuxServer::register: mnemos_d1_core::drivers::sharp_display: Toggling vcom, vcom=true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant