-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Test for go-ipfs-cmds#282 and boxo#855 #10738
Test for go-ipfs-cmds#282 and boxo#855 #10738
Conversation
Signed-off-by: Abhinav Prakash <[email protected]>
hi @lidel I noticed the the tests in Logs (w/o my changes)
Logs (with my changes)
Well there is no difference in Errors (if that's what we want to prove) |
My initial file limit was I even cleared all the processes that might be holding open files. |
|
This is a companion PR for ipfs/boxo#855 and ipfs/go-ipfs-cmds#282 that adds an HTTP RPC test for content blocking functionality.
addresses: ipfs/boxo#855 (review)
Description
[WIP] This PR adds a new test case in test/cli/content_blocking_test.go to verify that content blocking works correctly over the HTTP API. The test ensures that:
Blocked content returns the expected HTTP status code (410 Gone)
The response body contains the appropriate error message
[WIP] This demonstrates that the new error handling implemented in the companion PRs (replacing string-based checks with proper error types) maintains compatibility with existing functionality while providing a cleaner approach for future development.
The test directly verifies the HTTP response code, which is critical for ensuring our APIs behave as expected when content is blocked.