[Bug] Session must be marked as failed when apply failed (not as complete)

Open
#359 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend

Research direction

The payload names no files, so start by searching the repository for where the apply report status and the session status are set, and confirm that a Failed apply currently results in COMPLETED. Reproducing that path needs a failing apply, which the issue doesn't describe, so ask in the issue for a repro first. Done means a Failed apply report produces a Failed session, with a test covering that case.

Written by the indexing model from the issue text.

Description

core
Description

Mark a session Failed when the apply report is Failed, instead of COMPLETED.

Steps to Reproduce

Apply failure

Expected Behavior

No response

Version / Environment

No response

Additional context or logs

No response

Dominant language
Python
Stars
148
Forks
8
Avg merge
12h 32m
Merged PRs (30d)
63

Getting set up

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 InditexTech/kumoss

All issues in InditexTech/kumoss

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.