-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[7947] Updated docs for checksum_read_buffer_size_in_bytes in server_… #285
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider adding some words to the Troubleshooting page with some key words that might lead people there who are experiencing the problem which inspired this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Found one last thing.
Once the final review comment is addressed, squash it.
4166b73
to
ced034f
Compare
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the commit message needs to be updated to refer to [irods/irods#7947], but otherwise looks good.
Do we need to hold on merging this until we approach releasing 4.3.4, or is that just the documentation in the S3 plugin? (See irods/irods_resource_plugin_s3#2217 (review))
… in server_config.json
ced034f
to
48be4f3
Compare
I made the commit message change without the pound. |
Let's leave this open until we're closer to a 4.3.4 release. |
Okay. I've written down the various PRs and their expected timings here: irods/irods#7947 (comment) |
Please look over / make suggestions for wording changes.
I will also update the README for the S3 plugin to point people to this setting if they have errors on checksum calculations.