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

[Tenable Vuln Management] : Inconsistent "pagination" presence in API response should be handled gracefully #3544

Closed
flavienSindou opened this issue Mar 3, 2025 · 0 comments · Fixed by #3546
Closed

[Tenable Vuln Management] : Inconsistent "pagination" presence in API response should be handled gracefully #3544

flavienSindou opened this issue Mar 3, 2025 · 0 comments · Fixed by #3546
Assignees
@flavienSindou
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.5.4

Comments

@flavienSindou
Copy link
Contributor

No description provided.

@flavienSindou flavienSindou self-assigned this Mar 3, 2025
@flavienSindou flavienSindou added bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. labels Mar 3, 2025
@flavienSindou flavienSindou linked a pull request Mar 3, 2025 that will close this issue
[Tenable Vuln Management] fix: inconsistent pagination section presence in response api should be handled gracefully #3546
Merged
4 tasks
@flavienSindou flavienSindou mentioned this issue Mar 3, 2025
Merged
4 tasks
flavienSindou added a commit that referenced this issue Mar 4, 2025
@flavienSindou
[Tenable Vuln Management] fix: inconsistent pagination section presen…
2783e56 
…ce in response api should be handled gracefully (#3544)
@flavienSindou flavienSindou added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 4, 2025
@flavienSindou flavienSindou added this to the Release 6.5.4 milestone Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flavienSindou flavienSindou

Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.5.4
1 participant
@flavienSindou