Karan Lokchandani

icon company none

Results 38 comments of Karan Lokchandani

fix(validator): enforce subtyping depth limit during validation

I agree, this could cause chaos, I have just added more debug statements.

fix(validator): enforce subtyping depth limit during validation

I'm not sure why macos 14 arm 64 build fails, since it seems to be passing on the run I did on my fork and im on a m3 macbook...

fix(validator): enforce subtyping depth limit during validation

all commits squashed and pushed.

fix(validator): enforce subtyping depth limit during validation

I've removed ValidatorSubtypeNoGcTest as they shouldn't have been there in the first place ([discussion](https://github.com/WasmEdge/WasmEdge/pull/4134#discussion_r2136428134)). I initially added them thinking I had regressed a functionality, but after reviewing the spec, it...

fix(validator): enforce subtyping depth limit during validation

@q82419 Thanks for the review! I've addressed all the suggested refactors in the latest commit. LMK if anything else needs tweaking.

feat: add homeDirectory accessor to FileSystem

hey @cnaples79 are you still working on this?

Add RWKV Inference Plugin to WasmEdge

hey @ShigrafS are you still working on this?

bug: WasmEdge compiled mode outputs "Segmentation Fault"

This doesn't seem like an AOT-specific issue on my system am I doing something wrong here? On macOS, this is the behavior I observe with WasmEdge: ```bash > wasmedge --enable-all...

bug: WasmEdge compiled mode outputs "Segmentation Fault"

**update**: This is what i see on a fresh ubuntu VM install, it would seem like it does segfault on linux but not just in AOT but also in JIT...

bug: WasmEdge compiled mode outputs "Segmentation Fault"

@teyahb8 I'll try to work on this when I get some free time. In the meantime, could you confirm whether you see the StackOverflow in both JIT and interpreted modes...