Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Auto_update flag not working within config.toml file #6594

Closed
noswald opened this issue Sep 26, 2017 · 4 comments
Closed

Auto_update flag not working within config.toml file #6594

noswald opened this issue Sep 26, 2017 · 4 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P7-nicetohave 🐕 Issue is worth doing eventually.
Milestone
1.10

Comments

@noswald
Copy link

noswald commented Sep 26, 2017 •
edited by 5chdn

I'm running:
Parity version: 1.7.0
Operating system: Linux
And installed: via installer or source (can't remember which)

I recently noticed that parity was not auto updating on my machine, even after using the config.toml file, as outlined here: https://github.com/paritytech/parity/wiki/Configuring-Parity#cli-options

The config.toml file has the following lines:

[parity]
# Auto-updates to every release.
auto_update = "all"

Is this a known issue? What is the recommended fix to enable auto_updates?
@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Sep 26, 2017
@5chdn
Copy link
Contributor

5chdn commented Sep 27, 2017

Can reproduce with --auto-update all --release-track beta on 1.6.10

@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P7-nicetohave 🐕 Issue is worth doing eventually. and removed Z1-question 🙋‍♀️ Issue is a question. Closer should answer. labels Sep 27, 2017
@tomusdrw
Copy link
Collaborator

Is it a Parity issue or the new release was just not pushed to the contract?

@5chdn
Copy link
Contributor

5chdn commented Sep 28, 2017

Probably not pushed. Where is the contract?

@5chdn 5chdn added this to the 1.9 milestone Oct 5, 2017
@debris
Copy link
Collaborator

debris commented Oct 15, 2017

we've investigated this issue with @arkpar . It has been fixed in 1.7.7 and in 1.8.0. Master will be fixed once #6742 is merged

@debris debris mentioned this issue Oct 15, 2017
Merged
@5chdn 5chdn modified the milestones: 1.9, 1.10 Oct 17, 2017
@debris debris closed this as completed Oct 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P7-nicetohave 🐕 Issue is worth doing eventually.
Projects
None yet
Milestone
1.10
Development

No branches or pull requests
4 participants
@tomusdrw @noswald @debris @5chdn