Snippets Groups Projects

This is an archived project. Repository and other project resources are read-only.

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Evaluated and written values may not correspond in FO

Noticed with the ddt2 and zero-grad FO. It is possible to select evaluate intervals and write intervals such that the value written is actually rather out of date at the time of writing. Or even set things that the FO is never evaluated, but only written. Should add extra logic to catch this.

Child items

0

Show labels

No child items are currently assigned. Use child items to break down this issue into smaller parts.

1

Activity

Mark OLESEN Changed title: Evaluated and written values may not correspond → Evaluated and written values may not correspond in FO 8 years ago

Changed title: Evaluated and written values may not correspond → Evaluated and written values may not correspond in FO
Mark OLESEN Mentioned in commit cf9000df 8 years ago

Mentioned in commit cf9000df
Andrew Heather @andy · 8 years ago

Owner

Why not add as a general solution? e.g. see MR !79 (merged)
Mark OLESEN @mark · 8 years ago

Author Maintainer

That makes even better sense, since this problem will certainly crop up more often.
Andrew Heather Mentioned in commit 0cdd0347 8 years ago

Mentioned in commit 0cdd0347
Mark OLESEN Status changed to closed 8 years ago

Status changed to closed

Please register or sign in to reply

Labels

None

Milestone

None

Due date

None

Confidentiality

Not confidential

0 Participants