Adds tests to ensure context remains "stable" through multiple reloads #443
Conversation
|
@bplatz Might it be related to this change? https://github.com/fluree/db/pull/437/files#diff-a5569ed9d3dfd9a2bc3db76de1bc16f90dfa375e70099274139f8e24a8833cdaL420-R416 |
|
|
||
| (deftest ^:integration default-context-stability-file | ||
| (with-tmp-dir storage-path | ||
| (let [conn @(fluree/connect |
There was a problem hiding this comment.
Small thing but it would be good to configure our editors to treat with-tmp-dir as a two-level indent form instead of an align-args form. So you would have this instead:
(with-tmp-dir storage-path
(let ...))There was a problem hiding this comment.
In Cursive you can either do that by configuring the indent directly or by telling it to resolve this as one of the core with-... forms it already knows about from the "context actions" menu (right click on with-tmp-dir and select "Show Context Actions"). One of those might get it to understand that you're defining storage-path here as well.
Agh... I think you are correct. I wrote the tests wrong, so this is testing the wrong thing. Let me correct them and see if they break. |
@aaj3f was investigating an issue via http-api-gateway where after multiple transactions the default context seemed to revert back to the connection default.
We confirmed this behavior looking at the commit files written, and they do in fact loose all reference to the default context file.
I threw together these tests to attempt to replicate the issue, but they all pass. I figured they are good tests to have regardless.