Skip to content

The first Dataset in the training reset to the first on the dataset list when editing the configuration. #620

@alcaitiff

Description

@alcaitiff

This is for bugs only

Did you already ask in the discord?

Yes

You verified that this is a bug and not a feature request or question by asking in the discord?

Yes

Describe the bug

Steps to reproduce:

I have five datasets available in my workspace, listed in alphabetical order: A, B, C, D, and E.
I created a LoRA training job using datasets C and E (selected in that specific order: first C, then E).
After the job was done or paused, the job details page correctly shows the datasets used as C and E, in the expected order.

Issue:
When I click the "Edit" (pencil) button to modify the job configuration:

The first dataset in the configuration is sometimes automatically changed from C to A (the first dataset in the overall list of available datasets).
The second dataset remains E.
As a result, the edited configuration shows datasets A and E instead of the original C and E.

From my experience, this behavior occurs very often but not every single time (it's intermittent). This makes it harder to reproduce consistently, which I understand could complicate debugging and fixing the issue.
This appears to override the originally selected dataset with the first one in the alphabetical list in many cases when the job is opened for editing.
Could you please investigate this when possible? It affects the reliability of editing jobs .

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions