error to read app.toml

[tac0turtle]

Summary of Bug

When trying to start a node while recording a tutorial I receive this error:

 gaiad start
Error: failed to read in app.toml: While parsing config: (275, 10): no value can start with e

It is non-deterministic.

This happens even when I don't touch the app.toml file.

Version

cosmos/gaia stargate3-a

Steps to Reproduce

Try screen recording on a mac or do something that consumes a lot of memory then initialize a node and start it.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[robert-zaremba]

Hi @marbar3778 - could you update the status here? Is there any progress? Is anyone handling this? Is this blocking for Stargate?

[tac0turtle]

could you update the status here?

Still a bug.

Is there any progress? Is anyone handling this? Is this blocking for Stargate?

Dont think it's blocking for stargate and not sure if there's progress. I just opened the issue.

[helder-moreira]

This happens when error is in config.toml.

For example, when removing the double quotes from moniker string in config.toml:

$ cat .gaia/config/config.toml | grep moniker
moniker = "test

We get the same error, complaining about app.toml:

$ gaiad status
Error: failed to read in app.toml: While parsing config: (18, 12): unescaped control character U+000A
Usage:
  gaiad status [flags]

Flags:
  -h, --help          help for status
  -n, --node string   Node to connect to (default "tcp://localhost:26657")

Global Flags:
      --home string         directory for config and data (default "/home/ubuntu/.gaia")
      --log_format string   The logging format (json|plain) (default "plain")
      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
      --trace               print out full stack trace on errors

EDIT: I believe it should be config.toml in this error string

[amaury1093]

I don't think #8643 fixes the non-determinism reported by @marbar3778.

[tac0turtle]

There were non-deterministic failures by users on the upgrade yesterday. Lots of interface nil panics

[cyberbono3]

@marbar3778 Unfortunately, I had no luck to reproduce an error today. Perhaps we can close it.