Play past OpenStruct loading issue with global 'require' #2022
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
We've been seeing "uninitialize constant" errors for OpenStruct like ``` uninitialized constant ProjectHelper::OpenStruct ``` which we only see the deployed environments, not in local development or in CI. This appears to be a file/class/module loading problem which occurs after unrelated changes to the codebase. To play past this issue we now explictly `require "ostruct"` from the main `application.rb` file.
… issue" This reverts commit 5f3b67d. This is now fixed generally by requiring OpenStruct in the main `application.rb` file: ``` require "ostruct" ```
|
lozette
approved these changes
Dec 5, 2024
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.
Play past OpenStruct loading issue with global 'require'
We've been seeing "uninitialize constant" errors for OpenStruct
like
which we only see the deployed environments, not in local development
or in CI.
This appears to be a file/class/module loading problem which occurs after
unrelated changes to the codebase.
To play past this issue we now explictly
require "ostruct"from themain
application.rbfile.