Morgan Jones
Morgan Jones
Do you think this patch will work for FLRig control? In that case, something like a rig_port of localhost:12345 needs to be used.
Ah, I was referring to hamlib's "FLRig" rig :-) ``` $ rigctl -l | grep FLRig 4 FLRig FLRig 1.4 Stable ``` Instead of taking a serial port path, hamlib...
@PhilTaken Yeah. The new build fixes a DNS leak reported in #104.
I feel the same, though Nebula itself is MIT: https://github.com/slackhq/nebula/pull/614#issuecomment-1072061924 As for what that means for this project, I was thinking about maintaining my own fork but really can't if...
Might have found a fix, actually. edit: nope, not threadsafe in any way. Still need to figure out a way to get the binding we're `eval`-ing code in into the...
The solution I thought up was storing the binding as state in the sandbox, then replacing line 156 with something like: ``` sandbox.get_current_binding.eval "`#{str}`" ``` However, this wouldn't be threadsafe....
IMO it's still a bug, and deviates from Ruby standard behavior. Consider the following code, where we redefine the ` method and evaluate `whoami` in its binding: ``` require 'shikashi'...
Let me check about the 1.9 series too
On `ruby 1.9.3p0`, same result: ``` ctx1, stock ruby: arctus ctx2, stock ruby: imaohw ctx1: shikashi: arctus ctx2: shikashi: arctus ``` Let me know what help you need if you...
Any updates on this? I've got some ideas, but it might involve adding a binding parameter to several methods in both evalhook and shikashi.