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
Since writeOne() checks if the file size exceeds the limit after writing the data instead of checking if writing the data will cause the file size to exceed the limit before writing, this causes the maximum file size to be maxBytesPerFile + maxMsgSize + 3.
The text was updated successfully, but these errors were encountered:
Good catch, I suppose we should do this check the other way around and from a quick scan of the code I think everything else should work (particularly after #23)
ploxiln
added a commit
to ploxiln/go-diskqueue
that referenced
this issue
Sep 12, 2021
Since writeOne() checks if the file size exceeds the limit after writing the data instead of checking if writing the data will cause the file size to exceed the limit before writing, this causes the maximum file size to be maxBytesPerFile + maxMsgSize + 3.
The text was updated successfully, but these errors were encountered: