freeCodeCamp

The Step 9 test currently expects the condition to use not isinstance(dictionary, dict). Although comparing the Boolean result to False is logically equivalent, it does not match the accepted test pattern. Replace the condition with:

if not isinstance(dictionary, dict):
    print(f'Invalid format: expected a dictionary at position {index}.')
    is_invalid = True

This detects the same non-dictionary values and passes the Step 9 tests. A curriculum fix has been proposed to accept equivalent type-check expressions.

Python sequences are zero-indexed. "hello world" has 11 characters at indexes 0 through 10; index 11 is already past the end, so greet[11] raises IndexError: string index out of range. Use greet[-1] for the last character or len(greet) - 1 for its index.

Also, input() always returns a string. The error occurs only when that string cannot be converted with int(), such as entering letters or a blank value. Handle it with try/except:

greet = "hello world"
print(greet[10])   # d
print(greet[-1])   # d

try:
    number = int(input("Enter a number: "))
except ValueError:
    print("Please enter a valid integer!")

The tests call the stack operations as standalone functions. The stack object returned by initStack() is passed as the first argument, and push also receives the new element as its second argument. Store items in stack.collection, with the last array element treated as the top of the stack.

Example implementation:

function initStack() {
  return { collection: [] };
}

function push(stack, element) {
  stack.collection.push(element);
}

function pop(stack) {
  return stack.collection.pop();
}

function peek(stack) {
  return stack.collection[stack.collection.length - 1];
}

function isEmpty(stack) {
  return stack.collection.length === 0;
}

function clear(stack) {
  stack.collection.length = 0;
}

After push(stack, 'first') and push(stack, 'second'), the test expects stack.collection to equal ['first', 'second']. Do not add or remove items at index 0 with unshift()/shift(). The original user stories omitted these calling conventions and collection-order requirements; a pull request updates the instructions.

The error is caused by Windows-style CRLF (\r) line endings being added to ./bash/sourcerer.sh and ./bash/.bashrc when cloning the repo on Windows (outside WSL). The repo files themselves use LF endings, so this is a local Git configuration issue. Fix options:

1. Prevent Git from converting line endings, then re-clone the repository:

git config --global core.autocrlf false

2. Or strip the carriage returns from the affected files inside the container:

sed -i 's/\r$//' ./bash/sourcerer.sh ./bash/.bashrc

You can verify invisible characters with sed -n 'l' ./bash/sourcerer.sh. After fixing the line endings, run the freeCodeCamp: Run Course command again — the course should load normally. If you develop on Windows, working inside WSL avoids this problem entirely.

The breadcrumbs in the freeCodeCamp lesson represent the page's position in the site hierarchy, not the user's actual route. For example, Home / Electronics / Phones / Smartphone XYZ means those pages are parent sections in the site structure; a user arriving directly from search should see the same trail. Do not describe breadcrumb links as necessarily "previously visited pages." History-based breadcrumbs, which track the actual path taken, are a separate and less common pattern and should be explicitly labeled as such. Main navigation links may be shortcuts to nested categories, so they do not have to correspond only to top-level hierarchy levels. Follow the W3C ARIA breadcrumb pattern and use a dedicated <nav> element, such as <nav aria-label="Breadcrumb">, for the hierarchical trail.