I'm testing graphhopper for some days now but there is a strange problem
when a Location ist to far away for the next street graphhopper returns the error "not found"
the strange thing is that it works on the graphhopper-demo-server
I tried with alps, europe and now with the whole planet - the error keeps the same
so here it works: https://graphhopper.com/maps/?point=47.50562070,14.10270890&point=47.80000740,13.04219230&locale=de&layer=Lyrk
but not on my server: http://osm.testerl.webseiten.cc:8989/?point=47.50562070,14.10270890&point=47.80000740,13.04219230&locale=de&layer=Lyrk
is there a problem with my configuration? I played with index.highResolution ad index.maxRegionSearch but also without a change
other routes are working great
thanks for help :)
You can try to play with the settings "prepare.minOnewayNetworkSize=200" or decrease "prepare.minNetworkSize", this way the router does not get stuck in an (oneway) island.
Related
This issue has taken up all my day, and I can't figure out whats going on
I can see that my service worker is registered , however "sometimes" when I click offline in developer tools the ServiceWorker for my domain just disappears!!
But this is the main problem when I reload the app I see the following behaviour.
You can see the ngsw.json is loaded twice and the main.js is loaded 3 times! main.d3ae2084xxxx && main.bbe5073dxxxx && then main.d3ae2084xxxx again!
If I inspect the response of both ngsw.json requests you can see that both show main.d3ae2084xxxx as the correct version of main.js but it still loads main.bbe5073dxxxx...
First ngsw.json request
Second ngsw.json request
Whats even more frustrating is the actual loaded version is the previous main.bbe5073dxxxx...!!!!
If anyone has any ideas how this can be happening please let me know.
Update... So found out about this excellent little endpoint
https://you-app-url/ngsw/state
This will give you lots of debug information about your service worker.
In my case this
Driver state: EXISTING_CLIENTS_ONLY (Degraded due to failed
initialization: Hash mismatch (cacheBustedFetchFromNetwork):
https://dev-xxxx.net/main.eb8468bb3ed28f02d7c2.js: expected
b5601102b721e0cf777691d327dc965d40d1c96e, got
83c18fdb4a5942c964a31c119a57e0b8e16fe46e (after cache busting)
So looks like this is going to be a CDN issue of some sort in my case, will update with an answer when I know for sure.
You've probably resolved this by now, but I had the same issue which turned out to be due to the CDN (Cloudflare in my instance) was optimising the content.
In Cloudflare the key option is 'Auto minify' that needs to be disabled.
On a script which has been working fine for some time and unchanged, today I get
'Execution failed: Data storage error'
on a line which consists simply of:
PropertiesService.getScriptProperties().setProperty('runMode', 'LIVE');
What can I do to fix this?
Is this some kind of server error?
It's an error from Google. An issue as already been submitted, you can upvote it (click the star in the title) : https://code.google.com/p/google-apps-script-issues/issues/detail?id=6856
[EDIT] Seems to be up and running now.
Yes, the google-apps-scripts-issues 6856 describes the problem exactly, as experienced today by dozens of users. Appears to have been fixed at approx 14:00 GMT 24-Mar-17.
Would like to know whether we need to code around the possibility of a repeat of this error.
In one of our client deployments of jboss5.1 mysql and an JSF application we get this one line error
16:46:08,970 ERROR [org.jboss.aspects.tx.TxPolicy] [] - [] (WorkManager(2)-17) javax.ejb.EJBTransactionRolledbackException
it happens every 15 seconds eaven if we dont have any chron jobs on that time scale.
We have two ears deployed on the server and if I undeploy one of them the error stops. So it must be something related to the aplication. The strange thing is that we have not touched that ear for a long time and this error started to appear withowt redeploy or any code change.
Any hints on how can I dig furthure to resolve this strange error?
go look at the following link
https://community.jboss.org/message/830295
https://community.jboss.org/message/635405?_sscc=t
I'm using this example to test geolocation API http://www.w3schools.com/html/tryit.asp?filename=tryhtml5_geolocation_error
But, I always get Location information is unavailable. message. I tested it on different browsers, same problem. I have geolocation enabled in browser.
Also, I tried uploading this to a local server (XAMPP), but problem remains (same error code).
What am I doing wrong here, its taking me hours now?...I appreciate any help on this, thank you.
EDIT: When I try to locate myself using this service http://www.hostip.info/index.html its giving me error message ... actually we haven't a clue.. When I type in some random IP address, works perfect. Whats going on here?
Has anyone tried accessing bungie.net reach stats api (statistics from Halo Matchmaking)?
As described here http://www.bungie.net/fanclub/statsapi/Group/Resources/Article.aspx?cid=545064
I can't seem to get any data returned, for example if i use this (with correct API key and gamertag values of course) ignore the first 2 asterisks ...
**http://www.bungie.net/api/reach/reachapijson.svc/player/details/byplaylist/MyIdentifierAPIkey/Gamertag
I don't receive a response - but no errors either, am i doing something wrong?
looking to use this for a Titanium (appcelerator) app eventually.
Any help or advice welcome, thanks in advance.
Unfortunately the API is not yet live to the public. I asked in a Private Message. They didn't say when it would be live.
In the Docs that Achronos posted, he put spaces in the URL's, I'm not sure if those are supposed to be there or not, so I tried it with the spaces and I got a 403 Forbidden error page. When I remove all the spaces, I get an error page that says:
Request Error
The server encountered an error processing the request. See server logs for more details.
I kinda can't check the server logs though... Bungie did say they were having some issues with the site though, so this might be a biproduct of that. I want them to get it working soon though, I wanna see just what it can do!