Summary
The user faced a gRPC message size issue during cluster runs, which affected their access to certain nodes' inputs and outputs. After receiving help, they resolved the initial issue and can now access data from the dashboard. However, they still cannot access outputs via FlyteRemote locally, despite configuring the settings in ~/.flyte/config.yaml. They discovered that changing the parameter locally requires modifying flytekit to set new gRPC options. The user is inquiring if there is an alternative method to change this parameter or if modifying flytekit is the only option. They also confirmed that they experience the same error when trying to fetch outputs with FlyteRemote.