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

Build Failure After Updating and Attempting to Merge Changes #5301

Open
paulo-rossy opened this issue Oct 1, 2024 · 0 comments
Open

Build Failure After Updating and Attempting to Merge Changes #5301

paulo-rossy opened this issue Oct 1, 2024 · 0 comments

Comments

@paulo-rossy
Copy link
Contributor

I recently attempted to update to the latest version and encountered a build failure during the merge process. After running the yarn build command, the build failed with the following error:

@open-condo/miniapp-utils#build: command (/app/packages/miniapp-utils) /tmp/xfs-25ee4603/yarn run build exited (1)
Tasks: 3 successful, 6 total
Cached: 0 cached, 6 total
Time: 1m52.803s
Failed: @open-condo/miniapp-utils#build

ERROR run failed: command exited (1)

It seems to be related to the @open-condo/miniapp-utils package, specifically an issue with an ArrayIterator type not being recognized correctly, as seen in this part of the error:

@open-condo/miniapp-utils:build: Type 'IterableIterator<[number, number]>' is missing the following properties from type 'ArrayIterator<[number, number]>': map, filter, take, drop, and 9 more.

Additionally, there was a Docker build failure at this point:

Dockerfile:64

RUN set -ex \
    && yarn build \
    && rm -rf /app/out \
    && rm -rf /app/.env  \
    && rm -rf /app/.config /app/.cache /app/.docker  \
    && ls -lah /app/

The full error message:

ERROR: process "/bin/sh -c set -ex     && yarn build     && rm -rf /app/out     && rm -rf /app/.env      && rm -rf /app/.config /app/.cache /app/.docker      && ls -lah /app/" did not complete successfully: exit code: 1

Is there any known issue with the @open-condo/miniapp-utils package, or could it be related to a type mismatch in the iterator? Any guidance on resolving this would be greatly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant