-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Stack Overflow in BoundingBox #5217
Comments
Have you tried updating within the last 24-48 hours? There were a number of these stack overflows whose root cause was recently fixed (e.g. JuliaInterop/ZMQ.jl#39). |
I noticed this too, fixed. |
Tim, I still have error after your fix:
|
@jiahao I've used the most recent Julia version when I've sent this issue. But stack overflow still exists for me. |
Totally-separate error. You need to update to master on Winston: |
Tim, thank you for fixing both bugs. Plotting works now. |
* upstream/master: (89 commits) fix JuliaLang#5225 update pcre fix off-by-1 in isqrt. closes JuliaLang#4884 Add more keywords to ctags regex, plus README annotate the types of arguments for derived trigonometric & hyperbolic functions fix doc for && and || and update helpdb only show ccall literal address warning in imaging mode. closes JuliaLang#5215 minor update of hypot to ensure consistency of output types Fix JuliaLang#5217 silence compiler warning hopefully more robust way of getting github URL (don't assume module name is Pkg name) add text/html writemime for MethodList and Method (fix JuliaLang#4952) update NEWS doc: `import M: single,name` syntax, close JuliaLang#5214 clean up native finalizers code specialized abs2 for bool remove use of callback API in REPL Some error message cleanup to fix segfault when transposing sparse vector with illegal values. test/git*.jl: don't use `echo` to read-and-write from processes. test/git*.jl: don't use `echo` to read-and-write from processes. ...
There are problems with Winston plotting on recent Julia build:
I assume it is related with similar recent issue #5201
The text was updated successfully, but these errors were encountered: