-
Notifications
You must be signed in to change notification settings - Fork 43
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
Fix empty client behavior with app-attached sandboxes #2159
Fix empty client behavior with app-attached sandboxes #2159
Conversation
48dbab0
to
c936fbf
Compare
@prbot approve |
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.
Approved 👍. @erikbern will follow-up review this.
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.
It would be great to add a test if it's easy, but either way 👍
@erikbern this is actually a bit tricky to test because in our tests, we have to explicitly provide a client. So I'm not quite sure how to test client from env behavior. Not sure if you have any suggestions. |
Previously, if a clientless app was attached to a sandbox, it would error with NoneType. This commit checks app._client to make sure it exists before using it.
c936fbf
to
bb54004
Compare
I figured it out with |
@prbot automerge |
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 required workflows are pending. Will automerge once they complete successfully. Please bear with us in this difficult time.
Describe your changes
Previously, if a clientless app was attached to a sandbox, it would error with NoneType. This commit checks app._client to make sure it exists before using it.
Backward/forward compatibility checks
Check these boxes or delete any item (or this section) if not relevant for this PR.
Note on protobuf: protobuf message changes in one place may have impact to
multiple entities (client, server, worker, database). See points above.
Changelog