Hi @nagyrobir , let's start - hot to coordinate this :) ?
@justb4 the tips:
tcp_keepalives_idle = 300 # TCP_KEEPIDLE, in seconds; # 0 selects the system default tcp_keepalives_interval = 30 # TCP_KEEPINTVL, in seconds; # 0 selects the system default tcp_keepalives_count = 10 # TCP_KEEPCNT;Are settings in
postgresql.conf. In another (non-GHC) project we needed those because of datacenter connectivity/firewall settings.
There is a lot of info on the web, as this is purely PostgreSQL related.
seems to work! in ther last couple of days the service is running with no issue and the graph are updated regularly :)
@nagyrobir in this case is just one file.po .. not really need to set-up a translation environment .. but that could be something good to learn in any case. we can follow https://github.com/geopython/GeoHealthCheck/pull/403/files --> I guess we want to fork geohealthcheck and make a new branch to start .. then add the directory/file: 'GeoHealthCheck/translations/no_NO/LC_MESSAGES/messages.po'
maybe cross check it. I am not native in Norwegian, but i think we can do a good enough job.
I have been busy with kid/ family.. I may take Kare of the Italian translation and share your Norwegian to one of my Norwegian colleague for review
@epifanio could you check it and merge it in if you agree with the translations?
@nagyrobir Yes,
Language support has been recently added to
pygeoapi also uses Babel (.po files). Info in the README there.Language support has been recently added to
pygeoapi, there is even a YouTube Presentation from FOSS4G 2021 by the developer.
@justb4
FYI https://nvd.nist.gov/vuln/detail/CVE-2021-43818
see Dependabot PR at geopython/GeoHealthCheck#411
Not yet, but especially if you run Docker on the Pi, that should be possible. Folks run HA on Pi for example with Docker: https://www.home-assistant.io/.
In plain Python (v3) on e.g. Raspbian should be possible as well if , a little more install-work.
In plain Python (v3) on e.g. Raspbian should be possible as well if , a little more install-work.
For running GHC on a raspi I changed the base image of the Dockerfile to
I guess it should be possible to use GitHub actions to also build Docker images for other architectures.
FROM arm32v7/python:3.7-alpine. Because my RaspberryPi has a ARM 32bit architecture. I built the image on the RaspberryPi - I took roughly 2hours :sweat_smile: I could not built the image on my computer, because it has another architecture.I guess it should be possible to use GitHub actions to also build Docker images for other architectures.
I can run GHC on the RaspberryPi using docker-compose. However, there is still an error with ghc_web. But I assume it is not related to the RaspberryPi:
Traceback (most recent call last):
File "/venv/lib/python3.7/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
worker.init_process()
File "/venv/lib/python3.7/site-packages/gunicorn/workers/geventlet.py", line 133, in init_process
self.patch()
File "/venv/lib/python3.7/site-packages/gunicorn/workers/geventlet.py", line 124, in patch
eventlet.monkey_patch()
File "/venv/lib/python3.7/site-packages/eventlet/patcher.py", line 296, in monkey_patch
from eventlet.support import psycopg2_patcher
File "/venv/lib/python3.7/site-packages/eventlet/support/psycopg2_patcher.py", line 27, in <module>
import psycopg2
File "/venv/lib/python3.7/site-packages/psycopg2/__init__.py", line 68, in <module>
from psycopg2 import extensions as _ext
File "/venv/lib/python3.7/site-packages/psycopg2/extensions.py", line 211, in <module>
from psycopg2. _range import Range # noqa
File "/venv/lib/python3.7/site-packages/psycopg2/_range.py", line 502, in <module>
oid=3904, subtype_oid=23, array_oid=3905)
File "/venv/lib/python3.7/site-packages/psycopg2/_range.py", line 283, in __init__
self._create_ranges(pgrange, pyrange)
File "/venv/lib/python3.7/site-packages/psycopg2/_range.py", line 302, in _create_ranges
if isinstance(pgrange, basestring):
NameError: name 'basestring' is not defined
@nagyrobir @epifanio there was an NO(rwegian) translation file somewhere? Could not find back.
If working with Git/PRs is a problem, you can open an issue and attach the .po file there.
If working with Git/PRs is a problem, you can open an issue and attach the .po file there.
@justb4 This should be the link to the file https://files.gitter.im/575f1fdcc2f0db084a1db0a6/JEQ5/NO.po
Ok, have at least opened the issue #414. Need to find time, but ideal first issue for newcomers.
That is how I started joining GHC dev (NL translations)!
That is how I started joining GHC dev (NL translations)!
Fixed annoying issue #418. CI/CD now successful again, was due to stale ESRI FeatureServer URL used in test fixtures.
@astroidex hope you as well. First make sure that each WMS Resource has the status
Every 1440 min is every 24 hour. What could be, if you just created the WMS Resources in GHC, that they are still to be run.
The Scheduler sets a random time for the first Run within the time delta of the frequency , as to prevent that many Probes run at the same time, e.g. after a restart. There were also some changes there recently like PR #385. But overall this could mean that when scheduled every 24h, it could take up to 24h for the first run.
Usually Resources run in terms of minutes so this effect is not visible. We may need to adapt the schedule randomizer.
Activ(e) True. That is the default.Every 1440 min is every 24 hour. What could be, if you just created the WMS Resources in GHC, that they are still to be run.
The Scheduler sets a random time for the first Run within the time delta of the frequency , as to prevent that many Probes run at the same time, e.g. after a restart. There were also some changes there recently like PR #385. But overall this could mean that when scheduled every 24h, it could take up to 24h for the first run.
Usually Resources run in terms of minutes so this effect is not visible. We may need to adapt the schedule randomizer.
@justb4, similarly to the question asked by Astrid, we have a resource that is schedule to run every 24 hrs to check the status code of a URL. That status code is updated depending on a file that is updated once daily. Currently, the random timing of the check makes it so that the check occurs a couple of hours before the change, and therefore we must wait a significant portion of the day before GHC notifies us again. Is there a possibility to run the check at a specific time via the web app without having to resort to the cron scheduling I see mentioned in the documentation?
@astroidex : did my answer clarify your situation?
@Dukestep : GHC uses an internal Python-based scheduler. There is no functionality to schedule at a specific time. The random timing was introduced to solve problems, a bit similar to "soldiers marching in-step on a bridge". This especially applied to smaller time-delta's. But 24h schedules could suffer from the current solution. Maybe for those cases the scheduling algorithm could be refined. Note that the randomness is (out of my head) only for the first run. From then the interval is constant.
Scheduling at exactly a specific time would be a new feature with some impact, like database (now only "frequency" in mins attribute).
@Dukestep : GHC uses an internal Python-based scheduler. There is no functionality to schedule at a specific time. The random timing was introduced to solve problems, a bit similar to "soldiers marching in-step on a bridge". This especially applied to smaller time-delta's. But 24h schedules could suffer from the current solution. Maybe for those cases the scheduling algorithm could be refined. Note that the randomness is (out of my head) only for the first run. From then the interval is constant.
Scheduling at exactly a specific time would be a new feature with some impact, like database (now only "frequency" in mins attribute).
#409 was just merged. Thanks to @jochemthart1 Vector Tiles Probe "MapBox TileJSON", got major fixes. Just tested three different implementations on GHC demo server that were all failing before, but are now succeeding. In several cases now a lat/lon parameter needs to be provided. Also T-rex working, heads up for @pka.