Do not open already generated ZGY file ReadWrite
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
The SEGYtoZGY converter opens the newly generated ZGY file after the ZGY file has been stored to get the actual file size. This open does not need to be (and should not be) as ReadWrite. In the issue here, the open will fail due to lack of privileges unless the file is opened as ReadOnly the second time.
Edited by Erik Dahl