Epoch/time mismatch #54

New issue

Closed

opened 2025-12-28 18:14:00 +00:00 by sami · 0 comments

sami commented

2025-12-28 18:14:00 +00:00

Owner

Originally created by @roman-khimov on GitHub (Jun 21, 2023).

Originally assigned to: @mike-petrov on GitHub.

Expected Behavior

Objects stored for the specified number of epochs which can be approximately associated with some number of hours.

Current Behavior

The dropdown counts from "12 hours (2 epochs)" to "4 days (16 epochs)", but this suggests that an epoch is six hours long, while in fact it's one hour long. This means that the object supposed to be stored for 12 hours in fact is available just for two hours.

Possible Solution

Make it:

12 epochs (hours)
24 epochs (1 day)
48 epochs (2 days)
96 epochs (4 days)

Epochs first since that's the real limit and it can deviate from wall clock time.

Steps to Reproduce (for bugs)

Push an object with "12 hours (2 epochs)" setting, in ~3 hours it's gone.

Context

33344d140e was wrong.

Your Environment

Version used: 0.5.1

Originally created by @roman-khimov on GitHub (Jun 21, 2023). Originally assigned to: @mike-petrov on GitHub. ## Expected Behavior Objects stored for the specified number of epochs which can be approximately associated with some number of hours. ## Current Behavior The dropdown counts from "12 hours (2 epochs)" to "4 days (16 epochs)", but this suggests that an epoch is six hours long, while in fact it's one hour long. This means that the object supposed to be stored for 12 hours in fact is available just for two hours. ## Possible Solution Make it: ``` 12 epochs (hours) 24 epochs (1 day) 48 epochs (2 days) 96 epochs (4 days) ``` Epochs first since that's the real limit and it can deviate from wall clock time. ## Steps to Reproduce (for bugs) Push an object with "12 hours (2 epochs)" setting, in ~3 hours it's gone. ## Context 33344d140e6d9c9e3179e5b8c02b9b6f24af6ee9 was wrong. ## Your Environment * Version used: 0.5.1