ArcGISRuntimeClustering
Simple example showing how clustering can be accomplished in ArcGIS Runtime 100.x.
- 0
- C#
- 6 y ago
The maintainer has not written a description at the source.
Repo johncdoherty/FlowExceptionsTest, read from GitHub 1 min ago. johncdoherty has not joined Take My Repo.
johncdoherty/FlowExceptionsTest is a public repo on GitHub by johncdoherty. It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it. It is written mainly in C#, has 0 stars and last changed on 2026-03-04. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-22.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
A comprehensive test harness to validate CommunityToolkit.Mvvm's FlowExceptionsToTaskScheduler parameter before implementing workspace-wide changes.
VALIDATION DATE: March 4, 2026
| Test # | Pattern | FlowExceptions? | Expected Behavior | Actual Result |
|---|---|---|---|---|
| 1 | async Task |
✅ Yes | Exception caught | ✅ PASS - Caught by TaskScheduler |
| 2 | async Task |
❌ No | App crash | ✅ PASS - Crashed as expected |
| 3 | Sync Task (no async) |
✅ Yes | Exception caught | ❌ FAIL - App crashed unexpectedly |
| 4 | Sync Task (no async) |
❌ No | App crash | ✅ PASS - Crashed as expected |
| 5 | Nested async call | ✅ Yes | Exception caught | ✅ PASS - Caught by TaskScheduler |
| 6 | Task.Run | ✅ Yes | Exception caught | ✅ PASS - Caught by TaskScheduler |
| 7 | Fire-and-forget | ✅ Yes | Exception caught | ✅ PASS - Caught by TaskScheduler |
| 8 | Immediate throw (before await) | ✅ Yes | Exception caught | ✅ PASS - Caught by TaskScheduler |
| 9 | async void |
❌ No | App crash | ✅ PASS - Crashed as expected |
KEY INSIGHT: Only Test 3 failed unexpectedly. All 5 async Task tests with FlowExceptions worked perfectly (Tests 1, 5, 6, 7, 8).
async Task methods WITH FlowExceptionsToTaskScheduler = true
TaskScheduler.UnobservedTaskException after GCTask-returning method (no async keyword)
async keyword = no state machine = no Task to capture exceptionFlowExceptionsToTaskScheduler protects ANY method with the async keyword, even if it throws BEFORE the first await.
// ✅ WORKS - async keyword creates state machine that captures ALL exceptions [RelayCommand(FlowExceptionsToTaskScheduler = true)] private async Task DoWorkAsync() { throw new Exception("Captured!"); // ✅ Routes to TaskScheduler (Test 8 proves this) await Task.Delay(100); // Never reached - doesn't matter! } // ❌ DOES NOT WORK - no async keyword = synchronous execution [RelayCommand(FlowExceptionsToTaskScheduler = true)] private Task DoWorkSync() { throw new Exception("Crashes!"); // ❌ Throws immediately on caller's thread (Test 3) }
Why This Matters:
async keyword creates a state machine that captures exceptions ANYWHERE in the methodasync Task)async) failedasync Task methodsasync Task methods (5/5 patterns worked)async Task)async Task vs sync Task# 1. Run the app cd /Applications/Melbourne/FlowExceptionsTest dotnet build -t:Run -f net10.0-maccatalyst # 2. In the app: # - Click any GREEN button (Test 1-8) # - Wait 3 seconds # - Click PURPLE "Force GC" button # # 3. Watch Debug Console for: # ✅ "SUCCESS: TaskScheduler.UnobservedTaskException FIRED!" = WORKS! # ❌ "FAILURE: AppDomain.UnhandledException FIRED!" = DOESN'T WORK
Success Criteria: All 6 GREEN tests should show ✅ SUCCESS → Proceed with 40% effort reduction
Failure Criteria: Any GREEN test shows ❌ FAILURE → Revert to manual try/catch plan
This test project answers the critical $250K question: Does [RelayCommand(FlowExceptionsToTaskScheduler = true)] actually route exceptions to TaskScheduler.UnobservedTaskException instead of crashing the app?
Impact:
Test Coverage: 9 scenarios across all async patterns (async/await, sync Task, nested calls, Task.Run, fire-and-forget, immediate throw, async void)
Time to Run: 5 minutes per platform
Tests the claim made in FAULT_TOLERANCE_ANALYSIS.md that adding FlowExceptionsToTaskScheduler = true to [RelayCommand] attributes will route exceptions to TaskScheduler.UnobservedTaskException instead of crashing the app.
cd /Applications/Melbourne/FlowExceptionsTest
dotnet build -t:Run -f net10.0-maccatalystcd /Applications/Melbourne/FlowExceptionsTest
dotnet build -t:Run -f net10.0-ioscd /Applications/Melbourne/FlowExceptionsTest
dotnet build -t:Run -f net10.0-androidcd /Applications/Melbourne/FlowExceptionsTest
dotnet build -t:Run -f net10.0-windows10.0.19041.0Launch the app and watch the Debug Output window (VS Code: Debug Console)
Test GREEN buttons (WITH FlowExceptions) - All should route to TaskScheduler:
After clicking any GREEN button:
✅ SUCCESS: TaskScheduler.UnobservedTaskException FIRED!
Test RED buttons (WITHOUT FlowExceptions) - Should crash or go to AppDomain handler:
Test ORANGE button (Async Void) - For comparison:
AppDomain.UnhandledException (different behavior than RelayCommand)All GREEN button tests (1, 3, 5, 6, 7, 8) should show:
✅ SUCCESS: TaskScheduler.UnobservedTaskException FIRED!
RED button tests (2, 4) should show:
❌ FAILURE: App crashes or AppDomain.UnhandledException fires
ORANGE button test (9) should show:
⚠️ AppDomain.UnhandledException fires (expected for async void)
GREEN and RED buttons would behave the same (both crash or go to AppDomain)
The test app validates FlowExceptionsToTaskScheduler across these scenarios:
| Test | Scenario | FlowExceptions | Expected Handler |
|---|---|---|---|
| 1 | Async Task (await then throw) | ✅ Yes | TaskScheduler |
| 2 | Async Task (await then throw) | ❌ No | AppDomain/Crash |
| 3 | Sync Task (immediate throw) | ✅ Yes | TaskScheduler |
| 4 | Sync Task (immediate throw) | ❌ No | AppDomain/Crash |
| 5 | Nested async calls | ✅ Yes | TaskScheduler |
| 6 | Task.Run background | ✅ Yes | TaskScheduler |
| 7 | Fire-and-forget (unobserved) | ✅ Yes | TaskScheduler |
| 8 | Throw before await | ✅ Yes | TaskScheduler |
| 9 | Async void handler | N/A | AppDomain |
This covers:
Every async pattern used in the Melbourne codebase:
From the conversation summary: "LOW-MEDIUM confidence" based on single unverified usage. This test converts assumption into evidence through systematic validation.
[RelayCommand(FlowExceptionsToTaskScheduler = true)]✅ SUCCESS = TaskScheduler handler caught the exception (FlowExceptions WORKS!)❌ FAILURE = AppDomain handler caught it OR app crashed (FlowExceptions FAILED)⚠️ MAUI = MAUI's handler caught it (platform-specific behavior)ForceGC() button is critical - TaskScheduler.UnobservedTaskException only fires when the Task is garbage collected✅ Project builds successfully with minor deprecation warnings:
Application.MainPage is deprecated (use Windows[0].Page instead)DisplayAlert is deprecated (use DisplayAlertAsync instead)These warnings don't affect the test functionality.
FlowExceptionsTest/
├── FlowExceptionsTest.csproj ← Project file (minimal config, no custom resources)
├── FlowExceptionsTest.sln ← Solution file for VS Code
├── MauiProgram.cs ← App initialization (no custom fonts)
├── App.xaml ← App resources
├── App.xaml.cs ← ⭐ Exception handlers configured here
│ • TaskScheduler.UnobservedTaskException
│ • AppDomain.UnhandledException
├── AppShell.xaml ← Shell navigation
├── AppShell.xaml.cs
├── MainPage.xaml ← ⭐ Test UI (9 test buttons)
├── MainPage.xaml.cs ← ⭐ 9 test scenarios
│ • 6 WITH FlowExceptionsToTaskScheduler
│ • 2 WITHOUT (for comparison)
│ • 1 async void (baseline)
├── Platforms/
│ ├── Android/ ← Android-specific files
│ ├── iOS/ ← iOS-specific files
│ └── MacCatalyst/ ← MacCatalyst-specific files
├── Resources/
│ └── Styles/
│ ├── Colors.xaml ← Color definitions
│ └── Styles.xaml ← UI styles (no custom fonts)
└── README.md ← This file
Key Features:
[RelayCommand] attribute)Why CommunityToolkit.Mvvm 8.4.0? This is the same version used across the Melbourne workspace (Survey123, QuickCapture, etc.), ensuring the test results accurately reflect production behavior.
cd /Applications/Melbourne/FlowExceptionsTest
dotnet build -f net10.0-maccatalystcd /Applications/Melbourne/FlowExceptionsTest
dotnet build -t:Run -f net10.0-maccatalystcode /Applications/Melbourne/FlowExceptionsTest/FlowExceptionsTest.sln
cd /Applications/Melbourne/FlowExceptionsTest dotnet clean && dotnet build -f net10.0-maccatalyst
## FlowExceptionsToTaskScheduler Test Results **Date:** [Date] **Platform:** [iOS / MacCatalyst / Android / Windows] **Device:** [Device/Simulator info] **Tester:** [Name] ### Results | Test | Scenario | Expected | Actual | Pass/Fail | |------|----------|----------|--------|-----------| | 1 | Async Task + Flow | TaskScheduler | [Result] | ✅/❌ | | 2 | Async Task no Flow | AppDomain | [Result] | ✅/❌ | | 3 | Sync Task + Flow | TaskScheduler | [Result] | ✅/❌ | | 4 | Sync Task no Flow | AppDomain | [Result] | ✅/❌ | | 5 | Nested + Flow | TaskScheduler | [Result] | ✅/❌ | | 6 | Task.Run + Flow | TaskScheduler | [Result] | ✅/❌ | | 7 | Fire-forget + Flow | TaskScheduler | [Result] | ✅/❌ | | 8 | Immediate + Flow | TaskScheduler | [Result] | ✅/❌ | | 9 | Async void | AppDomain | [Result] | ✅/❌ | ### Conclusion [Overall assessment: Proceed / Qualify / Revert] ### Debug Output \`\`\` [Paste relevant debug output here] \`\`\` ### Screenshots [Attach screenshots of alerts/debug console]
Created: March 2026
Purpose: Validate FlowExceptionsToTaskScheduler before $250K remediation project
Status: Ready for testing
johncdoherty/FlowExceptionsTest is a public repo on GitHub by johncdoherty. Its maker has not written a description.
It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it.
Its maker tagged it for macOS and Windows. That is declared by the maker; Take My Repo has not tested it.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-03-04. GitHub counts 0 open issues and pull requests. Take My Repo does not judge from that whether it is maintained.

Simple example showing how clustering can be accomplished in ArcGIS Runtime 100.x.

Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/johncdoherty/FlowExceptionsTestTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.