Fridolin Glatter

TL;DR: this has gotten and taken much longer than anticipated. For my money, the issue can likely be explained by understanding the changes you made for Python 3.11. Jpype1 1.5.0...

Postponing due to lack of time/urgency.

Hi @meng25meng, one hint first: I'm editing your comments to render the code blocks in a better way. For multiline code, you want to use triple backticks like "```" before...

As for your problem, I haven't worked with a Community license for GAMS yet, but it looks to me like the model starts solving and then hits the error message...

As mentioned in the email just now, you or we would need to study the `\path\for\model\files\MESSAGE_run.lst` file to understand why the model is considered infeasible.

Eventually, you might need to look at `\path\for\model\files\MESSAGE_run.gms` line 2759 to see which equation is considered, but for now, the whole `\path\for\model\files\MESSAGE_run.lst` (which is different, note the file extension `.lst`)...

Thanks for this PR @daymontas1 :) Currently, all test failures complain about a GAMS compilation error: ```python FAILED message_ix/tests/test_macro.py::test_calc_valid_years - ixmp.model.base.ModelError: GAMS errored with return code 2: There was a...

Unfortunately, this will have to be postponed until we find time for a proper cleanup.

Hi @brendandanaher, thanks for reaching out! This typo is somewhat intentional, I would say. Please note that we have recently released version 3.8.0 of message_ix, which changed the syntax of...

It seems like this flaky behaviour wasn't completely resolved by the first PR: - [ ] ```python ERROR message_ix/tests/tools/test_add_year.py::test_add_year - RuntimeError: unhandled Java exception: Error opening GDX file: Expected data...