You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After several reads of a file (.json or .txt for example), the file crashes and stops being read correctly.
For reading and writing I use (io.open(fileName, "r")) and (io.open(fileName, "w+")).
This has been happening since it was forced to have the files read within the same resource. Previously and for more than 5 years, this method had never failed even with very high read and write loads.
Expected result
The information in the files should be read correctly and not get a nil return
Reproduction steps
I request reading information to the file with a specific name and extension.
If the file does not exist, the file with a specific name and extension is automatically created.
Reads and writes are made to this file continuously every "X" seconds.
After reading and writing the file for several minutes (random time), the file breaks and becomes unreadable.
If I delete that broken file, everything works fine again until the new file breakage.
Importancy
Crash
Area(s)
FiveM
Specific version(s)
FiveM 12847, Server 12906 linux
Additional information
Highlight the change in the version of the artifact that began to force the files to be located within the resource itself
The text was updated successfully, but these errors were encountered:
This has been happening to me since the new versions of Artifacts. In my case, I can't read files outside my resource, which makes it difficult to work on some interconnections.
I saw this in the FiveM documentation, but in my case, I'm not trying to read a resource; I'm trying to read a path that is not a resource. Specifically: "/txData/default/data/playersDB.json"
Is there any alternative we might not be aware of?
What happened?
After several reads of a file (.json or .txt for example), the file crashes and stops being read correctly.
For reading and writing I use (io.open(fileName, "r")) and (io.open(fileName, "w+")).
This has been happening since it was forced to have the files read within the same resource. Previously and for more than 5 years, this method had never failed even with very high read and write loads.
Expected result
The information in the files should be read correctly and not get a nil return
Reproduction steps
Importancy
Crash
Area(s)
FiveM
Specific version(s)
FiveM 12847, Server 12906 linux
Additional information
Highlight the change in the version of the artifact that began to force the files to be located within the resource itself
The text was updated successfully, but these errors were encountered: