Dekart stop working with no error messages (deadlock) about dekart

[delfrrr]

I was able to reproduce dead lock here https://github.com/dekart-xyz/dekart/blob/v0.7.0/src/server/report/report.go#L36
Getting my head around it

[philipmargeotab]

Some example errors (with identifying data removed):

googleapi: Error 403: Access Denied
googleapi: Error 404: Not found
googleapi: Error 400: Unrecognized name

these errors caused the self-hosted website to crash.

[delfrrr]

Hey @philipmargeotab will try to help you. I'm running Dekart instance on GCP for the Playground, so it should be possible.

Can you please tell:

• which version do you use
• copy here app.yaml (without sensitive details of course)

Also can you please set DEKART_LOG_DEBUG: "1" in env_variables and share here logs

[philipmargeotab]

Version is 0.7
###

# https://cloud.google.com/appengine/docs/flexible/custom-runtimes/configuring-your-app-with-app-yaml#intro
service: dekart-test
runtime: custom
env: flex

manual_scaling:
instances: 1 # important as dekart designed to work on single instance

resources:
memory_gb: 64.0 # recommended to handle up to 1M points
cpu: 16
disk_size_gb: 100

env_variables:
DEKART_LOG_DEBUG: "1"
DEKART_POSTGRES_DB: "xxxxxx"
DEKART_POSTGRES_USER: "xxxxxx"
DEKART_POSTGRES_PASSWORD: "xxxxxx"
DEKART_POSTGRES_PORT: "xxxx"
# see https://cloud.google.com/sql/docs/mysql/connect-app-engine-flexible
DEKART_POSTGRES_HOST: "10.x.x.x" # UNKNOWN
DEKART_CLOUD_STORAGE_BUCKET: "geotab-dekart-test" # "$BUCKET"
DEKART_BIGQUERY_PROJECT_ID: "test-xx" # "$PROJECT_ID"
DEKART_MAPBOX_TOKEN: "pk.eyxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" #
# "$MAPBOX_TOKEN"

beta_settings:
# see https://cloud.google.com/sql/docs/mysql/connect-app-engine-flexible
cloud_sql_instances: "test-xx:europe-west1:dekart-db=tcp:xxxx"
# "$PROJECT_ID:europe-west1:$DB_INSTANCE_NAME=tcp:xxxx"

###

[delfrrr]

Hey I think I did manage to reproduce problem, will keep you posted here

[delfrrr]

Hey so I believe that problem was with a deadlock. In Dekart there is of course a lot error handling but deadlock formally is not an error. It's not easy to reproduce locally.

I found few potential issues in the code and address them d4395ce

@philipmargeotab could you pease update Dekart to 0.7.2 and share a feedback if issue still reproducing

[philipmargeotab]

Yes it appears to work now; no more deadlock. Thank you!

[delfrrr]

Great!

[delfrrr]

Fixed in 0.7.2