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
When working with HDF5 I realized that HDF5 allows for writes with length of 0, this results current in an j_object_write call of size 0 which will trigger an error because the data buffer is NULL because there are no data to transfer.
Now the question:
should the user/our HDF5 integration catch writes of size 0, or
should the object client just swallow a write request if data == NULL && size == 0
FYI: if we currently write something of length 0 but with a "valid" pointer, we will send a message with payload 0
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When working with HDF5 I realized that HDF5 allows for writes with length of 0, this results current in an
j_object_write
call of size 0 which will trigger an error because the data buffer is NULL because there are no data to transfer.Now the question:
data == NULL && size == 0
FYI: if we currently write something of length 0 but with a "valid" pointer, we will send a message with payload 0
Beta Was this translation helpful? Give feedback.
All reactions