Repository navigation
Conversation
Core refuses an acquire query matching more than NEOPS_LOCK_MAX_QUERY_RESULTS entities (1000 by default). A workflow over a large inventory needs it raised, and .env had no way to reach core with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Author
|
Not needed: a deployment that needs a higher limit sets it in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Core refuses an acquire query that matches more than
NEOPS_LOCK_MAX_QUERY_RESULTSentities (1000 by default): "Search query '...' returned more than 1000 results". A workflow over a large inventory, e.g. a sync of every imported device to another system, needs a higher limit. Core reads the limit from its environment only, and.envcouldn't reach it:cms.envpasses through onlyOPTIONAL_CORE_KEYS.neops_compose/render.py:NEOPS_LOCK_MAX_QUERY_RESULTSadded toOPTIONAL_CORE_KEYS. When unset it's left out ofcms.env, so core keeps its own default..env.example: listed, commented out, under "Core settings passed through unchanged".docs/50-troubleshooting.md: a short entry for the refusal and how to raise the limit.tests/unit/test_render.py: the value reachescms.envwhen set and is absent when unset.make lint,make compose-configandmake doc-buildpass.make testpasses excepttest_ownership.py::test_chown_via_container_changes_and_restores_ownership_without_sudo, which fails the same way ondevelopon my Mac (Docker Desktop bind-mount ownership).Checklist:
🤖 Generated with Claude Code