fix(cli): validate BASHUNIT_SHARD_INDEX/TOTAL set outside the --shard flag by Chemaclass · Pull Request #969 · TypedDevs/bashunit

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass · 2026-08-02T10:51:10Z

🤔 Background

$ BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/./src/main/run.sh: line 39: _i % _shard_total: division by 0
$ echo$?0

Sharding is configurable two ways — the --shard flag, or the environment variables directly (including from .bashunitrc). Only the flag path was parsed and range-checked: set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic.

🐛 Two bad outcomes

Zero or non-numeric total — leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing
Out-of-range index — quietly printed No tests found, which reads as a filter problem rather than a misconfiguration

The exit-0 half is what matters: it's the same shape validate_config_or_exit was introduced to close in #873 and #879, where bad input ran the wrong thing and reported success.

💡 Changes

Validation hangs off bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks. Non-sharded runs are untouched, and --shard keeps its own parsing and existing message.

Verified: total=0, index>total, index=0 and non-numeric all now exit 1 with a clear message; valid 1/2, no-shard, and both --shard 1/2 (0) and --shard 5/2 (1) unchanged.

✅ Verification

3 acceptance tests, confirmed RED against the unfixed source.

make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅ · 1639 sequential / 1598 parallel-simple-strict.

… flag BASHUNIT_SHARD_INDEX=1 BASHUNIT_SHARD_TOTAL=0 ./bashunit tests/ ./src/main/run.sh: line 39: _i % _shard_total: division by 0 # exit 0 Sharding can be configured two ways: the --shard flag, or the environment variables directly, including from .bashunitrc. Only the flag path was parsed and range-checked -- set_shard_or_exit runs solely when --shard is seen. Setting the variables directly walked straight into main/run.sh's arithmetic. Two distinct bad outcomes. A zero or non-numeric total leaked a raw bash error to the user and still exited 0, so a sharded CI job reported success while running nothing. An out-of-range index quietly printed "No tests found", which looks like a filter problem rather than a misconfiguration. The exit-0 half is the part that matters: the same shape validate_config_or_exit was introduced to close for other settings in #873 and #879, where bad input ran the wrong thing and reported success. Validation is attached to bashunit::env::is_shard_enabled, so it covers both entry points rather than duplicating the flag path's checks, and non-sharded runs are untouched. The --shard flag keeps its own parsing and its existing message. 1639 sequential / 1598 parallel; baseline + 3 acceptance tests, RED first.

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Chemaclass added the bug Something isn't working label Aug 2, 2026

Chemaclass self-assigned this Aug 2, 2026

Chemaclass merged commit 0616c0e into mainAug 2, 2026
37 checks passed

Chemaclass deleted the fix/shard-env-bypasses-validation branch August 2, 2026 11:05

Chemaclass mentioned this pull request Aug 8, 2026
docs(changelog): fold the later entries into the tightened style #1001
Merged

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 2, 2026

🤔 Background

🐛 Two bad outcomes

💡 Changes

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 2, 2026

🤔 Background

🐛 Two bad outcomes

💡 Changes

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 2, 2026

🤔 Background

🐛 Two bad outcomes

💡 Changes

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 2, 2026

🤔 Background

🐛 Two bad outcomes

💡 Changes

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 2, 2026

🤔 Background

🐛 Two bad outcomes

💡 Changes

✅ Verification