Skip to content

[BUG] March and June Quarters: Fix known nil reference paths #633

Open

Description

@general-kroll-4-life

Describe the bug

There exist some nil pointer dereferences possible. Most, if not all, are cushioned by the golang built in recover(). No matter, all should be fixed. Bugs thus fixed in the 2026 March and June quarter should tag, but not close, this issue.

Activity

  1. changed the title [-][BUG] June Quarter: Fix known nil reference paths[/-] [+][BUG] March plus June Quarters: Fix known nil reference paths[/+] on Mar 29, 2026
  2. changed the title [-][BUG] March plus June Quarters: Fix known nil reference paths[/-] [+][BUG] March and June Quarters: Fix known nil reference paths[/+] on Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions