Fix: explicit opt_article relationship declaration in retail_planning_local.py#73
Merged
nikolaoszygouras-rai merged 1 commit intoMay 21, 2026
Conversation
…RAI SDK typo warning
nikolaoszygouras-rai
requested review from
jablonskidev and
somacdivad
as code owners
|
The docs preview for this pull request has been deployed to Vercel!
|
nikolaoszygouras-rai
deleted the
fix/retail-planning-explicit-opt-article-relationship
branch
2 tasks
cafzal
pushed a commit
that referenced
this pull request
May 21, 2026
* Update retail_planning README for predictive reasoner setup - Bump minimum relationalai SDK version to 1.3.1 (required for predictive reasoner) - Replace `rai init` quickstart step with instructions to edit raiconfig.yaml directly, since the SDK now prioritizes .yaml over the .toml that rai init produces - Add quickstart step with SQL commands to create the experiment database/schema in Snowflake and grant required permissions to the RAI Native App - Remove inapplicable has_time_column=True troubleshooting entry Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Bump minimum relationalai version to 1.4.1 The predictive reasoner requires relationalai >= 1.4.1. Updates both the pyproject.toml dependency and the README prerequisites line. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Install relationalai with [gnn] extra The predictive reasoner requires GNN dependencies, which are pulled in via the [gnn] extra. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Pin relationalai to ==1.4.1 and revert configure step to rai init - pyproject.toml and README now pin relationalai[gnn]==1.4.1 (exact) - Quickstart step 4 reverted to `rai init` Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Merge pull request #73 from RelationalAI/fix/retail-planning-explicit-opt-article-relationship Fix: explicit opt_article relationship declaration in retail_planning_local.py * Add ensure_change_tracking note after rai init step Tell users to add `data.ensure_change_tracking: true` to raiconfig.yaml after rai init generates it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: nikolaoszygouras-rai <nikolaos.zygouras@relational.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
ProdCapacity.opt_articlerelationship was used without being explicitlydeclared, triggering a RAI SDK "potential typo" warning (it resembles
pc_article_id).Added an explicit
model.Relationship(...)declaration before themodel.define()call to suppress the warning.No behavioral change — the code already worked correctly.