-
Notifications
You must be signed in to change notification settings - Fork 409
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
СB-5796 Metadata/data editor - error when changing server settings #3051
СB-5796 Metadata/data editor - error when changing server settings #3051
Conversation
} else { | ||
} else if (!connection.connected) { | ||
await this.connectionInfoResource.init({ projectId: key.projectId, connectionId: key.connectionId }); | ||
} |
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.
this is not true fix i think, because this change is hides case but not solves the problem.
I suppose that problem is that one of extra requests to inner database resources silently re-opens connection on the backend. We need to investigate this case and solve the problem properly
f4b3970
to
fc15d5d
Compare
@@ -23,10 +23,11 @@ export const ConnectionShield = observer<PropsWithChildren<IConnectionShieldProp | |||
const notificationService = useService(NotificationService); | |||
|
|||
const connection = useResource(ConnectionShield, ConnectionInfoResource, connectionKey); | |||
const connecting = getComputed(() => connectionKey && connection.resource.isConnecting(connectionKey)); | |||
const connecting = getComputed(() => (connectionKey && connection.resource.isConnecting(connectionKey)) || connection.loading); | |||
const isConnectionReady = getComputed(() => !connecting && connection.data?.connected && connection.loaded && !connection.outdated); |
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.
Seems like we should implement some general solution for checking whether resource entity is fully available or not. Not now, but maybe in a tech sprint
…nging-server-settings
…nging-server-settings
…nging-server-settings
…nging-server-settings
…nging-server-settings
…nging-server-settings
…nging-server-settings
No description provided.