It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

this seems to have caused red dart-flutter hhh bot https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8818318172012638753/+/u/flutter_test_framework_coverage/stdout

27:55 +5519 ~13: loading /b/s/w/ir/cache/builder/flutter/packages/flutter/test/painting/continuous_rectangle_border_test.dart                                                                          
../../examples/layers/rendering/src/sector_layout.dart:623:34: Error: The argument type 'dynamic' can't be assigned to the parameter type 'HitTestResult'.
 - 'HitTestResult' is from 'package:flutter/src/gestures/hit_test.dart' ('lib/src/gestures/hit_test.dart').
  SectorHitTestResult.wrap(super.result) : super.wrap();
                                 ^
../../examples/layers/rendering/src/sector_layout.dart:635:41: Error: The argument type 'dynamic' can't be assigned to the parameter type 'HitTestTarget'.
 - 'HitTestTarget' is from 'package:flutter/src/gestures/hit_test.dart' ('lib/src/gestures/hit_test.dart').
  SectorHitTestEntry(RenderSector super.target, { required this.radius,  required this.theta })
                                        ^

@aam looks like that bot is not running with the super parameter experiment enabled (available starting with SDK 2.17.0-0). I am not familiar with the bot, but somewhere you'll need to bump the lower SDK constrains to be at least 2.17.0-0.

/cc @mit-mit

current hypothesis is that it was caused by https://dart-review.googlesource.com/c/sdk/+/239081 that landed in dart sdk, has not reached flutter repo yet.