New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken with latest Mapnik #107
Comments
Can you paste "npm list" output? Also, which node version? (How much I regret the NodeJS choice, amigo! That's unmaintainable unless you have a team of ten people to continuously checks all the conflicts with the thousands of dependencies and dependencies of dependencies that get upgraded on and on without any consideration for retrocompatibility over time…) |
stderr
fwiw, it was working, then in the middle of zooming in, it stopped. |
can you try |
Seems to work now |
with this specific version or without any change? |
with |
OK, so I need to investigate the problem with newer Mapnik version. @springmeyer any clue from the top of your head given the stacktrace on #107 (comment) ? |
I didn't notice any problems with latest master and |
Sorry about this breakage hitting in a patch release. That is my fault - I should have bumped at least the minor of node-mapnik, but this slipped by me. More details (and the recommended workaround) at mapnik/node-mapnik#590. |
To follow semver, should a 3.4.17 be released with it reverted and 3.5.0 be released with this change? |
@pnorman v3.4.17 has now been released with a back compatibility fix (https://github.com/mapnik/node-mapnik/blob/master/CHANGELOG.md#3417). Now any invalid indexes will be skipped rather than erroring out. This effectively makes using the new index format opt-in. |
Cool, thanks Dane, I'll bump explicitly the patch version then :) |
A
git clean -xfd
and newnpm install
did not fix this. Version 4c6fa1cThe text was updated successfully, but these errors were encountered: