Skip to content

fix: Always set last pods check timestamp#173

Merged
bpetit merged 1 commit intohubblo-org:devfrom
rossf7:fix/set-pods-last-check
Jun 15, 2022
Merged

fix: Always set last pods check timestamp#173
bpetit merged 1 commit intohubblo-org:devfrom
rossf7:fix/set-pods-last-check

Conversation

@rossf7
Copy link
Copy Markdown
Contributor

@rossf7 rossf7 commented May 13, 2022

Towards #166

If fetching the pods metadata fails pods_last_check is not set. This causes an error when checking whether to fetch the metadata again.

thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: Empty }', src/exporters/mod.rs:653:77
stack backtrace:

@bpetit bpetit merged commit a7ccdc2 into hubblo-org:dev Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Previous releases

Development

Successfully merging this pull request may close these issues.

2 participants