-
Notifications
You must be signed in to change notification settings - Fork 492
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
Add recursive directory watch #488
Conversation
🦋 Changeset detectedLatest commit: 13f0c78 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Overall this looks good from a code perspective 👍
From a product perspective, do you think it would be better not to make recursive
an option and just always watch recursively ? Also taking into account that the instructions said:
Make as few changes to the communication between envd and SDKs as possible
666b3d4
to
724e857
Compare
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.
The envd version check is missing in Python SDK
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.
Some last polishing, I will merge after we merge the envd part
I think the envd part is already merged, right? |
looks like it e2b-dev/infra#233 |
- Removed code runtime version check to prevent issues until further investigation
f4369e1
to
8c52e73
Compare
Adds recursive directory watch to the SDK and documentation section. Requires merging and deploying e2b-dev/infra#210 first.
Proposed API change:
JS
Python
Notes
Python SDK was generated using buf.build/protocolbuffers/python:v28.3. The runtime check was removed for now. Further tests might be required to make sure the runtime is at least the generated version before including the runtime check.
Changing the following in the file spec/envd/buf-python.gen.yaml (generator) allows using different protoc-gen-python version:
From:
plugin: python
To:
plugin: buf.build/protocolbuffers/python:v28.3