Fix SAML & LDAP integrations for on-prem

[rafatower]

Story details: https://app.clubhouse.io/cartoteam/story/144728

[shortcut-integration]

This pull request has been linked to Clubhouse Story #144728: Fix SAML Integration for onprem.

[rafatower]

@amiedes the test build timed out after 40 min

FATAL:  the database system is shutting down

EDIT: link to the logs https://console.cloud.google.com/cloud-build/builds;region=global/100743d8-e0c5-404a-ace8-de02ba5601b4;step=12?project=cartodb-on-gcp-ci-testing

[amiedes]

👍

[rafatower]

Closer to fix the tests problem:

$ cat match-pairs.rb
INPUT_FILE='log-1ec7bd34-a1e3-4530-a35a-447aa6744b4f.txt'
START_RE = /RTORRE Starting example (.*)/
FINISH_RE = /RTORRE Finishing example (.*)/ 

opened_examples = {}
File.readlines(INPUT_FILE).each do |line|
  m = line.match(START_RE)
  if m
    example = m[1]
    opened_examples[example] = true
  end

  m = line.match(FINISH_RE)
  if m
    example = m[1]
    opened_examples.delete(example)
  end
end

puts opened_examples.keys

$ ruby match-pairs.rb
Carto::UserCreation validation token neither creates a new User nor sends the mail and marks creation as failure if Central fails

[rafatower]

NOTE: The ruby timeouts do not work 100% of the time, definitely not in this case, I think because of the threading model, they cannot interrupt the ruby process when it is in a "native" section (most likely sequel pg client waiting for db)

[rafatower]

@amiedes I'm pretty sure it's that evil until provoking the stuck situation:

cartodb/spec/models/carto/user_creation_spec.rb

Line 245 in 37dd9d3

user_creation.next_creation_step until user_creation.finished?

I mean, I think I know now how to fix it, but a CI is not very robust if we can get it stuck like that.

[rafatower]

I decided to remove the timeouts code in tests ( 95a1506 and bf573f5 ) because it does not really work and it can be misleading.