plotman tracking same plot multiple times

[acceleratxr]

Describe the bug

Plotman is tracking each plot twice.

To Reproduce

1. Install current plotman pip install --force-reinstall git+https://github.com/ericaltendorf/plotman@development.
2. Run plotman interactive

Expected behavior

Each listed job has a unique plot id.

System setup:

• OS: Ubuntu 20.04 LTS

Config

full configuration

```yaml # Options for display and rendering user_interface: # Call out to the `stty` program to determine terminal size, instead of # relying on what is reported by the curses library. In some cases, # the curses library fails to update on SIGWINCH signals. If the # `plotman interactive` curses interface does not properly adjust when # you resize the terminal window, you can try setting this to True. use_stty_size: True # Where to plot and log. directories: # One directory in which to store all plot job logs (the STDOUT/ # STDERR of all plot jobs). In order to monitor progress, plotman # reads these logs on a regular basis, so using a fast drive is # recommended. log: /var/log/chia # One or more directories to use as tmp dirs for plotting. The # scheduler will use all of them and distribute jobs among them. # It assumes that IO is independent for each one (i.e., that each # one is on a different physical device). # # If multiple directories share a common prefix, reports will # abbreviate and show just the uniquely identifying suffix. tmp: - /chia/plotter0 - /chia/plotter1 - /chia/plotter2 # Optional: Allows overriding some characteristics of certain tmp # directories. This contains a map of tmp directory names to # attributes. If a tmp directory and attribute is not listed here, # it uses the default attribute setting from the main configuration. # # Currently support override parameters: # - tmpdir_max_jobs tmp_overrides: # In this example, /mnt/tmp/00 is larger than the other tmp # dirs and it can hold more plots than the default. "/chia/plotter2": tmpdir_max_jobs: 6 # Optional: tmp2 directory. If specified, will be passed to # chia plots create as -2. Only one tmp2 directory is supported. # tmp2: /mnt/tmp/a # One or more directories; the scheduler will use all of them. # These again are presumed to be on independent physical devices, # so writes (plot jobs) and reads (archivals) can be scheduled # to minimize IO contention. dst: - /chia/plot-tmp # Archival configuration. Optional; if you do not wish to run the # archiving operation, comment this section out. # # Currently archival depends on an rsync daemon running on the remote # host, and that the module is configured to match the local path. # See code for details. archive: rsyncd_module: chia rsyncd_path: /chia rsyncd_bwlimit: 1000000 # Bandwidth limit in KB/s rsyncd_host: 10.0.0.40 rsyncd_user: ubuntu # Optional index. If omitted or set to 0, plotman will archive # to the first archive dir with free space. If specified, # plotman will skip forward up to 'index' drives (if they exist). # This can be useful to reduce io contention on a drive on the # archive host if you have multiple plotters (simultaneous io # can still happen at the time a drive fills up.) E.g., if you # have four plotters, you could set this to 0, 1, 2, and 3, on # the 4 machines, or 0, 1, 0, 1. # index: 0 # Plotting scheduling parameters scheduling: # Run a job on a particular temp dir only if the number of existing jobs # before tmpdir_stagger_phase_major tmpdir_stagger_phase_minor # is less than tmpdir_stagger_phase_limit. # Phase major corresponds to the plot phase, phase minor corresponds to # the table or table pair in sequence, phase limit corresponds to # the number of plots allowed before [phase major, phase minor] tmpdir_stagger_phase_major: 2 tmpdir_stagger_phase_minor: 1 # Optional: default is 1 tmpdir_stagger_phase_limit: 8 # Don't run more than this many jobs at a time on a single temp dir. tmpdir_max_jobs: 4 # Don't run more than this many jobs at a time in total. global_max_jobs: 24 # Don't run any jobs (across all temp dirs) more often than this, in minutes. global_stagger_m: 30 # How often the daemon wakes to consider starting a new plot job, in seconds. polling_time_s: 20 # Plotting parameters. These are pass-through parameters to chia plots create. # See documentation at # https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference#create plotting: k: 32 e: False # Use -e plotting option n_threads: 4 # Threads per job n_buckets: 128 # Number of buckets to split data into job_buffer: 3390 # Per job memory # If specified, pass through to the -f and -p options. See CLI reference. # farmer_pk: ... # pool_pk: ... ```

Additional context & screenshots

Note how there are 14 jobs but only 7 actual plots.

[D4rk4]

Look like the same - #337 Chia from deb package?

[altendky]

If you could try out https://github.com/ericaltendorf/plotman/pull/418, that'd be great. Follow the regular readme installation but use git+https://github.com/altendky/plotman@skip_matching_plot_process_parents as the url.

[acceleratxr]

If you could try out #418, that'd be great. Follow the regular readme installation but use git+https://github.com/altendky/plotman@skip_matching_plot_process_parents as the url.

I get this when trying to install.

WARNING: Did not find branch or tag 'skip_matching_plot_process_parents', assuming revision or ref.
  Running command git checkout -q skip_matching_plot_process_parents
  error: pathspec 'skip_matching_plot_process_parents' did not match any file(s) known to git
ERROR: Command errored out with exit status 1: git checkout -q skip_matching_plot_process_parents Check the logs for full command output.

[altendky]

Please share the full prompt, command, and output. I suspect you used ericaltendorf rather than altendky.

[caskater4]

Please share the full prompt, command, and output. I suspect you used ericaltendorf rather than altendky.

Here is the full command I ran with the above quoted output.

ubuntu@chia:~$ sudo pip3 install --force-reinstall git+https://github.com/altendky/plotman@skip_matching_plot_process_parents
Collecting git+https://github.com/altendky/plotman@skip_matching_plot_process_parents
  Cloning https://github.com/altendky/plotman (to revision skip_matching_plot_process_parents) to /tmp/pip-req-build-_o574sbn
  Running command git clone -q https://github.com/altendky/plotman /tmp/pip-req-build-_o574sbn
  WARNING: Did not find branch or tag 'skip_matching_plot_process_parents', assuming revision or ref.
  Running command git checkout -q skip_matching_plot_process_parents
  error: pathspec 'skip_matching_plot_process_parents' did not match any file(s) known to git
ERROR: Command errored out with exit status 1: git checkout -q skip_matching_plot_process_parents Check the logs for full command output.

[bdgackle]

I tried the fix above as well with the same error. I did a git clone manually from https://github.com/altendky/plotman and looked at branches manually with 'git branch -a'

I don't think the skip_matching_plot_process_branch_parents branch is there -- perhaps it never got pushed?

It looks like it got merged around commit fa33c9d?

Edit to add: I see now that you linked to a PR up there, so this has in fact merged. Sorry about that. I can confirm that the current tip of the development branch fixed this for me.

[altendky]

My apologies, I think it got deleted after it was merged to development. Sorry for the wasted time. Yes, you can try it using official instructions from the readme except with @development instead of @main.

[ghost]

I just found this issue on Debian 11 as well after installing a few days ago. Do I need to uninstall and reinstall again or has it been merged yet?

[ghost]

I just found this issue on Debian 11 as well after installing a few days ago. Do I need to uninstall and reinstall again or has it been merged yet?

Going through the suggestions did not fix for me

[altendky]

When responding "me too" to a ticket at least fully document what you did and what you saw. Possibly just create a new ticket and reference the one you think is the same as your issue.

[ghost]

When responding "me too" to a ticket at least fully document what you did and what you saw. Possibly just create a new ticket and reference the one you think is the same as your issue.

Sorry, except for being on Debian 11 fully updated instead of Ubuntu and having the stock config at the time it was identical and the exact same problem. I was able to tread the maze of solution tickets listed, uninstall and install the dev version with the fix. Working fine now.

Next time I'll create a new ticket, Sorry again.