#I'm getting a backtrace after coming out
fading raptor
Now seems the editing may not be the issue. I'm getting BTs quite a bit
I'm on a mac running v0.18.10 installed from brew
short bough
Now seems the editing may not be the issue. I'm getting BTs quite a bit
what container base image invovled?
Any special commands executed?
Switch to a different shell?
fading raptor
I didn't switch shells while in the .Terminal. I was running commands and modifying files (mounted/created by my container config) to debug.
short bough
I didn't switch shells while in the .Terminal. I was running commands and modif...
If you can drop in a screenshot or text dump, it would help.
Or something I can repro with.
Was trying things like:
container | from alpine | with-mounted-file foo.txt $(host | file
testing.txt) | terminal
in shell
fading raptor
Not sure how to repo tbh. I can drop the bt, but not sure if that'll be helpful?
I mean, I can repo it pretty consistently it seems but it's not clear even to me what consistent things I'm doing to cause it
livid inlet
@fading raptor can you create an arbitrary test module and see if you can repro? I am on the same version but not seeing any issues exiting the terminal.
fading raptor
I wasn't before I started mucking around in the container to debug. I'll try to see if I can create a repo
fading raptor
Yes, zsh
livid inlet
should be fine. Try to repro with a dummy module. Maybe something to do with where you are invoking Terminal()
fading raptor
I didn't have issues when I just looked around. When I did stuff (modified files, built src, etc) that's when I have an almost 100% change to get the bt. I don't know if it's how I built the container or maybe something I did in container.
So, repo may be a simple module + instructions if I can create them
livid inlet
yup. Something easy enough to paste code here.