backend latency issue

[coder2343]

description of the bug We have an issue as it takes 20 seconds from submitting a summary to being able to call a summary. If you submit request for a summary before waiting 20 seconds you will have an issue where you will get a 503 error as the data has not been registered as saved on the server yet.

reproduction steps

1. http://csc324spring2024.us.reclaim.cloud/sendpolicy do this api request
2. https://csc324spring2024.us.reclaim.cloud/sum do this api request without waiting 30 seconds after the last api call
3. should get a 503 error returned.

what's going on with bug now Liam is discovered the bug and is working on investigating the issue and seeing possible way to overcome the latency issue right now. Curenlty we should ensure in our front end code that we wait around 25 seconds from sending privacy policy to back end for calling for a summary.

[coder2343]

hypothesis Bug is either with code taking to long to execute or is do to network connection with server

[coder2343]

Investigation Steps

Wednesday April 24

• discover the bug when setting up with web server

Monday morning

• time the latency from sending api request 1 and api request 2 without getting a 503 error. Found the latency was around 30 seconds.

Monday afternoon

• check if code can run locally in a fast manner. Found able to do both api requests one after another without getting a 503 error. So, the code is likely to not have an error or any other optimizations to do. Their could be some changes we could make to the code to ensure it runs smoother on server but this is unknown at the time

Monday evening

• do not have a solution to make the two api calls work without the 30 second wait between them. So, suggest moving to just doing one api call to the back end. This should be feasible

Tuesday morning

• test this idea and seems like it could be a feasible solution.

[coder2343]

purposed solution

• having the api just do one request with the url of privacy policy being passed in via the request heading. Solution in testing currently

[coder2343]

Reflection

• use tools like a timer and forming hypothesis of bug's cause is helpful for being able to more accurately pinpoint the issue.
• if we can not solve bug directly see if their is another solution that can help solve it in a indirect manor.

[annhmai-hoang]

Bug Report

Description: We encounter a 503 error if a summary request is made before 20 seconds elapse from submission, due to delayed data registration on the server.

Reproduction Steps:

1. Make an API request to http://csc324spring2024.us.reclaim.cloud/sendpolicy.
2. Without waiting 30 seconds after the last API call, immediately make another API request to https://csc324spring2024.us.reclaim.cloud/sum.
3. Observe the returned response, which should be a 503 error.

Communication about Bug Status:

• 4/24: Liam discovered the bug when he set up the web server.
• 4/29 morning: Timed latency between API requests: found approximately 30-second delay.
• 4/29 afternoon: Local code execution efficient; no immediate solution for server.
• 4/29 evening: Proposed solution: execute only one API call to backend.
• 4/30: Tested solution: deemed feasible.

Team Member Involved:

• Liam: investigator, debugger.