Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Correct EXPIRATION_EPOCH expectations #478

Closed
carpawell opened this issue Dec 21, 2022 · 1 comment · Fixed by #482
Closed

Correct EXPIRATION_EPOCH expectations #478

carpawell opened this issue Dec 21, 2022 · 1 comment · Fixed by #482
Assignees
@abereziny
Labels
U0 Needs to be resolved immediately

Comments

@carpawell
Copy link
Member

It was clarified that the expiration epoch is the last epoch for any entity to be valid. See nspcc-dev/neofs-sdk-go#370 and nspcc-dev/neofs-api#253.

Related to nspcc-dev/neofs-node#2097 and nspcc-dev/neofs-node#2099. neofs-cli
flags description clarification is in progress.
@carpawell carpawell added testcases U0 Needs to be resolved immediately labels Dec 21, 2022
@carpawell
Copy link
Member Author

lifetime flags should mean the following: specified --lifetime 10, made 10 epoch ticks, got the last valid epoch for an entity.

expire-at flags should mean the following: specified --expire-at 10, wait until currEpoch == 10, got the last valid epoch for an entity.

@abereziny abereziny mentioned this issue Dec 23, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abereziny abereziny

Labels
U0 Needs to be resolved immediately
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#478 Update lock tests abereziny/neofs-testcases
2 participants
@carpawell @abereziny