Implement simplified timeout logic and make configurable through API

Open
  • Is something wrong?
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend-api-design

Research direction

Start by locating ConfigInput and the existing timeout or completion-group entry points. Clarify the intended simplified hard/soft timeout behavior and client-facing configuration before implementation; the issue is done when that behavior is implemented and configurable through the API.

Written by the indexing model from the issue text.

Description

There's the concept of hard vs. soft timeouts and completion groups in SaaS TLM. Design and implement a simplified version of that logic and make it configurable by clients through the ConfigInput.

Dominant language
Python
Stars
9
Forks
6
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cleanlab/tlm

All issues in cleanlab/tlm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.