-
-
Notifications
You must be signed in to change notification settings - Fork 393
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.
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
Printing of large vectorized constraints should probably cause output eliding? #3757
Comments
These are the offending methods: Lines 746 to 786 in fad385c
I wonder if we should just drop some bytes, like the REPL does |
Sure, that would certainly be an improvement! I've said it before, and i'll repeat, i think such constraints should be printed as
spam really ought to be something like |
JuMP does not store constraints like this, so we cannot (without a lot of effort) print it like this. |
I think the bigger issue is that you're trying to use |
@odow thank you! |
This issue is quite similar to the issue of printing a model with large number of constraints (#3651),
it may produce too much output causing just the same issue described in #3651.
Example:
There is no eliding, it will still print the entire constraint even if there's 1000 elements,
and in fact it did successfully hand up browser tab with julia's jupyterlab for me.
The text was updated successfully, but these errors were encountered: