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
I'm having a similar issue to #231, however from what I can tell I am following the requirements correctly to return a bounded response from the Logs endpoint.
Here is a snippet of my code where I am calling get_logs, same as the referenced issue the code will execute on a loop until there are no more results from the log. I am specifying both since and until in the log query. The results returned are correct, but resp always returns has_next as True, even after reaching the end of available logs.
@cleavenworth, this was super helpful to me building a log call. Can you share what you mean by your user error comment, I'm fairly inexperience with coding and would love to see what it looks like after you discovered the issue to help understand it.
I'm having a similar issue to #231, however from what I can tell I am following the requirements correctly to return a bounded response from the Logs endpoint.
Here is a snippet of my code where I am calling
get_logs
, same as the referenced issue the code will execute on a loop until there are no more results from the log. I am specifying bothsince
anduntil
in the log query. The results returned are correct, butresp
always returnshas_next
as True, even after reaching the end of available logs.The text was updated successfully, but these errors were encountered: