Infinite computing when creating new route

[axrolld]

What happened?

I'm trying to fix a hole in the infrastructure so i created a track link and now i want to add a new route, but looking for compatible routes between start and stop has been computing for 5mn without finding anything

What did you expect to happen?

It should either find a route or return an error.

How can we reproduce it (as minimally and precisely as possible)?

1. Go to infra editor
2. Select France_en_qualite
3. Try to create a new route between this detector
   
   And this one
   

What operating system, browser and environment are you using?

• Browser: Chrome
• OS: Win 11
• Env: staging

OSRD version (top right corner Account button > Informations)

1280353

[axrolld]

Edit: it appears that this bug came from an editoast crash (not 100% sure). But i can't reproduce it right now. This needs to be investigated.

[younesschrifi]

I've tried to reproduce this bug but it's impossible at the moment. As we discussed with @axrolld, it must have happened at a time when Editoast crashed.

[axrolld]

Bug reproduced on staging near Sète train station

[Tristramg]

I can reproduce the bug.
Only in the infra editor, not in a simulation.
Editoast is at 100% CPU but in the end it finds a solution.

The pathfind makes a huge loop. The computation ends, but it takes a very long time and might timeout.

When asking a path starting in the inverse direction we find the solution we want.

Both detectors are ApplicableDirections=BOTH

The signals are all in the same direction at the station

[younesschrifi]

suggestions:

• add 2 additional limits on the number of steps and the maximum cost of the path
• potentially remove the start direction field and have editoast find the best direction