Grand-challenge-forge

Latest version: v0.6.1

Safety actively analyzes 681775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.6.1

- Fix not using algorithm URL correctly in README
- Use valid examples for JSON-like inputs/outputs
- Fix permissions not always being restored correctly when running on latest Ubuntu LTS
- Ensure .tif are correctly parsed by example scripts

0.6.0

- Add forging of algorithm templates.
- Split CLI commands into 'pack' for challenge packs and 'algorithm' for algorithm templates.

0.5.0

- Fixed interoperability issues when running challenge pack scripts on macOS.
- Fixed several Docker deprecation warnings.
- Added examples for file inputs.
- Reworked multithreading in example evaluation methods:
- Used concurrent.futures.ProcessPoolExecutor.
- Dynamically limited the number of workers in evaluation methods (via multiprocessing.cpu_count()).
- Introduced a controller thread.
- Silenced Docker volume shell calls.
- Mounted a dummy /tmp to test scripts, preventing final containers that users might build.
- Challenge packs now include a proper .gitignore.
- Added a save.sh script to Docker-based examples to demonstrate how to export a Docker image.
- Ensured Docker file-mounted inputs are read-only.
- Dist challenge packs under the Apache License 2.0.

0.4.0

- Stop using '/tmp' in example Dockerfiles to contain non-transient files.

0.3.0

- Replace "input"/"output" in the context JSON input with "algorithm_input"/"algorithm_output".

0.2.2

- Various improvements to spelling and wording in the challenge packs

- Report grand-challenge-forge version in generated pack README
- Use challenge-level archives instead of phase-level archives for the pack README
- Add support for reading and writing TIFF files
- Disable network in test runs

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.