Empty attributes supplied to backend
After resolving #27 (closed), the forks are now rolling in. A few things do still cause empty attributes. In the logfile, look for the 4 lines starting with ARPA2 Rules DB backend changes Access Domain, Name and Rule attributes:
that list the three output variables.
In a fork, all attributes exist; otherwise, a fork should not stay alive and be delivered to the backend (so no calls to _add
and no later reversal with _del
).
Too high up entries do not match/bind all variables. This appears to be the case with the BaseDN, or the one below, because not the full ... <- world
pattern was matched. In the logfile, this is the first backcall. This should not have been a fork and not a backcall.
DNattrs are delivered once even if they apply in multiple entries. In the logfile, arpa2.org
is delivered in two backend calls from the same entry (the second, and the first one to deliver all output variabels to the backend). It looks like the output variable bound by the DN is cleaned (and not matched again) when done with one entry.
The attributes inside an entry look good, and so does the list that is produced. So, for this first test, we've already got much going!
I'll add the log from commit c92b7634, test rules-ldap-pulled-nongoal
in ANSI color. The same pattern occurs in the -goal
test. Please ignore PulleyScript being killed and reporting exit (-2)
, that's the test being impatient and imperfect.