Chao Yang
@asterite I think the debugger works fine with forking, you can try below code out with the interpreter: Example code: ```crystal require "gc" GC.disable puts "loop.cr: #{Process.pid} Crystal::SignalChildHandler: #{Crystal::SignalChildHandler.hash}" ::Signal.setup_default_handlers...
For now, I'll keep using my workaround for this issue. And here is my current workaround in case someone needs it. ```crystal {% if flag?(:interpreted) %} GC.disable Signal::CHLD.reset Crystal::Signal.start_loop {%...
I got a different error on Ubuntu 22.04: ``` In lib/raven/src/raven/instance.cr:142:13 142 | Event.from(obj, **options).tap do |event| ^--- Error: compiling Event.from(obj, options[:configuration], options[:context]) Error: compiling self.from(arg0, arg1, arg2) In lib/raven/src/raven/event.cr:103:7...
I can bypass the error of `undefined constant ERROR` by changing property `level`'s default value to `Severity::ERROR` instead of `:error`. I think the enum casting is not working properly in...
With latest bug fixes(not merged), the interpreter runs all `bridge-cli` tests successfully on Ubuntu 22.04. @will, You can use the interpreter in docker container or vscode dev container if you...
You can fix this issue by setting env var `DYLD_LIBRARY_PATH` to the homebrew's openssl lib path. homebrew's crystal package depends on `[email protected]` so you can set it like below: ```sh...
@will I'm using locally built crystal. ```sh $ otool -L .build/crystal .build/crystal: /usr/local/opt/llvm@14/lib/libLLVM.dylib (compatibility version 1.0.0, current version 14.0.6) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.32.0) /usr/local/opt/pcre/lib/libpcre.1.dylib (compatibility version 4.0.0,...
I couldn't reproduce it with postgres. Maybe it's an issue with sqlite adapter. Could you share your migration files? Here's my test with postgres: https://github.com/cyangle/jennifer.cr/commit/566fec0dc8472d3817a701a8618df855bca3e531 @wonderix
This allows running shell commands with the interpreter. And I think it's worth it because several github issues were created due to not being able to run shell commands. And...
This is still a workaround with a much smaller impact than #14016.