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

[Feature] Post-GSoC ’24: Expand Error + Exception Handling #128

Open
1 task done
naishasinha opened this issue Aug 24, 2024 · 0 comments
Open
1 task done

[Feature] Post-GSoC ’24: Expand Error + Exception Handling #128

naishasinha opened this issue Aug 24, 2024 · 0 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@naishasinha
Copy link
Member

Context

Automating Quantifying the Commons was a project endeavor for the Google Summer of Code 2024 program, in which a baseline automation software for data gathering, processing, and analysis was successfully developed. However given the time and resource constraints that we had to consider, there are still addressable endeavors to improve this codebase over the upcoming quarters and years. This is the fifth (5) of five (5) issues raised specifically for post-GSoC contributions.

Problem

The current custom error and exception handling in the codebase — although customized specifically for the Quantifying codebase — is at a minimal stage, with basic messages that can be improved to ease the development process.

Description

This feature involves expanding the current error and exception handling mechanisms, adding more informative and detailed messages. This will make it easier to debug issues and improve the overall reliability of the system.

Implementation

  • I would be interested in implementing this feature.
@naishasinha naishasinha added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Aug 24, 2024
@TimidRobot TimidRobot added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Aug 27, 2024
@TimidRobot TimidRobot added the help wanted Open to participation from the community label Aug 28, 2024
@TimidRobot TimidRobot moved this to Backlog in Applications Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

No branches or pull requests

2 participants