eliza | Python implementation of the Eliza chatbot | Machine Learning library

Right, a lot of hints towards FILTER(), and looking at your data I do think the following should work:

Formula in E2:

I tried to validate the XML against the XSD.

The validation revealed few errors.

You need to make a decision about what is correct XML or XSD.

It's a good practice, when you hear "random without duplicates", to think "shuffle".

So to assign random, non-repeating, correctly gendered avatars, segregate the avatars by gender, shuffle the male and female avatars, then assign them sequentially to users....

Update: In the stacktrace, it says obj._meta.get_field(field), 'verbose_name') i.e., obj is a str, so the in the line:

If you didn't have any condition on employee ID at all you'd end up with records where a self-match had occurred, e.g. the results would show "Gracie Gardner was hired on the same day as Gracie Gardner"

We could then put ON e1.employee_id <> e2.employee_id - this would prevent Gracie matching with Gracie, but you'd then find "Gracie Gardner was hired on the same day as Summer Payne" and "Summer Payne was hired on the same day as Gracie Gardner" - i.e. you'd get "duplicate records" in terms of "person paired with person", each name being mentioned both ways round

Using greater than prevents this, and effectively means that any given pair of names only appears once. Because Gracie's ID is less than Summer's, you'll get Gracie in e1 paired with Summer in e2 but you won't get Summer in e1 paired with Gracie in e2

Another way of visualizing it is with a square/matrix

(Posted too soon)

The answer is static variables in your class!

Now you don't need a loosely related object to track state outside of an instantiation.

I don't understand why it is considered null,

It is "considered" null because it is null. The Java runtime does not lie¹.

^{1 - If you don't believe it, check this by adding a trace print immediately before the offending line to print out what the variable actually contains.}

You are getting an NPE (NullPointerException) because lists is null. It is null because your code doesn't initialize it.

(The other exceptions are a consequence of your code not handling the NPE ... which it probably shouldn't do. They will go away when your code no longer throws NPEs on the application thread. IMO, you don't need to do anything about them.)

It looks like you have been trying to initialize lists in various places, but you are making various mistakes.

1. The constructors have empty bodies. So the one that takes a list argument is ignoring it.

2. The static method setList2 should not be static if it is your intent that it can be used to set lists. A static method can't assign to an instance variable of this ... explicitly or implicitly.

3. The setList2 method is assigning to list not lists. That is the name of the parameter. So what it is actually doing is creating an empty ArrayList and assigning it to a local variable ... which then just disappears.

4. Your are not using either the Act(String num, ArrayList list) constructor or setList2. The call to the latter is commented out.

Advice:

1. Make sure that you understand the differences between regular and static methods. I mean really understand. (The mistakes you made in your setList2 method imply that you don't understand.) Go back and read your textbook, lecture notes, whatever again. Or find a good Java tutorial that explains it.

2. Avoid static methods, and static fields. They are usually not the solution.

3. Read your code, and error message carefully; e.g. there were probably clues at some point that would have told you that list and lists are not the same name.

4. If you get an compilation error don't just try to make the error go away with some random change; e.g. commenting out the code. You actually need to understand the what the error message is telling you and work out the correct way to fix it.

The "Programming by randomly changing things" technique is incredibly inefficient ... and frustrating ... and frequently ends up producing bizarre and broken code. So, don't do that. Instead, you might want to read about the Rubber Duck Debugging technique.

Using the Rubber Duck Debugging technique the Duck would have wanted to know why you were so sure that lists was not null. In explaining it to the Duck, you would have noticed the obvious: that nowhere in your code do you assign anything to list.

You need an ORDER BY clause in your query to get the manager with the most employees.
Use it as a subquery in the WHERE clause:

You can use another faker for nested types. You could then reference it in the other faker like this .RuleFor(h => h.User, () => userFaker). Here's a sample: