-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IP guessing on import fails silently, leaving some traces in error log #3909
Comments
uhmm first one smells to organization users + unqualified table name, because of Just a blind guess |
I couldn't reproduce the problem in local with an org user. For some reason the new tables are going into public schema. But I couldn't reproduce it in staging either, and made sure the tables are going into the user's schema in that case. I double-checked it. |
I also tested with a test org in production and it worked as expected, I'm kind of confused with this 😕 |
I've just reproduced the problem (while testing #3859). Users get created this way:
How have you created local users and org? I've created admin and org with Central, and then the user with organization page (juanignaciosl6 is a normal user, other are org owner and user). |
Just to be clear, I've added "Please note explicit geocoding works, it fails only during importing." to the description. |
I don't trust my local org users cause I created them manually at the time with a rake script. But I do trust the users in staging, created through central.
For testing in production I stole an org+user from Michelle. |
Add schema to temp table, fixes #3909
Geocoding fails importing this file. Rollbar displays these errors, which seems related:
https://rollbar.com/vizzuality/CartoDB/items/7045/occurrences/5699232468/
https://rollbar.com/vizzuality/CartoDB/items/3153/occurrences/5699232763/ --> failed geocoding reporting
https://rollbar.com/vizzuality/CartoDB/items/4503/occurrences/5699232903/ --> retry
https://rollbar.com/vizzuality/CartoDB/items/7536/occurrences/5699233028/
Please note explicit geocoding works, it fails only during importing.
cc @rafatower @Kartones @zenitraM
The text was updated successfully, but these errors were encountered: