add explicit close to db

[avallecam]

• Please check if the PR fulfills these requirements

• I have read the CONTRIBUTING guidelines
• I created a new feature branch
• I have opened and refer to an issue or I am referring to an existing issue
• Lesson builds locally
• Checks have been run on GitHub and pass
• No output errors in the Rendered Changes link generated by github-actions

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix in readepi episode

• What is the issue you are addressing?

Fix #241
Fix #224
Fix #202

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials-early/compare/md-outputs..md-outputs-PR-240

The following changes were observed in the rendered markdown documents:

 md5sum.txt        |   2 +-
 read-case-data.md | 213 ++++++++++++++++++++++++++++++++++++++----------------
 2 files changed, 150 insertions(+), 65 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2026-06-18 11:47:14 +0000