Modify ↓
#21604 closed defect (fixed)
Mapillary plugin: NullPointerException - MapillaryImageUtils.lambda$getImage$3
Reported by: | richlv | Owned by: | taylor.smock |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin mapillary | Version: | tested |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Download Mapillary images.
- Click around.
- That's about it.
What is the expected result?
No exception.
What happens instead?
Exception.
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2021-11-01 23:05:46 +0100 (Mon, 01 Nov 2021) Build-Date:2021-11-01 22:25:18 Revision:18303 Relative:URL: ^/trunk Identification: JOSM/1.5 (18303 en_GB) Mac OS X 10.15.7 OS Build number: Mac OS X 10.15.7 (19H1419) Memory Usage: 1985 MB / 3641 MB (943 MB allocated, but free) Java version: 1.8.0_311-b11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Look and Feel: com.apple.laf.AquaLookAndFeel Screen: Display 1127230987 1920×1080 (scaling 1.00×1.00) Display 69733382 1680×1050 (scaling 1.00×1.00) Maximum Screen Size: 1920×1080 Best cursor sizes: 16×16→16×16, 32×32→32×32 System property file.encoding: UTF-8 System property sun.jnu.encoding: UTF-8 Locale info: en_GB Numbers with default locale: 1234567890 -> 1234567890 VM arguments: [-Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlp.tk=awt, -Djnlpx.jvm=<java.home>/bin/java, -Djnlpx.splashport=-1, -Djnlpx.home=<java.home>/bin, -Djnlpx.remove=false, -Djnlpx.offline=false, -Djnlpx.relaunch=true, -Djnlpx.session.data=/var/folders/nl/flqxqsmj5q963r7tcnfrdt3c0000gn/T/session8843543126710251302, -Djnlpx.heapsize=NULL,NULL, -Djava.security.policy=file:<java.home>/lib/security/javaws.policy, -DtrustProxy=true, -Djnlpx.origFilenameArg=/Users/richlv/Library/Application Support/Oracle/Java/Deployment/cache/6.0/56/1ee8cfb8-72e8e992, -Dsun.awt.warmup=true, -Djava.security.manager] Dataset consistency test: No problems found Plugins: + HouseNumberTaggingTool (35814) + InfoMode (35543) + Mapillary (2.0.0-alpha.48) + PicLayer (1.0.1) + apache-commons (35524) + apache-http (35589) + buildings_tools (35823) + dataimport (35640) + ejml (35458) + geotools (35458) + imagery_offset_db (35640) + jaxb (35543) + jna (35662) + jts (35458) + measurement (35640) + opendata (35803) + pbf (35825) + photo_geotagging (35783) + reverter (35846) + utilsplugin2 (35856) Map paint styles: - https://josm.openstreetmap.de/josmfile?page=Styles/Coloured_Streets&zip=1 Last errors/warnings: - 01037.071 E: org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: Failed to authorise OAuth request 'EpAAbbt3MdmZtf11rRWGzYH3roSiOWyx5dkuzAeZ' - 01037.079 E: OAuth authorisation failed - <html>The automatic process for retrieving an OAuth Access Token<br>from the OSM server failed.<br><br>Please try again or choose another kind of authorisation process,<br>i.e. semi-automatic or manual authorisation.</html> - 01149.257 E: org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: Failed to authorise OAuth request 'EpAAbbt3MdmZtf11rRWGzYH3roSiOWyx5dkuzAeZ' - 01149.264 E: OAuth authorisation failed - <html>The automatic process for retrieving an OAuth Access Token<br>from the OSM server failed.<br><br>Please try again or choose another kind of authorisation process,<br>i.e. semi-automatic or manual authorisation.</html> - 01304.781 E: org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: stream is closed. Cause: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: stream is closed. Cause: java.io.IOException: stream is closed - 01304.789 E: Request Failed - <html>Retrieving an OAuth Access Token from 'https://www.openstreetmap.org/oauth/access_token' failed.</html> - 01323.863 E: org.openstreetmap.josm.gui.oauth.OsmOAuthAuthorizationException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: stream is closed. Cause: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: stream is closed. Cause: java.io.IOException: stream is closed - 01323.873 E: Request Failed - <html>Retrieving an OAuth Access Token from 'https://www.openstreetmap.org/oauth/access_token' failed.</html> - 01514.120 W: JCS - Silent failure during download: https://scontent.frix9-1.fna.fbcdn.net/m1/v/t6/An8ux-kTp6BwMD2dG4mTfm3tsqKkaRadXQ-lp5NYqp5WovbarJqF4sfMIEOCDOAnXsNS8N759CFSTjrRdTJ5MWPD2A2F8P7sub2LiEMRfY_J_kOJ4ALg-2HMcpfkEYqReTrDW8W0ybr73ziGhHkuQg?stp=s2048x1536&ccb=10-5&oh=1b79ccf16bf2317d9b263f46b88fef69&oe=61A66CB4&_nc_sid=122ab1 - 01514.134 E: Handled by bug report queue: java.lang.NullPointerException === REPORTED CRASH DATA === BugReportExceptionHandler#handleException: No data collected. Warning issued by: BugReportExceptionHandler#handleException === STACK TRACE === Thread: Mapillary-image-downloader-2 (339) java.lang.NullPointerException at org.openstreetmap.josm.plugins.mapillary.utils.MapillaryImageUtils.lambda$getImage$3(MapillaryImageUtils.java:142) at org.openstreetmap.josm.data.cache.JCSCachedTileLoaderJob.finishLoading(JCSCachedTileLoaderJob.java:265) at org.openstreetmap.josm.data.cache.JCSCachedTileLoaderJob.run(JCSCachedTileLoaderJob.java:243) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Attachments (0)
Change History (4)
comment:1 by , 4 years ago
Summary: | Mapillary plugin: NullPointerException → Mapillary plugin: NullPointerException - MapillaryImageUtils.lambda$getImage$3 |
---|
comment:2 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 4 years ago
No problem. There will probably be another location where it appears, but it will (hopefully) have more/better information (AKA a better stack trace). I haven't seen it in my testing yet.
Note:
See TracTickets
for help on using tickets.
Fixed in 2c91955d7a05657477ec9a657fd1bb6c03dcd594.