Updating D2297: add CNAME graph -> granet
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 18 2019
- add tests for parameter validation
- client.py: renamse check_status -> raise_for_status
- test_api_client: check HTTP status codes for bad requests
- test_api_client.py: do not test /walk parameter validation
- add /last sub-endpoint to only return destination in walks
- REST API doc: document /last for all applicable methods
- add /last sub-endpoint to only return destination in walks
- REST API doc: document /last for all applicable methods
- add tests for parameter validation
- client.py: renamse check_status -> raise_for_status
- test_api_client: check HTTP status codes for bad requests
merged in rDCOREd0e2f59a56bb
Nov 16 2019
- add /last sub-endpoint to only return destination in walks
- REST API doc: document /last for all applicable methods
- REST API doc: document /last for all applicable methods
this has been merged into master with commit 9cece1f6722ce836cec9353b928bb4bb4b7b77e6
this has been merged into master in commit 40daed1eaa06da82afd14652200b903c807c34ae
upon review, /last only makes sense for /walk and /randomwalk endpoints, for other endpoints it doesn't, as it will return arbitrary results (e.g., what's the point of knowing the last neighbor of one node, given they're in arbitrary order?)
Nov 15 2019
In D2265#53285, @vlorentz wrote:That would be ok with me.
- client.py: renamse check_status -> raise_for_status
- test_api_client: check HTTP status codes for bad requests
- RPCClent: rename and refactor check_status (now raise_for_status)
- RPCClient: add response attribute to RemoteException
Nov 14 2019
Nov 13 2019
merged in 97e79c289aff6625ebdd9068a006c10aca28fc12
- add random walk endpoint
- random walk: include starting node into returned path
- random walk: use reservoir sampling to pick random successor
In D2265#53268, @vlorentz wrote:Could you make the tests check for the error message? (with raises(RemoteException, match='regexp'):)
Nov 12 2019
- random walk: include starting node into returned path
- random walk: use reservoir sampling to pick random successor
Another simple way to reproduce is just removing the *.jar file and running pytest on test_api_client.py.
This is not even a Java exception, but chances are fixing that case will fix at least a significant part of the general problem, if not all.
swh-graph: add random walk endpoint
Closed in f9bdeef394329857c3500f0842e72a031aa996ff
Updating D2247: REST server: support HEAD requests
Closed in cc712446e8ef1e6aa7bf23488108778d5f847897
- REST server: validate all query parameters and refactor validators
REST server: support HEAD requests
- randomwalk: do not bother randomizing singleton sets
Related T2045
REST server: add validation for PID parameters
- skeleton for random walk endpoint
- REST client: add binding for /randomwalk
- test_api_client: add test case for /randomwalk
- REST doc: update /randomwalk doc to match what is returned
- access edge stats: also count skipped edges for /randomwalk
- /randomwalk: use proper runtime errors instead of assertions
- app.py: add TODO about making RANDOM_RETRIES configurable
- app.py: refactor random v. non-random walk iteration logic
REST server: support HEAD requests
- REST API doc: update to match current aiohttp implementation
- REST API doc: document /count method variants
- REST server: set content-type to text or ndjson where appropriate
- app.py: inline MIME types, they are single use anyway