wrong order of transport relation member's after member split if the member drives to a round about

[Bibi <jean-yvon.landrac@…>]

What steps will reproduce the problem?

1. create a PTV2 relation with at least a way driving to a round-about.
2. split the way.

What is the expected result?

Member's order in the PTV2 relation should remain logical.

What happens instead?

The order was wrong.

Please provide any additional information below. Attach a screenshot if possible.

During the Changeset: ​https://www.openstreetmap.org/changeset/161165941#map=19/47.582513/-2.692487, the way D 310 (​https://www.openstreetmap.org/way/295076007) was cut, creating the way D 310 (​https://www.openstreetmap.org/way/1349758227#map=19/47.582513/-2.692487).
The relationship ​https://www.openstreetmap.org/relation/9292178 has been updated, but the order of the members isn't correct if one of the ends of the way is on a traffic circle, here Giratoire de Kermarch (​https://www.openstreetmap.org/way/1026187060#map=19/47.582513/-2.692487), possibly because the junction=roundabout is not treated as oneway=yes.

Please note that the creator of the bug is not the reporter due to language issues. The reporter is not even the contributor that created the issue.
Nevertheless configurations should be similar. If needed I can ask to copy/paste reporter environment description.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2025-01-02 12:51:21 +0100 (Thu, 02 Jan 2025)
Revision:19277
Build-Date:2025-01-03 02:30:34
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (19277 fr) Linux Mint 20.3
Memory Usage: 456 MB / 11680 MB (48 MB allocated, but free)
Java version: 21.0.5+11-LTS, Eclipse Adoptium, OpenJDK 64-Bit Server VM
Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel
Screen: :0.0 1920x1200x[Multi depth]@60Hz (scaling 1.00×1.00)
Maximum Screen Size: 1920×1200
Best cursor sizes: 16×16→16×16, 32×32→32×32
Environment variable LANG: fr_FR.UTF-8
System property file.encoding: UTF-8
System property sun.jnu.encoding: UTF-8
Locale info: fr_FR
Numbers with default locale: 1234567890 -> 1234567890
Desktop environment: XFCE
libcommons-logging-java: libcommons-logging-java:all-1.2-2
fonts-noto: fonts-noto:all-20200323-1build1~ubuntu20.04.1
VM arguments: [--module-path=/usr/share/openjfx/lib, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, -Djosm.restart=true, -Djava.net.useSystemProxies=true, -XX:MaxRAMPercentage=75.0, --add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED]
Program arguments: [‐Dlog4j2.formatMsgNoLookups=True]
Dataset consistency test: No problems found

Plugins:
+ CommandLine (36344)
+ FastDraw (36344)
+ FixAddresses (36344)
+ Mapillary (1789)
+ OpeningHoursEditor (36344)
+ PicLayer (1.0.3)
+ SeaChart (36349)
+ SeaMapEditor (36345)
+ apache-commons (36349)
+ cadastre-fr (36344)
+ conflation (0.6.11)
+ ejml (36348)
+ geotools (36349)
+ jackson (36349)
+ jaxb (36349)
+ jts (36349)
+ opendata (36354)
+ reverter (36354)
+ tageditor (36350)
+ todo (141)
+ utilsplugin2 (36362)
+ wikipedia (418)

Tagging presets:
+ https://raw.githubusercontent.com/OpenNauticalChart/josm/master/INT-1-preset.xml
+ https://josm.openstreetmap.de/josmfile?page=Presets/DamageTagging&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/BAR-damage-assessment&zip=1
+ https://raw.githubusercontent.com/Sowa1980/Natural_disasters_disasters_danger_preset/master/Natural%20disasters_disasters_danger_preset.zip
+ https://raw.githubusercontent.com/yopaseopor/traffic_signs_preset_JOSM/master/FR.zip
+ https://josm.openstreetmap.de/josmfile?page=Presets/DisasterDamageAssessment&zip=1

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/BAR-damage-assessment&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Styles/DisasterDamageAssessment&zip=1

Last errors/warnings:
- 00035.518 W: Impossible de trouver le fichier '‐Dlog4j2.formatMsgNoLookups=True'.

[skyper]

Yes, I can reproduce after reverting the changeset. Another case where the sort function in the relation editor sorts properly but the cut action fails. A special case though as the uncut roundabout makes it more tricky.

[skyper]

example file; split node named "split"