Skip to content
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

Merged

Conversation

sergeyteleshev
Copy link
Contributor

No description provided.

@sergeyteleshev sergeyteleshev self-assigned this Nov 6, 2024
Comment on lines 107 to 109
} else {
} else if (!connection.connected) {
await this.connectionInfoResource.init({ projectId: key.projectId, connectionId: key.connectionId });
}
Copy link
Member

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

@sergeyteleshev sergeyteleshev requested a review from Wroud November 6, 2024 18:35
@sergeyteleshev sergeyteleshev force-pushed the CB-5796-metadata-data-editor-error-when-changing-server-settings branch from f4b3970 to fc15d5d Compare November 8, 2024 14:29
@@ -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);
Copy link
Member

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

@Wroud Wroud merged commit 4323578 into devel Nov 20, 2024
5 of 7 checks passed
@Wroud Wroud deleted the CB-5796-metadata-data-editor-error-when-changing-server-settings branch November 20, 2024 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants