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.

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

Executable editing utils #1

Open
wants to merge 6 commits into
base: prolific
Choose a base branch
from
Open

Conversation

dyld-w
Copy link
Collaborator

@dyld-w dyld-w commented Oct 30, 2024

  • Adds the executable editing functions to the utils file
  • Adds SUPREME.exe & SUPREME.app to the newly created data/base_executables directory
  • Adds base_exe & base_app to config, referring to SUPREME.exe & SUPREME.app respectively

Ran pytests & it completed successfully on my machine, generating new app bundles with updated workerID values. I tried to generally follow the practices established within the project already. The base executables themselves will be updated as we move towards a final version. The executables included here should work but are by no means finalized versions.

@dyld-w dyld-w requested a review from Shotgunosine October 30, 2024 15:20
format='%(asctime)s - %(levelname)s - %(message)s')


def edit_app_worker_id(app_path: str, new_worker_id: str, output_app_path: Optional[str] = None) -> None:
Copy link
Owner

Choose a reason for hiding this comment

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

I don't think the output_app_path should be optional in the version of this code included in the backend. I'd like to avoid the possibility of the base apps getting accidentally overwritten.

Copy link
Owner

Choose a reason for hiding this comment

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

I'd prefer not to include the executables in this repo.

Copy link
Owner

Choose a reason for hiding this comment

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

Do you think you could store the task version (maybe just the commit hash) in the executables themselves? Then we could include that version string in the app.ini file and have version checking and executable downloading from OSF happen in here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants