-
Notifications
You must be signed in to change notification settings - Fork 204
Update DBT package version #2012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughUpdated the git revision for the dbt-data-reliability dependency in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
Comment |
|
👋 @elazarlachkar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
elementary/monitor/dbt_project/packages.yml (1)
5-5: Prefer a tag/release over a raw commit when available (optional).If a release tag exists for this SHA, consider switching to a tag for traceability and supply‑chain hygiene. Example:
- - git: https://github.com/elementary-data/dbt-data-reliability.git - revision: 0f59f9f5407db890780f225f6c1e362f38221133 + - git: https://github.com/elementary-data/dbt-data-reliability.git + tag: vX.Y.ZIf you want, I can look up whether this SHA corresponds to a released tag and suggest the exact value.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
elementary/monitor/dbt_project/packages.yml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: test / test
- GitHub Check: code-quality
🔇 Additional comments (1)
elementary/monitor/dbt_project/packages.yml (1)
5-5: LGTM on the pin — commit present; regenerate & commit lockfile
- Verified: commit 0f59f9f5407db890780f225f6c1e362f38221133 exists on the remote.
- Action: elementary/monitor/dbt_project/packages.lock not found — run (cd elementary/monitor/dbt_project && dbt deps) and commit the generated packages.lock; ensure it pins the above SHA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (1)
elementary/monitor/dbt_project/package-lock.yml (1)
5-6: Prefer regenerating the lock via dbt, not manual edits.To avoid drift and checksum mistakes, update
packages.ymland then rundbt depsto regeneratepackage-lock.yml(commit both files). Consider adding a CI check that runsdbt depsand fails if the lock changes.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
elementary/monitor/dbt_project/package-lock.yml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: test / test
- GitHub Check: code-quality
🔇 Additional comments (1)
elementary/monitor/dbt_project/package-lock.yml (1)
5-6: Verify pinned git revision and tarball SHA1packages.yml and package-lock.yml both point to revision 0f59f9f5407db890780f225f6c1e362f38221133 and package-lock lists sha1_hash 0dde8f6be0323bd473ea26bae571cef6d53d8fba. The sandbox could not download the GitHub tarball due to SSL certificate verification errors, so the sha1 could not be validated. Re-run the verification script (or download the archive for that commit locally/CI and compute the SHA‑1) and confirm the computed hash matches the lock; if it does not, regenerate package-lock.yml or update the hash.
| revision: cbabcb2c348be2b4c45ad72c3b94e7800a52a542 | ||
| sha1_hash: 90d912df8d9c6a435f1936c7d93e4bf6c0efc4dd | ||
| revision: 0f59f9f5407db890780f225f6c1e362f38221133 | ||
| sha1_hash: 0dde8f6be0323bd473ea26bae571cef6d53d8fba |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix YAML indentation for sha1_hash (breaks parsing).
sha1_hash must be nested under the same list item as git and revision. It’s currently top‑level due to missing indentation and will cause YAML parse errors / dbt to ignore the lock entry.
Apply this diff:
-sha1_hash: 0dde8f6be0323bd473ea26bae571cef6d53d8fba
+ sha1_hash: 0dde8f6be0323bd473ea26bae571cef6d53d8fba📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| sha1_hash: 0dde8f6be0323bd473ea26bae571cef6d53d8fba | |
| sha1_hash: 0dde8f6be0323bd473ea26bae571cef6d53d8fba |
🤖 Prompt for AI Agents
In elementary/monitor/dbt_project/package-lock.yml around line 6, the sha1_hash
key is incorrectly placed at top level instead of nested under the same list
item as git and revision; indent sha1_hash so it is a child of the same mapping
that contains git and revision (match the indentation level of git/revision for
that list entry) so the YAML parser and dbt will associate the hash with the
correct package entry.
null
Summary by CodeRabbit