KarpelesLab / libwallet / 24508972981

25%

push

github

wltlog: route output through the event channel so iOS Flutter sees it

On Flutter+iOS, the Go runtime's os.Stderr is NOT captured by the
host app's logger — log.Printf writes literally go nowhere the
user can read. That made all of 0.3.12's diagnostic logging
invisible to the tester who triggered this work.

Fix: route every wltlog emission through the apirouter broadcast
channel (already used for Web3 requests, balance changes, etc.).
Dart subscribes to the channel, sees {"event":"log", "data":{
"level":"debug","msg":"..."}} and can forward it to
developer.log / print — which actually shows up in Flutter's log
output on all three platforms.

- wltlog gains a Sink type and SetSink() to install a host-side
  forwarder. wltbase/info.go:init wires it up to wltutil.
  BroadcastMsg("log", {...}).
- New LogEvent in dart/lib/src/events/events.dart with level +
  message fields; exported from libwallet.dart.
- New LibwalletClient.logs stream — convenience typed filter over
  the general events stream. Docstring shows the developer.log
  pattern.
- Sink panics are swallowed with a fallback to stderr, so a
  broken broadcast pipeline can never take down a user's send.
- Tests (no sink installed) keep the existing log.Printf stderr
  output they already rely on.

Recommended Flutter wiring (will also land in the example app):

    import 'dart:developer' as developer;
    client.logs.listen((e) {
      developer.log(e.message, name: 'libwallet.${e.level}');
    });

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

1 of 30 new or added lines in 2 files covered. (3.33%)

2132 of 10274 relevant lines covered (20.75%)

2.49 hits per line