stuf

log.md

@@ -1,5 +1,176 @@
 # Log
 
+## 2025-10-03
+
+### Tesflight and staging stuck AGAIN
+
+- testflight
+  - builds 1161 and 1162 fail again after the previous ones working
+  - In build 1162, it shows this error:
+  ```
+    Plan: 1 to add, 0 to change, 0 to destroy.
+
+    helm_release.lana_bank: Creating...
+
+    ╷
+
+    │ Error: installation failed
+
+    │ 
+
+    │   with helm_release.lana_bank,
+
+    │   on main.tf line 69, in resource "helm_release" "lana_bank":
+
+    │   69: resource "helm_release" "lana_bank" {
+
+    │ 
+
+    │ cannot re-use a name that is still in use
+
+    ╵
+
+    ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ Terraform Apply ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲
+
+    Failed To Run Terraform Apply!
+
+    2025/10/03 05:05:20 Apply Error: Failed to run Terraform command: exit status 1
+  ```
+  - In build 1161, it shows this error:
+  ```
+    ╷
+
+    │ Warning: Helm release created with warnings
+
+    │ 
+
+    │   with helm_release.lana_bank,
+
+    │   on main.tf line 69, in resource "helm_release" "lana_bank":
+
+    │   69: resource "helm_release" "lana_bank" {
+
+    │ 
+
+    │ Helm release "lana-bank" was created but has a failed status. Use the
+
+    │ `helm` command to investigate the error, correct it, then run Terraform
+
+    │ again.
+
+    ╵
+
+    ╷
+
+    │ Error: Helm release error
+
+    │ 
+
+    │   with helm_release.lana_bank,
+
+    │   on main.tf line 69, in resource "helm_release" "lana_bank":
+
+    │   69: resource "helm_release" "lana_bank" {
+
+    │ 
+
+    │ context deadline exceeded
+
+    ╵
+
+    ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ Terraform Apply ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲
+
+    Failed To Run Terraform Apply!
+
+    2025/10/03 04:07:58 Apply Error: Failed to run Terraform command: exit status 1
+
+  ```
+
+  - I go check the logs for build 1161 because it smells bad:
+    - the lana-bank-server container crashed with this error:
+    ```
+    Error: Couldn't parse config file
+
+    Caused by:
+        app: unknown field `root_folder`, expected `bucket_name` at line 2 column 3
+    ```
+    - Jiri jumps in and suggests that PR #2807 https://github.com/GaloyMoney/lana-bank/pull/2807 introduced some changes in the parsing of the config that are causing this problem (the config parsing has become stricter, and fields that are unknown )
+    - Also hightlights how the config in these private charts files is conflictive: it must be either local or gcp, not both:
+        - https://github.com/GaloyMoney/galoy-private-charts/blob/8b28e7f213b438a2664b71c44aeb3244c303fac6/charts/lana-bank/templates/config-map.yaml#L13-L16
+        - https://github.com/GaloyMoney/galoy-private-charts/blob/8b28e7f213b438a2664b71c44aeb3244c303fac6/charts/lana-bank/values.yaml#L24C1-L27C26
+    - I propose this PR to solve this conflict: https://github.com/GaloyMoney/galoy-private-charts/pull/1168
+    - Jiri proposes instead to modify the template file with this snippet:
+    ```
+    provider: {{ .Values.lanaBank.app.storage.provider }}
+    {{ if eq .Values.lanaBank.app.storage.provider "gcp" }}
+            bucket_name: {{ .Values.lanaBank.app.storage.bucketName }}
+    {{ end }}
+    {{ if eq .Values.lanaBank.app.storage.provider "local" }}
+            root_folder: {{ .Values.lanaBank.app.storage.rootFolder }}
+    {{ end }}
+    ```
+    - I merge his changes with this PR: https://github.com/GaloyMoney/galoy-private-charts/pull/1169
+    - That triggers testflight build 1163, which completes green
+  - Staging triggers build 1160 after that automatically
+  - Which fails
+    - because: 
+    ```
+        ╷
+
+        │ Error: installation failed
+
+        │ 
+
+        │   with module.lana-bank.helm_release.lana_bank,
+
+        │   on ../../../modules/lana-bank/main.tf line 87, in resource "helm_release" "lana_bank":
+
+        │   87: resource "helm_release" "lana_bank" {
+
+        │ 
+
+        │ cannot re-use a name that is still in use
+
+        ╵
+
+        ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ Terraform Apply ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲ ▲
+
+        Failed To Run Terraform Apply!
+
+        2025/10/03 09:37:42 Apply Error: Failed to run Terraform command: exit status 1
+    ```
+    - I'm tired of this helm release errors, I really need to understand what's borking this state in the cluster.
+    - Fuck it, I'll delete staging and trigger the CI pipeline manually again
+    - done, started build 1161 manually
+    - that does the trick, staging is up again
+
+## 2025-09-30
+
+Ideas for what to improve during oncall
+
+- We need alerts for CI important stuff failing
+    - How
+- Why don't we run bats tests in Cala Github CI?
+    - Lol we do
+
+Knowledge base new stuff
+- Link to video on how to debug on concourse
+- Add honeycomb and zenduty and add yourself to oncall rotation to onboarding checklist
+
+
+
+## 2025-09-18
+
+### Day summary
+
+- Today I reviewed José's PR (#2759) that changes some UUIDs for public ids in some parts of the regulatory reporting. I suggested that he improves some aliases names to avoid confusion.
+- I opened up PR #2765 to implement transaction details in the UIF report.
+
+Besides that, some thoughts:
+- José let me know that Meltano EL jobs from Postgres to Bigquery work as NON incremental append. So, if the source table has records A, B, C, and you run the EL twice, target tables ends up with A, B, C, A, B, C. That's the reason the staging models have such convoluted logic: to only load the "freshest" batch from Meltano. I let José know that I find to be Rube Goldberg-ian and that we definetely need to change it since it's just not acceptable, and that I have an experiment PR with Dagster on the way. He agreed we need to get rid of this.
+- Nicolas discussed about the offsite, making it clear that it's completely dependant on the outcomes of the budget discussion. El Salvador would be ideal, but if volcano doesn't move forward, Dubai or South East Asia might be discussed as alternatives since apparently for our Indian colleagues getting to El Salvador is a bureaucratic nightmare.
+
+
 ## 2025-08-13
 
 ### Meeting with Luis