Skip to content

Troubleshooting

Jump to bottom
Joe Wicentowski edited this page Sep 19, 2017 · 19 revisions

Troubleshooting

This article contains troubleshooting tips for problems that others have encountered. Hopefully this article will give you a path to finding a solution or workaround for any problem.

Have an idea for a new entry - a problem you've helped someone fix? Go ahead and add it!

The directions say X should happen, but it's not

Please let your trainer or the author of the directions know where the directions are diverging from what you're experiencing so they can help find the problem you're encountering and/or fix the directions. The sooner we fix the problem, the better.

If you're getting an error, copy and paste the entire error verbatim into an email, or take a screenshot and send it.

If the error is appearing on a web page, copy and paste the URL where the error appears into the email.

Deploying all repositories to localhost says BUILD FAILED

First, check:

  1. Are your copies of eXist and oXygen up-to-date with the versions stated in the Setup document?
  2. Have you run "Fetch updates" in oXygen today? (Do this to make sure you have the latest files.) Does the console window that appears when you run "Fetch updates" show any problems? If so, copy and paste the entire contents of the console into an email. If not, then try deploying the repositories to localhost again.
  3. Is eXist running?

If the problem persists, copy and paste the entire contents of the console window in oXygen into an email and send it to your trainer. The console output can be cryptic, but it often indicates the source of the problem or provides useful clues.

Uploading a file to localhost or hsg says BUILD FAILED

Causes can include:

  1. For localhost, eXist is not running.
  2. For history.state.gov, your connection to the internet is not working, or history.state.gov is undergoing maintenance.

The console window in oXygen should show a more detailed description of the problem. The console output can be cryptic, but it often indicates the source of the problem or provides useful clues.

If you're not able to solve the problem, then copy and paste the entire contents of the console window in oXygen into an email and send it to your trainer.

GitHub Desktop is saying there is a conflict

Git conflicts can be tricky to overcome, but take a screenshot and send it to your trainer.

If all else fails, try to save your work to another folder. Then delete the repository from your disk and re-run the "Clone all repositories" step in the HSG Setup directions. This will put a fresh clone of the GitHub repository onto your disk. Then you can try to fold your work back into the repository so you can commit it.

Clone this wiki locally