Avoid wipeout of content on restart with opened editors #146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apupier
force-pushed
the
44-fixWipeOutOnRestart
branch
from
d800d74 to
0f17dfe
Compare
The problem is that if the catalogs are not warmed up on first requests from kaoto UI, the content is wiped out because Kaoto backend seems to not waiting for the Catalog to be warmed up before returning an answer and consequently it is providing an empty results as it knows nothing of the content. Not found an easy way to provide a non-regression test as it requires a restart of VS Code (but maybe we can find some alternatives, reload of workspaces/resources? the thing is that it requires the extension to be deactivated and reactivated so that the kaoto backend shut down) fixes KaotoIO#44 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
apupier
force-pushed
the
44-fixWipeOutOnRestart
branch
from
0f17dfe to
877f0c1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem is that if the catalogs are not warmed up on first requests from kaoto UI, the content is wiped out because Kaoto backend seems to not waiting for the Catalog to be warmed up before returning an answer and consequently it is providing an empty results as it knows nothing of the content.
Not found an easy way to provide a non-regression test as it requires a restart of VS Code (but maybe we can find some alternatives, reload of workspaces/resources? the thing is that it requires the extension to be deactivated and reactivated so that the kaoto backend shut down) reported #147 - In fact, by side effect, in case of regression it fails because it will cause curren tUi tests to fail with a timeout. It will be the case if they stay with a timeout which is lower than the tiemout used waiting for the warmed up of the Kaoto backend
fixes #144