-
Notifications
You must be signed in to change notification settings - Fork 27
Sometimes API returns erroneously empty list of edges #87
Comments
Note that repeated (the same) requests return the same erroneous result. Neither docker-compose restart server nor restarting |
Also note in the past I had many "not enough disk space" errors inside the Maybe these "not enough space" in the past caused this bug in the present? Should I delete the data and start syncing the DB anew? |
Oh, it should be |
I reopen the bug: I read several HTML files "in chain" passing the cursor value from the previous query to the next query. And it produces a list of just three files, despite I have many. This seems to happen only from time to time. It is a serious bug. I do the following three requests in order, with no request (at least if no hacker intervened) in-between. Note that I changed the spacing below. query {
transactions(
first: 1,
tags: [{
name: "Content-Type",
values: ["text/html"]
}]
) {
edges {
cursor
node {
id
owner {
address
}
tags {
name
value
}
}
}
}
}
query {
transactions(
after: "WyIyMDIxLTA3LTAyVDA1OjQxOjAzLjgzOFoiLDJd"
first: 1,
tags: [{
name: "Content-Type",
values: ["text/html"]
}]
) {
edges {
cursor
node {
id
owner {
address
}
tags {
name
value
}
}
}
}
}
|
Sometimes request
is responded with erroneous
"edges": []
This seems completely random when edges are erroneously reported empty.
docker-compose
did not crash during this bug happening.gateway
commitf6d5d370806b8efe808218ccbcf3f4592afc25e9
.The text was updated successfully, but these errors were encountered: