fix e2e tests

[motatoes]

• fix e2e tests
• fix-e2e-errors dynamo creation

Summary by CodeRabbit

• Chores

  • Updated the AWS S3 bucket name used in end-to-end tests for improved environment consistency.

• Bug Fixes

  • Improved error handling when creating DynamoDB tables, allowing the process to continue even if unexpected errors occur during table description.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The updates include a change to the AWS S3 bucket environment variable in a GitHub Actions workflow and a modification to error handling in the DynamoDB table creation logic. The workflow now uses a different S3 bucket for end-to-end tests, and the DynamoDB logic proceeds to table creation even if non-"table not found" errors occur during the describe operation.

Changes

Files/Groups	Change Summary
.github/workflows/cli_test_e2e.yml	Updated AWS_S3_BUCKET environment variable from digger-tests-bucket to digger-tests-bucket-e2e.
libs/locking/aws/dynamo_locking.go	Modified error handling in createTableIfNotExists to continue on describe errors except "table not found".

Poem

A bucket renamed, a workflow set,
Dynamo errors, no longer a threat.
If the table’s missing or something goes wrong,
We hop right ahead, still humming our song.
With paws on the code and ears to the ground,
Progress keeps leaping, round after round! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 386cea3 and 247b6e9.

📒 Files selected for processing (2)

• .github/workflows/cli_test_e2e.yml (1 hunks)
• libs/locking/aws/dynamo_locking.go (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Commit Unit Tests in branch fix-e2e-tests
• Post Copyable Unit Tests in Comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[greptile-apps]

PR Summary

Changes to improve E2E test reliability by modifying DynamoDB table creation and S3 bucket configuration.

• Modified error handling in libs/locking/aws/dynamo_locking.go to continue with table creation on non-TableNotFoundException errors, requiring careful monitoring
• Changed S3 bucket name from 'digger-tests-bucket' to 'digger-tests-bucket-e2e' in .github/workflows/cli_test_e2e.yml for better resource isolation

_{2 files reviewed, no comments
Edit PR Review Bot Settings | Greptile}