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.

Sign up for GitHub

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

Jump to bottom

Fix/add-potential-fixes-for-not-found-error #176

Merged
merged 2 commits into from
May 1, 2024
Merged

Fix/add-potential-fixes-for-not-found-error #176

merged 2 commits into from
May 1, 2024

Commits on Apr 18, 2024

  1. add potential fixes if something is not found on the backend (mostly … 

    …typos or forgotten organization in datatset name)
    @segments-arnaud
    segments-arnaud committed Apr 18, 2024
    Configuration menu
    Copy the full SHA
    ef4938e View commit details
    Browse the repository at this point in the history

  2. rewrite message a bit

    @segments-arnaud
    segments-arnaud committed Apr 18, 2024
    Configuration menu
    Copy the full SHA
    92c059c View commit details
    Browse the repository at this point in the history