Fix issue #758.

[bdice]

Description

This PR attempts to fix #758.

Motivation and Context

Currently bundles are considered for status check operations as long as they start with a given prefix. This prefix is not uniquely identifying (through the inclusion of a hash, for example), because it is meant to be short and readable. However, this can cause projects to try to read status updates from other FlowProject instances (and potentially other users) if they share a common FlowProject class name.

This fixes #758 by only considering bundles that already exist within the project.

Note: These bundle ids are guaranteed to be unique (up to hash collisions) because they include the project's filesystem path in a hash when computing the id of each _JobOperation. These _JobOperation ids are then hashed together to produce a unique bundle id.

I do not have a way to test this PR on a scheduler. Support from reviewers in testing would be welcome.

Checklist:

• I am familiar with the Contributing Guidelines.
• I agree with the terms of the Contributor Agreement.
• My name is on the list of contributors.
• The changes introduced by this pull request are covered by existing or newly introduced tests.
• The package documentation and framework documentation in signac-docs are up to date with these changes.
• I have updated the changelog and added any related issue and pull request numbers for future reference.

[joaander]

Thanks! This turned out to be a simple fix.

As you say, we should test on a cluster before merging.

[CalCraven]

Tested this using the example I posted in #758. Works like a charm, thanks @bdice!

[bdice]

Great. @cbkerr I'll let you merge since you're taking care of the release in #833. Please add a changelog entry in the release PR.

[cbkerr]

@CalCraven Thanks for testing! I'll put it in the release