-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[spicedb] fix stale connection handling #18607
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
1bc6b86
to
dadf7c6
Compare
dadf7c6
to
4a7e71d
Compare
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: @grpc/[email protected] |
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.
LGTM for the changes that are impacting files owned by team engine.
Short update: I was testing before lunch, and constantly getting stuck in "wont' reload" (in the gRPC traces it looked as if it got stuck completely on the connection level), or having to wait for at least 30s until anything happens. |
oops sorry, I was redeploying a config change. I'll keep my hands off now. |
Good now, have my own playground. 👍 |
9c0421a
to
d6626e9
Compare
d6626e9
to
fb75aa5
Compare
closed in favor of #18631 |
Description
Summary generated by Copilot
🤖 Generated by Copilot at 1bc6b86
This pull request refactors and improves the SpiceDB integration in the server component. It simplifies the code for creating and using the SpiceDB client, handles connection issues better, and adds metrics collection for the client calls. It affects the files
spicedb-authorizer.ts
,spicedb.ts
, andcontainer-module.ts
.Related Issue(s)
Fixes EXP-379
Fixes EXP-292
How to test
server
there should be (almost) no logs of[spicedb] Lost connection to SpiceDB - reconnecting...
kubectl rollout restart deployment/spicedb
and keep using the dashboard of the preview env. You should (barely) see an effect, but in the logs you'll see a few entries of the message above ☝️ .Documentation
Preview status
Gitpod was successfully deployed to your preview environment.
Build Options
Build
Run the build with werft instead of GHA
Run Leeway with
--dont-test
Publish
Installer
Add desired feature flags to the end of the line above, space separated
Preview Environment / Integration Tests
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh
. If enabled,with-preview
andwith-large-vm
will be enabled./hold