Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

editoast: signals are not cached for search during import #3887

Closed
leovalais opened this issue Apr 13, 2023 · 1 comment · Fixed by #4403
Closed

editoast: signals are not cached for search during import #3887

leovalais opened this issue Apr 13, 2023 · 1 comment · Fixed by #4403
Assignees
Labels
area:editoast Work on Editoast Service kind:bug Something isn't working severity:major Major severity bug

Comments

@leovalais
Copy link
Contributor

What happened?

During an infra import, track sections are imported after signals so when the insertion triggers of osrd_infra_signalmodel is triggered, the track section of the new signal doesn't exist yet and therefore the signal is not cached in osrd_search_signal.

What did you expect to happen?

The new signals should all be cached after the import completes.

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

  1. Import a new infra
  2. Check osrd_search_signals
  3. The signals of the new import are not there

What operating system, browser and environment are you using?

N/A

OSRD version (top right corner Account button > Informations)

dev

@leovalais leovalais added kind:bug Something isn't working area:editoast Work on Editoast Service severity:major Major severity bug labels Apr 13, 2023
@celine-sncf
Copy link

@leovalais

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:editoast Work on Editoast Service kind:bug Something isn't working severity:major Major severity bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants