Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identical entity names will cause an infinite loop #148

Merged
merged 1 commit into from
Jan 19, 2022

Conversation

darlingtld
Copy link

Identical entity names will cause an infinite loop "RuntimeError: maximum recursion depth exceeded". Give a clear message about which applications have this entity.
Trying to self.name in Raise AmbiguousReferenceException will result in a dead loop.

splunklib\client.py", line 928, in _load_atom_entry
    raise AmbiguousReferenceException("Fetch from server returned multiple entries for name %s." % self.name)
  splunklib\client.py", line 1067, in name
    return self.state.title
  splunklib\client.py", line 1091, in state
    if self._state is None: self.refresh()
  splunklib\client.py", line 1011, in refresh
    self._state = self.read(self.get())
  splunklib\client.py", line 1071, in read
    results = self._load_state(response)
splunklib\client.py", line 934, in _load_state
    entry = self._load_atom_entry(response)
client.py", line 928, in _load_atom_entry
    raise AmbiguousReferenceException("Fetch from server returned multiple entries for name %s." % self.name)
client.py", line 1067, in name
    return self.state.title
.
.
.

test.json.zip

…imum recursion depth exceeded". Give a clear message about which applications have this entity.
@darlingtld
Copy link
Author

@itay
I have signed the CLA and attached the sample json for testing.

@ashah-splunk ashah-splunk merged commit a750f3b into splunk:develop Jan 19, 2022
@akaila-splunk akaila-splunk mentioned this pull request Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants