ticket summary component version type owner created _changetime _description _reporter resolution 24858 Duplicate warning due to duplicated mapcss rule Core validator defect team 2026-08-19T19:27:44+02:00 2026-09-14T09:09:43+02:00 "==== What steps will reproduce the problem? 1. Validate https://www.openstreetmap.org/node/5847777765 2. Get two identical warnings for this node ==== Origin The following rules in JOSM's build-in rules exists twice in [https://josm.openstreetmap.de/browser/josm/trunk/resources/data/validator/deprecated.mapcss deprecated.mapcss], starting at lines 2338 and 2361 {{{#!mapcss /* #20421 */ *[transformer=minor_distribution] { throwWarning: tr(""{0} is deprecated"", ""{1.tag}""); suggestAlternative: ""transformer=distribution""; group: tr(""deprecated tagging""); fixAdd: ""transformer=distribution""; } *[transformer=traction] { throwWarning: tr(""{0} is deprecated"", ""{0.tag}""); suggestAlternative: ""transformer=main""; group: tr(""deprecated tagging""); fixAdd: ""transformer=main""; } *[transformer=auto] { throwWarning: tr(""{0} is deprecated"", ""{0.tag}""); suggestAlternative: ""transformer=* + windings:auto=yes""; group: tr(""deprecated tagging""); fixRemove: ""transformer""; fixAdd: ""windings:auto=yes""; } }}} The fix is probably simply removing these rules from one of the two locations. The duplicated rule was added in r19591 ==== Please provide any additional information below. Attach a screenshot if possible. {{{ Revision:19613 Build-Date:2026-08-12 01:42:58 Identification: JOSM/1.5 (19613 nl) Windows 11 64-Bit OS Build number: Windows 10 Home 25H2 (26200) Memory Usage: 400 MB / 24368 MB (196 MB allocated, but free) Java version: 21.0.12+8-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 1920x1080x32bpp@60Hz (scaling 1.00×1.00) Maximum Screen Size: 1920×1080 Best cursor sizes: 16×16→32×32, 32×32→32×32 System property file.encoding: UTF-8 System property sun.jnu.encoding: Cp1252 Locale info: nl_NL Numbers with default locale: 1234567890 -> 1234567890 VM arguments: [-Djpackage.app-version=1.5.19613, -XX:MaxRAMPercentage=75.0, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --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, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, -Djpackage.app-path=%UserProfile%\AppData\Local\JOSM\JOSM.exe] Dataset consistency test: No problems found Plugins: + OpeningHoursEditor (36493) + imagery_offset_db (36503) + pt_assistant (684) + reverter (36503) + tageditor (36503) + turnlanes-tagging (1786514827) + utilsplugin2 (36503) Tagging presets: + https://josm.openstreetmap.de/josmfile?page=Presets/ParkingLanes&zip=1 Map paint styles: + https://josm.openstreetmap.de/josmfile?page=Styles/Potlatch2&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1 + https://josm.openstreetmap.de/josmfile?page=Styles/Sidewalks&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/ParkingLanes&zip=1 - https://josm.openstreetmap.de/josmfile?page=Styles/PublicTransport&zip=1 + %UserProfile%\Documents\tijdelijke bestanden\josm-eigen.mappaint.mapcss Validator rules: + https://josm.openstreetmap.de/josmfile?page=Rules/ChargeRules&zip=1 + https://raw.githubusercontent.com/Famlam/OsmMapcssValidationNL/main/netherlands.validator.mapcss + https://josm.openstreetmap.de/josmfile?page=Rules/SuspiciousSwimming_Pool&zip=1 + %UserProfile%\Documents\GitHub\osmose-backend\plugins\TagFix_MultipleTag2.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\TagFix_Destination.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Structural.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Power.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Phone2.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\notprefix.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Construction2.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Colour.validator.mapcss + %UserProfile%\Documents\GitHub\osmose-backend\plugins\Bicycle.validator.mapcss + %UserProfile%\Documents\tijdelijke bestanden\josm-eigen.validator.mapcss Last errors/warnings: - 00000.321 W: extended font config - overriding 'filename.Malgun_Gothic=malgun.ttf' with 'MALGUN.TTF' - 00000.322 W: extended font config - overriding 'filename.Myanmar_Text=mmrtext.ttf' with 'MMRTEXT.TTF' - 00000.323 W: extended font config - overriding 'filename.Mongolian_Baiti=monbaiti.ttf' with 'MONBAITI.TTF' - 00000.700 E: java.security.KeyStoreException: Windows-ROOT not found. Oorzaak: java.security.NoSuchAlgorithmException: Windows-ROOT KeyStore not available }}} " Famlam fixed 20510 Default maximum memory setting (-Xmx) for distribution packages Core defect Don-vip 2021-02-20T17:36:17+01:00 2026-09-13T14:04:20+02:00 "Currently for our distribution channels we have following maximum heap memory settings: ||= distribution channel =||= maximum memory =|| || [[https://josm.openstreetmap.de/download/josm.jnlp|josm.jnlp]] || 2048m|| || [[https://josm.openstreetmap.de/download/windows/josm-setup.exe|Windows Installer]] || 2048m|| || [[https://josm.openstreetmap.de/download/macosx/josm-macosx.zip|macOS package]] || 8192m|| Two questions: 1. Why for macOS we have 4x more memory than for other platforms? 2. Why do we set this up anyway? As far as I've tested, Java defaults to 25% of physical memory and taking into account current configurations, I'd assume that for 90+% users, this would at least give us the same result or higher. On the other hand, when we have `-Xmx` occupying high percentage of physical memory, overall performance may be unsatisfying due to high swap usage For a start, I'd lower the macOS -Xmx to be on par with other platforms. See: #20443, #20497, #19937" wiktorn fixed 12858 "Layout of ""Get access token"" window" Core latest defect team 2016-05-22T06:57:33+02:00 2026-09-13T13:44:21+02:00 "Доброго времени. При попытке произвести (полу)авто-вход у меня неактивная кнопка ""Принять маркер доступа"" всегда, а при попытке полу-авто-входа у меня ничего не происходит после нажатия на кнопку ""Получить маркер доступа"" (если точнее, то что-то секунду грузится и всё, ничего не изменилось) Без обид, если составил неверно. Как сделать ручную авторизация не разобрался. Снимки ниже: https://habrastorage.org/files/ac7/401/e3e/ac7401e3e7cd4d4da8f4abf3b2767ca1.png https://habrastorage.org/files/962/bb7/b76/962bb7b76b934618acf43931f5ff7388.png r10168" anonymous irreproducible 22810 [PATCH][RFC] OSM OAuth 1.0a/Basic auth deprecation and removal Core defect team 2023-03-13T12:48:09+01:00 2026-09-12T16:01:42+02:00 "pnorman has indicated that they are now looking at [https://www.openstreetmap.org/user/pnorman/diary/401157 deprecating] HTTP Basic Auth and OAuth 1.0a. Do we want to start hiding the Basic Auth and OAuth 1.0a authentication methods from new users in a few months? OSM will be shutting down OAuth 1.0a and HTTP Basic Auth starting June 01, 2024. https://community.openstreetmap.org/t/oauth-1-0a-and-http-basic-auth-shutdown/108490" taylor.smock fixed