That requires two steps:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 16 2024
D3291 can be use to deploy, IP in DNS record has been also been modified to match the server, not the IPFO.
Jan 15 2024
$ salt db-A-001 state.apply roles/dbserver-pgsql/monitoring db-A-001: ---------- ID: postgresql_monitoring_dependencies Function: pkg.installed Result: True Comment: The following packages were installed/updated: py39-pip Started: 21:40:59.667353 Duration: 2132.32 ms Changes: ---------- py39-pip: ---------- new: 23.3.2 old: ---------- ID: postgresql_monitoring_dependencies Function: pip.installed Name: lddcollect Result: True Comment: All packages were successfully installed Started: 21:41:02.873383 Duration: 4538.261 ms Changes: ---------- lddcollect==0.2.0: Installed ---------- ID: /usr/local/bin/check-postgresql-dependencies Function: file.managed Result: True Comment: File /usr/local/bin/check-postgresql-dependencies updated Started: 21:41:07.415152 Duration: 35.588 ms Changes: ---------- diff: New file mode: 0755 ---------- ID: /usr/local/bin/check-postgresql-xml-support Function: file.managed Result: True Comment: File /usr/local/bin/check-postgresql-xml-support updated Started: 21:41:07.450907 Duration: 32.835 ms Changes: ---------- diff: New file mode: 0755
Iodine is still maintained, and the DNS is already configured for Ysul, so why not reevaluate it with a live demo?
Alcali is still alive.
For example, when ICU was updated:
packages_prefixes
black
shellcheck
I've added documentation to https://agora.nasqueron.org/Operations_grimoire/FreeBSD#PostgreSQL without real conviction.
Fixed. Form works again.
I'm rebuilding PostgreSQL 15.4 with XML support on db-A-001.
Jan 14 2024
Jan 14 23:13:52 db-A-001 postgres[35351]: [7-1] 2024-01-14 23:13:52.659 UTC [35351] ERROR: unsupported XML feature
When upgraded to FreeBSD 14, we lost this.
When clicking to Save Progress:
Notification successfully reached the Notifications Center. Here an extract of the event through Sentry discover:
task_ids for task_instance.xcom_pull
Currently, the fetch pipeline fails at the notify step:
Rebase
Rebase. Bump Airflow version.
- Notification gate is singular
- Get FANTOIR connection from secret back-end
- Inject PATH in environment so we can find fantoir-datasource in /usr/local/bin
- Decode bytes and split lines into a list for stdout, stderr
Both fantoir-datasource fetch and fantoir-datasource import work correctly in airflow nasqueron shell: rows are correctly imported into PostgreSQL database.
Improve Makefile
Create table if it doesn't exist
Works fine. https://airflow.nasqueron.org/dags/fantoir_fetch/grid for example
TaskFlow DAGs are defined by a function, but that function needs to be called.
At the end of the TaskFlow DAG, function should be called, for example at the end of fantoir_fetch.py we need to add fantoir_fetch_dag().
s/dag/dags/g to be coherent with D3281
Fix state through Complector test deployment
Hunt insecable spaces