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

[Issue] init command erases certain variables in config.toml #4488

Open
JohnSmith-PrivacyRebels opened this issue Mar 20, 2024 · 1 comment
Assignees
Labels
bug Something isn't working bug-needs-triage A bug that needs discussing and triage needs-triage qa Quality Assurance

Comments

@JohnSmith-PrivacyRebels
Copy link
Contributor

Describe the issue
When I init my binary (either nym-mixnode or nym-gatweway) after the update, it erases certain variable values like landing page, hostname.

Expected behaviour
Init should not touch permanent variables

Stack Traces
no logs as such, simply blank variables in config.toml

Steps to Reproduce
run 'nym-mixnode init --id YOURID --host blah blah
check config.toml
certain variables will be blank (landing page, hostname, metrics_key, for example)

Which area of Nym were you using?

  • Application: [Gateway, Mixnode]
  • Version: [1.1.36 for mixnode and 1.1.34 for gateway but I noticed this behaviour on previous versions as well]
@JohnSmith-PrivacyRebels JohnSmith-PrivacyRebels added bug Something isn't working bug-needs-triage A bug that needs discussing and triage needs-triage qa Quality Assurance labels Mar 20, 2024
Copy link

Thank you for raising this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working bug-needs-triage A bug that needs discussing and triage needs-triage qa Quality Assurance
Projects
None yet
Development

No branches or pull requests

2 participants