Closed fm3 closed 2 weeks ago
[!WARNING]
Rate limit exceeded
@fm3 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 18 seconds before requesting another review.
⌛ How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.🚦 How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.📥 Commits
Files that changed from the base of the PR and between 2c84cfc4058370cfb00ee1fe96e05defbd7b0822 and a98589c5d82023fab6760ef039618166a317cb1f.
The changes primarily enhance the test cases in DataVaultTestSuite.scala
for various data vault implementations, particularly focusing on handling non-existent objects with unique identifiers. The S3DataVault.scala
file introduces a new private method, notFoundToFailure
, which modifies error handling for object retrieval operations, providing a more generalized failure response. These updates aim to improve robustness and clarity in the test suite and error handling logic.
File Path | Change Summary |
---|---|
test/backend/DataVaultTestSuite.scala | Enhanced test cases for Google Cloud Storage Vault and S3 Data Vault, including UUID usage for non-existent objects and updated assertions. |
webknossos-datastore/app/com/scalableminds/webknossos/datastore/datavault/S3DataVault.scala | Added private method notFoundToFailure for improved error handling in getObjectSummaries , replacing notFoundToEmpty . |
In the vaults where data hides,
With UUIDs, our test case glides.
No more empty boxes, just clear calls,
For non-existent treasures, we’ll stand tall!
With failures caught and clarity bright,
Our tests now dance in the soft moonlight. 🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Looks like someone created
s3://non-existing-bucket
. We shouldn’t rely on that really not existing. I now add a UUID to the request paths where we want to test stuff not existing.I also changed that directory listing for a non-existing bucket is supposed to return Failure, not Empty. This was inconsistent between DataVaults.
I noticed that there are other combinations that we are not currently testing, and considered adding them here, but let’s instead get this in master asap, as it currently blocks the CI of all branches.
Steps to test:
Summary by CodeRabbit
New Features
Bug Fixes
Tests