after this update, it seems all ghost fills on the weather market have disappeared. I’m really happy about that.
after this update, it seems all ghost fills on the weather market have disappeared. I’m really happy about that.
该用户的聊天记录定位。
after this update, it seems all ghost fills on the weather market have disappeared. I’m really happy about that.
after this update, it seems all ghost fills on the weather market have disappeared. I’m really happy about that.
thx
thx
HTTP 422 on deep pagination of GET /events Paging GET /events?closed=false&active=true&limit=100&offset=N works until offset≈2100, then returns HTTP 422 for everything beyond. totalResults is ~5000–8000, so I can only reach the first ~2000. Tested: the 422 depends purely on offset depth — happens at offset≥2100 regardless of params (no params, single param, full filter set all 422). So it's an offset ceiling, not a bad param. Q: Is this an intended deep-pagination limit? What's the recommended way to fetch the full result set? (Tried /events/keyset but the next_cursor doesn't advance correctly.) Thanks!
HTTP 422 on deep pagination of GET /events Paging GET /events?closed=false&active=true&limit=100&offset=N works until offset≈2100, then returns HTTP 422 for everything beyond. totalResults is ~5000–8000, so I can only reach the first ~2000. Tested: the 422 depends purely on offset depth — happens at offset≥2100 regardless of params (no params, single param, full filter set all 422). So it's an offset ceiling, not a bad param. Q: Is this an intended deep-pagination limit? What's the recommended way to fetch the full result set? (Tried /events/keyset but the next_cursor doesn't advance correctly.) Thanks!
HTTP 422 on deep pagination of GET /events Paging GET /events?closed=false&active=true&limit=100&offset=N works until offset≈2100, then returns HTTP 422 for everything beyond. totalResults is ~5000–8000, so I can only reach the first ~2000. Tested: the 422 depends purely on offset depth — happens at offset≥2100 regardless of params (no params, single param, full filter set all 422). So it's an offset ceiling, not a bad param. Q: Is this an intended deep-pagination limit? What's the recommended way to fetch the full result set? (Tried /events/keyset but the next_cursor doesn't advance correctly.) Thanks!
HTTP 422 on deep pagination of GET /events Paging GET /events?closed=false&active=true&limit=100&offset=N works until offset≈2100, then returns HTTP 422 for everything beyond. totalResults is ~5000–8000, so I can only reach the first ~2000. Tested: the 422 depends purely on offset depth — happens at offset≥2100 regardless of params (no params, single param, full filter set all 422). So it's an offset ceiling, not a bad param. Q: Is this an intended deep-pagination limit? What's the recommended way to fetch the full result set? (Tried /events/keyset but the next_cursor doesn't advance correctly.) Thanks!