[BUG]: [BUG]: Critical Build Failures in Main Branch (Docker, Vite, and Unresolved Merge Conflicts)

[nandannikam]

Description

While setting up the repository to work on a new feature, I discovered that the main branch is currently failing to build across multiple services due to several critical bugs and unresolved Git merge conflicts. These issues prevent new contributors from successfully spinning up the project locally.

Specifically, I found and diagnosed:

1. Docker Setup: docker-compose up fails immediately due to missing GROQ_API_KEY and JWT_SECRET variables being strictly required without fallbacks in the .env.example.
2. Frontend Build: The React Dockerfile fails at npm ci due to strict peer dependency conflicts with react-i18next.
3. Frontend Vite Errors: Running npm run build crashes due to syntax errors in Footer.jsx (duplicate display keys) and Header.jsx (re-declared baseStyle and displayLabel variables).
4. Python Backend: A <<<<<<< HEAD unresolved Git merge conflict exists in requirements.txt, crashing the pip install build step.
5. Java Backend: A massive, multi-line unresolved Git merge conflict exists in SecurityConfig.java, which causes the Spring Boot compiler to throw severe syntax errors (';' expected, illegal start of expression) and completely fail the build.

Steps to Reproduce

1. Fork and clone the main branch.
2. Run cp .env.example .env.
3. Run docker-compose up -d --build.
4. Observe the cascade of build failures across the frontend, Python, and Java containers.

Expected Behavior

The main branch should build cleanly without throwing syntax errors, dependency conflicts, or exposing raw Git merge markers to the compilers.

Actual Behavior

Instead of building successfully, the process fails at multiple stages with the following errors:

1. Docker (docker-compose up): Fails immediately, throwing required variable GROQ_API_KEY is missing and required variable JWT_SECRET is missing.
2. Frontend (npm ci): Throws an ERESOLVE error due to a strict peer dependency conflict with react-i18next@17.0.8 expecting an older version of i18next.
3. Frontend (npm run build): Vite crashes throwing Duplicate key "display" in object literal in Footer.jsx and The symbol "baseStyle" has already been declared in Header.jsx.
4. Python Backend (pip install): Fails with Invalid requirement: '<<<<<<< HEAD' due to an unresolved Git merge conflict marker in requirements.txt.
5. Java Backend (mvn package): The compiler crashes throwing multiple syntax errors (';' expected, illegal start of expression) because it is trying to parse massive, unresolved Git merge conflict markers (<<<<<<< HEAD, =======) left inside SecurityConfig.java.

Browser

No response

Version

No response

Relevant Log Output

[nandannikam]

/assign

[github-actions]

Hi @nandannikam, this issue has been successfully assigned to you! 🎉

Make sure to read our Contributing Guidelines and submit your PR within the GSSoC timeframe. Happy coding! 🚀

[github-actions]

Hi @nandannikam, this issue has been unassigned due to no activity/updates for 3 days. This keeps the repository active and open for other GSSoC contributors! Feel free to request it again if you are ready to submit a PR soon.

[nandannikam]

/assign