Debug Graft invocations
1. Enable byte-level Gateway logging
export GG_DEBUG=1 gg <module>
Warning: logs may contain sensitive payload bytes. Use only in controlled environments.
2. Verify the hosted surface
- Confirm the intended runtime in Gateway output.
- Open Vision on the configured HTTP port (default
81). - Compare discovered types/methods with your source.
- Re-copy the install command from this Gateway instance.
3. Verify Caller configuration
- Remote:
host/Hostset tows://orwss://before the first call. - In-memory: Receiver module locally resolvable.
- After config changes, restart the Caller process (context is cached).
4. Classify the failure
| Symptom | Likely cause |
|---|---|
FileNotFound Receiver DLL | inmemory without local module |
422 package generation | unsupported public type |
| Connection timeout | wrong host, proxy, or TLS termination |
| Missing method | filters, stale package, or discovery gap |
Receiver example
dotnet build ./Pricing/Pricing.csprojgg ./Pricing/bin/Debug/net9.0/Pricing.dll