You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Folks,
We've found that to get casperfpga working with our roach2 based system we need to add the additional patch of:
if hasattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE'):
setattr(katcp.CallbackClient, 'MAX_WRITE_BUFFER_SIZE',
katcp.CallbackClient.MAX_WRITE_BUFFER_SIZE * 10)
in katcp_fpga.py (v0.4.2) or probably in transport_katcp.py for v3.1 (untested). We aren't keen on this because it means forking and diving into internals.
Is there an undocumented way of perhaps calling casperfpga.katcp_fpga.KatcpFpga with a MAX_MESSAGE_LEN argument or some such so we can both avoid the write buffer overflow and mucking around with or forking the repo?
The text was updated successfully, but these errors were encountered:
Hi Folks,
We've found that to get casperfpga working with our roach2 based system we need to add the additional patch of:
in katcp_fpga.py (v0.4.2) or probably in transport_katcp.py for v3.1 (untested). We aren't keen on this because it means forking and diving into internals.
Is there an undocumented way of perhaps calling casperfpga.katcp_fpga.KatcpFpga with a MAX_MESSAGE_LEN argument or some such so we can both avoid the write buffer overflow and mucking around with or forking the repo?
The text was updated successfully, but these errors were encountered: