holidays | Java library to calculate holidays

You can use a cross join with a left join:

If one imports that calendar using the user-interface, they'll notice there's no event older than 1 January 2021. The same behavior can be noticed in other holiday calendars.

Most likely this kind of calendar updates its events each year, so that events corresponding to holidays from previous years are removed.

Therefore, this is not related to Calendar API. The events you are looking for do not exist.

The easiest way is to add all information to the networkx graph and directly create it in the way you need it. I guess you want to use some Graph Neural Networks. Then you want to have something like below.

1. Instead of text as labels, you probably want to have a categorial representation, e.g. 1 stands for Ford.
2. If you want to match the "usual convention". Then you name your input features x and your labels/ground truth y.
3. The splitting of the data into train and test is done via mask. So the graph still contains all information, but only part of it is used for training. Check the PyTorch Geometric introduction for an example, which uses the Cora dataset.

It may be faster with a join

After a little break, I understood what I did wrong. There is a way how to navigate between pages.

Rule #1: In WinUI, you have only one active window, and it's MainWindow. Always. If you want to change layout, you have to use Frames.

In MainWindow.xaml, you write this:

What is this.root in our school's provided code

Your school's template code does not manage what is the root of the tree, so this must be managed in a variable by the driver code. In the testing code this variable is named binarySearchTree, and it really is what would be called this.root in the second (2-class) implementation.

Now, while practicing, I've seen something odd. Upon creation of a new node of an empty binary tree, the first node ends up being completely empty [...] Is this a desired behavior?

No it is not desired behavior. The template code does not provide the concept of an empty binary tree. It expects you to create the tree with at least one value, which should be provided as argument to the constructor. It is not intended to leave out the argument when calling the constructor.

The 2-class implementation provides the idea of an empty tree. But the school's template code does not; you would just have to state binarySearchTree = null if you want an empty tree. But the downside is clear: you cannot use the methods of the class to add a value to that. The only way to get the first value in a tree is to call the constructor and assign the constructed object to your binarySearchTree variable. So adding the very first value to the tree requires a different approach than adding the other values. This is also what you see in the testing code: the first value is added as argument to the constructor -- which is always called with an argument -- while the other values are added by calling the add method. This is a pity and really shows the limitations of the template code.

How can I implement the .height method in order to measure the depth of a Tree.

The idea is that you use recursion:

If there is a left child, get the height of the left subtree through recursion. If there is none, use -1 as default, as it is an empty subtree, and empty trees have a height of -1. Do the same at the right side. Get the maximum of these two values, since only the higher subtree of the two determines what is the height of the tree. Finally add one to this result so to account for the current node.

I was able to pull a private image by doing the following:

1. Create a personal token in GitHub with repo access.
2. Build and push the image to GitHub's Container registry (I used okteto build -t ghcr.io/rberrelleza/go-getting-started:0.0.1)
3. Download my kubeconfig credentials from Okteto Cloud by running okteto context update-kubeconfig.
4. Create a secret with my credentials: kubectl create secret docker-registry gh-regcred --docker-server=ghcr.io --docker-username=rberrelleza --docker-password=ghp_XXXXXX
5. Patched the default account to include the secret as an image pull secret: kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "gh-regcred"}]}'
6. Updated the image name in the kubernetes manifest
7. Created the deployment (kubectl apply -f k8s.yaml)

These is what my kubernetes resources looks like, in case it helps:

Consider below approach

The problem here is that rules is a class attribute (a list of objects). See the code taken from here: