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.

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

Date bug with secrets #10

Closed
NikoTurunen opened this issue Aug 9, 2022 · 1 comment · Fixed by #11
Closed

Date bug with secrets #10

NikoTurunen opened this issue Aug 9, 2022 · 1 comment · Fixed by #11
Assignees
Labels
bug Something isn't working

Comments

@NikoTurunen
Copy link

There might be a bug on "date counting/TTL" for the secrets.

I've run Blurby in container for 6 days. I tested it right after the deploy and it worked perfectly. But now since blurby's container has run for 6 days, all new secrets get wrong date created and they wont work once linked forward since the TTL time is already gone.

Its 09/08/2022 15:25 and I just created new secret. When I open the secret and check its "Message will be kept untill" it shows "2022-08-05 13:22:21.199181" which was 4 days ago.

@joniturunen joniturunen self-assigned this Aug 9, 2022
@joniturunen joniturunen added the bug Something isn't working label Aug 9, 2022
@joniturunen
Copy link
Owner

Thanks for submitting! SQL schema received a function result rather than the function itself. Therefore default timestamp values were generated the same. Fix coming up soon.

@joniturunen joniturunen linked a pull request Aug 9, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants