Bugfix/error reading password env 35 #36
Open
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
…ts/results.py - Fixed the issue where the application was unable to read from the `password.env` file. - Updated the file reading logic in `apps/pages/results/results.py` to handle file paths correctly.
sikatikenmogne
force-pushed
the
bugfix/error-reading-password-env-35
branch
from
fcf8581
to
380cdd5
Compare
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.
Description
There was an error in the file apps/pages/results/results.py when attempting to read from the password.env file. The specific line of code causing the issue was:
This fix resolves the hardcoded file path and potential issues with file accessibility or format.
Changes
Desktop
OS: Windows
Version: 11
Related Issues
Closes #35
Additional context
Consider adding a .gitignore file to exclude the ./scripts/results/ folder from being tracked. Additionally, update the documentation to instruct developers to add this folder to their local .gitignore to prevent accidental tracking of output files.