Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion packages/cubejs-client-core/src/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -379,7 +379,7 @@ class CubeApi {
body.error = text;
}

if (body.error === 'Continue wait') {
if (body.error?.includes('Continue wait')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not do that, because potential it can be a part of error message that are not continue wait.

Copy link
Member Author

@MazterQyou MazterQyou Mar 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for this change is that we throw this Continue wait from backend-native as CubeError::internal which leads to the error having extra prefixes like External error:. I'm open to suggestions fixing the prefixes here but backend-native itself uses the same .contains method for testing continue wait so I felt like this brings them in line.

await checkMutex();
if (options?.progressCallback) {
options.progressCallback(new ProgressResult(body as ProgressResponse));
Expand Down Expand Up @@ -742,6 +742,7 @@ class CubeApi {
signal: options?.signal,
fetchTimeout: options?.timeout,
baseRequestId: options?.baseRequestId,
throwContinueWait: true,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like this, it's a breaking change, right? I believe we've agreed to let users configure this parameter by passing an explicit option, and then we'll make it true by default on the API side in the next minor. So, I believe we need to take throwContinueWait from options here—and in the React client library as well.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not a breaking change since this is a parameter passed by the client and client is designed to handle continue wait as it does with load (the same method is used behind the scenes).

};

if (options?.cache) {
Expand Down
Loading