You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on windows (.net legacy projects, sigh) and have a shared module between my server and client using the path option. The build tool generates a ./pubspec_overrides.yaml using '' in the path.
'' is the platform separator so I suspect this is coming from code that is trying to be platform independent. The problem is this breaks the docker build as a path with \ is not a valid Linux path.
I'm thinking this could be an issue on mac with ':' being the system separator (I haven't tested this). Maybe we need a way to specify the target separator for the process?
I'm willing to help with this if someone could give me a place to start looking.
The text was updated successfully, but these errors were encountered:
@alestiago: All I did was run the build on a windows machine, that produces a docker file with \ used in the file paths and then when you try to use that docker file to build a Linux image things break.
Deploy : to Cloud Run you will get this error: Because server depends on shared from path which doesn't exist (could not find package shared at ".dart_frog_path_dependencies\shared"), version solving failed.
I'm on windows (.net legacy projects, sigh) and have a shared module between my server and client using the path option. The build tool generates a ./pubspec_overrides.yaml using '' in the path.
'' is the platform separator so I suspect this is coming from code that is trying to be platform independent. The problem is this breaks the docker build as a path with \ is not a valid Linux path.
I'm thinking this could be an issue on mac with ':' being the system separator (I haven't tested this). Maybe we need a way to specify the target separator for the process?
I'm willing to help with this if someone could give me a place to start looking.
The text was updated successfully, but these errors were encountered: