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
Describe the bug
When we try to schedule a custom mission the mission loader assumes that all missions are echo missions and tries to fetch the mission from echo using the source ID. This causes an error as the ID is not an integer for custom missions, but rather the hash of the tasks of the mission. The problem can be traced to the "GetMissionById" function in "EchoAndCustomMissionLoader.cs", which is expected to handle echo and custom missions, but which currently always assumes that we are using echo missions.
To Reproduce
There are some example custom missions in Dev. Running these will cause an exception the echo service.
Expected behavior
We currently store custom missions directly in the Source model. When scheduling a mission we can check whether this value is set, and, if so, use the SourceService to read in the mission. As a further improvement, we could add an enum to the Source model which can specify the mission loader to use for that mission.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
When we try to schedule a custom mission the mission loader assumes that all missions are echo missions and tries to fetch the mission from echo using the source ID. This causes an error as the ID is not an integer for custom missions, but rather the hash of the tasks of the mission. The problem can be traced to the "GetMissionById" function in "EchoAndCustomMissionLoader.cs", which is expected to handle echo and custom missions, but which currently always assumes that we are using echo missions.
To Reproduce
There are some example custom missions in Dev. Running these will cause an exception the echo service.
Expected behavior
We currently store custom missions directly in the Source model. When scheduling a mission we can check whether this value is set, and, if so, use the SourceService to read in the mission. As a further improvement, we could add an enum to the Source model which can specify the mission loader to use for that mission.
Screenshots
The text was updated successfully, but these errors were encountered: