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

Receive JVM error retrieving status for staged child DB schema #582

Open
jrodewig opened this issue Jan 23, 2025 · 0 comments
Open

Receive JVM error retrieving status for staged child DB schema #582

jrodewig opened this issue Jan 23, 2025 · 0 comments

Comments

@jrodewig
Copy link
Contributor

jrodewig commented Jan 23, 2025

A Discord user reported that they receive the following error when retrieving the status of a staged schema for a new child database:

$ if fauna schema push --no-input --secret $FAUNA_SECRET_KEY --dir $CI_PROJECT_DIR/fauna_schema; then echo "Schema pushed succesfully."; else echo "Could not push new schema. Abandoning any staged schema."; fauna schema abandon --no-input --secret $FAUNA_SECRET_KEY --dir $CI_PROJECT_DIR/fauna_schema; exit 1; fi

Schema pushed succesfully.

$ fauna schema status --no-input --secret $FAUNA_SECRET_KEY

java.lang.IllegalStateException: Collection FalseAlarmFeeScheduleItem not found Please create a ticket at https://support.fauna.com

The error only occurs in the v4 CLI, not v3.

Related Discord thread: https://discord.com/channels/826528159389581342/1331835385176916069

@jrodewig jrodewig changed the title Receive JVM error when staging child DB schema Receive JVM error retrieving status for staged child DB schema Jan 24, 2025
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

No branches or pull requests

1 participant