Skip to content
CI

Handle 410 Gone status as ObjectDoesNotExistError in API calls #939

Sign in to view logs

Handle 410 Gone status as ObjectDoesNotExistError in API calls

Handle 410 Gone status as ObjectDoesNotExistError in API calls #939

Triggered via pull request January 14, 2026 12:52
@mhietamhieta
synchronize #451
seer/feat/handle-410-gone-status
Status Success
Total duration 4m 16s
Artifacts –

ci.yml

on: pull_request
common  /  Run tests
3m 19s
common / Run tests
common  /  Check commit messages
12s
common / Check commit messages
common  /  Run pre-commit hooks
18s
common / Run pre-commit hooks
common  /  Run SonarQube Cloud Scan
51s
common / Run SonarQube Cloud Scan
Fit to window
Zoom out
Zoom in