Skip to content

Issues: noobaa/noobaa-core

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

Clear current search query, filters, and sorts
9 Open 42 Closed
9 Open 42 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

S3 checksum support for validating object integrity S3-Compatibility S3 Compatibility and Namespace over AWS
#8487 opened Oct 29, 2024 by guymguym
List objects with unicode - should sort keys using byte-by-byte order and not using utf8 sort order S3-Compatibility S3 Compatibility and Namespace over AWS
#8218 opened Jul 21, 2024 by guymguym
1
1
S3 compatibility store and retrieve object headers Cache-Control and Content-Disposition if provided on PUT S3-Compatibility S3 Compatibility and Namespace over AWS Type:Technical Debt Known technical gaps left in the system
#8015 opened May 7, 2024 by guymguym 5.16.0
1
Presigned URL inaccessible from browser after 15 minutes S3-Compatibility S3 Compatibility and Namespace over AWS Type:Bug
#7565 opened Nov 6, 2023 by ndeahl 5.16.0
2
S3 delete object should always return success even if not exists S3-Compatibility S3 Compatibility and Namespace over AWS
#7353 opened Jun 19, 2023 by guymguym
13
technical debt: aws-chunk signature is not verified S3-Compatibility S3 Compatibility and Namespace over AWS Severity 2 Product is usable but severely limited. Task is unable to operate or caused other sw to fail Type:Technical Debt Known technical gaps left in the system
#5401 opened Apr 3, 2019 by tamireran
1
Put/Part copy return values of the VersionId that was copied from Comp-Namespace Namespace buckets related S3-Compatibility S3 Compatibility and Namespace over AWS Severity 3 Usable but a task runs with minor issues/limitations Type:Technical Debt Known technical gaps left in the system
#5156 opened Oct 10, 2018 by jeniawhite
1
Race conditions in versioning marking operations of objects (query vs bulks) S3-Compatibility S3 Compatibility and Namespace over AWS Type:Technical Debt Known technical gaps left in the system
#5139 opened Oct 3, 2018 by jeniawhite
1
AWS S3 get bucket versions missing encoding-type as parameter option S3-Compatibility S3 Compatibility and Namespace over AWS Type:Technical Debt Known technical gaps left in the system
#4796 opened May 21, 2018 by jeniawhite
1
ProTip! Add no:assignee to see everything that’s not assigned.