There are situations where a file close should fail that we don't currently capture. The scenario is:
1) Open a transaction in a session.
2) Make updates to a file from a second transaction.
3) Close the second session (so there are no references to the file).
4) Wait for the handle sweep code to close the file.
The handle sweep code will close the file handle, which requires that all updates are written, but the open transaction means that update can't be written yet.
The handle close should fail if there are updates that can't be written.
We'll need to add a flag to
Unable to find source-code formatter for language: ___wt_evict_file```. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
so it knows what to do when when a page is dirty after it's been written. We will also need to update the code in
__conn_dhandle_sweep{{`}} to not remove the handle from the list if it has un-writeable updates.