chore: DO NOT MERGE - source-shopify with CDK dev 7.17.3.post4.dev24792917452 (memory monitor test)#76915
Conversation
…92917452 (memory monitor test) Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
/publish-connectors-prerelease
|
|
Deploy preview for airbyte-docs ready!
Deployed with vercel-action |
|
|
approve |
This PR pins
source-shopifyto a dev/prerelease build ofairbyte-cdkfor validation purposes only. It is not intended for release. The dev CDK version will be yanked from PyPI once testing concludes.What
Bumps
source-shopifyfromairbyte-cdk = "^7"(currently resolving to7.17.0) to the exact prerelease pinairbyte-cdk = "7.17.3.post4.dev24792917452", which contains the memory-monitor threshold + formatting + instantiation-log changes from airbytehq/airbyte-python-cdk#995.Used to validate the CDK changes against a real connector before the CDK PR is merged and a proper release is cut.
How
pyproject.toml: pinairbyte-cdkto7.17.3.post4.dev24792917452; bump connector version3.3.0→3.3.1poetry.lock: regenerated viapoetry lock --no-updatemetadata.yaml: bumpdockerImageTag3.3.0→3.3.1docs/integrations/sources/shopify.md: changelog entry for3.3.1(PR link isTODO; will not be filled since this PR is not meant to merge)Review guide
airbyte-integrations/connectors/source-shopify/pyproject.tomlairbyte-integrations/connectors/source-shopify/poetry.lockairbyte-integrations/connectors/source-shopify/metadata.yamldocs/integrations/sources/shopify.mdUser Impact
None — this PR will not be merged. Its only purpose is to exercise the new memory-monitor fail-fast thresholds (
_CRITICAL_THRESHOLD0.98 → 0.95,_HIGH_PRESSURE_THRESHOLD0.95 → 0.90), humanized error byte formatting, and one-shotMemoryMonitor instantiated with critical threshold: …INFO log in a real connector context.Can this PR be safely reverted and rolled back?
Related
airbyte-cdk==7.17.3.post4.dev24792917452(publish run https://github.com/airbytehq/airbyte-python-cdk/actions/runs/24740803773)Link to Devin session: https://app.devin.ai/sessions/738dba1a2a1a4c15998cb1dd5d0cd487