add reader file format ipynb #1284
Merged
Conversation
This file contains 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
The get_step_response method in the Chain class was raising a KeyError when attempting to access the "id" key from chain_data because chain_data was an empty list instead of a dictionary. This scenario occurs when the chain is not found. Signed-off-by: Birdup <34012548+birdup000@users.noreply.github.com>
Signed-off-by: Birdup <34012548+birdup000@users.noreply.github.com>
Signed-off-by: Birdup <34012548+birdup000@users.noreply.github.com>
birdup000
changed the title
Signed-off-by: Birdup <34012548+birdup000@users.noreply.github.com>
birdup000
changed the title
Signed-off-by: Birdup <34012548+birdup000@users.noreply.github.com>
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.
Fixes crash thread crash when trying to read ipynb files
Types of changes
Changes visible to users:
fix- non-breaking change which fixes an issue)feat- non-breaking change which adds functionality)feat!!orfix!!- fix or feature that would cause existing functionality to not work as expected)Internal changes:
refactor- non-breaking change which only improves the design or structure of existing code, and making no changes to its external behavior)test- additions and improvements to unit tests and the smoke tests)chore- examples include GitHub Actions, issue templates)Checklist