Skip to content

Conversation

k0ushal
Copy link
Contributor

@k0ushal k0ushal commented Sep 19, 2025

  • ES-2678: Added checks to verify that clusterInfo() is availble before accessing it.

  • Fixed linter errors

  • Fixed error reported by Cursor Bugbot

  • Added Changelog entry

Scope & Purpose

(Please describe the changes in this PR for reviewers, motivation, rationale - mandatory)

  • 💩 Bugfix
  • 🍕 New feature
  • 🔥 Performance improvement
  • 🔨 Refactoring/simplification

Checklist

  • Tests
    • Regression tests
    • C++ Unit tests
    • integration tests
    • resilience tests
  • 📖 CHANGELOG entry made
  • 📚 documentation written (release notes, API changes, ...)
  • Backports

Related Information

(Please reference tickets / specification / other PRs etc)

  • Docs PR:
  • Enterprise PR:
  • GitHub issue / Jira ticket:
  • Design document:

* ES-2678: Added checks to verify that clusterInfo() is
availble before accessing it.

* Fixed linter errors

* Fixed error reported by Cursor Bugbot

* Added Changelog entry
@k0ushal k0ushal requested a review from neunhoef September 19, 2025 11:45
@k0ushal k0ushal self-assigned this Sep 19, 2025
@cla-bot cla-bot bot added the cla-signed label Sep 19, 2025
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

// log crash dump feature
CrashHandler::logBacktrace();
}
THROW_ARANGO_EXCEPTION(TRI_ERROR_SHUTTING_DOWN);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Cluster Info Null Error Masked

The clusterInfo() method now unconditionally throws TRI_ERROR_SHUTTING_DOWN when _clusterInfo is null. This is problematic because if the server is not shutting down, it previously triggered a fatal assertion. The new behavior replaces this critical error with a misleading TRI_ERROR_SHUTTING_DOWN exception, obscuring the actual problem of _clusterInfo being unavailable during normal operation.

Fix in Cursor Fix in Web

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is OK, because we maintain complete backwards compatibilitiy.

Copy link
Member

@neunhoef neunhoef left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

// log crash dump feature
CrashHandler::logBacktrace();
}
THROW_ARANGO_EXCEPTION(TRI_ERROR_SHUTTING_DOWN);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is OK, because we maintain complete backwards compatibilitiy.

@neunhoef neunhoef added this to the 3.12.5.4 milestone Sep 22, 2025
@KVS85 KVS85 merged commit 15f48f3 into 3.12.5 Sep 22, 2025
8 checks passed
@KVS85 KVS85 deleted the bugfix-3.12.5/backport-clusterinfo-upgrade-fix branch September 22, 2025 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants