oura icon indicating copy to clipboard operation
oura copied to clipboard

Bug? Oura always 1 block behind

Open gitmachtl opened this issue 2 years ago • 4 comments

Is there an internal technical reason why oura is always 1 block behind the current one?

gitmachtl avatar Jan 14 '22 19:01 gitmachtl

Oura's terminal sink has a throttling mechanism to facilitate the reading. Otherwise, all the events from a block would appear almost simultaneously.

On big blocks with many transactions, this artificial delay might exceed the total span between block minting, giving the sensation of a lag. I believe this is the symptom you're describing.

In PR #69, we add a new arg to the watch command called throttle. This arg takes the duration (in milliseconds) to wait between each output line. Passing the value --throttle 0 would be equivalent to not having any throttling at all.

scarmuega avatar Jan 18 '22 02:01 scarmuega

hey @scarmuega , no thats not what i ment. i already have compiled a version with a throttle set to 0 :smile:

what i mean is that the output for example stopps at:

BLOCK:3247435 █ TX:-- █ BLOCK  { slot: 48131779, hash: 83a79a5a9807b48277e21bc55865007541ca949f7e0451f21ca4cef5862cb0c8, number: 3247435, body size: 40533, tx_count: 4, issuer vkey: e7c3155586042372b19c1fe0491b771bfb2eb04f24af76f3870cda983551f4e7, timestamp: 1642500976 }

but, the current and last received block on the node is actually 3247436.

when the next block 3247437 comes into the node, the oura tool shows block 3247436 in the output ...

so even if there are 2mins between blocks, the last block will never show up. only if a new one arrives, so the output is always one block below the tip of the node.

gitmachtl avatar Jan 18 '22 10:01 gitmachtl

@gitmachtl Oura is one block behind but you're always one step ahead 😉 . Nice to see that you're beta testing the features from source, it's really helpful.

I don't have a final answer on this issue just yet. Would you mind telling me which tool are you using to check the last received block? is it gLiveView?

scarmuega avatar Jan 21 '22 12:01 scarmuega

i use several tools to track the cardano nodes. but you just need a synced node and a simple check would be via the prometheus metrics interface like:

watch -n 1 "curl -s localhost:12798/metrics | grep cardano_node_metrics_blockNum_int"

gitmachtl avatar Jan 21 '22 12:01 gitmachtl