Modify ↓
Opened 3 years ago
Last modified 3 years ago
#21301 new defect
Broken format of message for invalid searches
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | template_report search invalid | Cc: |
Description
What steps will reproduce the problem?
- Have some data
- In Search Dialog, search for
id
What is the expected result?
A well formatted user instruction
What happens instead?
A message with format syntax
Please provide any additional information below. Attach a screenshot if possible.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-09-05 22:35:08 +0200 (Sun, 05 Sep 2021) Revision:18194 Build-Date:2021-09-05 20:36:08 URL:https://josm.openstreetmap.de/svn/trunk Identification: JOSM/1.5 (18194 en) Linux Debian GNU/Linux 11 (bullseye) Java version: 17-ea+19-Debian-1, Debian, OpenJDK 64-Bit Server VM Look and Feel: com.formdev.flatlaf.FlatDarculaLaf Environment variable LANG: en_US.utf8 System property file.encoding: UTF-8 System property sun.jnu.encoding: UTF-8 Locale info: en_US Numbers with default locale: 1234567890 -> 1234567890 Desktop environment: GNOME Plugins: + flatlaf (35799) Last errors/warnings: - 05514.176 W: org.openstreetmap.josm.data.osm.search.SearchParseError: Range of primitive ids expected - 05606.709 E: Handled by bug report queue: java.lang.NullPointerException: Cannot invoke "java.lang.CharSequence.length()" because "this.text" is null - 05680.388 W: org.openstreetmap.josm.data.osm.search.SearchParseError: Range of primitive ids expected - 05723.569 W: org.openstreetmap.josm.data.osm.search.SearchParseError: Range of primitive ids expected - 05790.037 W: org.openstreetmap.josm.data.osm.search.SearchParseError: Range of primitive ids expected - 06068.318 W: org.openstreetmap.josm.data.osm.search.SearchParseError: Range of primitive ids expected - 06219.019 W: org.openstreetmap.josm.data.osm.search.SearchParseError: <html>Expecting <code>:</code> after <i>id</i></html>
Attachments (1)
Change History (5)
by , 3 years ago
| Attachment: | josm_invalid_search_format.jpg added |
|---|
comment:1 by , 3 years ago
| Summary: | Broken message format for invalid searches → Broken format of message for invalid searches |
|---|
comment:2 by , 3 years ago
| Milestone: | → 21.09 |
|---|---|
| Owner: | changed from to |
| Priority: | normal → minor |
| Status: | new → assigned |
comment:3 by , 3 years ago
It happens with all expression ending with a colon (:) and not just with id.
comment:4 by , 3 years ago
| Milestone: | 21.09 |
|---|---|
| Owner: | changed from to |
| Status: | assigned → new |
Mmm seems to be a side effect of r16306.. Will check that later.
Note:
See TracTickets
for help on using tickets.
screenshot of message