Skip to main content

Issues Encountered

Things we tried that didn't work and why​

Issues faced by Deven​

  • Issue with React and Django
    • Deven had created a dummy endpoint to generate fake data
    • No problem was faced while creating the API and using it from the backend at localhost:8000/riverbasin/fake_data
    • However, things got complicated when the API call was made from the React frontend
    • In the API call on the frontend, the url put in was
      const url = "/riverbasin/fake_data";
    • And the frontend server would try to reroute it to http://localhost:3000/login/?next=/riverbasin/fake_data"
    • It was trying to authenticate the request first and then fetch the data.
    • After going over a lot of links and cloning the repo again and trying other things, the issue was resolved by adding a trailing forward slash.
      const url = "/riverbasin/fake_data/";

Issues faced by Jake​

Issues faced by Melissa​

  • Upon pulling changes from various commits made by Deven, the frontend on Melissa's system does not show the graphs from the fake_data API in the Django backend.
  • Errors in the console show, API Gateway (504) Timeout and
    [HPM] Error occurred while proxying request localhost:3000/riverbasin/fake_data/ to http://localhost:8000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
    [HPM] Error occurred while proxying request localhost:3000/riverbasin/fake_data/ to http://localhost:8000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
    [HPM] Error occurred while proxying request localhost:3000/riverbasin/fake_data/ to http://localhost:8000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
    [HPM] Error occurred while proxying request localhost:3000/riverbasin/riverflows/ to http://localhost:8000/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
Last updated on by Deven, Jake