[Communication] Delete folder in starting communication is not working in many occasions, simulation gets stuck

[loumalouomega]

In line:

CoSimIO/co_sim_io/sources/communication/communication.cpp

Line 151 in f0e46e7

fs::remove_all(mCommFolder, ec);

I assume you are aware, but many times the simulation gets stuck because this remove folder fails and instead of an error a message is thrown, maybe is a good idea to make this an actual error. I prefer to get an error that get stuck ad infinitum. Furthermore, I am solving the problem locally, removing the folder before the simulation starts, so there is no conflict of permissions/lecture/reading/etc...

[philbucher]

Hm this has not happened to me yet

Which OS?

[loumalouomega]

More in windows than Linux, but also happened to me in Linux

[philbucher]

I had plenty of similar issues, but never this particular one
Snd I tested it extensively under different systems
Do you know about others having the same problem or is it just you?

I need to think about this 🤔

(Btw you can disable the comm in folder)

[loumalouomega]

I am just informing, we solved the problem locally

[philbucher]

How?

[loumalouomega]

Removing the folder before invoking the simulation, so no permissions conflict

[philbucher]

Ah so it is a permissions issue?

[loumalouomega]

Ah so it is a permissions issue?

Yes:

Furthermore, I am solving the problem locally, removing the folder before the simulation starts, so there is no conflict of permissions/lecture/reading/etc...

[philbucher]

Sorry didn't understand exactly

Can you please describe the different errors in more detail?

You say it hangs, but permission issues usually throw

[loumalouomega]

The message of error removing the folder appears, then it gets stuck. That's why I recommend changing the message for an error message instead.

[philbucher]

Does the primary side (the one that does the folder stuff) get stuck or the other one?

[loumalouomega]

The primary side is stuck because the secondary gets stuck. The primary just throws a warning, that's why I recommend changing the warning for an error.