Mikołaj Kuranowski
Mikołaj Kuranowski
Updating `cofigparser` unravels another dependency issue with `itsdangerous`; which in turn needs to be downgraded to 2.0.1. ``` Traceback (most recent call last): File "/home/mikolaj/Desktop/tables/excalibur/bin/excalibur", line 5, in from excalibur.cli...
```python import pyroutelib3.util pyroutelib3.util.SEARCH_LIMIT = 100_000 ``` Should do the trick, tough modifying what are essentially constants isn't perfect practice.
Seems similar to #16, but partially through OSM just decided you've downloaded too many tiles per unit time. Try to reproduce with local file first, and possibly for inter-city car...
Even if PATH literally points to the **binary** (not just a symlink) this issue persists ```terminal $ echo "$PATH" /home/mikolaj/.local/share/bin:/home/mikolaj/.local/bin:/home/mikolaj/.local/share/go/bin:/home/mikolaj/.local/share/cargo/bin:/home/mikolaj/Documents/External-Software/nim/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl $ which nim /home/mikolaj/Documents/External-Software/nim/bin/nim $ stat "$(which nim)" File: /home/mikolaj/Documents/External-Software/nim/bin/nim...
Note that `/home/mikolaj/.local/share/bin/` or `/home/mikolaj/Documents/External-Software/nim/bin/` are added to the path in `$HOME/.zshrc`; which would *normally* not be visible to programs launched from a DE. **However**, [VS Code sources `.zshrc`](https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-fails) so...
Launching VS Code from terminal (with changed PATH) makes the extension work. This should mean that the extension does not properly inherit/query VS Code environment.
After the run command add Java argument '-Xmx2G' where 2 stands for amount of GB you want to allocate for gtfs-editor. For 32bit Java the max is around 1.7GB (so...
As it goes from my own experience, 2GB of RAM is needed to be assigned to gtfs-editor to allow exporting and importing GTFS feed. I didn't check actual RAM need...
This issue still persists on v0.3.2 after installing the dbus config file (`make install`)
I have the same finding, 0.2.4 works fine; 0.3.1 and 0.3.2 no (0.3.0 does not build). git bisect suggest that the bug was introduced in 918ea63755a66d69373d7da431b61203fa878b41.