Sporadic Cohort Save Issues
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
(Using WebAPI 2.14.0 / Atlas 2.14.1)
Cohort Definitions save cleanly every time.
Actual behavior
When updating a cohort definition, with even small changes like the name, we see sporadically the save gets stuck.
This is hard to pin down, as it's not consistent. We can't find anything in the WebAPI logs, nor anything in the Postgres logs. The chrome console shows the in-flight PUT command for saving the updated cohort stalls out.
Steps to reproduce behavior
- Create a cohort definition
- Make some edits
- Try to save it
- See nothing happens
Tagging @konstjar
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the cohort definition update using the listed steps, then inspect the in-flight PUT request in Chrome alongside the WebAPI and Postgres logs. Done means small cohort edits save reliably and the request no longer stalls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100