update subm:eloqstore creates oss bucket if not exist

[thweetkomputer]

Here are some reminders before you submit the pull request

• Add tests for the change
• Document changes
• Reference the link of issue using fixes eloqdb/tx_service#issue_id
• Reference the link of RFC if exists
• Pass ./mtr --suite=mono_main,mono_multi,mono_basic

Summary by CodeRabbit

• Chores
  • Updated internal dependency reference to the latest version.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The submodule pointer for store_handler/eloq_data_store_service/eloqstore is updated to reference a new commit hash (from b1e1d9b to fcf5381d). No code modifications or behavioral changes are introduced.

Changes

Cohort / File(s)	Change Summary
Submodule Update store_handler/eloq_data_store_service/eloqstore	Submodule commit reference updated (new revision tracking)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• add submodule eloqstore #349: Also modifies the same submodule reference at store_handler/eloq_data_store_service/eloqstore.

Suggested reviewers

• xiexiaoy
• zhangh43

Poem

🐰 A tiny hop through git's domain,
One pointer changed, the rest remains,
A submodule's breath so fresh and new,
Updated refs for me and you! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only the template checklist with no actual content about the changes, objectives, or rationale.	Add substantive description of the changes made, the problem being solved, and why this update is necessary. Fill in the checklist items appropriately.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title correctly identifies the main change: updating the eloqstore submodule to add OSS bucket creation functionality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch create-bucket-eloqstore

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a43c2d2 and c46c9d3.

📒 Files selected for processing (1)

• store_handler/eloq_data_store_service/eloqstore

🔇 Additional comments (1)

store_handler/eloq_data_store_service/eloqstore (1)

1-1: Verify submodule implementation and complete PR checklist items.

The submodule pointer is updated to commit fcf5381d, introducing changes to bucket creation logic. Since submodule contents cannot be inspected directly from this PR, manual verification of the following is required:

• Correctness: Verify the OSS bucket creation logic handles race conditions, idempotency, and concurrent access properly
• Error handling: Confirm proper handling of permission failures, quota limits, and network errors
• Testing: Ensure test coverage exists for the new bucket creation functionality
• Security: Review bucket permissions, access controls, and encryption settings
• Documentation: Verify configuration requirements and operational considerations are documented

Additionally, the following PR checklist items remain unchecked and must be completed:

• Tests for the bucket creation feature
• Documentation of any new configuration requirements
• Issue reference linking to the feature request or bug fix
• Test suite execution (./mtr --suite=mono_main,mono_multi,mono_basic)

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}