feat: Sync fork

[ngudbhav]

CodeAnt-AI Description

Add Podman support, S3-backed nodestore/profiles migration, PGBouncer migration, local JS SDK hosting, and more robust installer checks

What Changed

• Installer can run with either Docker or Podman; commands, compose detection and version checks adapt to the selected engine and surface a clear error if Podman/docker is missing
• Automatically bootstraps SeaweedFS S3 buckets for nodestore and profiles, migrates existing profile files from the sentry-vroom volume to the "profiles" bucket, and applies bucket lifecycle policies
• Offers to (or automates when flagged) update sentry config files to point nodestore and profiles to S3 and to switch Postgres host to PGBouncer when a standard Postgres config is detected
• Optionally downloads and serves JS SDK bundles into the nginx volume for air-gapped environments, with an option to keep or prune previous assets
• Stronger preflight checks and safety: validates container engine + compose versions (docker vs podman), enforces minimum Bash version, checks CPU/RAM thresholds based on profile, and improves service start/wait logic and ClickHouse/Postgres upgrade flows
• Several new unit and integration test scripts exercising S3 bootstrapping, JS SDK asset setup, PGBouncer migration, multi-bucket handling, and other installer behaviors
• Multiple UX and reliability fixes: safer backup/restore/reset handling, deterministic logging, improved prompts with an APPLY_AUTOMATIC_CONFIG_UPDATES flag to avoid interactive prompts

Impact

✅ Podman installs supported (same flow as Docker)
✅ Fewer failed installs due to missing/incorrect container engine or service startup timing
✅ Local JS SDK bundles available for air-gapped or restricted environments

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Suggestion: Wrong Sentry API: captureFeedback is not a function in the Node SDK and will throw a TypeError at runtime; use the correct API captureUserFeedback and map the message field to comments. [type error]

Severity Level: Critical 🚨

- ❌ Integration test _integration-test/nodejs/user-feedback.js fails.
- ⚠️ CI job running Node integration tests will error.
- ⚠️ Developer local runs crash with TypeError.

Suggested change

	Sentry.captureFeedback({
	message: "I love your startup!",
	name: "John Doe",
	email: "john@example.com",
	Sentry.captureUserFeedback({
	name: "John Doe",
	email: "john@example.com",
	comments: "I love your startup!",

Steps of Reproduction ✅

1. Run the integration script directly: `node _integration-test/nodejs/user-feedback.js`.
The file imports Sentry at `_integration-test/nodejs/user-feedback.js:1`.

2. Execution reaches the call at `_integration-test/nodejs/user-feedback.js:3` where
`Sentry.captureFeedback({...})` is invoked.

3. At runtime Node attempts to look up `captureFeedback` on the imported Sentry object and
fails because the Node SDK does not export `captureFeedback`. Node throws `TypeError:
Sentry.captureFeedback is not a function`, with a stack trace pointing to
`_integration-test/nodejs/user-feedback.js:3`.

4. The script terminates with an uncaught exception before reaching the flush call at
`_integration-test/nodejs/user-feedback.js:11`. This is a concrete, reproducible failure
when the integration test/script is executed as-is.

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** _integration-test/nodejs/user-feedback.js
**Line:** 3:6
**Comment:**
	*Type Error: Wrong Sentry API: `captureFeedback` is not a function in the Node SDK and will throw a TypeError at runtime; use the correct API `captureUserFeedback` and map the `message` field to `comments`.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.

[codeant-ai]

Suggestion: The grep pattern uses a character class with '|' and '10' inside ([4-9|10]...), which does not implement alternation and will incorrectly match digits '1' and '0' separately (and the '|' character); this causes total_directories to be miscounted. Use extended regex alternation and proper anchors to reliably match version-like directory names. [logic error]

Severity Level: Critical 🚨

- ❌ CI unit test fails blocking merges.
- ⚠️ SDK asset verification reports incorrect counts.
- ⚠️ Release gating depends on these tests.

Suggested change

	total_directories=$(echo "$sdk_files" | grep -c '[4-9|10]\.[0-9]*\.[0-9]*$')
	total_directories=$(echo "$sdk_files" | grep -E -c '^(4|5|6|7|8|9|10)\.[0-9]+\.[0-9]+$')

Steps of Reproduction ✅

1. Run the test script directly: execute `_unit-test/js-sdk-assets-test.sh` from
repository root (script shebang is at the top of the file). The script sources
`install/setup-js-sdk-assets.sh` and then assigns `sdk_files` at line 11
(`sdk_files=$($dcr --no-deps nginx ls -lah /var/www/js-sdk/)`) and proceeds.

2. After assets are populated, the script computes `total_directories` at line 18
(`total_directories=$(echo "$sdk_files" | grep -c '[4-9|10]\.[0-9]*\.[0-9]*$')`). This
uses a character class `[4-9|10]` instead of alternation, per the code at line 18.

3. Observe result: when directory entries include names like `10.0.0` or other filenames
with digits in different columns, the character-class will match unintended characters
(`1`, `0`, or `|`) and either overcount or miscount directories; the variable
`total_directories` will not reliably equal the expected `7`.

4. The mismatch propagates to the assertion at line 20 (`test "7" ==
"$total_directories"`), causing the test to fail in CI. The improved grep with alternation
(grep -E '^(4|5|6|7|8|9|10)\...') reproduces the intended matching and fixes counts.

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** _unit-test/js-sdk-assets-test.sh
**Line:** 18:18
**Comment:**
	*Logic Error: The grep pattern uses a character class with '|' and '10' inside ([4-9|10]...), which does not implement alternation and will incorrectly match digits '1' and '0' separately (and the '|' character); this causes `total_directories` to be miscounted. Use extended regex alternation and proper anchors to reliably match version-like directory names.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.

[codeant-ai]

Suggestion: Race condition / flaky test: the script lists buckets immediately after creating them without retrying; the creation may not be visible instantly, causing intermittent failures—add a short retry loop with a timeout when collecting bucket_list. [race condition]

Severity Level: Critical 🚨

- ❌ CI test suite experiences intermittent failures.
- ⚠️ SeaweedFS bucket-tests become flaky.
- ⚠️ Developers face noisy, unreliable CI runs.

Suggested change

	bucket_list=$($s3cmd --access_key=sentry --secret_key=sentry --no-ssl --region=us-east-1 --host=localhost:8333 --host-bucket='localhost:8333/%(bucket)' ls)
	S3_ACCESS_KEY="${S3_ACCESS_KEY:-sentry}"
	S3_SECRET_KEY="${S3_SECRET_KEY:-sentry}"
	max_retries=5
	attempt=0
	bucket_list=""
	while [ $attempt -lt $max_retries ]; do
	bucket_list=$($s3cmd --access_key="$S3_ACCESS_KEY" --secret_key="$S3_SECRET_KEY" --no-ssl --region=us-east-1 --host=localhost:8333 --host-bucket='localhost:8333/%(bucket)' ls 2>/dev/null) && break
	attempt=$((attempt + 1))
	sleep 1
	done

Steps of Reproduction ✅

1. Run the script in CI: it creates buckets in the loop at lines 14-16, then immediately
lists buckets at line 19 into bucket_list.

2. If the SeaweedFS s3 endpoint or s3cmd exhibits eventual consistency or slight
propagation delay, the newly-created buckets may not appear instantly in the ls output.
The subsequent check (lines 20-25) will detect missing buckets and exit with error.

3. Reproduce by adding artificial delay to SeaweedFS or running tests under load: create
buckets (lines 14-16) then immediately run the ls command (line 19); observe intermittent
failures where grep at line 21 does not find entries and the script exits.

4. Because the script performs no retries, these timing-dependent failures manifest as
flaky CI unit-test failures. Adding a short retry loop with timeout (as proposed)
stabilizes the check and prevents transient test failures.

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** _unit-test/multiple-seaweedfs-bucket-test.sh
**Line:** 19:19
**Comment:**
	*Race Condition: Race condition / flaky test: the script lists buckets immediately after creating them without retrying; the creation may not be visible instantly, causing intermittent failures—add a short retry loop with a timeout when collecting `bucket_list`.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.

[codeant-ai]

CodeAnt AI Incremental review completed.

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI Incremental review completed.

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI Incremental review completed.

[codeant-ai]

CodeAnt AI is running Incremental review

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI Incremental review completed.