Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Improve `Model is infeasible, but there was no unmet demand` error message

Open
#1,223 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Search the repository for the exact Model is infeasible, but there was no unmet demand message, then read the related discussion in #1132 to understand the source of the confusion. Done means the error explains the situation more clearly and directs users to submit a bug report when no better diagnosis is available.

Written by the indexing model from the issue text.

Description

muse xiii

As came up in #1132, this error message is a source of confusion so should be clarified, in case it comes up again. I guess we don't really have a good explanation for this error so the guidance should probably be to submit a bug report

Dominant language
Rust
Stars
8
Forks
5
Avg merge
11h 31m
Merged PRs (30d)
33

Contributor guide

Open the contributing guide

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 EnergySystemsModellingLab/MUSE2

All issues in EnergySystemsModellingLab/MUSE2

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.