Repository navigation
fix: clearer lookup failure reasons, more tests and upgrade notes - #125
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ➖ Normal Merge Risk: 🟡 Moderate · up to
|
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Organization UI
- Review profile: CHILL
- Plan: Advanced
- Run ID:
413010c3-a363-4558-91b8-c03d66219912
📒 Files selected for processing: 6
README.mdhaproxy_agent.pytests/unit/conftest.pytests/unit/test_bind_mounts.pytests/unit/test_payload_validation.pytests/unit/test_requests.py
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
Signed-off-by: Oleksandr Piskun <[email protected]>
cd6b7f7 to
52d34a7
Compare
Follow-ups to #123 and #124.
When an ExApp lookup failed because the Kubernetes API answered with an error, the warning from #124 only said
HTTPServiceUnavailable: Service Unavailable, and a total timeout ended inTimeoutError:with nothing after it. The warning now gives the error's text, or only its type when there is no message. If one of several requests waiting for the same lookup is cancelled, the lookup itself no longer fails withInvalidStateError.The README's upgrade notes now say that a daemon whose Docker network name is empty or has a blank, a
:or a control character is refused (a refused update leaves the ExApp without a container), and that recovering from a failed ExApp update needs the deploy options again and is not done by rolling HaRP back.New tests cover mount modes other than
roandrw(the rules and the request to Docker treat them as read-write), the length limits at their boundary and the lookup cases above. The test fixture now also clears the negative lookup cache and checks after each test that no lookup is left in flight.