Closed hpk0304 closed 1 month ago
It seems the filename containing spaces and or special characters like >
leads to these errors. Is it possible to rename the folder without killing the migrations? @ericstumper
@mattinannt Yes, it is possible. However, it is not straightforward since renaming changes the status of the migration indicating that Hasura should execute it again. Therefore it is important to mark it as executed again right after renaming it. The steps are the following ones:
hasura migrate apply --version <version> --skip-execution
Replace <version>
with the version number (i.e., the timestamp) of the migration.Generally I would follow what you said @mattinannt, that it makes more sense to only support Codespaces and Gitpod since particularly with Windows there are a lot of issues.
Describe the bug The clone process succeeded but failed checkout due to invalid path in backend.
It might be an issue of operating system: A filename
uuid/down.sql
might work well on Linux instead of Window.Expected behavior Shall you rename the file, with suggestion from Stackoverflow here https://stackoverflow.com/questions/61614004/cloning-succeded-but-checkout-failed-due-to-invalid-path-what-is-the-path-probl
Screenshots![bug](https://github.com/eduhub-org/eduhub/assets/13078617/04cb47d8-a569-48f4-a16f-32e12caf8095)
Environment (please complete the following information):
Additional context Add any other context about the problem here.