c53dedc544
Render Retry beside Rename on a stopped failed run under both native
hosts, send only {run_id, request_key} for resume and add
retry_mode=restart for a fresh start, and open the run the accepted
reply names. Keep hidden actions out of the Wrap so native 8/4 dp
spacing is not doubled, and use a literal 2^32 entropy bound because
dart2js evaluates 1 << 32 as 0.
Adds wiring, guard and layout tests, a browser-only key regression and
the retry probe; notes/R2c-wire.md records the checks and limits.
23 lines
810 B
Dart
23 lines
810 B
Dart
import 'dart:async';
|
|
|
|
import 'package:flutter/foundation.dart';
|
|
import 'package:pipelines_app/application/bootstrap.dart';
|
|
|
|
/// Browser acceptance entrypoint for the run-retry wiring probe.
|
|
///
|
|
/// This is the normal app composition; the deterministic failed run, retry
|
|
/// replies and new-run details come from the isolated loopback fixture in
|
|
/// `tool/retry_wiring_probe.mjs`, never from app-side fake data. The zone and
|
|
/// `FlutterError` hooks only report probe failures to the driver; they do not
|
|
/// alter composition or behavior.
|
|
void main() {
|
|
FlutterError.onError = (details) {
|
|
debugPrint('FLUTTER ERROR: ${details.exceptionAsString()}');
|
|
FlutterError.presentError(details);
|
|
};
|
|
runZonedGuarded(
|
|
runPipelinesApp,
|
|
(error, stack) => debugPrint('ZONE ERROR: $error\n$stack'),
|
|
);
|
|
}
|