PyRun Bug & Issue Tracker

Welcome to the official bug and issue tracker for the PyRun cloud platform!

This repository is the central place to:

• 🐛 Report bugs or unexpected behavior you encounter while using PyRun.
• ✨ Suggest new features or enhancements for the platform.

⚠️ Important: Scope of this Repository

• Please DO report:

  • Bugs: Errors, crashes, incorrect results, UI glitches, unexpected behavior within the PyRun platform (web interface, runtime execution, monitoring, etc.).
  • Feature Requests: Concrete ideas for new functionality or improvements to existing features.
  • Documentation Issues: Errors or areas needing clarification in the official PyRun documentation (docs.pyrun.cloud).

• Please DO NOT use this repository for:

  • General Support Questions: "How do I...?", "Why is my code not working?" (unless you suspect a platform bug), configuration help. For support, please use [Your Support Channel Link - e.g., community forum, email, contact page].
  • AWS/Cloud Provider Issues: Problems related to your underlying AWS account setup, billing, or AWS service limits (unless directly caused by a PyRun bug).
  • Debugging Your Own Code: Issues specific to your Python script logic that are not related to the PyRun platform itself.

Reporting Bugs 🐛

Found a bug? Thank you for helping us improve PyRun! Before submitting:

1. Search Existing Issues: Please check if a similar bug has already been reported. If so, add any additional information you have to the existing issue or give it a 👍 reaction.
2. Use the Bug Report Template: When creating a new issue, please use the "Bug report" template if available. This helps ensure you provide all necessary information.
3. Provide Detailed Information: The more details you provide, the easier it is for us to reproduce and fix the bug. Please include:
   • Clear and Descriptive Title: Summarize the problem concisely.
   • Steps to Reproduce: Provide a clear, step-by-step sequence of actions to trigger the bug.
   • Expected Behavior: What did you expect to happen?
   • Actual Behavior: What actually happened? Include error messages (copy-paste the full text).
   • Screenshots or Screencasts: Visual evidence is extremely helpful!
   • Environment Details:
     • PyRun version (if applicable/known).
     • Browser and OS used to access the PyRun dashboard.
     • Workspace details (e.g., Lithops or Dask template used).
     • Runtime configuration details (relevant parts of environment.yaml or Dockerfile if customized).
   • Logs: Relevant logs from the PyRun monitoring dashboard or runtime build process.

Suggesting Features ✨

Have an idea to make PyRun even better? We'd love to hear it!

1. Search Existing Issues: Check if a similar feature request already exists.
2. Use the Feature Request Template: When creating a new issue, please use the "Feature request" template if available.
3. Explain the "Why": Clearly describe the problem you're trying to solve or the use case the feature would enable. Why is this feature valuable?
4. Describe the "What": Outline how you envision the feature working. Mockups or examples are welcome but not required.

Contribution Guidelines

Currently, contributions are primarily managed through issue reporting. We appreciate detailed and well-documented bug reports and feature requests! If you're interested in contributing code in the future, please keep an eye on this repository or the main PyRun documentation for updates.

Code of Conduct

All interactions in this repository are expected to follow our [Code of Conduct](Link_To_Your_Code_Of_Conduct - Consider adding a standard one like Contributor Covenant if you don't have one yet). Please be respectful and constructive.

Related Links

• PyRun Documentation: docs.pyrun.cloud
• PyRun Website: pyrun.cloud
• PyRun Discord: Discord

Thank you for contributing to PyRun!