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

fixup initialisation order of cpg generators (#5137) #159

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

khemrajrathore
Copy link
Member

We trigger the post-processing directly if a cpg is loaded on startup (e.g. ./joern cpg.bin). In that case, the typeRecoveryConfig has not been initialized. There's a reason why in Scala you have to explicitly make an effort to start with null, because more often than not you'll be missing out some random edge case... lazy val is the better alternative

fixes joernio#4999 (again...)

We trigger the post-processing directly if a cpg is loaded on startup
(e.g. `./joern cpg.bin`). In that case, the typeRecoveryConfig has not
been initialized. There's a reason why in Scala you have to explicitly
make an effort to start with `null`, because more often than not
you'll be missing out some random edge case... lazy val is the better
alternative

fixes joernio#4999 (again...)
@khemrajrathore khemrajrathore merged commit c09064d into backup_sync_4_0_29 Dec 13, 2024
7 of 17 checks passed
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.

3 participants