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

--[BugFix] GibsonSemanticScene JSON access. #2181

Merged
merged 2 commits into from
Aug 9, 2023
Merged

Conversation

jturner65
Copy link
Contributor

Motivation and Context

Reading a JSON element should be check exists then read, not attempt to read then check if null, which is what the GibsonSemanticScene attempts to do. This was failing an assertion in RapidJSON that was only visible if compiled in Debug mode; in Release RapidJSON silenced the assertion and attempted to work around the problem.

How Has This Been Tested

All C++ and python tests (in both release and debug)

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have completed my CLA (see CONTRIBUTING)
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@facebook-github-bot facebook-github-bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Aug 9, 2023
Copy link
Contributor

@aclegg3 aclegg3 left a comment

Choose a reason for hiding this comment

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

Thanks for identifying the issue and fixing it despite the silent failure. 🚀

Copy link
Contributor

@0mdc 0mdc left a comment

Choose a reason for hiding this comment

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

LGTM!

--Reading a JSON element should be check exists then read, not attempt to read then check if null.
1 lookup in string instead of two.
@jturner65 jturner65 merged commit 5243e46 into main Aug 9, 2023
10 checks passed
@jturner65 jturner65 deleted the BugFix_GibsonJSONLoad branch August 9, 2023 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Do not delete this pull request or issue due to inactivity.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants