Klesh Wong
Klesh Wong
Maybe we should skip those records without `started_at` value? What do you guys think.
@Brend-Smits . Good job, thanks for the PR.
@dsiebel @Joerg-Tech @charltonaustin Seems like you are getting errors from different tables/entities. Can you all share the detailed log like @charltonaustin ? Thanks
@petkostas Great investigation, much appreciated. I personally prefer using `*time.Time` for fields that are nullable and setting them to `nil` accordingly. For cases where we discover mismatches, we can handle...
Sounds good to me. > [@klesh](https://github.com/klesh) I did a quick check on the DB schema, and the fields are nullable :) so we should be able to just replace the...
Can you log into the mysql container and check if there is any record in the `_devlake_migration_history` table?
This could help: https://dba.stackexchange.com/questions/99304/use-db-name-takes-too-long-to-change-when-login-remotely > Delete all devlake pvc and pv, and re-install helm chart, proceed migration process. Wait a few mins and it successfully landed to the DevLake home...
@diwangcanada I am not familiar with helm-chart. Can you check why it got killed on the first boot? I think we need to address the problem because there were already...
> > @diwangcanada I am not familiar with helm-chart. > > Can you check why it got killed on the first boot? I think we need to address the problem...
> install helm chart because of the protection. This is properly by design, but does it make more sense to set pv reclaim policy I think it makes more sense...