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

[Kraken]: Journey status is NO_SERVICE if stop used is deleted by disruption #3995

Merged
merged 2 commits into from
May 5, 2023

Conversation

pbougue
Copy link
Contributor

@pbougue pbougue commented May 4, 2023

  • Some small refactors to share code in kraken
  • Update doc (also in navitia-proto)
  • Adjust bypass_disruption link creation
  • Tests (ability to send both chaos and kirin disruptions)

JIRA: https://navitia.atlassian.net/browse/NAV-1987 + https://navitia.atlassian.net/browse/NAV-1990

…uption

* Some small refactors to share code in kraken
* Update doc (also in navitia-proto)
* Adjust bypass_disruption link creation
* Tests (ability to send both chaos and kirin disruptions)

JIRA: https://navitia.atlassian.net/browse/NAV-1987 +
https://navitia.atlassian.net/browse/NAV-1990
@pbougue pbougue requested review from kadhikari and pbench May 4, 2023 07:35
If status is already NO_SERVICE from pt_not_served_in_rt, it's useless to
also iterate over disruptions.
@sonarqubecloud
Copy link

sonarqubecloud bot commented May 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 16 Code Smells

81.3% 81.3% Coverage
0.0% 0.0% Duplication

@pbougue pbougue merged commit ce50723 into dev May 5, 2023
@pbougue pbougue deleted the journey_status_no_service branch May 5, 2023 16:39
@kadhikari kadhikari changed the title [Kraken] Journey status is NO_SERVICE if stop used is deleted by disruption [Kraken]: Journey status is NO_SERVICE if stop used is deleted by disruption May 9, 2023
pbougue pushed a commit that referenced this pull request Aug 7, 2023
Sometimes none is available because the whole VJ is removed.
So getting the freshest returns a VJ unusable in RT.

Fixes almost "invisible" bug in
#3995: case of a trip being
canceled by a disruption without NO_SERVICE effect (see fixed test).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants