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

RAS-1228: Bug: Party service workers getting 139 SIGSEGV errors and restarting #433

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

SteveScorfield
Copy link
Contributor

@SteveScorfield SteveScorfield commented Sep 10, 2024

What and why?

There have been a lot of 139 SIGSEGV errors and restarting by the service. The main culprit appears to be the way the calls are being handled and data retrieval of the associations. Due to the complexity of the interconnections between the services, it wasn't possible to separate the calls to associations. There needs to be further investigation into what services are calling the endpoints and whether they actually need the associations.

This code change extracts out the various data dictionaries used by the business and party into one unified dictionary.

A new endpoint has been added that when called will only not bring back associations. I think this is the way to goto to help minimise the amount of calls being made.

How to test?

  1. Run unit tests
  2. Deploy this along with RAS-1228: Bug: Party service workers getting 139 SIGSEGV errors and restarting response-operations-ui#963 to your dev space
  3. Run acceptance tests
  4. Run checks to ensure that a CE can be created and linked to a business, that all related information is pulled for a business in from the reporting unit page (via the reporting search page), that the respondent data is being pulled correctly, messages can be sent and read correctly in rOps
  5. In Frontstage, just a general regression check to check everything is working correctly.

Jira

https://jira.ons.gov.uk/browse/RAS-1228

@SteveScorfield
Copy link
Contributor Author

/deploy scorfs

@ras-rm-pr-bot
Copy link
Collaborator

Deploying to dev cluster with following parameters:

  • namespace: scorfs

  • tag: pr-433

  • configBranch: main

  • paramKey: ``

  • paramValue: ``

@SteveScorfield
Copy link
Contributor Author

/deploy scorfs

@ras-rm-pr-bot
Copy link
Collaborator

Deploying to dev cluster with following parameters:

  • namespace: scorfs

  • tag: pr-433

  • configBranch: main

  • paramKey: ``

  • paramValue: ``

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I like the naming of this. But I couldn't think what would be a good name for this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to the retrieval of the enrolment DTO, I had to extract these functions out of the unified_business_party_functions.py

@@ -79,6 +79,13 @@ def get_business_by_ref(ref):
return jsonify(business)


@business_view.route("/businesses/ref/reporting-unit-only/<ref>", methods=["GET"])
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not keen on the naming of this endpoint. Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants