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.

Sign up for GitHub

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

Jump to bottom

[BUG] CalledProcessError due to incorrect mutable range in alicevision.py #13

Open
1 task done
JeS24 opened this issue Jul 23, 2023 · 5 comments
Open
1 task done

[BUG] CalledProcessError due to incorrect mutable range in alicevision.py #13

JeS24 opened this issue Jul 23, 2023 · 5 comments
Labels
alicevision aV related reports backend backend related reports bug Something isn't working

Comments

@JeS24
Copy link
Collaborator

JeS24 commented Jul 23, 2023

Problem description

If a new contribution (set of uploaded images) for a site (Mesh) is being processed by ImageOps and added to Mesh's /good/ folder, while a reconstruction Run is ongoing, it is possible that the inputSize() property will return different values for different steps of the AliceVision pipeline. This can sometimes lead to a CalledProcessError due to an incorrect range (or blockSize). In pratical terms, this is not a problem generally, due to MESHOPS_CONTRIB_DELAY and if a run fails, the next run should be able to handle it. Perhaps, we can ensure that the MESHOPS_CONTRIB_DELAY is added on to, after each new contribution? This would help us avoid failed "first" runs.

Relevant code can be found in workers.py and alicevision.py.

Self-check
@JeS24 JeS24 added bug Something isn't working backend backend related reports alicevision aV related reports labels Jul 23, 2023
@JeS24 JeS24 self-assigned this Jul 23, 2023
@JeS24 JeS24 changed the title [BUG] [BUG] CalledProcessError due to incorrect mutable range in alicevision.py Jul 23, 2023
@JeS24 JeS24 removed their assignment Jul 24, 2023
@github-actions
Copy link

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open.

@JeS24 JeS24 reopened this Oct 1, 2023
@JeS24 JeS24 removed the stale-issue label Oct 1, 2023
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 1, 2023

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open.

@JeS24 JeS24 removed the stale-issue label Dec 2, 2023
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open.

@JeS24 JeS24 removed the stale-issue label Feb 1, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 1, 2024

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open.

@JeS24 JeS24 removed the stale-issue label Apr 6, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Jun 5, 2024

This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open.

@JeS24 JeS24 removed the stale-issue label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
alicevision aV related reports backend backend related reports bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JeS24