Bug #4992
Updated by Greg Shah over 5 years ago
There seems to be a locking issue that we're experiencing with @ParseFile@ (ObjectModelParser) and @WriteFile@ (JsonConstruct) looks like being related to memory mapped files and might just be Windows specific. I've put together a test in @oo/json/quirks/file_lock.p@ but then while writing this thought to check with plain input/output streams and it gives the same error `Unable to open... (98)`.
We have that in one of the tests for http client state management where we need to make sure we don't have any cookies persisted in the jar so we call @clearPersistentCookies@ which in turn override the cookie jar file after emptying the jar. That was silently failing before but after adding routine level option on JsonConstruct the error gets propagated, silently eating it is not a valid option imho anyway :)
We have that in one of the tests for http client state management where we need to make sure we don't have any cookies persisted in the jar so we call @clearPersistentCookies@ which in turn override the cookie jar file after emptying the jar. That was silently failing before but after adding routine level option on JsonConstruct the error gets propagated, silently eating it is not a valid option imho anyway :)