search

labsyspharm / minerva-author

Tool to create images and configuration files for Minerva-Story
MIT License
15 stars 14 forks source link

ImportError: cannot import name 'escape' from 'jinja2' #43

Closed yolandaas closed 2 years ago

yolandaas commented 2 years ago

Occurs when trying to open minerva_author.exe and seems to be an issue with the version of Flask.

image

thejohnhoffer commented 2 years ago

Hi! Thank you for raising this to my attention, it should be fixed in the latest 1.10.9 release! Please let me know if you continue to face issues running the executable.

-John

yolandaas commented 2 years ago

Hi John,

I downloaded and opened the newest version, and I am getting an "Invalid tiff file" error, saying that there are "not enough values to unpack (expected 2, got 1)". This specific tiff file has worked on previous versions of Minerva Author (i.e. pre-Jan 2022) so I wonder if it might be a problem with the requirements.

thejohnhoffer commented 2 years ago

Hi - would you be able to provide the full error log that you see when attempting to load your tiff file? I believe this error may be something that I have encountered before.

Starahoush commented 2 years ago

Hi John,

I am facing the same issue of "Invalid tiff file", "not enough values to unpack (expected 2, got 1)". I donwloaded the ome.tiff file from nanostring . I am not sure how to get the full error log but with you can guide me, I will reply as soon as possible.

Here is the issue on the browser: browser

And here the message on the terminal: prompt

I tried multiple times, that's why there are many occurences. I am currently using windows 10. Tried running on Chrome and Opera GX.

Thank you in advance, Igor

Starahoush commented 2 years ago

Small update:

Not sure if this is helpful but the console says regarding the import tiff file issue: value @ bundle.3652200fbef473bea6f2.js:280

browser_warning1 browser_warning2

thejohnhoffer commented 2 years ago

@yolandaas @Starahoush -- The latest version of Minerva Author v1.11.1 resolves this newer issue (#51) when tested on Windows 11. The source of the issue was outdated dependencies in the generated Windows executable for v1.10.