Skip to content

Release 4.71.0#518

Merged
pnemere merged 117 commits into
mainfrom
development
Jun 23, 2026
Merged

Release 4.71.0#518
pnemere merged 117 commits into
mainfrom
development

Conversation

@pnemere

@pnemere pnemere commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Peter Nemere and others added 30 commits May 18, 2026 19:02
… new job manager to contain all the new job management functionality, which sits in API services. FS code was updated to allow testing bucket access but simulated with just a local test directory in place of all the buckets (this has its own test too). Some logs about upload/downloading changed do DEBUG level. Promoted getModuleVersion to a wsHelper so it can be reused. This change also involved fixing some circular dependencies and changing some data types to uint to make things more robust, so more files affected. Existing PIQUANT run code and tests have NOT changed and should still pass, this will be the case until the new code takes over the role. Added Local job executor (for testing only, runs the code directly, not through docker or other steps). NOTE: jobrunner was brought back from external repo to be local, so we can more easily debug/test it because if it's in another repo, we need to build the docker container so we can re-run job tests
… actually run expressions (not just read cached values)
… end. Lots of things renamed/made public so the new jobmanager can access it, eg parts of quantification package. The new tests don't rely on s3 buckets but can test in local file system using FS mocking. Other things moved to break circular references. Executor removed as it seems no longer needed with new JobNode code (that handles starting docker containers on an EC2 for eg)
Changing env vars for job runner
… - output structures and the ability to run job nodes on demand from API. Mostly working, need more testing and automated tests. Currently the QuantificationSummary structure still lacks the input param fields and it has yet to be tested in a new style environment on AWS. FOr testing we will ensure some word like legacy in the quant name will request an OG quant and we can run a new one and compare them, remove old code once new matches exactly in an environment
…AWSSecret config value is empty, we run it locally. Added check for timed-out job nodes in job manager. Log job run errors in jobnode where docker fails
Peter Nemere and others added 28 commits June 10, 2026 11:24
Allow specifying EC2 subnet id
… for given EC2 instances and cores per node settings
…re quant output's for a docker container weren't yet uploaded somehow. Also checked in comments documenting EC2 runtime speed with various configurations of EC2 instance type and cores per node settings
… we're checking. Unit tests were failing because output was not deterministic, now we don't print the PREPARING_NODES state, so it should work
…t how many cores/node we run, we just calculate it as how many jobs to break it into and then run that how we want in EC2
Fixing file sync for backup/restore
Fixing paths for restore of images/quant/scans
…, beam locations, diffraction peak statuses, manually entered diffraction peaks
dstFullPath := fs.filePath(dstRootPath, dstPath)

// Make the intermediate dirs as needed
err = os.MkdirAll(filepath.Dir(dstFullPath), 0777)
@pnemere pnemere merged commit a7799dc into main Jun 23, 2026
15 of 17 checks passed
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