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

Bug Report: Flickering screen when port localhost:4000/graphql is not found #2771

Open
VanshikaSabharwal opened this issue Dec 18, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@VanshikaSabharwal
Copy link

Describe the bug
When starting the talawa-admin application, the screen begins to flicker if the GraphQL API endpoint (localhost:4000/graphql) is not reachable.

To Reproduce
Steps to reproduce the behavior:

  1. Start talawa-api using docker
  2. Start talawa-admin
  3. The screen will start flickering if localhost:4000/graphql is not found
  4. Logs shows the error.
    Error logs: - Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:4000/graphql/. (Reason: CORS request did not succeed). Status code: (null)

Expected behavior

  • The screen should not flicker when the API endpoint is unreachable.
  • Instead, a clear error message should be displayed to the user indicating that the GraphQL endpoint is down or inaccessible.

Actual behavior
-The screen flickers continuously when the API endpoint (localhost:4000/graphql) is not found.
-Logs indicate a CORS request failure with no clear status code.

Screenshots

WhatsApp.Video.2024-12-18.at.15.23.17.mp4

Additional details

  • The issue occurs when the talawa-api backend is not up or misconfigured.
  • This results in talawa-admin failing to fetch the GraphQL endpoint, leading to flickering.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@VanshikaSabharwal VanshikaSabharwal added the bug Something isn't working label Dec 18, 2024
@github-actions github-actions bot added the unapproved Unapproved for Pull Request label Dec 18, 2024
@VanshikaSabharwal
Copy link
Author

@palisadoes can i work on this issue.

@Coolsheru2526
Copy link

@palisadoes can i work on this issue

@dhanagopu
Copy link

@VanshikaSabharwal Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. You have reached your limit, please wait until your existing issues are closed before requesting more issues.

@dhanagopu dhanagopu removed the unapproved Unapproved for Pull Request label Dec 19, 2024
@akshayw1
Copy link

@dhanagopu Can In work on the issue

@Cioppolo14
Copy link
Contributor

@akshayw1 If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

@Coolsheru2526
Copy link

@Cioppolo14 I am facing issue with the docker installation to replicate the issue and start working on it
Screenshot (606)
Screenshot (607)
Screenshot (608)
Screenshot (615)

@Aad1tya27
Copy link

Shouldn't this issue be in Talawa-Admin repo? It might just fix by clearing local storage before navigating to login screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants