A tool for automating the installation of the Microsoft Windows operating system on various device platforms.

Setup Guide
Glazier Configurations
└─New Actions
└─Config Layout
YAML Files
└─YAML Specs
└─Chooser UI
└─YAML Tips
└─Installer Actions
└─Policy Modules
└─Error Handling
└─Config Handlers
Mailing List 💌
File A Bug 🐛

Hosted on GitHub Pages — Theme by orderedlist

Error Codes

The question of how to implement error codes has already been answered a plethora of ways. An example is how Microsoft uses BSOD codes to identify fatal failures with the Windows Operating System. Leveraging the same philosophy, error codes should be added to all exceptions thrown by Glazier. There is a difference between error codes and error return values. An error code gives a user actionable feedback. An error return value is a coding technique to indicate that your code has encountered an error.


For simplicity, Glazier error codes are all four digit numbers that follow the pattern 7XXX. If no status code is defined by the error, the default (7000) will be used.

Error codes achieve the following objectives:

  1. Convey the error code.
  2. Provide short*, actionable log messages.
  3. Documentation explaining error codes is a living document and can be updated as necessary.
  4. Data can be inferred based on the error code itself with where the issue originates (e.g. 7060 could relay information about not receiving an NTP response)

* Having short status codes is essential since every exception will have this string appended to it. The aim is to give the end consumer concise and actionable steps for troubleshooting most known errors.

Error Code Reference

Always refer to for the most up-to-date error code values. All critical error codes should be added to that library, rather than individual libraries. The expectation is error codes point to anchors in your internal documentation.

Defining Fatal Errors

The below pattern should be used when defining and raising any custom Exception, in order to ensure details are logged appropriately. In this example, we’ll be introducing a new module,

# In

class ErrorCode(enum.IntEnum):
  DEFAULT = 7000
  DIVIDE_BY_ZERO_ERROR = 7999  # Our new error code.
# In

from glazier.lib import errors

class Error(errors.GlazierError):
  """Base class for all Exceptions in"""

class DivideByZeroError(Error):

  def __init__(self, numerator: int, denominator: int):
        message=f'You tried to divide {numerator} by {denominator}')

def VeryBadCode():
  a = 1
  b = 0
    a / b
  except ZeroDivisionError as e:
    raise DivideByZeroError(a, b) from e  # Use raise/from whenever possible.

In this example, the error message will be as follows:

You tried to divide 1 by 0 (Error Code: 7999) (Cause: division by zero)

NOTE: When raising a custom GlazierError subclass (in this example, DivideByZeroError), it behooves you to raise that Exception using Python’s raise from syntax. The reason for this is that GlazierError will include the root-cause message (in this example, “division by zero”) along with whatever custom error message you define.

Once this exception is caught by, the following log message will be displayed:


* Root Cause: You tried to divide 1 by 0 (Error Code: 7999)

* Location: <>:<lineno>

* Logs: /Logs/glazier.log

* Troubleshooting: