Flaky test: `ReplicationWriteQuotaTest.updateWriteQuota()`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
```
ReplicationWriteQuotaTest > updateWriteQuota() FAILED
org.opentest4j.AssertionFailedError:
expected: 200 OK
but was : 500 Internal Server Error
at sun.reflect.GeneratedConstructorAccessor88.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at com.linecorp.centraldogma.it.ReplicationWriteQuotaTest.getSessionId(ReplicationWriteQuotaTest.java:145)
at com.linecorp.centraldogma.it.ReplicationWriteQuotaTest.setUp(ReplicationWriteQuotaTest.java:90)
```
Contributor guide
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 running ReplicationWriteQuotaTest.updateWriteQuota() and read its setup and getSessionId() calls at ReplicationWriteQuotaTest.java lines 90 and 145. Trace the failed HTTP response and replication write-quota path, then confirm the test consistently receives 200 OK instead of 500 Internal Server Error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100