RHOAIENG-84556: Updating Elyra to 4.3.3

[jesuino]

Updating Elyra to 4.3.3, which includes a fix to the error from PR: github.com//pull/2718

[github-actions]

@jesuino — This PR is from a fork.
The build-rhoai CI job was skipped because subscription
builds (RHEL, AIPCC) need secrets unavailable to forks.
ODH builds and code quality checks still ran.

Recommended: Push your branch to the main repo for full CI:

git remote add upstream https://github.com/red-hat-data-services/notebooks.git
git push upstream HEAD:jesuino/your-branch-name

Then open a new PR from that branch.

No push access? A maintainer will cherry-pick and test your changes.

See CONTRIBUTING.md for details.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

---

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.}

[mtchoum1]

Everything looks good. Just rebase, then merge.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mtchoum1
Once this PR has been reviewed and has the lgtm label, please assign atheo89 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jesuino]

@mtchoum1 I will close this because it seems that Elyra was updated on Jiri's PR --> #2760

Thanks!

[jiridanek]

@coderabbitai rebate this pr

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@jiridanek, do you mean rebase PR #2767?

A rebase rewrites the PR branch history. Please confirm that you want this operation.

---

🧠 Learnings used

Learnt from: jiridanek
Repo: red-hat-data-services/notebooks PR: 0
File: :0-0
Timestamp: 2026-08-14T06:52:53.990Z
Learning: In the `red-hat-data-services/notebooks` repository, RHOAI Pulp package indexes can expose different `requests` versions by runtime flavor. For Elyra dependency installation that uses the base image `PIP_INDEX_URL`, use the compatible range `requests>=2.32.5,<2.35`: RHOAI 3.4 CUDA and ROCm indexes lack `2.34.2`, while the reported 3.5-EA2 CUDA test index lacks `2.33.0` and `2.33.1`; `2.32.5` is available in both.

_{You are interacting with an AI system.}

[jiridanek]

@coderabbitai confirmed, rebase this pr

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@jiridanek, I cannot perform a rebase from this interface.

Rebase the PR branch locally, then force-push the rewritten history:

git fetch origin
git rebase origin/main
git push --force-with-lease

_{You are interacting with an AI system.}

[jiridanek]

@coderabbitai rebase

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@jiridanek I cannot rebase pull request #2767 from this interface.

Rebase the branch locally and force-push the rewritten history:

git fetch origin
git checkout <pr-branch>
git rebase origin/main
git push --force-with-lease origin <pr-branch>

_{You are interacting with an AI system.}

[jiridanek]

@coderabbitai help

[coderabbitai]

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

CodeRabbit commands

These commands are invoked using PR/Issue 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 review --preview-config to test the unmerged CodeRabbit configuration on a draft PR. The requester must have repository write access; preview results are non-authoritative.
• @coderabbitai rate limit to show your current review rate limit status.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai evaluate custom pre-merge check --instructions <custom-checks-instructions> --name <custom-checks-title> [--mode <error|warning>] to validate the custom pre-merge checks instructions. Defaults to error when --mode is omitted.
• @coderabbitai ignore pre-merge checks to override pre-merge checks and get an approval on PR.
• @coderabbitai run pre-merge checks to run pre-merge checks on the pull request.
• @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 generate unit tests to generate unit tests for this PR.
• @coderabbitai emit path instructions to emit generated path-specific review instructions for this repository.
• @coderabbitai resolve merge conflict to automatically resolve merge conflicts.
• @coderabbitai autofix to automatically fix issues identified in unresolved review comments.
• @coderabbitai fix-ci to automatically fix failing CI checks in a stacked pull request.
• @coderabbitai fix-ci commit to automatically fix failing CI checks by committing fixes to the current branch.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai generate configuration to create a PR that adds the current resolved configuration as .coderabbit.yaml (or show it if already present).
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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.

Status, support, documentation and community

• Visit our status page to check the current availability of CodeRabbit.
• Create a ticket on our support page for assistance with any issues or questions.
• Visit our documentation site for detailed information on how to use CodeRabbit.
• Join our Discord community to connect with other users and get help from the community.
• Follow us on X/Twitter for updates and announcements.

[jiridanek]

@coderabbitai resolve merge conflict

[coderabbitai]

❌ An unexpected error occurred while resolving merge conflicts:

Invalid tree info - https://docs.github.com/rest/git/trees#create-a-tree