Skip to content

fix: Premature link success message #220

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

Merged
merged 24 commits into from
Sep 5, 2022

Conversation

github-actions[bot]
Copy link
Contributor

Problem

Only one file needed to be linked, yet one file linked and one file failed.
They're all the same one??? I reckon that "linked" text isn't running conditionally. Not sure why, but let's figure it out.

Pasted image 20220818121720

Additional Improvements

It would also be nice if we could get a list of the proxies that failed. But we shouldn't assume that the user would always want that. If it's a lot, that'll be a total console spam... Maybe print log location on screen?

closes #214

@github-actions github-actions bot added the bug Something isn't working label Aug 29, 2022
in03 added 23 commits August 30, 2022 11:37
- Removed the "spoon-feed/hand-holding" wizard prompts yuck
- Also added new exceptions module with proper exceptions for Resolve module
- Mutate original jobs with queuer data instead of tasks (needs more work)
- Add proper handling for different kinds of link fails
- Add logic to handle project change detection
- link_with_mpi is now ProxyLink class
- Removed find_and_link linking function, may resurrect in future
if necessary, but linking with mpi should cover all reasonable use cases.
@in03 in03 changed the title Premature linking success message fix: Premature link success message Aug 31, 2022
Copy link
Owner

@in03 in03 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took this a lot further than the original issue scope...
Fixes #214 and #212.

Link logic improvements:

  • remove unused find_and_link() method
  • check Resolve is open before linking
  • check Resolve project is same before linking

Other improvements:

  • add several custom exceptions definitions for Resolve
  • improve importing with __init__py-level imports
  • fixed incorrect syntax for private functions
  • use tuples instead of lists for linkable type definitions

Some more adjustments to import statements may be necessary for better readability

@in03 in03 marked this pull request as ready for review September 5, 2022 00:27
@in03 in03 merged commit 2d6cac7 into main Sep 5, 2022
@in03 in03 deleted the bugfix/issue-214-Premature-linking-success-message branch September 5, 2022 00:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Premature linking success message
1 participant