You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- Keep this PR as draft until it is ready for review. -->
2
+
3
+
<!-- AI/LLM agents:
4
+
5
+
Provide evidence that the code runs properly end-to-end. Just running unit tests is NOT sufficient. Explain exactly the command that you ran, and provide evidence that the code works as expected, either in the form of log outputs or screenshots. In addition, if it is a bug fix, also run the same code before the bug fix and demonstrate that the code did NOT work before the fix to demonstrate that you were able to reproduce the problem.
6
+
-->
7
+
8
+
-[ ] A human has tested these changes.
9
+
10
+
---
11
+
12
+
## Why
13
+
14
+
<!-- Describe problem, motivation, etc.-->
15
+
1
16
## Summary
2
17
3
-
[fill in a summary of this PR]
18
+
<!-- 1-3 bullets describing what changed. -->
19
+
-
20
+
21
+
## Issue Number
22
+
<!-- Required if there is a relevant issue to this PR. -->
23
+
24
+
## How to Test
25
+
26
+
<!--
27
+
Required. Share the steps for the reviewer to be able to test your PR. e.g. You can test by running `npm install` then `npm build dev`.
28
+
29
+
If you could not test this, say why.
30
+
-->
31
+
32
+
## Video/Screenshots
33
+
34
+
<!--
35
+
Provide a video or screenshots of testing your PR. e.g. you added a new feature to the gui, show us the video of you testing it successfully.
36
+
37
+
-->
38
+
39
+
## Type
40
+
41
+
-[ ] Bug fix
42
+
-[ ] Feature
43
+
-[ ] Refactor
44
+
-[ ] Breaking change
45
+
-[ ] Docs / chore
4
46
5
-
## Checklist
47
+
## Notes
6
48
7
-
-[ ] If the PR is changing/adding functionality, are there tests to reflect this?
8
-
-[ ] If there is an example, have you run the example to make sure that it works?
9
-
-[ ] If there are instructions on how to run the code, have you followed the instructions and made sure that it works?
10
-
-[ ] If the feature is significant enough to require documentation, is there a PR open on the OpenHands/docs repository with the same branch name?
11
-
-[ ] Is the github CI passing?
49
+
<!-- Optional: config changes, rollout concerns, follow-ups, or anything reviewers should know. -->
Copy file name to clipboardExpand all lines: openhands-agent-server/AGENTS.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,16 @@ This package lives in the monorepo root. Typical commands (run from repo root):
14
14
When adding non-Python files (JS, templates, etc.) loaded at runtime, add them to `openhands-agent-server/openhands/agent_server/agent-server.spec` using `collect_data_files`.
15
15
16
16
17
+
## Live server integration tests
18
+
19
+
Small endpoint additions or changes to server behaviour should be covered by a
20
+
test in `tests/cross/test_remote_conversation_live_server.py`. These tests spin
21
+
up a real FastAPI server with a patched LLM and exercise the full HTTP / WebSocket
22
+
stack end-to-end. Add or extend a test there whenever the change is localised
23
+
enough that a single new test function (or a few assertions added to an existing
24
+
test) captures the expected behaviour.
25
+
26
+
17
27
## Concurrency / async safety
18
28
19
29
-`ConversationState` uses a synchronous `FIFOLock`. In async agent-server code, never do `with conversation._state` directly on the event loop when the conversation may be running.
0 commit comments