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

nit: keyerror exception handling #35

Merged
merged 1 commit into from
Jul 18, 2024
Merged

Conversation

myungjin
Copy link
Contributor

Description

There is a chance that remove_world in world_manager is called twice. The funcall call removes a key from worlds_stores. So, the second call leads to KeyError.
We currently can't ensure call the function only once because the current remove_world is not clean due to a deadlock issue. So, we mask the key error.

Type of Change

  • Bug Fix
  • New Feature
  • Breaking Change
  • Refactor
  • Documentation
  • Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • All code style checks pass
  • New code contribution is covered by automated tests
  • All new and existing tests pass

There is a chance that remove_world in world_manager is called twice.
The funcall call removes a key from worlds_stores.
So, the second call leads to KeyError.
We currently can't ensure call the function only once because
the current remove_world is not clean due to a deadlock issue.
So, we mask the key error.
@myungjin myungjin merged commit fb8a6a7 into cisco-open:main Jul 18, 2024
1 check passed
@myungjin myungjin deleted the keyerror branch July 18, 2024 02:25
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.

1 participant