-
Notifications
You must be signed in to change notification settings - Fork 19
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
gosh_profile errors on startup of substrate #71
Comments
Further investigation results: I added the following blocks to the reflect-config.json to make some things work:
This way the error with |
The issue about the
In the substrate version the resolve seems to be not resolved correctly for whatever reason (I wonder why it works as resolve takes a Bundle[] argument and motd is a simple file). I changed this to
which makes an assumption on the location of the motd file. Maybe this can be done in a more elegant way, but my Gogo shell scripting knowledge is not that experienced. Anyhow, it doesn't seem to be an issue in Atomos, maybe interesting for the examples to add the handling of the exit command etc. I'll leave it to the Atomos team if the ticket should be closed or not, dependent on the decision if it is important for the examples. |
Perhaps open an issue against |
If I try to configure a custom gosh_profile and motd with the created substrate I get the following error:
With the Atomos substrate examples the error looks a bit different, but almost the same:
Somehow the
gosh_profile
execution does not work correctly.I tried several things to make it work, but I don't get the point what is missing in the reflection configuration. Even using the java_agent and inspecting the resulting configs did not uncover anything related to this specific thing. Any ideas what could be missing?
The text was updated successfully, but these errors were encountered: