2. Project management¶
This week I worked on defining my final project idea and started to getting used to the documentation process.
The Git Nightmare¶
For some reason partway through the course this spring, the github system stopped responding. Pipelines started failing, and I couldn’t upload anything any more. Eventually, with help from the central FabAcademy IT and my local instructor, we reset my account. It was apparently something to do with “pushing through a different branch which wasn’t the master”.
I backed up my local files to a zipfile, then deleted everything. I started putting files back and tried to commit them. I kept getting the pipeline failed messages. Finally I managed to google the right question, and it turned out the problem was a corrupted mkdocs.yml file, which had acquired from odd code at the end. After I deleted that, I checked the .yml file with the CI Lint function in the CI/CD section of my repository. It came through ok, so I created a new file in my base directory using the webIDE, and pasted the ok text into it.
The next commit also failed, but at least this time it gave me a useful error message indicating that the requirements.txt file was missing. So I created a new one of those and pasted in the text from the zipfile version of the file. When I next committed the files, the pipeline error was gone.
So then I restored the rest of the files from the zipfile to the directory structure, and tried the commit again. This generated a different error message telling me that there were two separate versions of the repository on the home and remote machines, and helpfully suggesting I should git pull … the repo. It took a while to figure out what … was, but in the end I remembered something about the SSH address in the Overview section of my online git repo. Cut and paste that into the … and presto, new error message. This time that there were two versions of the mkdocs.yml file, and telling me that the remote file had been given an odd name. It also told me to clean up the repo and commit again. I deleted the weirdly named file, recommitted, and now everything works properly.
Ah for the days of simple ftp…
Research¶
“Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.”
“Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.”
Useful links¶
Code Example¶
Use the three backticks to separate code.
// the setup function runs once when you press reset or power the board
void setup() {
// initialize digital pin LED_BUILTIN as an output.
pinMode(LED_BUILTIN, OUTPUT);
}
// the loop function runs over and over again forever
void loop() {
digitalWrite(LED_BUILTIN, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(LED_BUILTIN, LOW); // turn the LED off by making the voltage LOW
delay(1000); // wait for a second
}
Gallery¶
Video¶
From Vimeo¶
Sound Waves from George Gally (Radarboy) on Vimeo.